STOP / GO Decision Framework

Skill 2 of 5

Why it matters

Most crashes and bike damage come from forcing a line when fatigue or uncertainty is already high. A simple shared language (“STOP or GO?”) makes group decisions faster and safer.

How to use it

• Ask before features: Do we understand the terrain, line, and run‑out?
• If confidence is low, regress: scout, spot, or choose an easier line.

GO looks like

• You’ve seen or walked the section and know the exit.
• There’s a clear run‑out and a spotter if needed.
• You can perform a simpler version cleanly.
• You’re fueled, hydrated, and mentally present.

STOP looks like

• Unknown terrain, hidden run‑outs, or moving water you can’t read.
• Fatigue causing sloppy clutch/brake inputs or repeated dabs/falls.
• Heat/cold stress, dizziness, or pain.
• Bike faults (fading brakes, boiling clutch, loose controls).

Reset protocol

Stand down, breathe, discuss options, and regress: smaller feature, different line, or call it. Progress is consistency, not hero sends.