The point of a checklist is not to remember the obvious things. You will remember the venue and the speakers and the catering on your own. The point is to catch the quiet ones: the thing that only matters at half past eight on the day, the detail that no single person owns, the assumption everyone made and nobody confirmed. Those are what turn a calm get-in into a scramble.
What follows is the shape of the list we run before every event. It is ordered by when each item is due rather than by department, because a checklist sorted by category is a checklist nobody reads in sequence. Adapt the dates to your own timeline.
Three to four weeks out: lock the foundations
This is the window where decisions are still cheap to change. Spend it confirming the things that everything else depends on.
- Confirm final capacity with the venue in writing, including the fire limit, not just the comfortable number.
- Agree the run-of-show in draft, even if details move later. A bad draft beats no draft.
- Open registration and check that the confirmation email actually lands, in an inbox you do not control, not just your own.
- Decide your check-in method now: staffed desks, self-service kiosks, or a mix. This drives how many people and how much hardware you need.
- Confirm who owns the guest list and how changes get made, so you do not end up with three versions by the day.
The single most useful habit here is to test the attendee's view, not the organiser's view. Register as a stranger would. Receive the email a stranger would. The gaps show up immediately.
A checklist sorted by deadline gets used. A checklist sorted by department gets admired and ignored.
One week out: rehearse the door
The week before is when an event stops being a plan and starts being a place. Our piece on the week before goes deeper, but the door-specific items matter most here.
- Freeze the guest list import and check it holds up: no duplicate emails, no blank names, no smart quotes turning into question marks. A list that imports cleanly is a list that scans cleanly.
- Decide how walk-ups are handled. They will arrive whether you planned for them or not, so plan for them.
- Brief whoever is on the door, even informally. Who handles a name that is not on the list, who handles a VIP, who handles a complaint.
- Charge everything. Scanners, tablets, the spare phone, the battery packs. Then label the chargers so they come home with you.
- Print or prepare badges if you are using them, and check the printer actually talks to the laptop before the morning.
The aim of this week is to remove every decision you can make in advance, so that on the day your team is executing rather than improvising.
The morning of: a calm get-in
By the time doors open, the checklist should be almost boring. If the earlier work was done, the morning is about setup and a few final checks rather than firefighting.
- Arrive early enough to fail at something and still fix it. The first thing you try will not work; budget for that.
- Set up the desk or kiosks and run a real check-in on a real record before the first guest arrives.
- Confirm the network. If the venue wifi is shaky, know your fallback before you need it; our note on scanning when the venue wifi drops covers the options.
- Position signage so the first thing a guest sees points them at the door, not at a closed cloakroom.
- Agree a single point of contact for problems, so questions flow to one calm person rather than scattering.
What the checklist quietly prevents
It helps to remember what each phase is protecting you from. The pattern is consistent across events of every size.
| When | The task | What it prevents |
|---|---|---|
| 3–4 weeks out | Confirm capacity and method | Booking the wrong room or the wrong door plan |
| 3–4 weeks out | Test the confirmation email | Guests arriving with no proof of registration |
| 1 week out | Freeze and check the import | A dirty list that fails at the scanner |
| 1 week out | Brief the door team | Decisions made badly under pressure |
| Morning of | Run a test check-in | Discovering a setup fault on the first real guest |
| Morning of | Confirm the fallback | A full stop when the wifi wavers |
None of these tasks is clever. That is the point. The events that run well are rarely the ones with the most ingenious ideas; they are the ones where the dull things were done on time.
Keep the list, then keep editing it
A checklist is only as good as the last event that taught you something. After every door closes, spend ten minutes adding the thing that caught you out and removing the item that never earned its place. Over a few events the list stops being generic advice and becomes yours, shaped by your venues, your audience and your team's habits.
We built CheckInHub partly so that several of these items, the clean import, the tested email, the fallback when the network wavers, stop being things you have to remember at all. But the discipline of the list is what makes the day calm. The tool just keeps the list shorter.
