The Team Coordinator Guide is the handbook for the adult running the team, and it is a download. It is written for the person organising, not for the students competing, and it assumes no robotics background.
This is the indi edition, for the U9 division, Grades K-2.
What it covers
- Season checklists, in order, from registering on myTEAMevents through preparing the team to the day itself and on to a Championship Event.
- An Online Submission season checklist, for teams entering without travelling, and the tips that go with it.
- Tips for competitions, which is the practical advice that is hard to work out on your own the first season.
- Team roles: Programmers, Engineers, Debuggers, Designers and a Mission Manager. Handing students a role is the difference between a team and a crowd around one laptop.
- The competition field and the materials a team needs to bring.
- Meeting agendas, so a coordinator has somewhere to start rather than an empty hour.
- Event formats and event types, so the difference between an In-Person Event and an Online Submission is clear before you register for the wrong one.
What a Team Coordinator actually does
Registration, a room, materials, and getting everyone there on the day. The students do the driving, the coding and the problem solving, and the guide is explicit that a coordinator may not help during a Mission. If you can organise a field trip you can run a team.
Questions go to support@teamalliance.org.
