There's No Ratio for How Many Staff You Need

Two events with identical headcounts can need completely different staffing plans, and a ratio cannot see the difference. What determines whether an event feels well-run is not how many people attend but how many arrive in the same ten minutes - and no number divided by fifty will ever tell you that.

Quick answer

The commonly cited baseline of one staff member per 50 attendees comes from real industry guidance, and is a reasonable first-pass budget figure - but the same guidance immediately qualifies it with adjustments that matter far more than the ratio.

Published registration guidance suggests around five aides for 100 people arriving simultaneously, against two to three for 200 people arriving across eight to ten hours. Same job, double the attendees, half the staff.

More recent staffing guidance states plainly that no universal staff-to-attendee ratio works across formats, and recommends building from peak-arrival timing, transaction throughput and zone mapping instead.

The baseline everybody quotes

Ask how many staff an event needs and you will get one number back more often than any other: one per fifty attendees. It appears in industry guidance from Meetings & Conventions and has propagated widely from there.

It is not a bad number. For an early budget conversation, before a floor plan or a schedule exists, a rough per-head figure is genuinely the only thing available, and one-in-fifty is a defensible starting point.

The problem is what happens next, which is that the estimate hardens into a plan without ever being revisited. The same guidance that provides the baseline immediately qualifies it, and the qualifications are where the real method lives.

The qualification that undoes the ratio

For registration specifically, that guidance recommends adding one to two staff when the arrival window is under two hours, and subtracting one to two when arrivals are staggered across a longer period.

It then offers two worked examples that, placed side by side, dismantle the ratio entirely: roughly five registration aides for 100 people arriving simultaneously, against two to three helpers for 200 people arriving over eight to ten hours.

Scenario - Attendees - Arrival pattern - Registration staff

Fixed start time - 100 - All at once - ~5

Rolling attendance - 200 - Over 8–10 hours - 2–3

A per-attendee ratio would have given the second event twice the staff of the first. The real answer is that it needs roughly half. The variable that actually drives the number is not attendance at all - it is arrival concentration.

Nobody has ever been understaffed on average. Events are understaffed for about fifteen minutes, and that is the fifteen minutes everybody remembers.

The source that rejects ratios altogether

More recent staffing guidance takes a firmer position. TempGuru's 2026 guide states directly that there is no universal staff-to-attendee ratio that works across event formats, and that there is no fixed number of event staff per 100 guests once venue, format and programme are accounted for.

In place of a ratio it proposes three inputs, and they are worth taking seriously because each one is something you can actually measure rather than assume.

• Peak-arrival timing. When is the busiest ten to fifteen minutes of the event, and where in the venue does it happen? Almost every event has exactly one, usually attached to a fixed start time.
• Transaction throughput testing. How long does one check-in, one badge scan, one drink order actually take? Time it for real rather than estimating, then multiply by expected arrivals in the peak window.
• Zone and time-block mapping. Which areas need coverage, and during which blocks? Staffing every zone at full strength for the whole event spreads people thin across areas that only need attention for twenty minutes.

Throughput testing is the step that produces the most surprise. Organisers routinely estimate check-in at fifteen seconds a person, and a real timed test with a real list, a real badge and a real conversation frequently comes in at forty-five. At two hundred arrivals, that estimate error is the difference between a smooth desk and a queue out of the door.

Working the arithmetic once

The method sounds abstract until you run it, at which point it takes about ten minutes and produces a defensible number.

Take an event with 200 attendees and a 9:00 start. Experience suggests roughly 60 percent arrive in the fifteen minutes before the start - that is 120 people through a door in 900 seconds. If a timed check-in takes 40 seconds, one desk position processes about 22 people in that window. Reaching 120 requires between five and six positions.

The ratio method, applied to the same event, would have suggested four staff for the entire event including everything other than registration. The gap between those two answers is the queue.

Method - Registration staff - Basis

1 per 50 attendees - 4 (total, all roles) - Headcount

Throughput calculation - 5–6 (registration alone) - 120 arrivals ÷ 22 per position per 15 min

The encouraging half of this arithmetic is that those five or six people are only needed for about twenty minutes. This is precisely why zone-and-time-block mapping matters: the same humans who staff the desk at 8:45 can be doing something else entirely by 9:15, provided somebody planned for them to.

Booth and exhibition figures, which behave differently

For trade-show-style presence the same industry guidance offers two alternative rules of thumb, and they are worth knowing because they are structured differently from the event-wide ratio.

The first: a minimum of two staff for a standard 10-by-10 booth, plus one additional staffer per 1,000 total show attendees. The second, framed spatially: one staff member per 100 square feet of booth space.

Both are estimates rather than formulas, but notice that the first one scales with total show attendance rather than booth size - an acknowledgment that what drives booth staffing is the flow of people past it, which is a throughput variable wearing a ratio's clothing.

Volunteers are not staff, and the difference is scheduling

Most community events are staffed by volunteers, and applying professional staffing figures to volunteers directly produces plans that fail in a specific, predictable way.

A paid staff member works the shift they are given. A volunteer is also an attendee, wants to see the event, and will drift toward the interesting part of the room - not from unreliability but because that is why they came.

• Schedule volunteers in blocks, not for the duration. A two-hour block with a clear end is honoured far more reliably than an open-ended commitment.
• Overstaff the peak, understaff the middle. This matches both the throughput reality and the volunteer's own preference, which is to help hard and then enjoy the event.
• Give every position a written task, not a place. "Stand near the door" degrades within ten minutes; "check names against this list and hand out badges" does not.
• Name a person who owns each block's handover. The most common volunteer failure is not absence but a gap between two shifts that nobody owned.

That last point connects staffing back to the production side of running an event: a staffing plan is really a set of rows in a timeline with names attached, and the failures show up in the seams between rows rather than inside them.

What to actually count on the day

The most valuable thing you can do at your next event costs nothing and makes every subsequent staffing decision defensible.

• Time ten real check-ins with a stopwatch. Not an estimate. The number will be higher than you think and it is the input everything else depends on.
• Note the clock time when the queue was longest. That is your peak window, and it will be more concentrated than you remember afterwards.
• Count how many people arrived in the fifteen minutes before the start. This ratio - peak arrivals as a share of total - is stable enough per event type to plan against.
• Write down which zones were empty and when. Every empty-zone minute is a person who could have been at the desk during the peak.

Two events of this and you will never need a per-head ratio again, because you will have the three numbers that actually determine the answer for your specific event.

Ten stopwatch measurements at one event will outperform every published staffing ratio, permanently.

Three questions before your next event

• When is the busiest ten minutes, and where? If you cannot answer this, you do not yet have a staffing plan - you have a headcount estimate.
• How long does one transaction actually take, timed? An estimate that is off by twenty seconds is off by an entire queue at scale.
• Which zones need cover the whole time, and which only in blocks? Full coverage everywhere is usually thin coverage where it counts.

What to take from this

Use one-per-fifty for a first budget line and nothing beyond that. It is a placeholder, and treating a placeholder as a plan is how events end up with a queue at the door and idle volunteers by the coffee.

Once you have a real schedule and a real venue, replace it with the three things a ratio cannot see: when the crush happens, how long one transaction takes when you actually time it, and which parts of the room need people during which blocks.

Events are not understaffed on average. They are understaffed for fifteen minutes, at one door, and that quarter of an hour is what everybody means when they say an event felt well-run or didn't.

Frequently asked questions

Is the one-staff-per-50-attendees rule accurate?

It is a reasonable first-pass budget estimate and comes from real industry guidance, but it cannot account for arrival patterns, venue layout or transaction speed - the factors that actually determine whether a plan holds up.

How many staff does a registration desk need?

It depends on arrival concentration rather than total attendance. Published guidance suggests around five aides for 100 people arriving simultaneously, but only two to three for 200 people arriving over eight to ten hours.

What is transaction throughput testing?

Timing how long one real instance of a task takes - one check-in, one badge scan, one drink order - and multiplying it by how many need to happen during your busiest window. Estimates are typically far too optimistic.

How do I find my event's peak arrival window?

Look for any fixed start time in the schedule. Arrivals cluster hard in the fifteen minutes before a keynote or a doors-open moment rather than spreading evenly across the event.

Should every zone be staffed for the whole event?

Usually not. Zone-and-time-block mapping lets the same people cover the registration crush at 8:45 and something else entirely by 9:15, which is more efficient than thin coverage everywhere all day.

How many staff does a trade show booth need?

Industry guidance suggests a minimum of two for a 10-by-10 booth plus one additional per 1,000 total show attendees, or alternatively one staff member per 100 square feet of booth space.

Do volunteers count the same as paid staff?

Not directly. Volunteers are also attendees and will drift toward the interesting part of the room, so they need defined blocks with clear end times and written tasks rather than open-ended positions.

What is the single most useful thing to measure at an event?

Time ten real check-ins with a stopwatch. That one number, combined with how many people arrive in the fifteen minutes before the start, replaces every published staffing ratio for your specific event.

Ontaym Editorial Team

Ontaym builds tools for organising real-world gatherings, so the team spends its days on the coordination problems this article describes. Articles are researched against primary sources, reviewed before publication, and revised when the underlying facts change rather than on a schedule.

Keep the plan, the people and the timings in one place.