New Team Guide

Starting Your Team

You have decided to start an ARC team at your school–congratulations! Now what?

  1. Recruit

    Talk to your friends, classmates, roommates, and anyone who you think might be interested. For new teams, we recommend at least 10. Some individuals will leave or step back due to academics, health, loss of interest, and/or other reasons. There is no correct size for a team, but it is always safer to overestimate. Good skills to look for include programming, CAD, and project management.

  2. Structure

    Time to organize. There is no “best” way to do this, so try whatever makes sense to you. Some ideas for sub-teams include: Admin, Software, Hardware, or Robot Specific (Infantry, Hero, Sentry). Larger teams can split into more specific sub-teams, but for newer teams like yourself, it is a better idea to keep things simple and tight.

  3. Register

    Make your team official as a student club/organization with your university/department. This will legitimize your team. Many universities require a President, Treasurer, and Faculty Advisor. This will also help you in recruiting and fundraising. Teams also register with ARC using the registration form.

Sourcing Funding

If you thought this would be easy–think again.

Funding is hard to get, and most universities/departments will only give you a small grant (and even that is not guaranteed), so your team will need to spend some considerable effort fundraising.

Here are some ideas:

  • Membership dues

  • Corporate sponsors

    • Either cash or in-kind donations like materials and fabrication
  • University/Department grants

    • Club and Student Organization grants
    • Research grants
  • Individual donations

Registering Your Team

Paperwork and Logistics

  1. Official team registration typically opens in the fall; see the current season's Participant Manual for exact dates. This is when you will provide details about your team such as name, size, logo, school affiliation, and contact information.

  2. Event registration for the ARC Championship opens later in the season. Payment is due up front. Late registration is optional for a fee.

  3. In order to help run the ARC Championship, we charge teams a participation fee that varies by event. Events and fees for each season are listed in the Participant Manual.

  4. The championship dates and venue are announced each season.

Building Your Robot

Here is an example of a development timeline.

  1. Read the Rules

    September-October

    Spend some time understanding rules of the game as well as robot specifications. The Robot Building Specification and Event Manuals are released each season.

  2. Research/Plan

    October

    Watch videos, talk to other teams, and look at open-sourced designs. A common mistake teams make is that they overestimate what they can accomplish.

  3. Design/Redesign

    November-December

    Start your CAD and build your pseudocode. Try to break things up into subsystems. Be careful, but do not spend too much time here.

  4. Prototype/Test

    January-March

    Fail early and fail often. Work out all the kinks. Push it till it breaks–better now than later.

  5. Manufacture

    April-May

    Time for things to come together. Aim to give yourself as much time as possible before the competition.

Attending Competition

Competition Checklist

Do these 4 things:

  1. Double/Triple Check

    Your robot(s), club travel guidelines, and visas (for international students).

  2. Set Clear Expectations

    You are a new team. Just showing up is already an accomplishment.

  3. Something Will Go Wrong

    Do not panic. Work as a team and do not be afraid to ask others for help.

  4. Have Fun!

    Explore the city and talk to different teams from around the world.

Resources

Bring on the bots!

Have more questions? Get integrated in our community.

The community Discord server is full of current and former participants, as well as members of operations. It is a great place to get started.