The Cvent OnArrival check-in checklist that prevents event-day chaos

Onsite check-in is the most visible part of your event — it’s the first thing every attendee experiences, and the first thing that goes wrong in front of an audience. The good news: almost every check-in disaster is preventable, and almost none of them are actually solved on event day. They’re solved in the two weeks before.

Here’s the checklist we run for every Cvent OnArrival deployment.

Two to three weeks out

• Confirm your check-in model. Self-service kiosks, staffed stations, or a hybrid? This drives hardware counts, layout and staffing. The free Onsite Check-in Calculator gives you a first estimate of stations, staff and printers for your peak arrival window.
• Lock the badge design. Sizes, stock, what data prints, QR/barcode for scanning, and any sponsor or track colour-coding. Print a physical proof — screens lie about scale. If you’re putting the QR code in brand colours (the Badge Designer supports custom colours and transparent backgrounds), heed its contrast warning and test-scan the printed proof.
• Decide your data source of truth. Registration list freezes, walk-in policy, and how last-minute changes sync to the onsite app.

One week out

• Test badge printing end to end on the actual printers and stock you’ll use onsite, not a lookalike.
• Running an Essentials event? As of October 2026, OnArrival prints badges from Android as well as iOS, using the badge layout you already built in the event. Set the printer under Settings → Printer Settings on each Android device.
• Configure session scanning if you’re tracking attendance or CEUs, and confirm the scanners are enrolled.
• Set up LeadCapture for exhibitors if applicable, and brief them on how it works.
• Build the walk-in / on-site registration flow so day-of additions don’t require a laptop and a prayer.

The day before

• Stage and label hardware by station. Chargers, spares, and a known-good backup for every critical device.
• Do a full dress rehearsal — register a fake attendee, check them in, print the badge, scan into a session. Every step, in order.
• Brief the staff on the three or four things that actually go wrong: name mismatches, duplicate registrations, and the “I’m not on the list” conversation.

Event day

• Open early and watch the first 30 minutes. That’s when you catch the issue that will otherwise repeat 500 times.
• Keep one person on data, not lines. Someone needs to own duplicates, corrections and edge cases so the queue keeps moving.

The teams that have calm check-ins aren’t lucky. They front-loaded the decisions.

Where a build partner helps

If your team only runs a few events a year, it’s genuinely hard to keep this muscle memory sharp. That’s exactly the kind of thing a build partner carries for you — the checklist, the dress rehearsal, and the hands on-site.

Want this configured and rehearsed for you? See our Cvent OnArrival check-in and badge service, or talk to us. The pre-event launch checklist covers the rest of the run-up.