How Many People Do You Need to Run an Event?

"How many people do we need?" is usually answered with a number that is too low, because the plan counts the desk and forgets everything that happens away from it.

The roles that exist at every size

• Event lead. Decides. Does not also run a desk.
• Registration. Check-in, badges, walk-ups, problems.
• Floor / rooms. Doors, timing, speaker handling, session chairs.
• AV. Sound, slides, recording.
• Speaker liaison. Green room, call times, the missing laptop adapter.
• Comms. Attendee messages, social, the online audience.

At fifty people, one person may hold four of those. At five thousand, each is a team. What does not change is that the event lead has to be free to answer questions, and the moment they are behind a desk, the event has no lead.

Ratios that decide queue length

Registration is where crowding is visible. As a working rule for an on-site check-in with scanning:

• One check-in station per 150 attendees arriving in the peak hour.
• One floater per three stations to handle the problems that would otherwise block a queue — name not found, wrong ticket, badge reprint.
• One person on badge printing if you print on demand.

Five hundred people arriving across an hour therefore wants about four stations, one floater and a printer — six people for forty-five minutes, not two for three hours. The full method is in getting 500 people in under 30 minutes, and self check-in kiosks change these numbers if your data is clean.

Rough crews by size

• Up to 100, single track: 2–3 people. One lead, one desk, one floating. AV from the venue.
• 100–500, one or two tracks: 6–8. Lead, two on the desk at peak, one room per track, one AV, one comms.
• 500–1,500, multi-track: 15–25, in two shifts. Registration becomes a team with its own supervisor; speaker liaison becomes a full-time role.
• 1,500+: departmental. Each area has a lead, and the event lead talks to leads, not to individuals.

Volunteers are staff with a shorter brief

They can do anything with a clear script and a named supervisor: doors, wayfinding, queue management, room counts. They should not be the only person who can solve a payment problem or open a locked room. Brief them in person, give them one page, and tell them explicitly what to escalate rather than improvise.

Build the rota around arrivals, not around the day

Staff follow the crowd, not the clock. Look at last year's check-in timestamps: most events have a sharp peak in the first ninety minutes and a long tail. Put your people in the peak, then move half of them to the floor. If you are running more than one day, the middle days need cover more than the first one does.

Give everyone the same view

Most staffing pain is information pain: someone at a door who cannot see whether a person is registered, a liaison who does not know a session moved. When the attendee list, the agenda and the messaging are one system, a small crew covers a big event — that is what Gathervo is for. Try it free, or see the plans.