How to staff a large event: the event staffing plan for 200 to 2,000+ workers

Staff-per-guest ratios work for a 150-person wedding. At 5,000 or 20,000 attendees they fail, because demand is uneven: the gates take most arrivals in two hours, the bars peak after the headliner, the sampling tent is empty at noon and slammed at 4 PM. A large event staffing plan starts from the list of posts (every place a worker must stand at a given time) and the demand driver behind each one.

Write the scope down with the client first. Security, medical, production and cleaning usually come from other vendors, and the classic gap is a post everyone assumed someone else covered (re-entry, the artist wristband desk). The plan says in writing which posts are yours.

Then add the layers that never appear on the site map: team leads, a relief crew for breaks, runners, a check-in desk and a standby pool for no-shows. For a first pass, the event staffing calculator gives a starting headcount to refine post by post.

Big crews borrow their structure from incident management because it is built for hundreds of people who met that morning. FEMA's Incident Command System training sets a supervisor's span of control at 3 to 7 people, 5 being optimal, and says to reorganize when a supervisor falls outside it. On static posts within sight (scan lanes, info points) a team lead can stretch to 8 or 10. On mobile or complex work (runners, activations, a bar in a rush), stay at 5 to 7.

A radio plan that keeps the command channel quiet

Radios go to team leads and above. One channel each for command (ops managers and client event control, incidents only), gates, bars, guest services, activations and the staffing desk (arrivals, no-shows, breaks). Callers name who they call, then themselves ("Gates Lead 2, Staffing Desk"), and use site map codes ("Bar 4", "Gate B lane 6"). Agree code words for medical, lost child and evacuation with event control before doors, and swap radio batteries at the meal break.

The full plan for the festival above: Saturday, 18,000 tickets, gates at 12 PM, last set ends at 10 PM, site clear around 11 PM. The agency covers check-in, gates, bars, activations, guest services (including the crowd managers the permit requires), runners and the strike of its own areas.

• The day bar shift is 8.5 hours with a 30-minute unpaid meal: 8.0 paid hours. In California, where daily overtime starts after 8 hours, one more half hour would cost 80 × 0.5 h × $30 = $1,200 in overtime pay.
• Day and evening crews overlap by 1 to 2 hours where the peak is, so handovers happen with two crews on site, not an empty post.
• Guest services runs two waves so nobody does 12 hours in the sun and the crowd manager count holds through the 6 PM handover.
• Standby is released at 4 PM once evening crews confirm, or rolls into evening posts already known to be short.

One call time for 400 people means a queue at check-in, a jammed staff lot and an hour of paid waiting. Work back from each crew's first deadline (gates open, bars pour) and leave time to check in, walk to the post, get briefed and set up.

Every brief gives the staff entrance address (not the public one), the parking or shuttle plan and the walk to check-in. On large sites that walk can take 15 to 20 minutes, and it belongs inside the call time.

Check-in confirms identity against the booking, issues the credential, confirms the post and lead, and hands out equipment. Each step takes seconds, and seconds multiply by hundreds.

At 2,000 workers, run one desk per zone so nobody crosses the site twice. At any size, the staffing desk keeps a live count per crew (booked, checked in, missing): it drives the standby decision 15 minutes before each call, and it is the first thing the client asks for.

Nobody briefs 400 people from a stage and expects it to stick. Brief in three layers.

1. Written brief, 48 hours before: staff entrance, parking, call time and wave; post, lead and what the post does in two sentences; dress code; what to bring (ID, certifications, sunscreen); break plan; where shelter and water are; the three rules that get people removed (drinking on shift, phones at the bar, leaving a post unannounced); who to text if late, and the deadline after which the shift goes to standby.
2. Leads briefing, 30 to 45 minutes before each wave: the ops manager covers changes since the brief, the incident tree, radio channels, each crew's break rotation and the day's heat plan. Leads leave with their crew list and know who is missing.
3. Zone huddles, 10 minutes at the post: each lead gathers 5 to 10 people at the actual post, points at exits, first aid, the break area and restrooms, and repeats the three things that matter there (for a bar: ID rule, pour size, restock signal).

A site map with posts, first aid, shelter and break areas goes to every lead and into the brief, so workers find their way without asking on the radio.

Federal law does not require breaks, but under the FLSA short breaks (usually 20 minutes or less) are paid time, and a meal is unpaid only if the worker is fully relieved of duty, typically for 30 minutes or more. Many states go further. The schedule must place the breaks: on event day nobody has time to work them out post by post.

Heat is the summer field risk most likely to hurt someone, and day-one workers are the most exposed: OSHA reports that almost half of heat-related worker deaths happen on the first day on the job, and over 70% in the first week. OSHA's federal heat rule, proposed in August 2024 with heat index triggers of 80°F and 90°F, was still a proposal in late 2026, so the federal baseline is OSHA guidance (water, rest, shade, acclimatization) plus state rules. California's outdoor standard, Title 8 section 3395, is the most detailed:

You cannot acclimatize a one-day crew, so cut each person's time on sun-exposed posts instead: rotate scanners and outdoor guest services into shade every 60 to 90 minutes, and add a person or two per exposed crew to make rotations possible.

Lightning, wind and holds

The National Weather Service rule: when thunder roars, go indoors, and wait 30 minutes after the last thunder before going back out. NWS also recommends a designated lightning monitor who is not busy running the event. Event control decides holds and evacuations. The agency needs a shelter location per crew, a way to reach everyone (radio for leads, SMS for all), a headcount at the shelter by crew list, and a contract clause on how hold time is paid and billed.

Fire codes require trained crowd managers at assembly events, and at large events they often come from the guest services crew your agency supplies. Which code applies depends on the jurisdiction:

• NFPA 101, Life Safety Code (sections 12.7.6 and 13.7.6): trained crowd managers or supervisors at 1 per 250 occupants. Maryland's State Fire Marshal applies it (2015 edition) to assembly occupancies above 50 people.
• International Fire Code as adopted by states (New York: section 403.11.3): for gatherings over 500, at least two trained crowd managers and one per 250 persons or portion thereof, outdoor events under 1,000 exempt, and the fire code official can adjust the number.

Your workers see incidents first: a guest collapsing in a queue, a fight at a bar, a coworker who looks heat-sick. The tree must be short enough to remember and printed in the brief.

1. Worker tells their lead at once. The event's emergency plan says whether staff call 911 directly in a life-threatening emergency or go through event control: get that in writing before doors.
2. Team lead radios the zone supervisor with a location code and incident type, and stays on scene.
3. Zone supervisor escalates medical, security and fire issues to event control on the command channel, and tells the ops manager.
4. Ops manager logs it, covers the post and informs the client's on-site contact.
5. Ops director calls the client's account owner for anything serious (an injured agency worker, police, a removal for misconduct) and opens the written report.

The job ends when the client approves the invoice without a dispute. The FLSA requires a record of hours worked each workday and workweek for every non-exempt worker, so the reconciliation is also your compliance record. Do it that night or the next morning, while leads remember who left early.

The recap goes out within 24 hours: headcount booked versus arrived by crew, no-shows and how fast each was replaced, any unfilled post (credited on the invoice), incidents involving agency staff, activation results with photos, hours by crew matching the invoice, and three fixes for next time. Running several days? See the multi-day festival staff schedule guide and the event staff schedule template.