The day before the event is not when you change the concept — it is when you verify that everything you arranged actually works. Go through five areas: communication, attendee data, equipment at the entrance, badges, and the people who will handle check-in. Adjust the scope and time of the check to the different attendee journeys, devices, and people handling check-in.
Block out time for this check the day before, not on the morning of the event. By the morning there is no room to fix things — you cannot source a printer, staff accounts cannot be enabled, and a sent e-mail cannot be taken back.
Did the logistics e-mail reach registered attendees? Check in the campaign detail that the mailing went out and how many e-mails were not delivered. For undelivered messages, check the available reason and the specific case. The count alone neither proves bad addresses nor rules out another cause.
Is the morning campaign ready? If you plan to send an e-mail with the QR ticket in the morning, the campaign has to be written and scheduled now.
Do both language versions match? On a bilingual event, open both versions of every prepared message. An empty second version is the most common mistake, and nobody has time to fix it on the day.
Did you send yourself a test? Send the campaign scheduled for the morning to your own address first and open it on a phone.
How many people are registered versus merely invited? The gap identifies contacts without completed registration; it does not predict how many will arrive. Invited people without a registration have no QR code.
Does everyone have an e-mail address? A contact without one gets no ticket and will have to be handled by hand on site.
Are the groups right? If you control VIP access or gift handout by group, check the group counts. Filling them in on the morning is too late.
Do you know who needs special handling? Speakers, VIP guests, companions — go through them by name and verify they are in the right groups.
Do the staff accounts work? Have every member of the event staff sign in to the Service app today.
Is the app installed on the devices that will actually be on site?
Are the check-in places set up with types matching the layout of the event?
Has a test scan been done? Register a test account and walk the whole path from the Confirmation e-mail to the scan.
Is everything that runs on a battery charged — phones, tablets, the printer, power banks.
Did you print a test badge? Verify that the longest name and company in your data fit on the label.
Do you have enough labels and a spare roll? Changing a roll mid-queue goes badly.
Do you know who prints? Decide whether badges are printed on demand at check-in or in advance.
Test a regular QR arrival and separately cover a missing registration, an incorrect group, or a correction of attendee details where relevant. The procedures are in How to fix things after the fact.
Use the devices and staff access that will actually be on site. A successful admin check does not establish that the Service app works for the operator.
Check what a scan actually records at your event. Only a place of type Check-in sets the Checked-in status; Recurring check and One-time check serve a zone, a shuttle bus, or a gift pickup, the scan counts toward that place, and the attendee status does not change. With several entrances, make sure each operator has selected their own place and its type.
If you print badges in advance, keep in mind that attendance is created by the scan at the entrance, not by printing. A scan between attendees in Networking is a different thing: it saves a contact and has nothing to do with attendance, so do not look there for who arrived.
Size the check-in places for the expected arrival peak, the measured flow, and exception handling; the total number of guests is not enough.
Record who makes decisions when a problem occurs and how staff hand over a question they cannot resolve.
Does everyone know where they stand and what they do? Assign a specific check-in place to a specific person.
Does someone have admin access? A laptop with the web Check-in tool is useful at the entrance — it is the only place where you can resend a ticket, show the QR code on screen, or generate a one-time password for the app.
Do you have a fallback? Agree in advance what happens if the Wi-Fi drops, the labels run out, or the printer jams.
In the morning you will find the problem but have neither the time nor the means to fix it. Customer success enables staff accounts, a rental printer will not arrive within the hour, and a sent e-mail cannot be recalled. The day before, all of those options are still open.
The most common source of chaos at the entrance is not the devices but the data and the people: guests who have not registered and have no QR code, missing e-mail addresses, nobody knowing who is stationed where. Staff can work around a device problem; they cannot work around disorientation.
An eyeball check in the admin does not show what the attendee sees. Walk the path for real — registration, Confirmation e-mail, QR code on a phone, scan in the app. Include paths with different permissions or devices, and leave time for corrections and a retest.
