Stop Guessing Your Registration Desk Headcount

Three people on the registration desk. Two hundred stands. Opening time in forty minutes, and the pre-reg list just printed at 1,847 names — which is 300 more than last year and nobody updated the roster.\n\nThis is how registration queues actually start. Not because the software failed. Not because the venue was awkward. Because the staffing plan was last year's staffing plan, and nobody rebuilt it from the data.\n\n## Why headcount planning breaks down at shows\n\nMost organiser teams are good at one thing: getting bodies on the desk. What they're less good at is figuring out how many bodies, and when. The default is gut feel — "we did five last time and it was fine" — which works until it doesn't.\n\nThe problem compounds across three variables that almost nobody tracks cleanly:\n\nArrival shape, not just arrival count. A 2,000-attendee day is meaningless for staffing if you don't know that 800 of those people arrive in the first 45 minutes. Opening hour at a trade show is almost always the crunch; by 11 a.m. the queue has cleared and you're overstaffed for the rest of the day. Build your plan around the arrival curve, not the day total.\n\nPre-reg vs walk-in split. Pre-registered attendees take 60–90 seconds at a well-run desk. Walk-ins take 3–5 minutes — longer if they need a badge printed from scratch, longer still if there's a waiting exhibitor they need to be matched against. A show with 40% walk-ins needs a different desk configuration to one with 85% pre-reg, even at the same headline attendance.\n\nShow day versus event day. Day one of a three-day show plays differently to day two. Exhibitors arrive in force on day one (often an hour before doors); the press and VIP list is heaviest on day one; the walk-in wave hits hardest on day one. Days two and three are calmer but not empty. If you staff a flat roster across all three days, you're simultaneously under-resourced on day one and burning budget on days two and three.\n\n## The staffing model that holds up under pressure\n\nThe approach that actually works is built around three inputs: your historical arrival data (or your best estimate if this is a new show), your badge workflow time per attendee type, and a target maximum queue length you're willing to tolerate.\n\nStep 1: Build your arrival curve. Pull your registration system export from the last two shows. Group arrivals into 30-minute slots per day. If your platform doesn't surface this, badge scan timestamps will do it. What you're looking for is the peak half-hour — the window where the most people are hitting the desk simultaneously. That number drives everything else.\n\nStep 2: Set your service time. Time your desk agents. Honestly. A practiced agent with a good registration system will clear a pre-reg attendee in under 90 seconds. A first-day volunteer using an unfamiliar interface takes 3–4 minutes. Badge printers that run through a separate queue add another variable. Know your real numbers, not the optimistic ones.\n\nStep 3: Apply the ratio. With a 90-second service time and a target maximum queue of 10 people, one desk can process about 40 pre-registered attendees in 30 minutes before the queue starts building. If your peak half-hour brings in 320 pre-reg arrivals, you need eight desks running, plus separate walk-in lanes. Rough rule of thumb for UK and Australian shows with a well-configured registration platform: one agent per 80–100 pre-reg arrivals per peak hour. That's the number to staff to, not last year's headcount.\n\nStep 4: Add your float. No-shows, late agency confirmations and sick calls are a fact of show life. Build a minimum 15–20% float into your final headcount. For a six-agent peak shift, that's at least one named backup who knows they may be called in. "We'll figure it out on the day" is not a float.\n\n## Where this plan lives (and dies)\n\nThe staffing plan is useless as a PDF in someone's inbox. It needs to be a live document that shows agents which shift they're on, what their role is (pre-reg desk, walk-in desk, exhibitor check-in, runner, float), and who their on-the-floor supervisor is.\n\nMost organiser teams still run this across two or three spreadsheets — one for the rota, one for the contact list, one for the run sheet — none of which talk to each other. Someone updates the rota, forgets to tell the contact list manager, and by show morning the shift supervisor has a printed sheet with a name who pulled out two days ago.\n\nIf you're running more than one show a year, this is exactly the kind of process that is worth systematising. A purpose-built staffing module inside your show operations platform — or even a tightly structured template that feeds from your registration data — will save you a bad opening hour at least once a season. For the maths on whether that's worth investing in, the Booth Staffing Calculator gives you a structured starting point on headcount and shift cover, even if it's primarily built for exhibitor booths rather than organiser desks.\n\n## The brief for your ops team: shift structure that works\n\nFor a three-day trade show, a working shift structure looks like this:\n\n- Opening shift: All hands. Earliest badge-scan time minus 90 minutes. This is when exhibitors arrive, early press badges are collected, and walk-in processing starts. You want your most experienced agents here, not your newest.\n- Peak cover: Full peak staffing maintained until arrival rate drops below 50% of morning peak (check your historical data — this is usually 10:30–11:00 on day one).\n- Mid shift: Reduced desk count. Keep at least one walk-in lane open; pre-reg queues will be minimal. Good time to rotate breaks without pulling down capacity.\n- Close shift: Thin cover on the desk, but someone must own the "I lost my badge" queue, which spikes in the final two hours of day one.\n- Day two/three opening: Smaller crew. The late registrants and badge-collection tail from day one compresses into the first 20 minutes; after that it's light traffic.\n\nName every shift. Name the backup for every shift. Brief every agent on their specific role, not just "you're on registration". The agent running the walk-in lane needs to know the form, not the badge printer queue.\n\n## What breaks this plan (and how to fix it)\n\nThe registration system is slow. If your platform is lagging on badge printing or lookup, every service-time estimate is wrong. Test under load before show day — not the morning of. This is one of the clearest signs your registration setup needs attention; if you're recognising it show after show, the case for replacing your registration system gets stronger each time.\n\nVolunteers instead of trained agents. Volunteers cost less but slow the desk. If you're using them for peak shifts, factor in a 50–100% longer service time and build your headcount plan accordingly. Alternatively, assign volunteers to runner and wayfinding roles and keep trained agents on badge lookup and printing.\n\nThe exhibitor check-in is mixed with attendee registration. Separate these. Exhibitors collecting staff badges, adding a last-minute team member, or sorting a contractor pass do not belong in the general registration queue. A single dedicated exhibitor lane — even just one agent with a tablet — keeps the main queue clear and stops exhibitors getting frustrated before the show has opened.\n\nNo data from last year. If your current platform can't tell you arrival volume by 30-minute slot per show day, that's a capability gap worth fixing before you plan next year's staffing. The difference between guessing and knowing your peak arrival window is the difference between three agents and six. For a broader read on whether your show ops toolset is keeping up, the five signs your show ops have outgrown spreadsheets is worth 10 minutes.\n\n## Building the plan as a repeatable template\n\nThe goal isn't a staffing plan for this show. It's a staffing plan you can rebuild in 20 minutes for every show, because the structure is fixed and only the inputs change.\n\nThat means:\n- Arrival curve template (slots pre-populated, fill in from data)\n- Service time benchmarks per attendee type (update when your platform or process changes)\n- Ratio calculation (desks required = peak 30-min arrivals ÷ throughput per agent)\n- Shift roster template with roles named and float flagged\n- Post-show debrief note: actual vs planned queue length, actual vs planned headcount, what to adjust\n\nThe debrief note is the part most teams skip. It's also the only reason this year's plan is better than last year's. If you don't record where the queue blew out and why, you rebuild the same guess next time.\n\nFor teams thinking about a more integrated approach — connecting your registration data to your staffing plan, or building show-specific ops tooling — the guide to choosing an exhibition software development partner covers what to look for when you're ready to go beyond templates.\n\nStart with the arrival curve. Everything else follows from that number.

Useful tool

Try Samvara's Organiser Exhibition ROI Planner — For organisers — show P&L by day.