
present my team’s silent signal to the field day organizers, using our code key and test data to explain why it is a strong solution.
Phase 5: Prove It
Showcase day! The field day organizers are our audience. What do they need to hear to choose a signal? Think like the client.
What will the field day organizers care about MOST?
A pitch is a short, clear talk. You have 2 to 3 minutes. You will show one live message, then explain your code with evidence.
A strong pitch has four parts.
Worked example 1: a pitch opening. Jamal says: “Field day is loud, and not everyone can hear a whistle. Our flag code uses big motions that everyone can see. Watch: this is ‘water break.’” He waves the flag twice overhead. The audience reads it right away.
Worked example 2: using data. Priya says: “Our light code got 3 of 5 in round 1. We made the patterns more different. In round 2 it got 5 of 5. A flag code got 4 of 5. Both use patterns you can see. Ours mixes long and short flashes, so each message stands out.” She compares, uses numbers, and names the pattern.
Listen like an engineer. When other teams present, write one idea you could borrow. Sharing findings creates more possible solutions.
Plan and practice your pitch as a team.
After all the pitches, reflect on the ideas you heard.
Name one idea from another team's pitch. How could it be combined with your code to make an even better solution?
Present your team’s silent signal to the field day organizers. Your pitch is 2 to 3 minutes. Bring your code key card, your signal tool, and your test data. Show the client one live message, then explain why your code is a good choice for a loud, crowded field.
| Criterion | What proficient looks like |
|---|---|
| Pattern design | Each message has a clear, different pattern, and the code key is easy to read. |
| Test data | Accuracy and time are recorded for two rounds, using a fair test. |
| Comparison | The team compares its code with another code using the criteria, the constraints, and real data. |
| Science and client needs | The team explains how light, motion, or sound patterns carry the message and how the code works for everyone. |
You did the job of real engineers: you met a client, designed, tested, and presented. Next lesson is the unit checkpoint.
Exit ticket: if the organizers could pick only one code, which should it be? Use data and the criteria to explain.
Materials: posters or cards, markers, signal tools, a timer, printed rubrics for the audience. Invite a real field day organizer, a gym teacher, or another class as the client if you can.
Setup: set a presentation order. Give the audience the rubric and one sticky note per pitch.
Listen for: pitches with no numbers; claims like “ours is best” with no comparison; forgetting the classmate who cannot hear well.
Support / stretch: allow pitch frames (“Our code uses… Our data shows… Compared with…”) and partner speaking. Stretch: teams recommend one combined code for the whole school.