Make ticket scanning quick at a crowded door
A QR code on an event ticket lets door staff scan each guest in seconds, whether the ticket is printed or shown on a phone. The code carries the ticket's unique reference, so entry is a scan and a nod rather than a name checked against a list.
What trips people up on the night is not the code itself but the phone showing it: dim screens, auto-rotation and low-resolution screenshots stall the queue. Getting the code and the guest instructions right beforehand is what keeps the door moving.
One code per ticket, never shared
Each ticket must carry its own unique code tied to a single reference. If two guests hold the same code, the second to arrive gets turned away or, worse, both get in and your count is wrong. Generate a distinct code per ticket and let your door system mark each as used on first scan.
Treat the code as the ticket. Anyone who forwards a screenshot has effectively forwarded their entry, so guests need to know it is single-use.
- Unique reference behind every single code.
- Mark it used at first scan so it cannot re-enter.
- Tell guests the code is single-use and not to share it.
Screen brightness and screenshots at the gate
Phones auto-dim to save battery, and a dim screen behind a scratched protector is the number-one reason a ticket won't scan. Tell guests to turn brightness to full and disable auto-lock as they approach the door.
A screenshot usually scans fine, but a screenshot of a screenshot, or one cropped too tight with no quiet margin, does not. Ask guests to keep the whole ticket visible rather than pinching in on the code.
Printed tickets versus phone tickets
Printed tickets sidestep the brightness problem entirely and scan under any light, but they get folded through the code. Advise guests not to crease across the pattern. Phone tickets are convenient and impossible to leave at home, but depend on a charged, bright screen. Supporting both, and telling each group how to present the code, gives the door the fewest failures.
Keeping the queue moving
Scan speed comes from a code large enough to catch quickly — aim for 3 cm square or more on a printed ticket — and door staff who know to ask for full brightness before they even raise the scanner. A short briefing beats any technical tweak for throughput on a busy door.
How to set up ticket codes
- Give each ticket a unique reference. Encode a distinct code per ticket so no two guests can enter on the same scan.
- Print or size it for fast reading. At least 3 cm square with a quiet margin so a handheld scanner locks on instantly.
- Brief guests on brightness. Tell phone-ticket holders to set full brightness and stop auto-lock before they reach the door.
- Mark codes used on scan. Have the door system flag each code as spent. The common mistake is allowing a forwarded screenshot to walk in twice.
Technical details
- Maximum characters: 2953
- Recommended error correction: Q (quartile) recommended for tickets shown on screens and folded in pockets, so a scratched screen or a crease across the code still reads.
- The event/reference code is short by nature, which keeps density low and helps fast scanning at the door.
- Higher error correction is especially worth it on phone tickets, where glare and scratches routinely obscure part of the pattern.
Frequently asked questions
- Why won't my ticket scan on my phone?
- Almost always screen brightness. Set brightness to maximum and turn off auto-lock so the screen stays lit while staff scan. A scratched screen protector or a heavily cropped screenshot with no white margin around the code makes it worse.
- Can two people use the same ticket code?
- No, if it is set up correctly. Each ticket should carry a unique code that the door system marks as used on first scan. The second person presenting the same code is refused, which is exactly what stops screenshot sharing.
- Do screenshots of tickets work at the door?
- Usually yes, a clean screenshot scans fine. It fails when it is a screenshot of a screenshot, or cropped so tight the quiet margin is gone. Keep the whole ticket in frame rather than zooming into the code.
- Should I print the ticket or use my phone?
- Either works. Printed tickets scan under any lighting and never run out of battery, but keep the fold away from the code. Phone tickets can't be left at home but need a charged, bright screen. Bring the printed one if your battery is low.
- How big should the code be on a printed ticket?
- At least 3 cm square with a clear margin. Bigger reads faster on a busy door, where staff scan under harsh entrance lighting and want the scanner to lock on without the guest repositioning the ticket.
- What if the door has no internet to validate scans?
- Use a door system that validates offline or caches the guest list locally. Many venues have poor signal at the entrance, and a scanner that needs a live connection per scan will stall the queue the moment reception drops.