Judges Room Presentation Path

Right Brain · Path No. 2

The Judges-Room Presentation Path

The portfolio gets you in the door. The judges’ room decides what you walk out with. This path and the Engineering Portfolio path are built together and presented together — by the whole team.

Your engineering portfolio is the document that proves how your team thinks. The judges’ room is the moment that proves it live. Both matter. Neither stands alone — and critically, neither can be done well by the Right Brain team working in isolation.

At every FTC event you face two kinds of judging. The first is the formal panel interview — five minutes in front of two or three judges, doors closed, stopwatch running. The second is the informal pit interview — judges walking into your pit whenever they feel like it, asking whatever they feel like, watching how your team handles cold questions under pressure. In both settings, the judges are looking at the whole team. Right Brain students carry the story. Left Brain students stand beside the robot and answer the technical questions. The presentation is a joint performance, not a Right Brain solo.

Robots can be beautiful and still lose. Portfolios can be polished and still lose. What winning teams discover is that the trophies go to teams that can tell their story out loud — together.

The Most Important Thing to Understand First

This Is a Companion Project to the Engineering Portfolio — Not a Separate One

Who Presents

The Judges’ Room Is a Joint Appearance by Right Brain and Left Brain Leaders

👥

This Is Not a Right Brain Solo Performance

The formal panel interview is presented by a small group — two to three students maximum. That group should include at least one strong Right Brain communicator who owns the team story, outreach, and the portfolio narrative, and at least one Left Brain lead who can speak fluently about the robot’s design, the engineering decisions, and the code.

The pit interview works the same way. When judges walk into your pit, the students who answer their questions should be whoever actually built or programmed what they are asking about — not the coach, not the team captain reading from a script. This means your Left Brain leads need to be comfortable talking to strangers under pressure too. That is a shared responsibility across both sub-teams, and it needs to be practiced together.

Build your presentation team with this in mind from the start. Assign roles. Rehearse with the actual people who will be in the room.

Before You Start — Required Reading

The Five-Stage Journey

How to Build a Presentation That Wins the Room

1 Stage

Study Inspire-Winning Presentations on Video

You cannot deliver what you have never seen. Search YouTube for FTC Inspire Award team presentations — especially the official post-event recordings from FIRST Championship. These are public, free, and full of patterns you can study and adapt.

Watch at least three presentations from different seasons. Take notes on how each team opens — the first thirty seconds matter more than almost anything else. Note how they describe failures without apologizing or stumbling. Note how the team splits the talking — strong presentations are rarely one student doing everything. Note the rhythm between the student narrating the story and the student standing at the robot.

📌 Output: A short list of patterns you noticed — opening hooks, failure stories, team handoffs — that you want to incorporate into your own presentation.
2 Stage

Write the 5-Minute Team Pitch — Together

The panel interview is exactly five minutes. Not six. Not four-and-rambling. Five. You need a written script with a tight structure. Memorize the spine. Improvise the details. Write it as a team — the Right Brain lead drafts the story, the outreach section, and the close; the Left Brain lead drafts the robot story section. Then rehearse the transitions between speakers until they feel natural.

Recommended structure: a thirty-second hook that makes judges lean in, sixty seconds on team identity and why this team exists, two minutes on the robot story with a real failure inside it, sixty seconds on outreach with specific names and numbers, and a thirty-second close. Two or three speakers total — never the whole team crowding the front of the room.

📌 Output: A written pitch script with speaker assignments marked, plus a timing card. Every speaker knows their section cold.
3 Stage

Build the Robot Demo Narration — with the Left Brain Team

Inside the panel interview and again at the pit, you will run the robot live while talking. This is where many teams fall apart — the driver is focused on the controller, the narrator goes silent, and the robot does something nobody explains. Judges are left to guess what they just watched.

Write a sixty-to-ninety-second narration script that maps to one full demo run. Call out each subsystem as the robot uses it. Name the design decisions that went into each mechanism. Practice with the robot powered on — do not stop the robot mid-run to explain something. The Left Brain driver and the Right Brain narrator need to rehearse this sequence together until the narration and the robot motion are in sync. Have a backup driver ready.

📌 Output: A narration script matched to a full demo run, plus at least one rehearsal video showing driver and narrator working together in real time.
4 Stage

Run Mock Pit Interviews — With Mentors as Judges

This is the stage that separates teams that practice from teams that perform. Have mentors role-play as judges and ambush the team with cold questions while students are working in the pit — or set up a simulated pit in your meeting space. Run at least two sessions on different days, with different mentors each time. Include both Right Brain and Left Brain students in every session, because the judges will ask both groups questions.

The questions below are the ones every team gets. Drill them until the answers are automatic, specific, and confident. The Left Brain leads handle the technical ones. The Right Brain leads handle the story and outreach ones. Both groups should be able to cover for each other in a pinch.

📌 Output: Two recorded mock pit interviews on video, watched back as a full team, with a short punch list of what to sharpen before competition day.
5 Stage

Record the Full Pitch — Watch It Back — Fix Three Things

This is the capstone and the most important practice session of all. Set up a phone or camera in front of the full presentation team — Right Brain and Left Brain leads together — and record the complete five-minute pitch in one take, no restarts. Then watch it back as a team with mentors taking notes.

The first time you see yourselves on video you will find fifteen things to fix. Do not fix fifteen things. Pick the three that matter most — the stumbled transition, the section that ran too long, the moment the robot demo went sideways — fix those, record it once more, and call it done. Chasing perfection past this point is diminishing returns. The goal is confidence, not flawlessness.

📌 Output: Final pitch video plus a short punch list of micro-fixes. Both Right Brain and Left Brain leads have seen themselves perform and are ready. Capstone complete.

The Question That Wins the Room

Every Judge Will Ask This. Every Team Must Have an Answer Ready.

🎯 Questions to Drill — Right Brain and Left Brain Together
“What didn’t work?”
Rookie answer: “Uh, nothing really — everything went pretty well.” The judges write zero.

Winning answer: “Our first intake design used surgical tubing rollers. They worked for two weeks until we noticed the tubing was stretching under load and intake speed dropped by about thirty percent. We tried tightening the tubing, but friction caused premature wear. So we redesigned around compliant wheels — you can see the v3 on page seven of the portfolio. Compliant wheels are slower on intake, but ten times more reliable. We traded speed for repeatability.” That answer wins three awards at once. It needs to come from the Left Brain lead who actually lived it — not from a Right Brain student reading it off a card.
“Walk me through your design decisions on the X subsystem.”
The Left Brain lead answers this one. They should be able to walk through the design history — what was tried first, why it was changed, what the final solution is — in under ninety seconds without prompting. The Right Brain lead has heard this answer enough times in build sessions to follow up naturally if the judge has a clarifying question.
“Who built that part?”
The student who built it answers. Not the coach. Not the team captain. Not “it was kind of a group effort.” Judges ask this to confirm that students are doing the work. Have an answer ready for every major subsystem.
“How did you decide between option A and option B?”
This tests whether you have a real engineering design process or just built something and called it a design process. The answer should reference actual criteria: weight, cost, complexity, reliability, build time. If your team used a decision matrix, mention it. If you prototyped both, say so.
“Tell me about your outreach. What impact did you actually have?”
Names and numbers. Not “we did a bunch of community events.” How many events? How many students reached? What specific partnerships? What will continue next season? The Right Brain lead owns this answer and should be able to give it with specifics in sixty seconds flat.
“What would you change for next season?”
This is the question that reveals whether your team reflects and grows. Have a genuine answer that shows real self-awareness — about the robot, the portfolio process, the team structure, or the outreach strategy. Judges love teams that know exactly what they would do differently and why.

Ready to Start Practicing?

Your mentors and student team leaders can run mock interviews, critique your pitch on video, and help coordinate the joint rehearsals with the Left Brain team. Reach out early — the qualifier comes faster than you think.

✉ Email the Coach Engineering Portfolio Path →
The Truth

Trophies don’t go to the best robots. They don’t go to the best writers either. They go to the teams where everyone — builders, programmers, communicators — can stand in front of three strangers and tell one coherent story about what they built, why they built it, and what they learned when it broke.