Skip to content
2 min read
In progress

Communication During Matches

How a drive team talks during the 2.5 minutes that count: shorthand vocabulary, the chain of command, and avoiding chaos.

Lesson
14 / 34
Reward
+10XP

Sign in to track progress, earn XP, and save lessons.

Communication is a designed system, not improvisation

A match is loud, fast, and stressful. FIRST's Best Practices for Drive Coaches resource is blunt about it: the drive team must communicate clearly, concisely, and efficiently, using agreed-upon shorthand decided before the match — not invented in the moment. Good drive teams design their communication the way they design the robot.

Build a shorthand vocabulary

Come up with short, unambiguous calls for the things you'll say constantly, for example:

  • Game state: "loaded," "empty," "jammed," "ready."
  • Movement: "go," "hold," "back out," "left lane."
  • Targets: name scoring locations the same way every time.
  • Endgame: a single clear trigger like "climb now" with a countdown.

The official caution: don't assume everyone interprets a word the same way. If "high" means the top row to the operator but the upper goal to the coach, you'll mis-score under pressure. Define terms explicitly and write them down.

Keep one chain of command

The channel should flow cleanly:

  • The coach issues strategic calls (where to go, what to prioritize, when to defend or climb).
  • The operator reports mechanism status back ("loaded," "jammed").
  • The driver mostly listens and drives, acknowledging briefly.
  • The human player reacts to feed/score calls.

Avoid everyone talking at once and contradictory instructions, both of which the coaching resource flags as performance killers. One voice should own strategy at any moment; if the coach and operator both shout different things, the driver freezes.

Talk loud enough, not too much

Alliance stations are noisy. Speak loudly and at a steady volume, but don't fill every second — constant chatter drowns the calls that matter. Many teams find that less but clearer communication outperforms a running monologue. Confidence in your voice matters too: a calm coach steadies a rattled driver; a panicked coach makes a good driver worse.

Debrief every miscommunication

The official resource stresses learning from mistakes: if a call was misunderstood mid-match, discuss it afterward and fix the vocabulary or the chain of command. Over a season these debriefs compound into a drive team that barely needs to talk because everyone already knows what the others will do. Treat each miscommunication as a bug to be fixed, not a person to be blamed.

Spot an error or something out of date?Log in to suggest an edit

Key takeaways

  • Agree on concise shorthand before matches; never invent vocabulary mid-match.
  • Define terms explicitly so words like "high" can't be interpreted two ways.
  • Maintain one chain of command: coach calls strategy, operator reports status, driver drives.
  • Avoid contradictory or constant chatter, and debrief every miscommunication afterward.

Lesson quiz

Required

Answer all 3 questions correctly to complete this lesson.

01.A drive team's communication works best as a designed system. What should teams do with their shorthand vocabulary to keep it reliable during a match?

02.In a drive team's single chain of command, what is the driver's main role during a match?

03.How should a drive team manage its talking volume and amount of communication during a noisy match?

Answer every question to submit.

All 34 lessons in Drive Team