Passing the Baton on the Ground: Designing a Mid-Event Marshal Handover That Holds

A festival's afternoon shift change rarely appears in a post-event debrief. It is not a headline moment: no gate opens, no artist walks on, no crowd surge is captured on camera. Yet the ninety minutes in which one marshal team hands its responsibilities to another are among the most fragile in the operating day. The outgoing team is tired and already thinking about the journey home. The incoming team is fresh, unfamiliar with the morning's small anomalies, and inclined to assume that a quiet site is a settled one.

The gap between those two states of knowledge is where incidents are born. A handover is not an administrative courtesy between colleagues; it is a transfer of operational control, and it deserves the same rigour as a gate opening or a crowd management plan.

Why the changeover deserves its own plan

Most event documentation treats the shift change as a staffing matter. Names are ticked off, high-visibility tabards are exchanged, and the incoming team is pointed towards a position. What that approach ignores is that a marshal's effectiveness depends far less on the tabard than on what they know: which gate has been running hot since eleven o'clock, which steward is managing a difficult group near the bar, which access route has been blocked by a delivery that never left.

None of that knowledge is written on a rota. Unless the process is designed to move it deliberately from one team to the next, it evaporates at exactly the moment the site is busiest and the margin for error is thinnest.

What has to travel with the team, not the person

A useful handover passes on a defined set of artefacts and observations. The list should be agreed before the event, printed on a single sheet, and completed by the outgoing supervisor rather than assembled from memory.

• The incident log. Every entry from the shift, including those closed with no further action. A minor issue logged at midday is often the context for a larger one at five.
• The hotspot map. A marked site plan showing where crowding, queueing, obstruction or behavioural pressure has been concentrated, annotated by time.
• Radio state. Channels in use, any faults reported, spare handset locations, and the names and call signs of the current shift.
• Site walk observations. What the outgoing team saw on its final lap: damaged barriers, standing water, lighting failures, unlocked gates, signage that has blown over or been ignored.
• Outstanding tasks. Anything begun but not finished, with an owner and a time by which it should be resolved.
• Welfare and staffing notes. Fatigue, illness, a marshal who has been stood in full sun for too long, a team that needs rotation earlier than planned.
• Stakeholder status. Which conversations with the safety officer, the local authority licencing team or the medical provider are open, and what has been agreed.

Structuring the ninety minutes

The most reliable handovers follow a three-phase structure rather than a single briefing at the gate. The first phase is shadowing: incoming supervisors join their outgoing counterparts for twenty to thirty minutes at the busiest positions, watching rather than taking over. This is the only point in the day when two people with authority can compare notes on the same view.

The second phase is a joint site walk. It should follow the operational perimeter rather than the public route, and it should be led by the outgoing supervisor, who knows where to look. A walk that covers only the main arena will miss the service road, the rear of the stage compound and the temporary pedestrian route that has already started to erode into mud.

The third phase is confirmation. Both supervisors sign the handover sheet, agree the top three priorities for the incoming shift, and confirm the trigger points at which the incoming team will escalate to the event control room. Fifteen minutes is usually enough, provided the previous two phases have been done properly.

Radio continuity is not a formality

A handover that changes the voice on the channel without changing the discipline around it creates confusion at the worst possible moment. Incoming teams should be briefed on the phraseology in use, the escalation path, and any channel restrictions imposed because of interference or congestion. Where a radio scheme has been running for several hours, the outgoing team can also flag which positions are over-transmitting and which are silent when they should not be. Silence on a channel is not necessarily good news.

The failures worth designing against

Three patterns recur. The first is the verbal handover with no written record, which leaves nothing to audit when a decision is later questioned. The second is the handover conducted on the move, at the gate, with one eye on the crowd; it produces agreement without comprehension. The third is the assumption that the incoming team has read the event plan, which in practice many will have skimmed at best. None of these failures requires bad faith. They require only a busy day and an unstructured process.

Scaling the model across different event types

A town-centre event with a two-position footprint can run the same three phases in forty-five minutes rather than ninety. A stadium day has the advantage of a fixed site and the disadvantage of interior circulation that changes character as concourses fill; its handover should include a concourse walk, not just a perimeter check. Multi-day festivals benefit from a written overnight summary that bridges the last shift of one day and the first of the next, so that no team starts a morning believing it is the first to arrive.

The principle is constant. Handover is a transfer of responsibility, and responsibility transfers badly when it relies on goodwill and memory. A repeatable process, a single sheet, a joint walk and a signed confirmation cost an organiser very little. The absence of them tends to cost rather more.