FeaturesPricingCompareBlogContact Us
Loading...

How to Set Up QR Code Check-In for Your Event (And Why Paper Lists Are Costing You)

Anyone who's managed a door knows the 6:55pm scramble — a printed list, a Sharpie, and 80 people in line. Here's how to replace that chaos with a setup that takes five minutes and scans tickets from any phone.

The Paper List Problem

Picture the 6:55pm door. Your show starts at 7. You've got a printed guest list, a highlighter that stopped working, and 60 people waiting outside who all bought tickets online over the past three weeks. Someone inevitably says "I'm on the list" and you can't find them because they booked under their partner's name. Someone else screenshoted their confirmation email and the name doesn't match any row. And two people show up with what looks like the same reservation number because someone shared a screenshot.

Paper lists fail in predictable ways, and those failures have real costs — longer door lines, frustrated attendees, staff stress, and occasionally letting in people who shouldn't be there or turning away people who should.

3–5s
Average scan time per ticket with QR check-in
30–60s
Average time per person on a paper name list
0
Duplicate tickets that pass real-time server validation

The math is stark. At 3–5 seconds per scan versus 30–60 seconds per name lookup, QR check-in is 6–10× faster. For a 200-person show with a single door, that's the difference between a 12-minute door window and a 2-minute one — with one scanner. Two scanners working simultaneously cuts it further.

But speed isn't the only win. Unlike a paper list, QR check-in is validated against a live database. Each QR code is unique and single-use. If someone tries to scan the same ticket twice — or share a screenshot — the second scan fails immediately and flags the attempt. You can't forge a paper list either, but you also can't tell if someone shares a photo of their confirmation email.

How QR Code Check-In Actually Works

The mechanics are simpler than they look from the outside. Here's what happens under the hood:

1
Buyer purchases a ticket
The ticketing platform creates a unique order record in its database and generates a QR code tied to that specific order. The code encodes a token — a short, cryptographically signed string — not just a plain order ID.
2
Confirmation email with QR code
The buyer receives an email with their QR code attached. They can screenshot it, print it, or show it from their phone — no app download required on the buyer's side. The QR code is just an image.
3
Door staff open the check-in app
Staff open the venue's check-in app on their phone — any modern iOS or Android device works. No special scanner hardware. The app uses the phone's camera.
4
Scan → server validates → instant result
When the camera reads a QR code, the app sends the token to the ticketing server. The server checks: Does this token exist? Has it been used already? Is the event today? The response comes back in milliseconds — green for valid, red for already-scanned or invalid.
5
Attendee record marked as checked in
The database marks the ticket as used. Any subsequent scan of the same QR code will return a "already checked in" error — even if a different device scans it simultaneously. The validation is atomic at the server level.

Why this matters for fraud: the QR code contains a cryptographic token, not just an order number. You can't generate a valid token by guessing or incrementing a number. And once scanned, it can't be scanned again — on any device, by any staff member.

Setting Up QR Code Check-In in 5 Minutes

With TixHQ, the setup is genuinely short. Here's the complete process from a new account to your first scan:

1
Create your event and ticket types
Go to your TixHQ dashboard, click "New Event," fill in the details, and add your ticket types. Set capacity limits and pricing. This takes 3–5 minutes for a standard event.
2
Publish and start selling
Share your event link, embed it on your website, or both. Every buyer who completes checkout automatically receives a confirmation email with their unique QR code ticket. You don't configure this separately — it happens for every order by default.
3
Open the check-in app on the night
On event day, door staff navigate to your TixHQ check-in page from any phone. No app store download — it works in the mobile browser. Tap your event, tap "Start Check-In," and the camera activates.
4
Scan tickets as people arrive
Point the camera at each attendee's QR code. Green flash = valid and checked in. Red flash = already scanned or invalid. The attendee's name appears on screen so you can greet them by name if you want. Multiple devices can scan simultaneously — give your whole door team a phone.
5
Review attendance in real time
Your dashboard shows a live count of checked-in vs total ticket holders as the event progresses. After the show, export the full attendee CSV — including check-in timestamps — for your records.

Test it before event day. Create a test ticket for yourself, send the confirmation email to your phone, and do a practice scan. The whole process takes two minutes and eliminates 90% of door-night surprises.

What Good Check-In Software Actually Does

Not all QR check-in implementations are equal. Here's what separates a real system from a glorified spreadsheet with a camera attached:

Server-side validation
Each scan validates against the live database, not a local cache. Two devices scanning the same ticket simultaneously can't both pass — only the first one through wins.
📱
No buyer app required
Buyers show a QR code — from their email, a screenshot, or a printed page. Making buyers download an app before the door is a friction point that creates lineups.
👥
Multi-device, multi-scanner
Every door staff member can scan on their own phone simultaneously. The central database keeps everything consistent — no double-counting, no duplicate entries.
🔒
Cryptographic tokens
QR codes should encode a signed token, not just an order ID. A plain order ID in a QR code can be guessed or incremented; a signed token cannot be forged without the server's key.
📊
Real-time attendance count
A live dashboard showing checked-in vs total lets you track capacity fill rate in real time — useful for deciding when to open walk-up sales.
📤
Exportable attendance data
Post-event, you should be able to export a full CSV of who showed up, when they checked in, and which ticket type they held. This is your attendance record and marketing list.

Watch for: systems that download the full attendee list to the scanning device and check in locally. This is faster when offline but means two scanners can independently check in the same ticket — a real fraud risk at busy events. Always confirm that the check-in validation hits the server, not a local cache.

Common Check-In Mistakes (And How to Avoid Them)

Most door-night disasters are preventable. These are the mistakes venue managers make most often when switching to QR check-in for the first time:

⚠️
Not testing before event day
Buy a test ticket for yourself and scan it with the check-in app the day before. Confirm the green flash works, the attendee name appears correctly, and the second scan correctly returns a failure. Five minutes of testing prevents 90% of surprises.
⚠️
One scanner for a 300-person show
Even at 5 seconds per scan, one scanner at 300 people is 25 minutes of continuous scanning with zero pauses. Give every door staff member a phone and have them all scanning simultaneously. Most platforms support this with no additional cost.
⚠️
Relying on venue WiFi at the door
Door WiFi is notoriously unreliable — the venue's router is inside, the door is outside, and peak event load hammers the connection. Use cellular data on the scanning device instead of WiFi. 4G is plenty for QR scanning; the validation requests are tiny.
⚠️
No plan for attendees who can't find their email
Some attendees will lose their confirmation email. Your dashboard should let you search by name or email and manually check in individuals. Confirm this works before the event — you'll use it more often than you think.
⚠️
Scanning staff don't know what a red result means
A red scan result means either the ticket was already used or the QR code is invalid. Brief your staff: red means pause and flag to a manager, not automatically refuse entry — the buyer may have accidentally scanned twice on arrival, or there may be a legitimate duplicate. Escalation beats confrontation.

Frequently Asked Questions

Do attendees need to download an app to show their QR code?

No. The QR code is sent as an image in the confirmation email. Attendees show it from their email app, a screenshot, or a printout. No app download, no account creation on the buyer's side. This is a deliberate design choice — any friction at the confirmation step results in no-shows.

What happens if an attendee's phone dies at the door?

This is the most common real-world edge case. Your check-in app should let you search by name or email and manually mark someone as checked in. Pull up the admin view, search for the attendee, confirm their identity verbally, and check them in manually. It takes 15 seconds — less time than arguing.

Can attendees share a screenshot of their QR code with a friend?

They can try. If the original ticket holder scans in first, any subsequent scan of the same code fails immediately — the server marks it as used on the first successful scan. If the friend scans first, the original ticket holder gets turned away. Either way, only one person gets in per ticket. This is a feature, not a limitation — it's what makes QR check-in more fraud-resistant than paper lists.

Do I need special scanner hardware?

No. The check-in app uses the phone's built-in camera. Any modern iOS or Android device from the last five years can scan QR codes reliably in normal indoor event lighting. Dedicated scanner hardware costs more, requires charging, and offers essentially no practical advantage for venue-scale events.

What if there's no internet at the venue?

Real-time server validation requires connectivity. In practice, cellular coverage in most venues is sufficient — 4G data handles QR scan requests easily, and you don't need strong signal, just occasional data access. If you're running an event in a truly offline location (a basement, a rural site with no coverage), talk to your ticketing platform about their offline options — some support limited offline caching.

Can I have multiple ticket types on the same event?

Yes, and your check-in display should show which ticket type each attendee holds — General Admission, VIP, Press, Staff Comp. This matters at the door for access differentiation (VIP enters a different area, press needs a lanyard, etc.). Confirm your platform shows ticket type on scan results.

Set up in five minutes

QR check-in that works from any phone.

Create your event, sell tickets, and scan at the door — no hardware, no app for buyers, no per-ticket platform fee.

Get started free →

No credit card required. Zero platform fee, ever.