A QR code on a ticket is one of the fastest ways to move a line of guests through a door — but only when the setup behind it is sound. Maybe you have been checking people in from a printed spreadsheet, or you are switching platforms and want to get entry right the first time. Either way, this guide walks through exactly how QR code check-in works, how to set it up from scratch, and how to keep the door moving when something goes wrong. No prior experience assumed.
How QR code check-in works, end to end
The idea is simple: every ticket carries a small square barcode, and at the door a phone or tablet reads that square, confirms the ticket is real and unused, and lets the guest in. What makes it reliable is what happens between those two moments.
When someone registers or buys a ticket, your platform generates a code that is unique to that specific ticket and attaches it to the confirmation — usually an email, a PDF, or a pass saved to a phone wallet. On event day, a scanning app reads the code, matches it against your live guest list, and instantly shows whether the ticket is valid. If it is, the app marks that ticket as used so it cannot pass again.
What is actually inside the code
A ticket QR code is not a photo of your guest or a link to their personal details. It typically encodes a unique reference — a string of characters that is meaningless on its own and only becomes useful when your scanner app looks it up against the record in your event. That is why a screenshot of a ticket still scans, and also why a well-built system can still tell a genuine ticket from a copied one, as we will cover below.
Why a unique code beats a generic image
It is tempting to make one QR code — say, a link to your registration page — and print it on everything. That is fine for promotion, but it is not check-in. A single shared image cannot tell one attendee from another, cannot be marked as used, and cannot stop the same code from walking through the door fifty times. Real check-in depends on every ticket carrying its own distinct code. If you want the mechanics of how those codes are generated and added to tickets, see our guide to creating QR codes for event tickets.
How to set up QR code check-in, step by step
You can have working QR entry in an afternoon. The four steps below assume you are using an event platform that issues tickets; if you are assembling this from separate tools, the same logic applies, it is just more manual.
Step 1 — Issue tickets that already carry a unique code
Most registration platforms, Everlage included, generate a unique QR code for every ticket automatically and deliver it in the confirmation email. There is nothing to design by hand. Before your event, send yourself a test registration and confirm the code arrives and looks scannable on a phone screen.
Step 2 — Put a scanning app on your door devices
Any reasonably modern phone or tablet can be a scanner — you do not need dedicated hardware for most events. Install your platform's scanning app on each device that will work the door. Everlage's scanner app, for example, validates each QR ticket against your guest list so a staffer only has to point the camera and read the result.
Step 3 — Load the right event and sync your guest list
Sign in on each device, select the correct event, and let the app pull down the current guest list. Do this a little ahead of time rather than at the door, and make sure every device is signed in to the same event so they all update the same list.
Step 4 — Test before doors open
Scan your own test ticket on every device. Confirm you see a clear valid result, then scan the same ticket again and confirm you get a duplicate warning. This thirty-second check catches the two things most likely to embarrass you at the door: a device on the wrong event, and a guest list that has not finished syncing.
Your door-day workflow and staffing
Scanning is fast, but a door is only as fast as its slowest step. Decide in advance how many scanning lanes you will run and put clear signage above each one. As a rough guide, add a lane whenever the line starts forming faster than a single scanner can clear it — a greeter watching the queue can open or close lanes on the fly.
Give each lane a simple script: greet, scan, glance at the result, wave the guest through or step them aside. Anything that needs a conversation — a name that is not on the list, a refund question, a group that got separated — should move to a side table so it never blocks the main flow. Keep will-call, walk-ins, and door sales at their own station rather than mixing them into the scan lanes. For the broader playbook on line math and event-day operations, see our pillar on event check-in best practices.
Offline fallbacks — what to do when the Wi-Fi dies
Venue connectivity fails more often than anyone plans for: basements, marquees, old buildings, and rooms full of people all conspire against a signal. Your check-in should not depend on a perfect connection.
The usual defense is a scanner app that caches the guest list on the device, so it can keep validating tickets from local data and sync the results once the connection returns. Because offline behavior — and especially how multiple devices avoid letting the same ticket in twice while disconnected — varies between platforms, confirm exactly how your tool handles it before the day rather than discovering the limits at the door. It is also worth keeping a low-tech backup: an exported guest list you can search on a phone, or a printed copy for the worst case. We go deeper on this in how offline event check-in works.
Security — preventing duplicate and copied-code scans
The most common worry with QR tickets is people forwarding or screenshotting them. Here is the reassuring part: because each ticket carries its own unique code and the system marks it used on the first valid scan, the second person to present that code gets flagged. The image copied perfectly; the entitlement did not.
Practically, that means your staff should trust the result on the screen, not the paper or phone the guest is holding. A duplicate warning is doing its job — the fix is a quick, calm conversation, not waving the guest through because the ticket “looks fine.” Legitimate transfers should be handled inside your platform (reissuing the ticket to the new attendee) rather than by forwarding an email, so the code stays valid for exactly one person. Anti-fraud specifics differ between tools, so confirm how your platform handles single-use validation and transfers, and brief your door team on what a warning means before they are standing in front of a queue.
Troubleshooting quick reference
- Code will not scan: ask the guest to raise screen brightness and hold the phone still; a cracked or very dim screen is the usual culprit.
- “Already used” on a valid guest: check whether they were scanned at another lane, or whether a group forwarded one ticket to several people — verify against the name on the record.
- “Not found” or wrong event: confirm the device is signed in to the correct event and the guest list has finished syncing.
- No signal: switch to your offline mode or cached list and keep scanning; reconcile when the connection returns.
- Slow line at one lane: pull conversations to a side table and, if needed, open another lane.
FAQ
Do guests need to print their tickets?
No. A QR code on a phone screen scans just as well as a printed one — most guests will simply open the confirmation email or a wallet pass. Printing is a fallback, not a requirement.
Do QR tickets work without internet at the venue?
They can, if your scanning app supports an offline mode that caches the guest list on the device. Because the details vary, confirm your platform's offline behavior before the event and keep an exported list as a backup.
Can someone get in with a screenshot of a ticket?
A screenshot will scan, but the code is single-use: once the genuine ticket has been checked in, any second attempt with the same code is flagged. Unique, single-use codes are what make screenshots harmless.
How many scanning devices do I need?
Enough to keep the line moving without a queue building faster than you can clear it. Many small events run on one or two devices; add lanes as your expected arrival rate grows, and keep a spare charged device on hand.
What if a guest cannot find their QR code?
Look them up by name on the guest list and check them in manually — a good scanner app lets you do this without the code. Keep this at a side station so it does not slow the main lanes.
QR code check-in rewards a little preparation: unique codes on every ticket, a tested app on each device, a couple of clear lanes, and a plan for when the signal drops. Get those right and entry becomes the calmest part of your event. When you are ready to try it, the Everlage scanner app validates QR tickets out of the box — and our check-in best practices guide covers everything around the scan itself.
