VELOCITY ARENA FACILITATOR · PREP
0 / 10 complete
The ten items 10 ITEMS
✓
Item 01
Calculate all four stat formulas for every point value 1–8, by hand, in under 10 seconds each.
▾
Speed charge % (Speed × 5)
1 = 5%2 = 10%3 = 15%4 = 20%5 = 25%6 = 30%7 = 35%8 = 40%

Linear. Multiply point value by 5.

Power charge % (Power²)
1 = 1%2 = 4%3 = 9%4 = 16%5 = 25%6 = 36%7 = 49%8 = 64%

Note the critical non-linearity: Power 4 → Power 8 does not double — it quadruples then halves (16% → 64%). This is the primary math surprise of Day 4.

Endurance remaining power at end of a 3-min match — P(3) = 100 − (20 − E) × 1.5 × 3
E=1: 14.5%E=2: 19%E=3: 23.5%E=4: 28%E=5: 32.5%E=6: 37%E=7: 41.5%E=8: 46%

Allocations 1–3 leave a bot below 25% power by match end. This is the intentional design trap: low Endurance produces a visibly dying bot.

Turn Ratio = 0.2 + (Turning × 0.02)
T=1: 0.22T=2: 0.24T=4: 0.28T=8: 0.36

Controls the arc radius. You will be asked mid-match by a stressed student. If you hesitate, you become an unreliable resource at the moment that matters most.

✓
Item 02
Memorize the four-step loss-recovery script word for word. Practice it aloud with a partner at least five times.
▾

The script only works if you have internalized it well enough to say it calmly in an emotionally charged moment without improvising.

Step 1: "That result was frustrating. That's a real feeling and it makes sense." (Stop. 30 seconds. Say nothing else.)
Step 2: "Your model predicted [X] goals. You scored [Y]. That gap is the most interesting thing that happened today. Let's find the one decision that created it." (Dashboard. One stat only.)
Step 3: "You have [N] matches left. You now have data you didn't have before. What's one thing you'd change?" (Write the answer down.)

Peer-sharing prompts by season:

Season 1 (Weeks 1–2) · Stat-Focused

"Walk to one other team. Tell them: 'We're changing _____ because _____.' One sentence. Then come back."

Season 2 (Weeks 3–4) · Equation-Focused

"Walk to one other team. Tell them: 'Our residual was _____, so we're changing _____.' One sentence. Then come back."

✓
Item 03
Set up and program a BBC micro:bit v2 + Cutebot Pro bot. Navigate (0,0) → (4,2)→ stop → (8,4). Introduce and debug at least two MakeCode errors.
▾

You cannot facilitate the Match-Build-Make phases without hands-on hardware experience.

Required experience: You must have experienced a motor power percentage mismatch between your MakeCode code and the bot's actual behavior, and know how to trace the error back to the calculation. This is LO 6.3. You cannot teach it if you have not done it.
✓
Item 04
Pre-fill one complete sample data dashboard with realistic fake Season 1 match data for four days, including two prediction-vs-actual mismatches greater than 20%.
▾

You will only be able to spot a blank entry, a missing prediction row, or a percent change error if you know exactly what a correct dashboard looks like at every stage of the program.

The most common dashboard error: students writing predictions after they know the actual outcome. You catch this only if you know what the sequence of entries should look like. Your sample dashboard must include one correct percent change calculation next to one wrong percentage point calculation.
✓
Item 05
Practice delivering each of the five misconception corrections using only numbers from a made-up stat sheet, without notes, in under 5 minutes each.
▾

For each correction: put a made-up number on the board and walk through the calculation once. Then hand it back to the students. Do not explain it twice.

Day 5 · Equals sign as balance
Day 6 · Percent change vs. percentage point difference
Day 8 · Additive vs. multiplicative reasoning
Every post-match debrief Wk 2+ · Model as guaranteed truth
Day 11 · Correlation vs. causation
✓
Item 06
Learn and physically rehearse all three required improv activities for Days 1–2: Sound and Movement, Mirror, and Failure Bow.
▾

These activities require you to model them, not just describe them. If you are uncomfortable doing them yourself, the room will feel uncomfortable doing them. Practice in front of a mirror until you can lead each one without hesitation.

Sound and Movement (circle pass)

Stand in a circle. Pass a sound-and-movement combination around the circle. Each person copies and adds to it.

Mirror (pairs)

Partners face each other. One leads slow movements. The other mirrors exactly. Switch roles. Third round, no leader.

Failure Bow

One person makes a theatrical mistake. The group cheers. They bow.

✓
Item 07
Read the facilitation protocol and practice three redirection types until you can give a question back — not an answer — for each one.
▾

Practice until you cannot give a direct answer to any of these three question types without thinking about it.

"Did we do this right?"
"What would a correct answer look like on your graph? Is that what you see?"
"What is the equation?"
"What two data points do you have? What do you do with them?"
"What does this mean?"
"What does your line look like compared to theirs? What would cause that difference?"
✓
Item 08
Score two sample Commissioner proposals — one strong, one deliberately weak — against the Commissioner rubric before Day 11.
▾

The Commissioner's Meeting (Day 12) requires you to redirect accuracy checks to the room rather than correct proposals yourself. You can only do this confidently if you can identify in real time:

  1. Whether a cited data point is accurate
  2. Whether the proposed rule change addresses the last-place team
  3. Whether the argument is causal or correlational
Required before camp: Prepare two practice proposals from fake Season 1 data and score them. If you cannot score them accurately, you are not ready for Day 12.
✓
Item 09
Prepare the physical room before Day 1: four labeled corners, driving question posted large, bot-naming wall with team slots, and stat allocation reference cards at every seat.
▾

Room environment is curriculum. Students read the walls before they read the materials.

  • Four corner labels — one per stat name
  • Driving question — large text, visible from every seat. If it cannot be read from the back row, it does not function as a driving question.
  • Bot-naming wall — blank space with team-number slots already labeled. Pre-labeled empty slots signal that something meaningful will go there, creating anticipation before Day 2.
  • Stat allocation reference cards — one at every seat before students arrive
✓
Item 10
Study the cognitive reveal sequence until you can explain, without notes, why each stat lands on its specific day and what happens if all four are introduced on Day 1.
▾
Day 1 · Speed only
Day 2 · + Endurance
Day 3 · + Turning
Day 4 · + Power
Day 5 · Full budget equation + equals sign correction
The logic of each day

Day 1 — Speed only. Proportional reasoning: one formula, one stat, maximum simplicity.
Day 2 — Endurance. Rate of change builds directly on proportional reasoning from Day 1.
Day 3 — Turning. Coordinate geometry adds a spatial dimension.
Day 4 — Power. Ratio reasoning builds on everything prior.

Introducing all four stats on Day 1 is the single most likely cause of early disengagement. It is not because the content is hard. The cognitive load overwhelms a student who is simultaneously managing a new social environment and math anxiety.
Making a Claim from Data
"My data shows _____ because _____."
"When I changed _____ from _____ to _____, the result went from _____ to _____."
"The pattern I notice is _____. I know this because _____."
Describing a Calculation
"The percent change from _____ to _____ is _____% because I calculated (_____ − _____) ÷ _____ × 100."
"I used the formula _____ and plugged in _____ for _____, which gave me _____."
"My answer is _____. I got this by first _____, then _____, then _____."
Comparing Two Things
"_____ and _____ are different because _____. The numbers that show this are _____ and _____."
"Both _____ and _____ have _____ in common, but they differ in _____."
"_____ is better for _____ because _____, but _____ is better for _____ because _____."
Explaining a Mismatch
"The formula predicted _____, but the actual result was _____. The gap is _____ because _____."
"I expected _____ because _____, but instead I got _____. One reason could be _____."