Event Check-In Station Calculator

Estimates how many check-in stations an event needs to keep the busiest arrival window moving, for organizers planning their registration desk.

Your numbers

Attendees checking inpeopleEveryone you expect to physically arrive, including likely walk-ups.Share arriving in the busiest window%Use last year's scan timestamps if you have them; otherwise estimate the share that shows up right before the opening session.Length of the busiest windowminutesHow long that arrival surge lasts, often the 30 to 60 minutes before doors.Seconds per check-in at one stationsecondsTime from an attendee stepping up to walking away with a badge. Scanning a code runs faster than a manual list lookup, so measure your own flow.Target average wait at peakminutesThe average time in line you are willing to accept during the surge.Maximum station utilization%How busy each station may be at peak. Lower values leave room for clumped arrivals, printer hiccups, and questions. Results update as you type.

Your estimate

Stations needed...

Arrivals in the busiest window...

Estimated average wait at peak...

Station utilization at peak...

Estimates only. Assumptions are listed below, and you can change every input.

The first hour of a conference is where check-in either works or falls apart. Most attendees arrive in a narrow window, and the number of stations you staff decides whether that window feels like a quick badge pickup or a hallway queue. Guessing high wastes staff and rented hardware; guessing low costs you the first impression of the whole event.

This calculator takes the number of attendees you expect, the share that arrives in your busiest window, and the average seconds each check-in takes at one station. It converts those into an hourly arrival rate and a per-station throughput, then runs a standard multi-server queue model (Erlang C) to find the smallest number of stations that keeps the estimated average wait under your target and station utilization under your ceiling. It is a planning estimate, not a promise: real arrivals come in clumps, so treat the answer as a floor and add a station if you have the staff.

How to use this tool

Enter the number of people you expect to arrive, then set the share that shows up in the busiest window and how long that window lasts.
Time a few real check-ins with your actual hardware, or use last year's scan logs, and enter the average seconds per attendee at one station.
Set the average wait you will accept and the utilization ceiling, then read the stations needed; if you are unsure, lower the utilization ceiling rather than raising the wait target.

What the math assumes

Arrivals during the busiest window are treated as random at a steady average rate, and service times as exponential around the average you enter; this is the standard Erlang C queue model and it tends to be a little conservative for badge lines.
Every station works the full window at the same average speed, with no breaks, printer jams, or stations closing early.
Attendees form a single shared line feeding all stations; separate lines by last name or ticket type will run slower than this estimate unless they are evenly balanced.
The station count is the smallest whole number that satisfies both your target average wait and your utilization ceiling, capped at 5,000 stations; if even that many cannot keep up, utilization reads above 100 percent and the wait becomes a plain backlog estimate averaged over the window.
No walk-up registration or problem-solving time is added; route those attendees to a separate help desk or raise seconds per check-in to account for them.

Frequently asked questions

How do I estimate seconds per check-in before the event?

Run a short dress rehearsal with the real scanners, printers, and badge stock and time the whole interaction: greeting, scan or lookup, badge handoff, lanyard or swag. Scanning a code is usually much faster than typing a name into a search box, so measure both if you are still deciding.

Why does the calculator suggest more stations than arrivals divided by throughput?

Because arrivals bunch up. If two stations can technically handle the hourly volume, they run close to full utilization and the line grows every time a group walks in together. The queue model and your utilization ceiling add enough capacity to keep the average wait under your target.

Should I count on-site badge printing in the seconds per check-in?

Yes. If a badge prints while the attendee waits, include the print time in your average. If you print in a separate step and hand badges out from a pickup table, time each step and size the slower one.

Link to this toolhttps://badgecheckr.com/tools/check-in-station-calculator/

Free for readers and publishers alike. If you cite the result in an article, a link to this page helps others find it.

More free tools from BadgeCheckr

On-Site Badge Printing Cost Calculator: Compares the total cost of pre-printing every badge against printing badges on demand at the door, for organizers deciding how to produce badges.
Badge Scanning Time Saved Calculator: Estimates the staff hours, labor dollars, and line time an event saves by scanning badges instead of checking names off a list, for organizers weighing check-in software.

A check-in line that moves

Event attendee badge check-in and scanning.

Set up check-in