Event day is calm or chaotic depending almost entirely on decisions made in the seven days before it. By the time the doors open, the room for fixing anything has shrunk to almost nothing, so the final week is really about closing decisions down rather than opening new ones. The teams who arrive relaxed on the morning are not the ones who worked hardest on the day. They are the ones who locked the right things down in the right order during the week before, so that nothing was left to invent under pressure.
The trick is knowing what to freeze and when. Lock things too early and you cannot absorb the inevitable late changes. Lock them too late and you are making decisions at the worst possible time, surrounded by guests.
Seven days out: freeze the shape
A week before, the shape of the event should stop moving. Not the details, the shape: the run of show, the room layout, the crew roster, the headline timings. These are the load-bearing decisions, and every day they stay open is a day someone might quietly change them in a way that ripples through everything else.
This is the moment to write down the plan in a form other people can read, not keep it in your head. A clear run of show that the whole team shares is the document everything else hangs from, and a realistic run-of-show for event day is worth building properly now rather than scribbling on the morning. If the shape is still arguable a week out, the week will be spent arguing rather than preparing.
Freeze the shape early so the week is spent preparing, not deciding.
Five days out: lock the list
This is the point at which the guest list should become the guest list. There will be late additions and you can handle them, but the bulk of the data should be clean, final and imported by now, not arriving in fragments over the final weekend.
A clean list five days out gives you time to catch the problems that always hide in real data: the duplicates, the malformed emails, the rows that do not quite make sense. Fixing those calmly midweek is trivial. Fixing them at the door is a queue. The work of importing a guest list that actually holds up belongs to this part of the week, with enough runway that a surprise in the data is an inconvenience rather than a crisis.
Once the list is clean, this is also when passes go out. Sending QR passes a few days before, from an address that looks like you rather than a shared noreply, means guests arrive with their code ready and the door moves faster for it.
Three days out: confirm the kit and the crew
With the plan frozen and the list clean, the back half of the week is about confirming that the things you are relying on actually exist and work. This is the point to physically check the equipment rather than assume it.
A short, honest list for this stage:
- Every device that needs to scan can scan, charged and tested, not just present.
- The connection plan is real, with a mobile data backup for when venue wifi drops.
- Every member of crew has confirmed, knows their role, and knows when to arrive.
- The kit list is checked against the actual bags, not against last year's memory.
- Someone has tested the full check-in flow end to end, as a guest would experience it.
That last item is the one most often skipped and most often regretted. Walking through the entire arrival yourself, the way a guest will, surfaces the small breakages, the sign that points the wrong way, the step that confuses, while there is still time to fix them. The fuller version of this lives in the pre-event checklist we run every time, and it is genuinely the cheapest insurance an event can buy.
One day out: brief and rest
The day before is not for new work. It is for briefing the people and then stopping. A crew that arrives on the morning already knowing the plan, the layout and their role is a crew that does not need micromanaging when the queue forms. The briefing should be short, concrete, and cover the things that go wrong: the VIP process, the latecomer process, who to find when something breaks.
Then, genuinely, rest. The single most underrated piece of event preparation is a team that slept. A well-prepared event run by exhausted people still goes worse than it should, because tiredness is where the small errors and the short tempers come from. If the week has been spent locking things down in order, the night before should be quiet, and that quiet is the reward for the work.
What "locked down" actually buys you
The point of all this freezing is not control for its own sake. It is that a decision made calmly in advance is almost always better than the same decision made under pressure with guests watching. Every thing you lock down in the week before is one fewer thing to invent on the day, and event day has a hard ceiling on how much inventing anyone can do well.
CheckInHub carries the parts of this that benefit most from being settled early: a clean imported list, passes sent ahead from your own address, a check-in flow you can test before anyone arrives, and a count that is live and trustworthy from the first scan. The platform does not run the week for you. But it does mean that when you lock the list down on the Wednesday, it stays locked, tested and ready, so the Monday morning feels less like a deadline and more like an arrival you have already rehearsed.
