Most parts of an event get a rehearsal. The AV is tested the night before, the caterers confirm numbers, the speakers get a run-through. The check-in, oddly, is often the one system that meets its first real guest live, at nine on the morning, with a queue already forming behind them. That is a strange thing to leave untested, because it is the first thing every guest touches and the one failure that happens in full view.
A dry run fixes it, and it does not take long. Twenty minutes with the real kit, a few days before, will surface almost everything that would otherwise go wrong at the worst possible moment.
Why the door is worth rehearsing
The front door sets the tone before a word is said from the stage. In Bizzabo's 2025 State of Events report, 71% of attendees said the ease of check-in can make or break their event experience (Bizzabo, 2025 State of Events). That verdict is formed in the first minute, and it is formed on whatever you did or did not test beforehand. A queue caused by a login that does not work, or a guest list that never finished importing, costs you the same first impression as one caused by being genuinely short-staffed, except this one was avoidable.
What a dry run actually is
A dry run is not a full rehearsal of the event. It is a short, deliberate walk through the exact steps a real arrival will take, on the real equipment, using real data. You are not checking that the software exists. You are checking that your particular list, on your particular tablets, on the venue's particular network, does what you expect when a real person is standing there.
Set aside twenty minutes, put the kit on the desk you will actually use, and run a handful of real arrivals from start to finish. The point is to be surprised now, in an empty room, rather than at the peak.
The seven things to test
Work through these once and you have covered the failures that actually happen at doors.
- The real guest list, imported. Not a sample. Bring in the file you will use on the day and confirm the count matches what you expect. Imports are where quiet problems hide, which is why we wrote importing a guest list that actually holds up.
- A genuine pass, scanned end to end. Send yourself a real confirmation, present the code, and watch it check in. This proves the whole chain, from email to scan to a live count, not just one link of it.
- A manual check-in by name. Someone will always arrive without their pass. Search a name, check them in by hand, and know where that button is before you need it in a hurry.
- A walk-up who is not on the list. Add a new guest at the desk and check them in. If your event takes registrations on the day, this is a main path, not an edge case.
- The offline fallback. Turn the venue wifi off and try to scan. Knowing how the door behaves when the network drops is the difference between a pause and a panic, as we covered in kiosks that fall back gracefully when the wifi drops and scanning attendees when the venue wifi drops.
- Every crew login. Each person on the door should sign in under their own account and successfully check one guest in. A login that works on your phone but not on the borrowed tablet is exactly the thing to find today.
- The kiosk flow, front to back. If guests will check themselves in, walk the kiosk as a first-time guest would, with no help, and see whether the prompts make sense to someone who has never seen them.
Do it on the real kit and the real network
The single most valuable part of a dry run is that it happens on the actual hardware and the actual venue wifi. Software behaves; venue networks do not. A check-in that flew on the office broadband can crawl on a saturated conference wifi, and the only way to know is to stand in the room and try it. Test on the tablets you are bringing, on the connection you will have, at roughly the time of day the room will be busy.
While you are there, time a single check-in. A clean scan should take about eight seconds, the pace CheckInHub runs at across live events, and confirming that holds on your kit tells you how many lanes your arrival peak really needs.
Let the dry run double as the brief
The neat thing about testing the door is that the crew who help you test it have now, in effect, been briefed. They have seen the manual check-in, watched a walk-up get added, and know what the screen does when a pass is already checked in. Roll the two jobs together and the dry run pays for itself twice. We set out the short version in the door brief that takes five minutes and the fuller one in briefing your door crew before doors open.
Rehearsed doors are calm doors
Nobody remembers a check-in that simply worked, which is the goal. The calm at a good front door is not luck on the day. It is a short rehearsal a few days earlier, on the real kit, with the real list, doing the things that real guests will do. Twenty minutes now buys you a first minute you do not have to worry about, and a first impression you have already seen go right.
