Scan the attendee's badge
The badge in the app is scanned at the door — the ordinary path, and the fastest one.
Session tracking and check-in
QR check-in for individual sessions, workshops and meals — run from a link you hand to a volunteer, or by attendees scanning themselves in when nobody is on the door.
Workshop · Room 4B
AI in Practice
Why door counts are not enough
A room booked for two hundred and filled by sixty is a fact worth knowing before you book it again — and for accredited sessions, catering and capacity limits, it is a fact you are required to have.
Registrations flatter you. Scans do not. The gap between the two is the most useful figure your event produces.
Session doors are staffed by students, volunteers and whoever was free. They cannot be given dashboard accounts.
Workshops, VIP sessions and paid add-ons have rules about who is allowed in, and the door is where that gets enforced.
Plenty of sessions have no staff at all. That should mean self check-in, not no data.
How check-in runs
The badge in the app is scanned at the door — the ordinary path, and the fastest one.
A physical badge can be scanned by its printed number, so an attendee whose phone is flat still gets counted.
Manual entry exists for the case every event has, where scanning simply will not work for one person.
The session shows its own rotating code and attendees scan in from their phones, with no scanner and nobody on the door. A photograph of it stops working within about a minute.
For a room with no screen: a fixed QR for a poster by the door or a card on each table. Make several per session, label each one, and the report shows which code each person scanned. Replace one and every printed copy stops working.
Every scan records how it happened, so “nobody staffed the door, they all self-scanned” is visible in the report rather than hidden in the total.
Eligibility is checked at the point of scanning, so a session limited to certain ticket types enforces itself.
One scan per person, or repeat participation up to a limit — three coffees per pass, one shuttle each way. A scan past the limit is refused with the number, and a short repeat-scan window stops a badge held in front of the camera counting twice.
Check-ins and unique attendees side by side, when the door was busy, how people got in, which device recorded it, the ticket mix, the activity log, and an exportable list of everyone who took part.
For the organizing team
Scanning runs from shareable links that need no dashboard account, so the people on the doors never touch your console or your attendee data.
FAQ
No. Scanning runs from a shareable link, so volunteers and door staff can check attendees in without a dashboard account and without access to your event data.
Their printed badge number can be scanned instead, or the check-in can be entered manually. Both are recorded as attendance like any other scan.
Yes. A session can display its own rotating code for attendees to scan from their phones — on any screen, through a link that needs no dashboard login — which means a room with nobody on the door still produces attendance data. For a room with no screen, a printed code on a poster or table card works too.
Yes. Eligibility rules are checked when the scan happens, so a workshop limited to certain ticket types enforces itself at the door.
Yes. Every scan records how it was made, so a session everybody scanned themselves into looks different in the report from a staffed door.
It is the same engine. A tracked session can also be a passport stop, so attendance tracking and stamp collecting are configured once rather than twice.
Only if you allow it. By default it is one scan per person per session. For things that repeat — meals, coffee, a workshop that runs twice — you can allow multiple participations with an upper limit, and the report shows check-ins and unique attendees separately.
No. Tracked activities are separate from agenda sessions, so a coffee break, a booth crawl or a lunch can be tracked without appearing in the programme.
For organizers
QR check-in that volunteers can run from a link, and attendees can run themselves.