How to marshal a 10k road race
A 10k looks simple on paper and eats marshals in practice. Junctions, road crossings, a two-way section you forgot about, and one gap that puts a runner on the wrong street. This is the sequence experienced race directors use, in the order they use it.
8 min read
1. Walk or drive the route before you count heads
Never plan marshal numbers from a map alone. Cover the route in the direction runners will travel and note every decision point: a junction, a fork, a gate, a spot where a runner could plausibly go straight on instead of turning. Those decision points are your marshal positions — everything else is optional cover.
2. Work out how many marshals you actually need
For a typical closed-or-coned 10k, budget on these categories rather than a blanket ratio:
- Every decision point (junction, fork, turnaround): one marshal minimum, two if traffic is live.
- Every road crossing with vehicles: two, so one always faces traffic.
- Start and finish: a crew rather than individuals — funnel, timing, water, bag drop.
- One sweeper at the back so you know the course is clear.
- 10% spare for no-shows. Someone always wakes up ill.
3. Give every position a name and a job
"Marshal point 4" means nothing at 7am in the rain. Name positions after what the volunteer will see — "Church Lane junction", "canal bridge turnaround" — and write the single instruction that matters at that spot: point left, hold runners for traffic, count laps. One clear sentence beats a page of general guidance.
4. Tell them when runners arrive, not just where to stand
The most common marshal complaint is standing in the cold for 40 minutes longer than necessary. Work out a front-runner pace and a sweeper pace, apply them to the distance at each position, and you get an arrival window per point. Publish that window: it sets shift times, tells volunteers when they can pack down, and stops people leaving early.
5. Brief in writing, one page per person
A single group email with everything in it is not a brief. Each volunteer needs their own page: their position on a map, how to get there, where to park and what to display, their arrival and release times, their instruction, the emergency number, and who is beside them. Print it and send it the night before — phone signal is not a plan.
6. Cover parking and release explicitly
Two details cause most race-morning phone calls: where do I park, and when can I go home? Write the parking spot, the walk from it to the position, and the release condition — "stay until the sweeper passes you", not "until the end" — onto every brief. It removes the calls almost entirely.
7. Run check-in, then watch for gaps
Check volunteers in as they arrive so you know who is missing while you can still fix it. Track it live rather than on a clipboard: an unmanned junction spotted 20 minutes before the gun is a reshuffle, spotted after the gun it's an incident report.
8. Thank them the same week
Retention is cheaper than recruitment. Message everyone who turned out within a few days, referencing their actual position and hours. Organisers who do this consistently rebuild most of their team from last year's list instead of starting from zero.
The short version
- Count marshals from decision points, not distance.
- Name every position after what the volunteer will see.
- Publish arrival windows from real pace bands.
- One page per volunteer, printed, sent the night before.
- Parking and release conditions kill the phone calls.