How many people you actually need on event day

Crew is the cheapest thing you can add to an event and the most visible thing you can get wrong. A lane is one person with a phone. A queue out of the lobby is a photograph the client remembers for a year.

Most under-staffing is not a budget decision. It is an arithmetic one that nobody did.

Start with the door, then work outwards

The door is the only part of the day with a hard capacity limit, so size it first and let everything else follow.

One lane clears roughly one guest every four seconds once warmed up, so about 15 a minute. This table is that rate against a 10-minute worst-case queue, which is our default for an event with a soft or rolling start:

Note what that is measured against. Not total headcount — arrivals in the busiest fifteen minutes. On our events that is usually around 60% of the room, because corporate guests leave the office together and aim for the start time.

If your event has a hard start — a Minister, a livestream, a programme that cannot slip — halve the queue you are willing to accept and the lane count doubles. That is the whole difference between this table and the four lanes in the 500-pax runbook. The full working, including how to substitute your own throughput and no-show numbers, is in how many check-in lanes an event needs.

The two jobs that must never be the same person

A scanning lane and an exception must never share a person. The moment a lane stops to solve a problem, everyone behind that problem stops too. One confused guest can cost a lane two minutes, which at 15 a minute is thirty people who did not move.

The walk-in and exceptions desk exists to absorb every non-clean arrival: someone who lost their QR code, someone who was never registered, someone whose name is spelled differently on the list. It is not a nice-to-have on a big event. It is what keeps the lanes at full speed.

If you only have budget for one extra person all day, make it this one.

The rest of the crew

These are descriptive names, not job titles anyone is precious about. Use whatever your run sheet already calls them. What matters is the split: no one person holds two of the first three roles, because each of them stops working the moment its holder is interrupted.

Door and lane staff — as per the table. These can be your least experienced people. The job is genuinely simple if the software is good, and it is where you train new crew.

Walk-in and exceptions — your most capable person on the door. They need judgement, the authority to make a call, and access to the full attendee record.

A floater with the client — one person whose only job is to stand next to the client contact and answer them. Without this role, the client interrupts whoever is closest, which is usually someone mid-scan. It looks like a luxury and it protects the whole door.

Registration lead — watches the queue rather than working in it, opens and closes lanes, and reads the live arrival count. On a 500-person event this person should have no fixed task at all before the spike ends. That feels wasteful right up until the moment it is not.

Room stewards — inside, not at the door. Directing to seats, managing session rooms, handling the people who arrive after the programme starts. Roughly one per entrance to a room plus one per session room with a capacity limit.

Badge printing — one person on the printer if you are printing on demand, and they run no other task. A printer with nobody on it is a printer that jams unnoticed.

Runner — one person who is deliberately unassigned. Something will happen. On a well-run event, this person spends the morning looking underused and then earns their whole fee in ninety seconds.

Sizing the whole crew

For a 500-person corporate event with a hard start, the shape we would plan. This is arithmetic from the lane figure rather than a crew list we have run and counted, so it is written out line by line — disagree with any line and the total moves with it:

That is 12 to 13 people at the peak, most of them for a two-hour window rather than the whole day. Below about 150 guests the same structure collapses to three or four people wearing several hats, and that is fine — the roles still exist, they are just combined.

The timeline the crew works to

• T-90 everyone on site, devices charged and logged in, lanes physically set up, wifi tested from where the lanes will actually stand.
• T-75 full crew briefing. Everyone scans a ticket, scans it a second time to see the duplicate message, and registers one walk-in. Fifteen minutes here removes most of what goes wrong later.
• T-60 lanes open. Early arrivals are your rehearsal with real guests.
• T-30 to T-0 the spike. Nobody does anything except process the door.
• T+15 read the live arrival count. Collapse lanes if you are done.
• T+60 one staffed desk for latecomers, release everyone else.

Two mistakes worth naming

Rostering for the whole day at peak size. Most of your crew is needed for two hours. Rostering twelve people for eight hours costs four times what it needs to and makes the budget conversation harder than it should be. Staff the spike properly and release people.

Giving the registration lead a lane. It happens every time someone tries to save a head, and it removes the only person whose job is to notice that the queue is growing.

The short version

Size the door against arrivals in the busiest fifteen minutes, not against headcount. Never let an exception block a lane. If you can afford one extra person, make it the walk-in desk. And keep the registration lead out of the lanes, because someone has to be watching.