Every organizer knows the failure mode: a queue out the door while volunteers hunt for names on a printed list. An event check-in system fixes that — and QR codes plus a phone are usually enough to build one.
A QR code event check-in system pairs unique codes on tickets or badges with a scanner at the door: each attendee's code is scanned and matched against your guest list. For small and mid-sized events, a free batch-scanning app plus a simple attendee list covers check-in without paying for an event platform.
This guide covers the whole setup: how QR check-in works, how to build a free flow with QRBot, and where a lightweight system stops being enough.
How Does QR Code Event Check-In Work From Ticket to Door?
QR code check-in has three moving parts: a unique code per attendee, a scanner at the entrance, and a list to match scans against. Before the event, every ticket or badge gets its own code — usually a short ID or ticket number encoded as a QR code. At the door, staff scan each code as attendees arrive; each scan is logged with a timestamp and matched against the attendee list to confirm the person was registered and mark them present. That is the entire system. Everything else — ticketing platforms, badge printers, turnstiles — is layered on top of the same loop: code on ticket, scan at door, match against list.
The difference between systems is where matching happens: platforms check each scan against a live database instantly; a lightweight setup logs scans on the phone and matches them on the spot or afterwards. For a 150-person workshop, lightweight is usually all you need.
How Do You Set Up a Free QR Code Check-In Flow Step by Step?
A free check-in flow takes about an hour to set up: export your attendee list to a spreadsheet, give every attendee a unique code, send or print those codes, then scan them at the door with a batch-scanning app and reconcile the scan log with your list afterwards. There is no platform subscription, no per-ticket fee, and no account for you or your attendees to create. The approach works whether your registrations come from a form tool, an email RSVP thread, or a ticketing service you only use for sign-ups — as long as each person ends up with a unique code, the door process is the same. Here is the full sequence.
- Start with your attendee list. Export registrations to a spreadsheet with one row per person and a unique ID column — a ticket number or just a sequential number.
- Generate one QR code per attendee. Encode each person's ID as a QR code, or reuse the codes your registration tool already puts on tickets.
- Deliver the codes. Email each attendee their code, or print it on their badge or ticket, at least a day early.
- Scan at the door. Open QRBot in batch mode and scan each arriving attendee. Every scan lands in the searchable history with a timestamp — that history is your check-in log. QRBot is free on iOS and Android, no account needed.
- Reconcile after the rush. Review the scan history and mark scanned IDs as "attended" in your spreadsheet.
Be honest about step five: the matching is manual. A scanner records who was scanned; it does not update your spreadsheet. For a few hundred attendees that takes minutes — the trade-off that makes the flow free.
Why Does Batch Scanning Matter at the Door?
Batch mode is the difference between a check-in line that moves and one that stalls. A standard scanner app treats every scan as a one-off: scan, show result, tap to dismiss, point at the next code. At an entrance, those taps are dead time repeated hundreds of times. Batch mode removes them — the scanner stays live continuously, logging each code the moment it locks on, so the workflow becomes scan, next person, scan, next person, with the phone never leaving scanning mode. Over a few hundred attendees, saving even a couple of seconds per person is the difference between a line that clears in minutes and a lobby full of people missing the opening session.
QRBot's batch mode works exactly this way: continuous scanning, no tapping between attendees, each code saved straight to history. For a deeper look, see our guide to QR code batch scanning; if you are still comparing tools, our best QR code scanner apps roundup covers what to look for in a door scanner.
Can QR Code Check-In Work Without Internet?
Yes — and this matters more than most organizers expect, because event venues are exactly where connectivity fails. Basement conference rooms, metal-clad exhibition halls, rural wedding venues, and any space where a thousand phones hit the same cell tower at once are all hostile to a check-in system that phones home on every scan. A cloud-dependent scanner that needs to validate each ticket against a server will hang precisely when the line is longest. An offline-capable scanner sidesteps the problem entirely: reading a QR code is pure camera work, so nothing about the scan itself requires a connection.
QRBot scans fully offline: codes are read and written to the local scan history with no network involved, so a dead spot at the venue never slows the line. The trade-off is that offline scanning means offline records — matching scans against your master list happens on the device or after the fact, not live on a server.
How Do You Handle Multiple Entrances or Several Staff Members?
The simple approach: put a phone running the scanner at each entrance, have every phone scan continuously, and merge the scan histories after the event. Each device keeps its own local log, so with three doors you end up with three check-in lists that together cover everyone who arrived — combine them in your spreadsheet, drop any duplicates, and you have the full attendance record. To keep the door experience clean, assign each entrance a segment of the guest list, split alphabetically or by ticket type, so staff can answer "am I on the list?" questions from their own subset without radioing another door.
Be clear about the limitation: separate phones do not sync in real time. If someone is scanned at door A and walks to door B, door B's phone has no way to know. For most meetups and conferences that is a non-issue — but if live cross-gate awareness genuinely matters, that is a platform feature, covered below.
How Should You Design Badges and Tickets So Codes Scan Fast?
A check-in line is only as fast as its slowest scan, and slow scans are almost always a design problem, not a scanner problem. The rules are simple: print codes at least 2 x 2 cm (larger if staff will scan from any distance), use dark modules on a light background with strong contrast, and leave a clear quiet zone — empty margin — around the code. Avoid glossy laminate that throws glare under venue lighting, never print a code across a fold or crease, and keep heavy logo overlays and decorative styling away from door codes. A stylized code that scans in two seconds instead of half a second costs you that difference hundreds of times over.
Check-in codes carry only a short ID, so they stay low-density — forgiving to print and fast to lock onto. If you want branded codes that still scan reliably, our custom QR code design guide covers how far styling can go. Always test at final print size, under similar lighting, with the phones your staff will hold.
When Do You Need a Real Ticketing Platform Instead?
A scanner-plus-spreadsheet system covers the door; it does not cover the business of ticketing. You need a proper platform when money and fraud enter the picture: paid tickets require payment processing, refunds, and receipts, none of which a scanner app should touch. You need one when duplicate codes are a real threat — if tickets are resold or screenshots get shared, only a system where every gate validates against the same live database can reject a copied code the second time it appears. And you need one when live synchronization matters: real-time attendance dashboards, cross-entrance deduplication, or capacity limits enforced at the moment of scan all require a synced backend that standalone phones cannot provide.
QRBot deliberately does not pretend to be that platform. It covers the door-scanning side — batch scanning, offline capability, a searchable log — while registration lives in a spreadsheet, form tool, or ticketing service. Free community events, workshops, and private functions rarely need more; paid events with fraud exposure usually do.
How Do You Protect Attendee Privacy in a QR Check-In System?
The rule is simple: put the minimum possible data inside the code. A check-in QR code needs to identify a registration, nothing more — so encode an opaque ID like a ticket number, and keep names, emails, and phone numbers in your attendee list, not in the code itself. Anything printed in a QR code is readable by any scanner, including an attendee's own phone and any camera that photographs a badge, so a code containing personal details is effectively a public record of them. An opaque ID leaks nothing: without your list, "REG-0417" means nothing to anyone.
This design also keeps your tooling honest: the scan history on the door phone then contains only IDs and timestamps — useful to you, useless to anyone else. Delete the logs and shared spreadsheet copies once attendance is recorded, and your check-in system leaves almost no personal data trail.
Frequently Asked Questions
How do I check people in with QR codes for free?
Export your attendee list to a spreadsheet, give each attendee a unique QR code (or reuse the codes on their tickets), and scan arrivals with a free batch-scanning app. QRBot does the scanning side at no cost on iOS and Android, no account required: batch mode logs each attendee without tapping between scans, and the searchable history becomes your check-in record. Afterwards, match the scanned IDs against your spreadsheet — that reconciliation is the only manual step, and the trade for skipping platform fees.
Can QR check-in work without internet?
Yes. Scanning a QR code is a camera operation, so an offline-capable scanner like QRBot reads codes and saves them to its local history with no connection at all — useful in basements, exhibition halls, and venues with overloaded networks. What offline scanning cannot do is validate tickets against a live server or sync between devices. Your scan log stays complete and timestamped on the phone; checking it against the master list happens on the device or after the event rather than in the cloud.
How do events prevent duplicate ticket scans?
It depends on the system. A synced ticketing platform checks every scan against a central database, so an already-used code is rejected instantly at any gate — the only way to get live deduplication. An offline scanner logs every scan, duplicates included, so a copied code shows up as two entries for the same ID in the history: you catch it in after-the-fact review rather than at the door. For free and low-stakes events that is normally sufficient; for paid tickets with real fraud incentive, live dedupe is worth paying for.
What should an event QR code contain?
As little as possible: a unique, opaque identifier such as a ticket number or registration ID, and nothing else. Short content keeps the code low-density, so it prints cleanly at small sizes and scans faster at the door. It also protects attendees — anything encoded in a QR code can be read by any camera, so names, emails, and phone numbers belong in your attendee list, not in the code. The ID links a scan to a row in that list, and that link is all check-in requires.
Ready to run the door at your next event? Download QRBot free for iOS and Android — batch scanning, offline support, and a searchable scan history, with no account and no per-ticket fees.
