Event check-in throughput estimator
Doors open at one time, a committee member asks how many check-in desks are enough, and nobody has timed a single registration.
…
The short answer
The estimator works out how many guests a set of check-in desks can process in the arrival window: desks multiplied by the available seconds and the utilisation, divided by the observed seconds to serve one guest. The result is rounded down to whole guests.
It assumes uniform flow, with guests arriving evenly and every desk working at the same observed speed throughout. It is a simple capacity figure, not a queue-time or waiting-time estimate and not an assessment of how many people a space can safely hold.
What to enter
- The arrival window: when check-in opens and when the guests you are counting should all be through, on the same day.
- The number of check-in desks that will be open, as a whole number of at least one.
- The observed service time per guest, in seconds. Get it from a trial with the registration team or a past event. It must be above zero.
- Optionally, a utilisation percentage and an expected number of guests. Both are yours to choose from your own records.
The formula
Guests processed = desks x available seconds x utilisation / service seconds. Available seconds are the window length in minutes multiplied by 60. Utilisation is the share of the window the desks are serving, entered as a percentage.
If you leave utilisation blank, no allowance is made and 100% is used. The tool says so, because that treats every desk as working without a pause.
Comparing with expected guests
If you enter an expected number of guests, the tool shows how many fall short of the capacity, what share of the capacity the expected number represents, and how many desks would be needed for that number on the same assumptions.
A service time of zero or less is rejected, because capacity would be unlimited. A blank service time gives no result and nothing is assumed.
Why this is not a queue forecast
Real arrivals bunch up, desks pause for questions and speeds vary between guests and staff. A simple capacity figure cannot show how long anyone waits or how long a queue becomes.
It also says nothing about how many people a lobby, queue area or venue can safely hold. That is for the venue and the competent authority to confirm in writing.
Limits
The figure is only as good as the observed service time you enter, so state where it came from. Use it to compare options such as three desks against four, and then plan the arrival flow with the venue. For staffing the desks use the shift and break planner, and for the attendance numbers behind the window use the attendance scenario planner.
Worked example · Fictional example
A fictional conference check-in
Fictional figures, to show the calculation.
A fictional conference opens check-in from 08:30 to 09:30, which is 3,600 seconds. It plans four desks, an observed 30 seconds per guest from a trial, and an 80% utilisation assumption.
Capacity is 4 x 3,600 x 80% / 30 = 384 guests. With 420 guests expected, that is 36 short, and 5 desks would be needed on the same assumptions. Each desk processes 1.6 guests a minute on these inputs.
| Input or result | Value |
|---|---|
| Window | 08:30 to 09:30 (3,600 seconds) |
| Desks | 4 |
| Observed service time | 30 seconds per guest |
| Utilisation assumption | 80% |
| Guests the desks can process | 384 |
| Expected guests, shortfall, desks needed | 420, 36 short, 5 desks |
Use this yourself
Check-in capacity worksheet
Fill in the lines and work down. Round the last result down to whole guests.
| Line | What to write | Your figure |
|---|---|---|
| A | Arrival window length in minutes | |
| B | Available seconds (A x 60) | |
| C | Check-in desks open | |
| D | Observed seconds to serve one guest, and where it was observed | |
| E | Utilisation as a percentage (use 100 if you make no allowance) | |
| F | Guests processed (C x B x E / 100 / D), rounded down | |
| G | Expected guests, and the shortfall if G is above F |
Handle it in-house, or bring in help?
Your team can usually handle this when
- A single entrance, a small guest list and a registration team that can time a trial.
- The venue has already confirmed the queue area and entry arrangements.
Outside planning help earns its fee when
- Several entrances, ticket types and badge printing steps change the service time across the day.
- Arrivals are expected in sharp peaks and the arrival flow must be planned with the venue.
- Registration, venue access and staffing must be coordinated against one timeline.
Need check-in planned with the venue and staffing?
A project lead can coordinate the check-in plan with your registration team and the venue, test desk numbers against the arrival window and align staffing with the run-of-show. The venue and the competent authority confirm what a space can hold, and operational decisions stay with you.
Questions organisers ask
Does the result tell me how long guests will queue?
No. It is a simple capacity figure on a uniform-flow basis. It does not estimate queue length or waiting time.
Why is zero service time rejected?
With zero seconds per guest the capacity would be unlimited, which is not a meaningful result. Enter the observed seconds, above zero.
What utilisation should I use?
That is your own assumption, from your own trial or past events. If you leave it blank, 100% is used and the result is an upper limit on these inputs.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.