The planning essentials
A festival staffing plan should start with specific zones, tasks and shifts rather than a general ratio. Describe the starting state, decision route, break handover, reserve contact and close for each zone, then connect the staffing plan to the organiser's separate permit and safety work. Practical festival staff need to see where their role ends, who approves changes and what must be escalated promptly.
Keep the operations rota separate from safety and permit plans
A festival staffing plan can organise practical roles, shifts, breaks, contacts and handovers. It must not be presented as the organiser's safety or authority documentation. Responsible parties determine risks, audience conditions, emergency arrangements, access and permit requirements. The staff plan reflects those approved boundaries; it does not create or validate them through a headcount table.
The Danish Police page on public events explains that an organiser may need permission and that using the organiser's own guards requires police consent. Define which tasks are service, practical crew or other event support and which demand a separate mandate or competence. A vague brief must never relabel EventVikar personnel as security staff.
Build the rota from the festival's actual zones
Start with areas where practical work will happen: approved service points, storage, backstage support, information areas, internal routes and other defined locations. Use the names found on the organiser's map and venue communications so radio calls and signs align. Add access, meeting point, zone owner and the visible deliverables staff should find when their shift begins.
A zone is more than a place. It has a function and decision boundary. State who may move staff between zones, who approves a changed task and who receives an exception. If a responsible lead closes or changes the area, staff need a confirmed new instruction before continuing elsewhere. Flexibility does not mean self-deployment across an unfamiliar site.
Describe roles as deliverables with boundaries
Festival staff is too broad for a live rota. Describe the practical result instead: replenishment to an approved point, runner movement between defined zones, handling campaign materials, providing information from an approved message or clearing an agreed area. Attach each deliverable to the relevant instruction, equipment, contact and visible completion condition.
State which requests the role escalates. Access decisions, conflict, medical situations, technical installations or changes to audience movement belong with the organiser's relevant leads. The helpful response is to activate the right route, not to solve a matter without authority. Use role names that the organiser's wider structure recognises rather than private labels inside one supplier team.
Plan shifts around changing work, not a universal ratio
Festival needs vary with programme, deliveries, open areas, service format and the teams already present. This guide cannot provide a universal staff-to-attendee ratio. Map tasks in each operating phase, required competencies and dependencies that can move the work before the organiser and employers validate the real shift structure.
Give every rota change an owner. If somebody moves, the releasing zone needs to know which deliverable is reduced or transferred. ‘Help somewhere else’ is inadequate when several leads set priorities. The central staffing owner should confirm the new zone, task, contact and duration through the agreed communication route.
Operations matrix for festival shifts
Organiser and employers validate this matrix against the programme, permits, risks and real conditions.
- Zone and function
- Use the official name and describe the practical deliverable supported there.
- Shift and zone owner
- Show who works and who prioritises or moves staff.
- Break and temporary owner
- Name who receives active tasks and acknowledges live changes.
- Instruction and equipment
- Attach work to the responsible instruction and approved tools.
- Escalation and stop
- Name the decision route for a changed zone, unclear role or missing prerequisite.
Treat a break as a handover, not a gap
Breaks must follow the employer's real plan and actual working conditions. The operations rota should show who authorises the break, who receives the zone and which active tasks transfer. Do not make an individual staff member responsible for discovering a quiet period that might never occur in their part of the live programme.
A concise break handover can cover material state, pending delivery, current contact and next expected action. When the staff member returns, the temporary owner confirms changes. This makes the transition predictable without promising a fixed rhythm that the organiser and employer have not validated against the programme and working setup.
Use shift changes to refresh the live reality
The incoming shift needs the current zone rather than the morning's original plan. Hand over active changes, open material points, changed contacts and tasks waiting for a decision. Remove closed points from the live view. Where instruction has changed, the responsible party must confirm the new version and which roles it covers.
Walk the zone when access, work area or material flow is difficult to understand from a map. The outgoing person can show practical conditions, but should not pass personal shortcuts off as new official instruction. Route useful learning to the zone owner, who decides whether it belongs in the validated brief for subsequent shifts.
Decision summary: plan festival operations by zone
Use this summary for the operating rota. Keep safety, permits and authority requirements in their responsible plans and obtain separate approval where required. Confirm the final choice in the shared live brief before the team follows it.
- Zones: Define each zone's deliverable, boundaries, access, owner and escalation route for the current operating phase.
- Shifts: Plan shifts around tasks and phase changes, giving every transition a short status handover.
- Breaks: Treat each break as a temporary handoff with agreed coverage and a clear return of ownership.
Planning questions
Can the operations rota replace the safety plan?
No. Keep the plans separate and connect them only through named interfaces and escalation routes. Responsible functions should define requirements and authority for each plan.
How should we assess staffing for a festival zone?
Map concurrent deliverables, distances, access and expected phase changes. Use that specific analysis as decision input and ask the responsible owners to approve adjustments.
What should a festival shift handover include?
Transfer the zone's current condition, changes, open actions, equipment and next priority. Include only information the incoming function needs in order to act.
Sources
- Danish Police: Offentlige arrangementer
The limited statements about possible permission for public events and police consent for an organiser's own guards.
- Danish Working Environment Authority: Systematisk arbejdsmiljøarbejde
The limited statement about employer planning, instruction and supervision responsibilities.
This is operational planning guidance, not a capacity, security, permit or safety plan. The organiser, employer, venue, authorities and relevant competent leads must validate requirements, roles and instruction for the actual festival.