- One unique QR code per ticket is the whole anti-fraud system โ duplicates are caught at the first duplicate scan.
- Offline check-in lists keep doors moving when venue Wi-Fi collapses under crowd load.
- Bigger codes with error correction level Q or H survive cracked screens and folded printouts.
- Rehearse the door: refunds, transfers and dead phone batteries are process problems, not scanning problems.
The Door Entry Nightmare: Long Lines and Duplicate Tickets
Whether you're managing a 300-person tech workshop or a 10,000-attendee music festival, the entry gate is the most vulnerable operational friction point. Slow check-ins create restless crowds, safety hazards, and negative brand impressions before the event even kicks off.
Compounding this challenge is the menace of ticket duplication and scalping. When attendees purchase non-verified tickets or attempt to pass screenshots to multiple friends, conventional barcode readers fail to provide cryptographic proof of authenticity.
Offline Reliability: Surviving the 'Cellular Blackout' at Large Venues
The single greatest operational mistake event organizers make is relying on real-time internet connectivity for ticket scanning. When thousands of attendees assemble inside a concrete convention hall or stadium, local cell towers saturate, causing 4G and 5G connections to collapse completely.
By using digitally signed QR codes (such as Ed25519 or JWT tokens encoded into static text QR codes), scanning handhelds can mathematically verify ticket authenticity against a pre-loaded local SQLite database completely offline. Zero network ping, zero waiting, and lightning-fast 0.4-second check-ins per person.
Optimal Error Correction: Designing for Cracked Screens & Crumpled Paper
In live event environments, QR codes rarely encounter ideal scanning conditions. Attendees present tickets on scratched smartphone glass, under glaring sunlight, with phone battery saving modes dimming screens, or on crumpled wristbands.
Always generate event ticketing QR codes with Error Correction Level H (30%). Level H allows the scanner algorithm to reconstruct the entire payload even if nearly a third of the QR surface area is smudged, torn, or obscured by finger thumbs.
Related Technical Guides
Access control beyond the front door
The same unique-ID system that admits guests can organise everything inside the venue. Issue each ticket a tier โ general, VIP, staff, vendor โ encoded in the ID itself, and door staff can route people without a second document. Backstage passes, meal vouchers and workshop seats all become check-off lists keyed to the same IDs, and because a text-based code works offline, a barn, beach or basement venue is no obstacle. Generate each batch in the free text QR code generator, keep the master list in a spreadsheet, and mark IDs as they are used. For the door workflow in full, read the companion QR code event ticketing system guide.
Designing tickets that survive the night
Tickets get folded, photographed, rained on and screenshotted under stage lights, so design for abuse. Print the code at 2.5 cm or larger with error correction H and your event logo in the centre โ branding is also security, because a copied screenshot is easier to spot against an official design. Keep the quiet zone empty, avoid glossy stock where you can, and put the human-readable ticket ID under the code so staff can type it when a screen is cracked or a print is smeared. Send digital tickets as PNG files rather than photos of screens, and remind buyers that the first scan wins: once an ID is checked in, later copies of the same code are politely refused.
The bottom line: access control is not the code โ it is the discipline of one unique ID per guest, checked off exactly once, on tickets built to survive real pockets and real lighting.
Refunds, transfers and the human edge cases
Real events generate exceptions: a guest who bought two tickets and arrives separately from their friend, a refunded ticket still circulating in an inbox, a name that must move from one attendee to another. A unique-ID system handles all three calmly โ the master list is simply edited: mark the refunded ID void, split a pair into two IDs, annotate the transfer. Problems only start when the list and the door drift apart, so sync the list at set times and make one person its owner. Announce the policy in the ticket email ("entry is by first scan of your unique code") and most edge cases resolve themselves before they reach the door, leaving staff free to welcome people instead of interrogating them. Keep one printed copy of the final list at every gate as the tie-breaker of last resort when devices fail, batteries die or two lists disagree in the middle of the entry rush.
Sizing, lighting and layout: the physical side of fast check-in
Door speed is set by physics before it is set by software. A ticket QR code displayed on a phone should be at least 3.5 cm wide on screen; printed wristband and badge codes need the same plus a full quiet zone, because lanyards curl and paper creases. Error correction level Q is the floor for badges that will be scanned hundreds of times in mixed light, and level H earns its keep outdoors where glare fights the scanner. Place door scanners so the guest presents the code in shade where possible, and keep one printed test ticket at every lane: if the test ticket scans, the lane works, and staff can blame the ticket instead of the system with confidence.
For the event page itself, a calendar event QR code on posters and emails lets guests add the event โ with venue, date and reminders โ to their phone calendar in one scan, which measurably cuts no-shows before door operations even begin.
Staffing the exceptions desk, not just the scanners
Every event generates the same handful of human edge cases: the transferred ticket still showing the buyer's name, the screenshot of a screenshot, the dead battery, the refund that was re-sold by mistake. Events that handle these well put one empowered person at an exceptions desk away from the lanes, with the full attendee list, a charger, and the authority to say yes. Events that handle them badly let each case block a lane while a queue forms and tempers rise.
- Export the attendee list (name, ticket ID, tier) to every door device before doors open
- Give the exceptions desk the refund and transfer log, not just the sales list
- Decide the screenshot policy in advance and print it on the ticket
- Log every manual entry โ those logs are next year's door plan
Frequently asked questions
How do I stop one ticket screenshot being shared with friends?
You cannot stop the sharing, but you can make it useless: each ticket carries a unique ID that is admitted once and then marked used, so copies arriving later are refused.
Can staff tickets and guest tickets use the same system?
Yes. Encode the tier inside the ID (for example STAFF-012 or VIP-104) and keep one master list โ the door process stays identical for every category.
What size should an event ticket QR code be?
At least 2.5 cm wide for arm's-length scanning in queues, with error correction H and a clear quiet zone so damaged or glossy tickets still read.
How do QR tickets stop people sharing one ticket with friends?
Each ticket carries a unique code and the check-in system marks it used at the first scan. A forwarded copy scans as already-redeemed, so only the first person through the door gets in.
What size should a QR code be on an event badge?
At least 3.5 to 4 cm wide with a clear quiet zone, printed at error correction level Q or H. Badges get scanned at angles, in motion and in poor light, so generous size is cheap insurance.