QR code badges and phone check-in
On the day, at the door: the team scans the badge with a phone, the name appears, and the list of who has arrived updates on every station.
What it does
A browser and the phone’s camera are all you need. Nothing to install on the team’s phones.
- Badge scanning on a phone, with no app to install; the badge can be printed on arrival.
- A live list: what one desk checks in appears on the others.
- Workshop attendance session by session, separate from entry to the event.
- A “Front desk” role that checks people in and cannot change anything else: a temp hired for the day has no access to pages or the programme, and you can hide statistics from them.
- Badge designs drawn on a free canvas, categories assigned by rules, and printing in batches, at the front desk or at a self-service kiosk.
- A certificate of attendance for everyone who came, listing the workshops attended, delivered by link and by email; its QR code makes it verifiable.
What it does not do
Check-in happens online, on purpose.
- No offline mode. Two phones checking in the same person without a network would create a conflict that no rule settles cleanly; we would rather require a connection and say so.
- No hardware badge reader: scanning uses the device camera. To print without a dialogue box, at the desk or the kiosk, the machine must run Chrome in kiosk mode.
Frequently asked questions
- Is an app required?
- No. Check-in is a web page; it asks for camera access, like any online scanner.
- What if the network drops?
- Check-in stops, and says so. That is a deliberate decision: offline check-in reconciled afterwards produces duplicates you discover too late.
- Can someone scan without access to the rest?
- Largely, yes: the “front desk” role checks people in and looks up participants without changing anything. You can also remove its access to statistics and limit it to a single event.