What is event check-in?

Check-in is the moment an expected attendee becomes a present one. Operationally it is a scan; strategically it is the first thing anybody experiences at your event.

In practice at an event

A staff member scans the code on an arriving attendee’s badge or phone, the system checks it against the guest list, and the arrivals count moves. Good implementations return “already checked in” on a repeat scan rather than an error, because a repeat scan is normal and an error message creates a queue.

The desk is also where app adoption happens. One person whose job is helping people install the app, rather than scanning, is worth more to your adoption number than any email you send.

What to look for

Ask what happens offline. Venue Wi-Fi at 08:30 with four hundred people arriving is the worst connectivity moment of the whole event.

Ask about walk-ins, because there will be some and the desk needs a path for a person who is not on the list.

And ask where the arrivals count is visible. A number only available in a report is a number nobody can act on; a live count tells you at 09:10 that a scanner is failing rather than that attendance is low.

How event67 handles it

Check-in scans an attendee’s QR badge at the door against the guest list, and a repeat scan returns “already” rather than an error. A live arrivals count runs against the guest list, visible both at the desk and as a widget in the organizer console. Every administrative action, including check-ins, is audit-logged.