How to Run a Successful FIRST LEGO League Scrimmage

A FIRST LEGO League scrimmage gives teams a realistic competition experience without the pressure of an official tournament. Students can test their robot, practise explaining their project, and learn how to work through nerves, timing issues and unexpected results. For coaches, it is a practical way to identify what needs attention before competition day.

The best scrimmages feel organised but welcoming. The aim is not to create a flawless replica of a state championship. It is to provide a safe, encouraging setting where students can try new strategies, make adjustments and see how other teams approach the same challenge.

In Australia, a scrimmage may take place in a primary school hall, community centre or council facility during a busy school term. Teams might travel several hours from regional areas, while city teams may be balancing public transport, parking limits and school calendar clashes. Planning needs to reflect those realities.

A clear run sheet, suitable equipment and well-briefed volunteers matter more than expensive production values. With the right preparation, a small event can give students the confidence and competition skills they need for the season ahead.

Area	Practice-focused scrimmage	Formal tournament
Main purpose	Learning, testing and feedback	Assessment and advancement
Schedule	Flexible, with time to reset	Fixed and tightly timed
Judging	Developmental comments	Official rubrics and awards
Match results	Useful for reflection	Recorded for competition
Volunteer experience	Smaller roles and cross-training	Defined specialist roles
Team atmosphere	Supportive and experimental	More competitive and ceremonial

Set the purpose and scope

Start by deciding what the event must achieve. A scrimmage could focus on robot game performance, the innovation project, team presentation skills, or all parts of the FIRST LEGO League experience. Share this purpose with coaches and volunteers so everyone understands that feedback and learning come before rankings.

Set a realistic capacity. Six to twelve teams may be enough for a school-based event, while a larger regional gathering needs additional rooms, officials and equipment. Confirm the number of teams early, then establish a registration deadline, arrival window, lunch arrangements and a simple cancellation policy.

Give coaches a short event guide explaining the challenge format, field setup, judging approach, safety expectations and contact details. If teams are new, include a plain-language description of robot game rounds and judging sessions. Clear information reduces repetitive emails and helps visiting teams arrive prepared.

Secure the venue and people

Choose a venue with a level floor, reliable lighting, accessible toilets and enough space for teams to work without crowding. A school hall can work well, provided there are nearby classrooms for judging and a quiet area for briefings. Check power access, Wi-Fi, parking, public transport and whether food may be prepared on site.

Australian organisers should also consider heat, storms, bushfire conditions and long travel distances. A summer event in western Sydney or Perth may need extra water stations and good ventilation, while a regional Victorian or Queensland event may require an earlier start to accommodate travelling teams. Confirm first-aid arrangements and any Working with Children Check requirements for adult volunteers.

Recruit more people than the minimum roster. A scrimmage may need a welcome desk, timekeeper, referees, judging panel, pit support, field resetters, photographer, first-aid contact and floaters. Invite parents, past students, local university students and nearby engineering or technology businesses to contribute.

Use a volunteer briefing rather than relying on informal instructions. Explain the event purpose, safeguarding expectations, escalation process and how to give constructive feedback. Someone who knows the local FIRST community can help keep communication friendly and practical, especially when a schedule changes.

Build a workable schedule

Create a timetable that protects transition time. Teams need to move from pits to judging rooms, repair robots, find water and listen for announcements. A schedule that looks efficient on paper can quickly fall behind if every session has no buffer.

A useful format includes check-in, opening briefing, several robot game rounds, project and robot design judging, lunch, an optional workshop and a final recognition session. Allow teams to arrive at different times if public transport or regional travel makes a single arrival window difficult.

Publish the schedule in advance and display a large printed version on the day. A shared digital document can help coaches, but do not rely solely on mobile coverage or Wi-Fi. Assign one person to announce changes and another to update the master schedule.

For sign-ups, a straightforward booking tool can help collect team details, volunteer availability and session preferences. Keep the registration form short, and ask only for information the event team genuinely needs.

Prepare the robot game area

Use an official challenge mat and mission models wherever possible. Build the models carefully, check attachment points and place the mat on a stable table. Mark the launch and inspection areas so teams understand where equipment must be positioned before each round.

Run a full test before the event. Confirm that the table is level, models remain secure, robots fit within the permitted starting area and referees can see the action clearly. Keep spare LEGO elements, batteries, tape, rulers and basic tools available, while ensuring repairs follow the current challenge rules.

Brief referees on consistent calls and respectful communication. A scrimmage is a learning environment, so referees can explain a ruling after a round without turning the match into a long debate. Record scores if useful, but remind teams that the numbers are feedback rather than a final judgement of their ability.

Plan a reset process that students can understand. Resetters should return models to their starting positions, remove loose pieces and check the table before the next team begins. This simple routine keeps matches moving and prevents avoidable disputes.

Make judging useful for students

Judging should feel like a conversation about the team’s work. Prepare separate spaces for the innovation project, robot design and core values or team presentation, depending on the current FIRST LEGO League format. Use the official rubrics and criteria as the foundation for every session.

Ask judges to notice evidence rather than polished performance alone. A team may show strong engineering through repeated testing and redesign, even if its robot has an occasional failure. Another team may have a promising project that needs clearer research or a more practical solution. Comments should identify what was demonstrated and what could be explored next.

Share rubrics with teams before the event. Coaches can then help students prepare without scripting every answer. Encourage students to explain their own choices, including problems they encountered, changes they made and how different team members contributed.

The wider FIRST network offers useful reminders that technical problems are part of the learning process. A story about programming challenges can help volunteers frame debugging as a normal engineering activity rather than a reason for criticism.

Run a calm and inclusive event day

Begin with a short welcome that explains the purpose, timetable, safety points and where to find help. Introduce volunteers and show teams the pit area, judging rooms, toilets and water station. Avoid a long opening ceremony when students are eager to start; a clear five-minute briefing is often enough.

Keep the pit area organised with visible team signs and walkways free from bags and loose parts. Provide tables, chairs and access to power where safe. Ask teams to label chargers and tools, and establish a quiet area for students who need a break from noise and activity.

Use encouraging language throughout the day. Words such as “reset”, “test”, “adjust” and “try again” support the engineering mindset. If a robot stops working, give the team a moment to troubleshoot before offering help. Adults should guide students towards solutions rather than taking over repairs.

A small hospitality touch can improve the experience: chilled water, fruit, tea and a clearly labelled allergy-aware lunch area are practical choices. Many Australian school events use a sausage sizzle or shared lunch, but check dietary needs, food rules and supervision requirements well ahead of time.

Review results and build momentum

End with recognition that celebrates different forms of contribution. Awards can acknowledge creative engineering, thoughtful research, teamwork, persistence, gracious professionalism and helpful peer support. Keep the language aligned with FIRST values and avoid making one high score the centre of the event.

Give each team a concise feedback pack. Include robot game scores if recorded, judging notes, attendance certificates and one or two clear next steps. Coaches can use this material during the next meeting to set priorities for programming, robot design, project research or presentation practice.

Hold a volunteer debrief while details are fresh. Note which rooms worked, where queues formed, whether the schedule had enough buffer and which instructions caused confusion. Share a short feedback form with coaches and families, but keep it focused so people are likely to complete it.

Future dates should be checked against school terms, local events and regional travel patterns. Teams can also monitor the Maryland FIRST events calendar for examples of how a broader FIRST organisation communicates competitions, workshops and community activities. A well-run scrimmage can become an annual fixture that strengthens relationships among schools, mentors and sponsors.

A successful FIRST LEGO League scrimmage begins with a modest, achievable plan and grows through careful listening. Confirm the venue, recruit and brief the right people, protect time for learning, and make every interaction supportive. Then invite local schools, community groups and industry partners to take part in the next event, using the experience to build a stronger robotics programme for students across your area.