Prepare, upload, verify, finalise
The presentation is the explanation inside your video; a separate slide deck is not required. Review the plan below first, then continue to Project Submissions.
Either the student may sign in with the linked RCC student account, or a parent/guardian may sign in with the linked family account. Both reach the same participant entry; the student account can access only its own record.
Junior Coding Path A
One MP4 or MOV presentation video · maximum 5 minutes
Presentation order- Short introduction
First name or team name, year level, project title and one-sentence game idea. Teams briefly introduce every member.
- Play the complete game first
Show the controls, goal, obstacles, scoring, ending and important features before discussing code.
- Explain the main code
After playing, show the main blocks and explain how they make the game work.
- Testing and learning
Describe one change, clearly say what was learned and name one future improvement.
Coding Paths B and C
Presentation video · maximum 5 minutes · plus editable SB3
Presentation order- Short introduction
Introduce the participant/team, project title, theme problem and the game's purpose. Teams introduce every member and contribution.
- Play the complete game first
Show controls, mission, obstacles, levels, scoring and the ending before explaining the code.
- Explain design, code and AI
Connect visible features to events, variables, conditions, functions and other important logic. Path C also shows its trained poses and pose-to-action mapping.
- Testing and learning
Show one problem and improvement, explain what was learned and identify the next improvement.
Robotics A and B
Combined presentation and operation video · maximum 6 minutes
What the video must show- Short introduction
A introduces the participant. B briefly introduces every team member and contribution. State the project title and rescue idea.
- Robot operation
Clearly show forward, backward, left/right movement or turning, servo control and response to the student-trained custom Pose model.
- Technical explanation
Show the important SB3 code and explain control logic, trained poses, pose-to-action mapping and robot design choices.
- Testing and learning
Describe one problem, test and change; clearly state what was learned and what would be improved next.
Robotics C
Combined presentation and operation video · maximum 6 minutes
What the video must show- Short introduction and problem
Introduce the participant/team, every member's contribution, project title, researched rescue problem and proposed solution.
- Robot operation
Show the movements, sensors, mechanisms and controls relevant to the solution and make the outcome visible.
- Engineering and code
Explain the structure, important control logic, design decisions and AI integration when AI is used.
- Testing and learning
Describe one problem, test and change; clearly state what was learned and the next improvement.
Show the project, then explain the thinking
Use one presentation video. PowerPoint, Google Slides, PDF slides, title cards and voice-over are optional; they do not replace a visible working demonstration or the student's own explanation.
Begin with a short personal or team introduction and finish by clearly explaining what the participant or team learned. Teams should briefly introduce every member and each contribution.
Who are you?
Give a short personal or team introduction: first name or team name, year level, category, project title and an interest or role connected to the project. Teams briefly introduce every member and each contribution.
What problem does it solve?
Explain the project idea and how it responds to the challenge theme or rescue scenario. Mention the research or observation that shaped the idea where relevant.
Does it work?
Show the actual game, AI system or robot operating. Make the input, action and outcome visible instead of describing them only in words.
How does it work?
Show the important code and explain the logic in the student's own words. Robotics entries also explain controls, mechanisms, sensors or the custom Pose model used.
What did you learn?
Give one concrete example of a test or failure, the change made and the result. Clearly state what the participant or team learned and what would be improved next.
Required order: introduce → play → explain code → reflect
- Give a short personal or team introduction
First name or team name, year level, category, project title, relevant interest or role, and a one-sentence game purpose. Teams briefly introduce every member.
- Play the game first
Before explaining code, show a complete play-through so judges can see the controls, goal, obstacles, scoring, ending and important features.
- Then explain code and AI
Connect the visible game features to important events, variables, conditions, functions or sequences. Coding C also explains its trained poses and how predictions control the game.
- Explain testing and learning
Describe one test and improvement, clearly say what was learned, and name the next improvement.
Applies to every Coding pathway: introduce first, play the game before the code explanation, and finish with what was learned. Junior Coding Path A may keep each explanation age-appropriate. An adult may operate the camera, but the student's own understanding should be clear.
Recommended video plan
- Give a short personal or team introduction
First name or team name, year level, category, project title and relevant interest or role. Teams briefly introduce every member and contribution.
- Explain the rescue problem
The need, proposed robot solution and why the design is useful.
- Show the robot operating
A/B show forward, backward, left/right movement or turning, servo control and response to the student-trained custom Pose model. C shows movements, sensors, mechanisms and controls relevant to its solution.
- Explain technical choices
Show the important code and explain control logic. A/B also explain trained poses, pose-to-action mapping and robot design; C explains engineering, sensors and AI where used.
- Show testing and iteration
Describe one problem, the change made and the observed result.
- Explain what you learned
Clearly state what the participant or team learned, then summarise the outcome and next improvement.
Robotics A and B: use the same content, technical evidence and judging requirements. The only difference is that A is one student and B is a same-school team of 2–5.
Submit one continuous or edited video. You may switch between the presenter, screen recording and close-up robot footage as long as the final video stays within the category limit.
Recording checklist
- Use landscape video where possible and make speech, screen text and robot movement easy to understand.
- Show the actual project running; slides, photos or claims without a working demonstration are not enough.
- Zoom in or use screen recording for code so judges can see the blocks or source being discussed.
- Notes and editing are allowed. Professional filming, effects and memorised speech are not required.
- Do not show contact details, passwords, login screens or unrelated students.
- Play the exported MP4 or MOV from beginning to end and check picture, sound and duration.
Complete these steps before finalising
- 1Choose the correct entry
Select a named student or an eligible same-school team of 2–5.
- 2Select pathway and title
The form displays the files required for that pathway.
- 3Upload the video
MP4 or MOV. Coding maximum 1 GB; Robotics maximum 1.5 GB.
- 4Upload the project
Coding B/C and Robotics A/B use SB3. Only Robotics C accepts an editable-source ZIP.
- 5Add the model URL
Required for Coding C and Robotics A/B; optional for Robotics C when AI is used.
- 6Wait for verification
Every required file must show Ready before finalisation.
- 7Confirm permissions and finalise
Judging, YouTube Unlisted processing and public-gallery display are mandatory. The entry then locks.
The video is evidence of the required operation and explanation. A competition field and complete mission run are not required online; the three-minute A/B mission applies at the in-person final.
For Python, Arduino, MakeCode, LEGO or another non-SB3 Category C platform, place the original editable project/source files in one `.zip`. PDFs, screenshots, repository links and media-only ZIP files do not replace the original project.
Supported by the UNSW Built Environment Women in Construction Project and the Department of the Prime Minister and Cabinet’s Office for Women. eLearning is delivered through MRT Robotics.
