Velocity Arena — Facilitation Guide

Minimum Success Floor Before Day 1

Every session clears this bar

✓

Students participate

✓

Students feel safe to be wrong

✓

Students explain some reasoning out loud

✓

Facilitators avoid solving every problem

✓

Students revise after mistakes

If all five are true at the end of a session, that session succeeded. This floor exists to protect the work from perfectionism — a session where students are thinking, talking, and revising is a good session, even if the facilitation wasn't flawless. Measure up from here, not down from ideal.

Guidance Ladder Before Day 1

Use the lowest rung that works. Start at 1. Move down only when the student is genuinely stuck — not just slow. The more of the work students do, the more transferable the learning.

1

Pause

Stop talking. Count 7 seconds. Most students will start working if you give them time and don't fill the silence.
2

Ask a question

"What does your data show?" / "What formula are you using?" A question returns the thinking to the student.
3

Point to data

Gesture to the Match Log or dashboard without explaining it. "Look here." Let them read it.
4

Clarify directions

Re-read the task prompt or worksheet instruction with them. Confusion about what to do is different from confusion about math — fix the former, don't solve the latter.
5

Model one example

Work through one step — not the student's problem, a parallel one. Then step back and let them apply it.
6

Give the method

Explain the procedure. "Here's how percent change works." Don't solve their specific numbers — give them the tool.
7

Give the answer

Only when safety, time constraints, or access requires it — or when a vocabulary barrier is blocking all progress and can't be resolved any other way.

Use sparingly. If you reach rung 7 frequently, that's a signal to revisit the task design or the student's readiness for that concept.

Not all help is rescue. Clarifying directions, modeling one example, and naming a pattern are not rescuing. Rescue means doing the thinking students can still do.

5 Core Talk Moves Use during session

Move	When to Use It	What to Say	What to Avoid
Press for Evidence	Any time a student makes a claim without a number	"Show me the number." / "Which formula?" Longer: "Where in your data does it show that?"	Accepting "I think" or "it feels like" as complete answers
Hold the Gap	After asking a question — wait before doing anything else	Wait 7 seconds. No rephrasing. If still nothing, use Turn and Talk.	Jumping in before 7 seconds; restating the question
Revoice	When a student says something significant but unclear	"So you're saying Speed 2 cuts Motor% by 2 — right?"	Paraphrasing in a way that adds precision the student didn't provide
Turn and Talk	When a question needs processing time before public sharing	"Tell your partner what you'd change and why. 90 seconds."	More than 90 seconds; skipping debrief after the talk
Agree / Disagree	After a student states a position, to activate critical thinking	"Agree or disagree — what number supports you?"	Asking agree/disagree without requiring a data anchor

These scripts are stabilizers, not personality replacements. Be warm. Be direct. Use normal human encouragement. Then return to evidence.

The Silence Protocol Use during session

A tool, not a rule.

Ask the question. Stop talking completely.
Wait. Don't rephrase. Don't add "think about it." Scanning the room is fine.
At ~7 seconds, look for a raised hand or visible processing. Call on them.
If no one responds, use Turn and Talk — not a repeat of the question.
After Turn and Talk, return to the original question.

7 seconds activates processing across confidence levels. Under 3 seconds produces short answers from high-confidence students only. If a student is in genuine distress rather than productive thinking, respond to the student — the pause is in service of thinking, not a rule to hold at all costs.

Gap Sentence Anatomy Use during session

Every gap sentence requires all three parts. Missing any one part means it's incomplete.

Part 1 — Predicted Value

"We predicted our bot would score 2 points..."

Must be a specific number. "We thought we'd win" is not a predicted value.

→

Part 2 — Actual Result

"...but the actual result was 0 points..."

Must come from the Match Log. Not memory.

→

Part 3 — Quantified Gap

"...so our gap was 2 points."

Must be a computed number. "A lot" is not acceptable.

Complete Example:

"We predicted our Motor% of 50 would let us clear the obstacle zone in 3 seconds, but the actual time was 5.2 seconds, so our gap was 2.2 seconds."

Incomplete — ask for the missing part:

"We thought we'd be fast but we were slow." → "What was your predicted time, and what was the actual?"

Thinking vs. Shutdown Use during session

Productive Thinking	Shutdown
Writing	Head down, no pencil movement
Pointing to data	"I don't care"
Whispering to partner	Waiting for an adult to answer
Trying numbers	Repeated random guessing
Rereading the prompt	No engagement with the task

Intervene earlier for shutdown signals than for thinking signals.

Participation Balance Protocol Use during session

When one or two students tend to speak for the group, use these moves before stepping in directly. Structure tends to work better than naming.

Observable Signal

One student answers before teammates finish reading or calculating

Assign roles (Reporter, Recorder, Analyst). Direct questions to the role: "Analyst, what does the data show?"

Observable Signal

Quieter members are recording but not reasoning aloud

Use Turn and Talk directed specifically: "Everyone explains to a different teammate — not the person you usually talk to." Debrief the quieter voices first.

Observable Signal

A student defers repeatedly: "I don't know, ask them"

Don't redirect to a different student. Use the Guidance Ladder — start with a pause, then a question they can answer from what's visible: "What do you see in Match Log row 2?"

Observable Signal

A student argues dismissively with teammates' ideas

Use Agree/Disagree with a data requirement: "You disagree — what number in the dashboard supports your position?"

Exit Check Standards by Week Use after session

Week	Days	Minimum Standard	Mastery Signal
Week 1	Days 1–4	Student can state the formula for their day's stat and apply it to one example with correct arithmetic.	Student explains the trade-off: raising this stat means lowering something else — with a specific number.
Week 2	Days 5–8	Student writes a complete 3-part gap sentence from their most recent match.	Student identifies which specific decision contributed to the gap and names a revision hypothesis.
Week 3	Days 9–12	Student applies the distance formula or linear equation from the week to a bot-related scenario.	Student connects two data points from the Match Log to a pattern and uses that pattern to predict a future result.
Week 4	Days 13–15	Student computes a residual and interprets whether the model over- or under-predicted.	Student uses residual + percent change together to recommend a reallocation, citing specific numbers for both.

3-Step Loss Recovery Protocol Use during session

Use on match days 7–10 and 13–15, and any time a team shows visible distress after a loss. Follow the sequence.

Step 1

Acknowledge the Emotion

~30 seconds

Name what happened. Give the team a moment. Don't redirect yet. Don't extend this into a longer support session.

"That was a tough result. Take a moment."

Step 2

Locate One Decision in Data

Match Log open

One — and only one — decision that connects to the result. This returns analytical control to the team.

"Open your Match Log. Find one decision — just one."

Step 3

Restore Hypothesis-Maker Role

Before they leave the table

End with a forward-looking hypothesis. The team leaves as people who have a next test to run.

"One change. What is it? 'We're changing _____ because _____.'"

The protocol ends at Step 3.

Adding advice after Step 3 — "here's what you should change" — takes the hypothesis away from the team. Stop at "One change. What is it?" and let them generate the answer.

Good Enough Debrief Use after session

The minimum that works

"Pick one number. Ask what formula produced it. Ask what it changes for next time."

That's enough. You don't need to review every moment of every match. One number with a formula and a next-step question closes the learning loop.

Observation Protocol — Match Day Use during session

Before matchPrediction logged?
During matchAnalyst recording?
After matchGap sentence complete?
After lossRecovery protocol started?
DebriefOne number, one formula, one connection?

3 Hardest Moves in This Program Use for coaching

01

Hold the Gap

After asking a question with no response, the impulse to step in is real. Students who don't answer quickly may still be processing — silence doesn't mean the question failed.

What to do instead: Count to 7. If still nothing, use Turn and Talk — never restate the question first.

02

Press Correct Answers

When a student gives a correct answer, the natural move is to confirm and move on. Correct answers deserve the same pressure as incorrect ones.

What to do instead: "That's right — show me the formula step that produces that number."

03

Stay Out of Allocation

A team presents an allocation likely to underperform. The urge to redirect is real. But a student-owned decision that doesn't work is valuable — the data does the correcting.

What to do instead: "Show me your steps." Ask questions until you understand their logic, then step back.

6 Common Facilitator Errors Use for coaching

#	The Error	Why It Tends to Happen	The Fix
01	Accepting "I think" without a number	Participation feels like it's happening	"Which formula gives you that answer?"
02	Breaking silence before 7 seconds	Silence can feel like failure on the facilitator's part	Count silently. Post "7 sec" on a sticky note. The pause is working even when it doesn't feel like it.
03	Steering a team's allocation before matches	You can see the allocation is likely to underperform	"What does your data suggest?" then step back. Clarifying the budget formula is fine. Steering away from a decision you disagree with is not.
04	Accepting a 2-part gap sentence	Two-thirds complete can sound complete	"You have the prediction and the result — what's the computed gap?"
05	Improving Commissioner proposals during prep	A weak proposal can feel like the facilitator's problem to fix	Clarifying format requirements is fine. Improving the argument is not — weak proposals go to the floor, and the class response is the learning.
06	Adding a 4th step to loss recovery	You want to help the team move faster	Stop at "One change. What is it?" The hypothesis belongs to the team.

When You Feel Overwhelmed Use during session

Facilitator Recovery Sequence

→ Stop talking.
→ Give the room a 3-minute task.
→ Sit down.
→ Pick one problem, not five.
→ Ask for data before giving advice.
→ Resume the schedule from the next clean transition.

Presentation Support Boundary Before Day 1

Applies to Commissioner's Meeting (Day 12) and Championship pitches (Days 15–16). The facilitator's job is format compliance, not content direction.

Appropriate Before the Meeting

Confirming that a proposal cites at least two data points and names one math concept type. Clarifying what those format requirements mean. Reminding teams of the rubric criteria.

Not Appropriate

Suggesting which data point makes a stronger argument. Rewriting a sentence in the proposal. Telling a team their argument won't work. Let the proposal go to the floor as written.

During the meeting: redirect accuracy challenges to the room. "Does this proposal's data check out against the dashboard? Someone verify." Don't correct proposals yourself — that's the Commissioners' job.

ENDS Closing Ritual — Types by Day Use after session

Goal Setting

Days 1, 5, 11, 13

Students set a specific, measurable goal for the next session.

Math Connection

Days 2, 6, 9, 10, 14

Students connect today's math concept to a specific number from the dashboard.

Team Pulse

Days 3, 7, 11, 15

Quick team check-in on collaboration — hold up a number (1–3), then complete one sentence aloud.

Skill Bridge

Day 12

Students name one skill used today and one place they'll apply it in Season 2.

Journal Entry

Days 4, 8, 16

Written reflection with a specific prompt. Five minutes maximum.

Facilitator Coaching Checklist Use for coaching

For observers. Use during or after a session to give specific, actionable feedback.

Did the I wait after questions (7 seconds before stepping in)?
Did students explain their reasoning — not just give answers?
Did I avoid taking over student thinking?
Did quiet students speak at least once?
Did losses lead to revision — not just disappointment?

Facilitation Overview

Facilitation Philosophy

Every session clears this bar

A tool, not a rule.

The minimum that works

Facilitator Recovery Sequence