Designing the Check-In Flow
A well-designed check-in flow processes 300 guests in 30 minutes without queues. A poorly designed one creates a 90-minute backlog. QR code scanning is fast — the bottleneck is usually process, not technology.
The Flow That Works
1.
Pre-event: All guests receive a QR ticket 48 hours before the event
2.
Arrival: Guest presents QR on phone or printed paper
3.
Scan: Staff member scans with tablet/phone using the event app
4.
Confirm: Screen shows green (valid) with guest name and ticket type (< 2 seconds)
5.
Wristband/badge: If applicable, issue the appropriate colour
6.
Entry: Guest proceeds
Total processing time per guest: 10–15 seconds. A single scanner lane handles 240–360 guests per hour.
Hardware for Check-In
| Scale | Recommended Hardware |
|---|---|
| < 100 guests | 1 smartphone with scanner app |
| 100–300 guests | 2 tablets, 2 staff, 2 lanes |
| 300–1,000 guests | 4–6 dedicated QR scanners, multiple lanes |
| 1,000+ guests | Professional turnstile-integrated scanners |
For large events, invest in dedicated handheld scanners (Honeywell, Zebra) — faster and more reliable than smartphone cameras in variable lighting.
Software for Check-In
-
Eventbrite Organiser App: Free, works with Eventbrite tickets
-
Ticket Tailor Box Office App: Fast, offline-capable
-
Pretix: Open-source, self-hostable
-
Zkipster: Premium events and galas — badge printing integration
-
Access Control Manager (ACM): Enterprise, multi-zone access
Multi-Zone Access
For events with VIP areas, backstage passes, and general admission, QR tickets encode the access level. Scanner apps display the zone permissions with the ticket:
- "General Admission — Main floor only"
- "VIP — Main floor + lounge + backstage"
- "Artist — All areas"
This eliminates wristband colour confusion and allows instant per-guest access modification from the management portal.
Crowd Management Data
Real-time check-in data enables crowd management:
- Current capacity by zone (prevent overcrowding)
- Arrival rate (queue length prediction)
- No-show count (real-time actual vs expected headcount)
- Early departure tracking (if exit scan is used)
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- Use the [QR size calculator](/qr-size-calculator) to match the printed size to the expected scan distance before you commit to a print run.
- The [QR size guide](/qr-size-guide) gives size recommendations for common placements.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
