Event Staffing: How Many People Does Your Event Actually Need?

Why guessing headcount fails

Staffing is one of the largest event-day cost lines most organizers carry, and the most common way the number gets set is also the worst: last year's figure, or whatever the supplier quoted. Both errors cost money. Understaffed gates push queues into the street, and queues are where crowding risk concentrates, one missing entry lane at the Green Guide's maximum rate means 660 people per hour standing outside your perimeter instead of spending inside it.

Overstaffing is the quieter failure: every role beyond what the risk assessment supports is margin handed to a supplier. The Sports Grounds Safety Authority (SGSA) is explicit that steward numbers should come from an event-specific risk assessment, not a habit or an industry rumor. The fix for both failures is the same, derive the number. Your crowd management plan already contains most of the inputs.

How do you calculate event staffing numbers?

In four steps: model when people will arrive, size the entry operation from published throughput rates, map every fixed post on the site, then apply role ratios on top. Each step feeds the next, and the same arithmetic that produces the headcount also produces the schedule.

Step 1: Model the arrival curve

Attendees do not arrive evenly across the ingress window, so an average-hour calculation understaffs the hour that matters. Your ticket-scanning data from comparable events tells you the real shape of the curve. At events webook.com operates on the ground, the pattern is consistent: arrivals compress into a narrow window before the main attraction, and the shape shifts with content, a headline act drags the curve late and steep, family programming spreads it early and flat. Plan for the peak hour, never the average hour.

Step 2: Size the gates from throughput

The Green Guide sets an upper limit of 660 persons per entry point per hour, and the SGSA adds a discipline most planners skip: if your recorded rate of entry is lower than 660 for reasons other than low demand, the lower figure is the one you must plan with. Bag checks, body searches and slow ticket validation all pull real-world rates down. Divide peak-hour arrivals by your true per-lane rate and you have your lane count; each lane needs an operator, plus search staff positioned ahead of it. Our stadium entry operations playbook covers how to raise the per-lane rate itself.

Step 3: Map the fixed posts

Walk the site plan and count every position that must be occupied whenever the venue is open: gates, exit stairs and vomitories, concourse pinch points, accessibility platforms, pit barriers, backstage access points, car parks. These are posts, not people, a post that needs 12 hours of coverage needs more than one person, and that multiplier is where naive headcounts collapse.

Step 4: Apply role ratios

The SGSA's published baseline for mobile stewarding is one steward per 250 of the anticipated attendance, explicitly adjusted by the event-specific risk assessment, crowd profile, event history, standing areas and alcohol all move it. The SGSA also draws a line that saves real money: it separates safety-critical stewarding, licensed security work, and non-safety-critical customer-service roles into distinct categories with distinct training requirements. Three different skill sets, three different day rates, do not pay licensed-security rates for wayfinding.

On top of the steward baseline: one scanning operator per entry lane; licensed security sized by the risk assessment, concentrated at search and response; hospitality and usher coverage for premium areas; dedicated accessibility staff at viewing platforms and access routes; and F&B staffing driven by transaction speed, a topic with its own economics in our cashless payments playbook.

A worked example: staffing a 20,000-attendee event

The arithmetic below applies the sourced ratios above to a hypothetical 20,000-attendee show. The assumptions are stated so you can replace them with your own data, that substitution is the whole method.

• Stewards: 20,000 divided by 250 gives a baseline of 80 stewards, before the risk assessment moves it up or down.
• Arrival assumption: doors open 2.5 hours before start; your scan history from comparable shows says 60 percent of attendees, 12,000 people, arrive in the single busiest hour. That 60 percent is this example's assumption, not a universal constant: replace it with your own curve.
• Entry lanes: 12,000 divided by 660 gives 18.2, so 19 lanes at the Green Guide maximum, and more if searches pull your real rate below 660.
• Scanning: 19 lane operators plus relief cover, roughly 22 people across the ingress window.
• Supervision: at events webook.com staffs, the working practice is roughly one supervisor per ten field staff plus a control-room presence, here, around 10 supervisors.
• Licensed security, hospitality, accessibility: sized from the risk assessment and the premium-area map rather than a ratio; search posts ahead of every lane are the largest security block.

Before F&B, cleaning and parking, the model already puts this event in the range of 130 to 160 event-day roles. Notice what produced that number: two published figures, one measured curve, and a site map, nothing guessed.

Schedule the peak, not the day

The same model that sizes the team schedules it, because the demand for staff follows the same curve the crowd does. Full gate complement across the ingress peak; redeploy scanning and search staff to concourses and response once gates quiet down; rebuild strength before egress, which is sharper than ingress, everyone leaves at once. A 12-hour event day at single-shift thinking either burns out the team or triples the invoice; shift design against the curve does neither.

Briefing and command structure basics

Headcount without command is decoration. The minimum structure: an event control room that owns decisions, zone supervisors who own areas, and post staff who own positions, with radio discipline connecting them. Every briefing covers the same four things: the site and the show, each person's post and hours, the emergency actions for their zone, and exactly who they escalate to. A steward who does not know their escalation path is a post filled on paper only.

Build in-house, contract, or hybrid?

The decision follows event frequency. A venue running events weekly justifies a permanent stewarding core that compounds venue knowledge. An organizer running three shows a year cannot, and should contract the volume. Most operators at scale land on hybrid: a permanent supervisory spine that owns command, briefing quality and the relationship with the venue, with contracted event-day staff supplying the volume. The rule that keeps hybrid honest: contract the numbers, never the command.

Staffing an event in a market where you have no team

For touring productions and festivals entering a new market, staffing is usually the first operational dependency with no in-house answer, ratios are portable, but trained people, local-language briefing and command experience are not. This is a service layer webook.com operates directly: trained ushering and manpower teams integrated with the on-ground operations stack, access control, scanning and zone management run by people who have staffed annual major events at Riyadh Season scale. Across 40M+ tickets processed and buyers reached in 180+ countries, the pattern holds: the entry experience is decided by the people at the lanes, not the technology behind them.

Put the model to work

If the arithmetic above produced a number your current supplier cannot explain, that is the conversation to have before your next on-sale. Talk to our operations team about trained ushering and manpower for your next event.

All articles