How many staff an event needs: calculate by pace, not by peak
The question comes up in almost every quote: how many people do I need for this event? The most common answer is to look at the busiest moment and staff for that moment throughout the whole event. That way nobody falls short, but you pay for hours of idle staff and the quote climbs without the event getting any better.
The approach I use is different: staff by pace, not by peak. Look at how much work there is in each time slot of the event and put in the people that work needs, with a few positions that are never touched.
The mistake of calculating by the peak
Calculating by the peak means thinking like this: “at opening everyone arrives at once, I need ten people at the entrance”. And then those ten people spend five hours at an entrance nobody walks through anymore.
The peak exists and has to be covered. But it doesn’t last long. If you use it as the measure for the whole event, you’re paying for the worst moment across every hour. And in an event business, staff is usually one of the biggest per-event costs: whatever you overpay there comes straight out of what you keep. If you don’t have that math at hand, start with how to know whether your event business makes money.
Step 1: split the event into time slots
Before counting people, sketch the event in one-hour or half-hour slots. For each slot, write down what happens:
- Setup and tests.
- Opening and entry.
- Reception, welcome, first drinks.
- The central moment: show, dinner, speech, whatever it is.
- Winding down.
- Exit and teardown.
Each slot has a different workload. What you’re looking for is where the people are concentrated and where they aren’t.
Step 2: how many people pass through per hour
For each slot, estimate how many people go through each station. Not the total number of guests: how many reach that station in that hour.
Sources for the estimate:
- The time on the invitation. If it says 8 pm, not everyone arrives at 8 pm. They spread out over the first hour and a bit more.
- Similar events you’ve done. Your best data is your own. If you didn’t log it, start from the next one.
- The type of crowd. A corporate event with a fixed start time arrives more bunched than a party.
Step 3: how long each task takes
Now measure how long one staff member takes to serve one guest at each station: scanning a ticket, handing over a badge, serving a drink, checking a coat. A watch at a real event is enough. If you don’t have the figure yet, run a test beforehand and write it down.
With those two numbers you do the math:
- Guests per hour at that station, divided by what one person handles per hour, gives you how many people you need in that slot.
- Always round up. There’s no such thing as half a person.
An example with round numbers
This is an illustrative example, with made-up round numbers to show the logic. Your numbers will be different.
An event with controlled entry:
- In the first hour, 300 people arrive.
- One person at the entrance handles 100 per hour.
- You need 3 people at the entrance in that first hour.
- In the second hour, 100 people arrive: 1 is enough.
- After that almost nobody comes in: 1 person stays for latecomers.
If you’d calculated by the peak, you’d have 3 people at the entrance for 6 hours: 18 hours of work. By pace it’s 3 in the first hour and 1 for the rest: 8 hours. The other 2 people brought in for the peak can move to another station that gets busy later, or work a short shift.
Step 4: staggered shifts and people who rotate
The step 3 math tells you how many people you need in each slot. Staggered shifts are how you make that happen without overpaying:
- Staggered start times. Not all staff have to arrive at the same time. Setup crew arrive early and leave earlier; whoever covers the close comes in later.
- People who switch stations. Whoever worked the entrance at opening moves to the bar or the coat check when entry slows. For that they need to know how to do both, and that’s solved with a briefing before the event.
- Short shifts for the peak. There are people you can hire just for the busy hour, if your agreement with them allows it.
One rule: the staggered schedule is built beforehand, in a spreadsheet, with names and times. If you improvise it on the day, it ends with everyone waiting around.
What never gets cut
Staffing by pace isn’t about cutting everything. Some positions are calculated by what happens if they fail, not by what they do in a quiet hour.
- Security. It isn’t sized by pace or by savings. The number and type of security staff depends on the venue, the number of people and what the permit or the venue itself requires. That’s defined by whoever is responsible at each venue, not by a productivity calculation. Always ask the venue and whoever handles the permit.
- The bar at peak. If the bar falls short in the busy hour, a line forms, guests complain and the client notices. The bar at peak is fully covered, even if it drops afterwards.
- The person in charge. There always has to be someone who decides, who isn’t tied to a station and who can solve problems. If you’re serving drinks, nobody is watching the event.
- First aid and emergencies. Whatever the venue or regulations require, no discussion.
How to carry it into the quote
With the slots and shifts built, staffing stops being a guess. You can quote it by real hours and explain it if the client asks. Two pieces of advice:
- Quote from the calculation, not from fear. Add a small margin for the unexpected, but make it a margin and not double the people. How to build the price is in how to price your event services.
- After the event, compare. Were you short at any point? Did you have too many at another? Write it down. By the third event you’ll have your own numbers and the math does itself.
If you’re thinking about bringing in permanent people and not just per-event staff, hiring your first event employee may help.
Frequently asked questions
What if I have no data from previous events?
Start with a cautious estimate and measure at the event. Note what time people arrived and how long each task took. With one event, you already have more data than most.
Isn’t it safer to overstaff?
It’s more expensive, not safer. What’s safe is covering the peak properly and the positions that never get cut. The rest of the time, idle staff don’t make the event better.
Does this work for any type of event?
The logic does: slots, pace, time per task and shifts. What changes are the numbers, and those are yours.
Building it with someone next to you
Doing the math once is easy; the hard part is turning it into the way you quote every event. We can work on the numbers for each event and then on prices with a real margin: how much you charge, how much it costs you and how much you keep, staff included. Message me on WhatsApp and we’ll look at it.
