How To Prepare A Team Video For The FIRST Innovation Challenge

A strong team video turns a promising idea into a clear, memorable story. For the FIRST Innovation Challenge, students need to show more than a finished prototype: they need to explain the problem, demonstrate the thinking behind their solution, and prove that their team can learn, test and improve together.

The best videos feel authentic rather than overly polished. A Year 7 student explaining a design choice in their own words can be more convincing than a scripted presentation delivered by an adult. Judges should quickly understand who the team is, what challenge they investigated, what they created and why the solution matters.

Australian teams can also use their local setting as an advantage. A problem connected to a Queensland school, a Melbourne community garden, a regional New South Wales town or a coastal Western Australian community may give the project useful context. Local observations can make the innovation feel real and grounded.

Video approach	Strength	Risk	Best use
Demonstration-led	Shows the solution working quickly	May not explain the research	A reliable prototype
Interview-led	Captures student voice and teamwork	Can become repetitive	A project with a strong personal story
Problem-to-solution story	Gives judges a logical journey	Needs careful planning	Most innovation projects
Documentary style	Feels authentic and engaging	Takes longer to edit	Community-focused ideas

Define The Story Before Filming

Begin with a one-sentence project summary: “We designed ___ to help ___ by ___.” If the team cannot complete that sentence clearly, the video concept probably needs refining. Use plain English and avoid technical terms that viewers may not know.

Next, identify the human need behind the invention. Explain who experiences the problem, how the team discovered it and what happens when it is ignored. Evidence might come from interviews, surveys, observations, measurements or research. A local example, such as water use during a dry spell or access issues on a large regional campus, can help establish why the problem deserves attention.

Create a simple narrative arc: problem, research, idea, testing, improvement and impact. The story does not need to follow the exact order in which the team worked. It should follow the order that makes the project easiest to understand.

Show The Innovation In Action

A team video should make the solution visible. Film the prototype operating from several angles, including a wide shot that shows the setting and close-ups that reveal important mechanisms, code, sensors or materials. If the invention is too small, use a stable overhead shot or a carefully framed demonstration.

Show an early version as well as the improved design. A failed test is useful when students explain what went wrong and what changed afterwards. Judges are looking for engineering habits: asking questions, making predictions, collecting evidence and responding to results.

If the project uses recycled or donated materials, explain how that choice supports the idea. For inspiration on giving ordinary cardboard a practical second life, teams could look at this cardboard display example. The point is not to copy another project, but to show how accessible materials can support thoughtful design.

Build A Credible Evidence Base

Avoid broad claims such as “this will help everyone” unless the team can support them. Instead, state what was measured. A prototype may have reduced assembly time, improved accessibility, lowered material use or achieved a particular success rate across a defined number of trials.

Include voices from people affected by the problem, with permission. A short interview with a teacher, community organisation, council worker, farmer or family member may add context, but students should remain the main presenters. If someone appears on camera, obtain the required consent and check the event’s media rules.

Keep research sources visible in the production notes or final credits where the competition rules allow. Screenshots of survey results, labelled sketches, test records and short quotations can make the work easier to verify. Do not fill the screen with tiny text; use one finding at a time and let a student explain why it matters.

Plan Every Shot

Write a shot list before setting up a camera. Decide who will speak, what action will be shown and what supporting footage will appear beside each explanation. A phone, tablet or school camera is sufficient if the image is steady, the lens is clean and the sound is understandable.

Record in a quiet room or outside away from wind and traffic. In Australia, outdoor filming can be affected by bright midday sun, sudden weather changes and background noise from ovals, roads or cicadas. Shade, a simple lapel microphone and a short test recording can prevent many problems.

A Practical Shooting Checklist

• Record a ten-second test for sound, lighting and focus.
• Film each important demonstration at least twice.
• Ask speakers to face the camera and speak slightly slower than usual.
• Capture hands, drawings, code, materials and testing as separate cutaway shots.

Allow students to repeat a sentence without embarrassment. Natural delivery is more important than perfect delivery. If a speaker loses their place, pause and begin the sentence again; editors can remove the gap later.

Edit For Clarity And Pace

Start editing by removing repetition, long pauses and technical explanations that do not move the story forward. A useful video often reaches the problem quickly, introduces the team, then spends most of its time on evidence and the solution. Check the current FIRST Innovation Challenge rules for the required duration, format, file type and submission process before locking the edit.

Use captions for names, key measurements and essential technical terms. Captions improve accessibility and help when judges watch in a noisy venue. Keep fonts large, colours high-contrast and text on screen long enough to read. Add music only when it supports the story, and keep it quiet under dialogue.

A polished edit should still sound like students. Avoid replacing every spoken explanation with narration from an adult. Team members can divide roles as presenters, camera operators, designers, interviewers and editors, giving each student a meaningful contribution.

A Clear Submission Checklist

• Confirm the video length, file format and upload deadline.
• Check that every voice is audible and every caption is accurate.
• Review permissions for students, interviewees, logos, music and locations.
• Watch the final file on a different device before submitting it.

Use a neutral file name that includes the team name and season, rather than “final-final-new.mp4”. Keep the original footage, project notes and a backup copy in a shared school or team location. If the upload platform compresses the video, watch the processed version as well as the local file.

Make The Team Visible

The project belongs to the students, so give them space to explain decisions in their own language. One student might describe the user research, another might demonstrate the mechanism and a third might explain how testing changed the design. This creates a stronger picture of collaboration than a sequence of individual introductions.

Connect the video to the team’s wider robotics experience without turning it into an advertisement. Teams moving between local programmes can use the FRC programme details to understand how engineering, strategy and community outreach are presented in a larger competition environment. Teams working with smaller robots and iterative builds may also find FTC resources useful when thinking about design documentation and student roles.

For Australian audiences, spell and caption words consistently in Australian English, use familiar local measurements and explain overseas references where needed. A school in Adelaide may have different transport, climate or community access issues from a team in Cairns, so the video should make its own setting clear rather than assuming every viewer shares it.

Finish with a concise statement of impact: what the team built, what they learned and what they would improve next. Then invite viewers to see the prototype, read the supporting evidence or follow the team’s progress. A focused, student-led video can give judges a clear reason to remember the idea and the people behind it.

Start with the one-sentence project summary, gather evidence from real users and schedule a short filming session while the prototype is working. With a clear story, careful sound and honest student voices, your team can submit a video that demonstrates innovation as a process, not just as a finished object.