QR Codes for Events
At events, a QR code is a throughput device. The 20 seconds between a guest reaching the check-in table and walking through the door is queuing-theory math: arrival rate, service time, number of scanner stations. A QR that scans reliably in half a second on the first attempt is the difference between a 3-minute queue and a 20-minute queue at 8:30am when 400 people show up at once. Sizing, placement, and error correction are downstream of the throughput decision. This guide works the problem from queue physics backward to QR design.
An event queue is a queuing-theory problem. The QR is a throughput lever.
Most event-planning content treats QRs as a ticketing convenience. They're not. They're one side of an input-output problem: guests arrive at a certain rate, each guest takes a certain amount of time to check in, and the length of the queue you end up with is a function of both. Little's Law gives it a name: L = λW, where L is the average queue length, λ is the arrival rate, and W is the average service time. If your arrival rate at an 8:30am event spikes to 80 people per minute (which happens when a keynote starts at 9:00am and 500 people arrive between 8:20 and 8:40) and your average check-in takes 20 seconds, your queue length is going to grow until your arrival rate drops below 3 per minute per scanner. At one scanner station, that's a 200-person queue by 8:45am. At four stations, it's a 50-person queue that clears by 9:00am. The only variables you control are the number of scanners and the service time.
The QR code is where service time gets won or lost. A well-designed event QR scans in under half a second at the first attempt, 95%+ of the time. A badly designed event QR (too small, too glossy, poorly contrasted, printed at the wrong resolution, using the wrong error correction level) scans in 2-5 seconds or fails and requires manual lookup. The difference between those two service times at 80 arrivals per minute is a five-minute queue versus a twenty-five-minute queue. Same event, same staffing, same arrivals — different QR.
That's the frame. Everything in this guide is downstream of it. Size is set by the scanner distance at the check-in table. Placement on the ticket or badge is set by how staff and guests orient it under the scanner. The decision between paper, mobile, and wristband delivery is set by the scan reliability at each substrate. Error correction level is set by the post-print damage the QR will take (paper tickets survive fine; crumpled mobile screenshots are a different story). Lead-capture QRs at booths are a different problem entirely — that's not throughput, that's conversion — and are covered separately below.
One preview: for 90% of events under 2,000 attendees, the right setup is a dynamic URL QR on the ticket (mobile or paper), 2 × 2 inches or larger, H-level error correction, high contrast, scanned at three or more check-in stations with dedicated handheld scanners (not staff phones). The rest of the decisions are covered below.
By Ahmad Tayyem, Founder & CEO of QRLynx
Little's Law applied: the check-in throughput calculator
Here's the math concretely. You're planning a 500-person event where the doors open at 8:30am and the keynote starts at 9:00am. Historically, 60% of guests arrive between 8:20 and 8:50 — that's 300 people in 30 minutes, averaging 10 per minute. But the peak isn't the average; the peak cluster is 8:35-8:45, where 150 people arrive in 10 minutes, meaning 15 per minute at the worst point. Your QR scan service time — the clock from when a guest hands you their QR to when they're through the door — is where the QR choices show up.
Service time breakdown at an event check-in. (1) Guest approaches, fumbles for phone or ticket: 3-8 seconds. Can't be shortened with QR design. (2) QR presented to scanner: 1 second. (3) Scan completes: 0.3-3 seconds, depending on QR quality, scanner, and lighting. This is where the QR design shows up. (4) System lookup and confirmation: 0.5-2 seconds. Depends on network and registration platform. (5) Badge printing / hand-off (if applicable): 5-15 seconds for on-demand printing, 0 for pre-printed. (6) Guest moves on: 2-3 seconds. Best case: ~8 seconds per guest. Typical case: 15-20 seconds. Worst case (poor QR + on-demand printing + slow network): 30-45 seconds.
Applying Little's Law to your numbers. At 15 arrivals per minute (the peak cluster) and 20-second service time, queue length per scanner = 15 × (20/60) = 5 concurrent guests at any moment. Sounds fine. But the formula assumes steady state — it's what happens when arrivals and service are matched. The problem is when arrival rate exceeds service rate: at 15/min arrival and 3/min-per-scanner service (20-sec service), you need 5 scanners to keep the queue from growing. Four scanners and a 10-minute burst leaves you with a 60-person queue that takes 5 minutes to clear after the burst ends. Three scanners is worse: 90-person queue, 8-minute tail clear.
So the planning question is: at your expected peak arrival rate and your realistic service time per guest, how many scanner stations do you need? The clean rule: peak arrivals per minute ÷ (60 ÷ service time in seconds) = scanner count needed. For the example above: 15 ÷ (60 ÷ 20) = 15 ÷ 3 = 5 scanners. Round up, always. Undersized queues damage the guest experience more than over-provisioned staff costs.
The QR leverage. If you can reduce service time from 20 to 12 seconds — achievable with a well-designed QR on a durable substrate and a dedicated scanner (vs. a staff phone doing scanner duty) — the same 5-station setup now handles 25 arrivals per minute. Or the same 15-arrival peak only needs 3 stations. Service time is the variable you control with QR design, and every second you shave off compounds across the whole check-in window.
Practical service time reductions. (1) Bigger QR (2.5 × 2.5 minimum on a badge, 3 × 3 on a ticket) saves 1-2 seconds per scan vs. 1 × 1 QRs. (2) H-level error correction prevents retry loops on slightly damaged QRs (crumpled tickets, cracked phone screens) — saves 2-4 seconds on 5-10% of scans. (3) Dedicated handheld scanners (Honeywell, Zebra, Datalogic) outperform phones by 1-2 seconds per scan in bright uneven lighting. (4) Pre-printed badges vs. on-demand printing: saves 5-15 seconds per guest at the cost of having to reprint no-shows later. For events over 300 people, pre-print. (5) QR positioned so guest doesn't have to rotate their device: saves 1-2 seconds.
Which QR setup for which event type
Conferences, festivals, weddings, corporate events, trade shows, and ticketed shows all have different throughput profiles. Here's the mapping that actually works at scale.
Conference (500-5,000 attendees)
Pre-printed badges with personalized QR (encodes attendee ID). 2.5 × 2.5 inches on badge face. 4-8 check-in stations with handheld scanners. Keynote start is the peak arrival cluster. Plan stations at 12-second service time, pre-print badges the night before.
Ticketed show / concert
Mobile-ticket QR (email-delivered, Apple Wallet / Google Wallet compatible) or PDF printable. 1.5 × 1.5 inches on screen minimum. 2-3 stations per 1,000 attendees. Critical: test scan reliability on the exact ticketing platform's QR rendering — some platforms apply screen shaders that degrade contrast.
Wedding / private event (under 300)
Optional — small events rarely need QR check-in. When used: dynamic URL QR on escort cards for guest details (table number, menu, schedule). The QR does hospitality, not throughput. Sizing 1.5 × 1.5 inches fits escort card budget.
Corporate event / internal
Employee ID QR (usually already on corporate badge) or single-event dynamic QR on meeting-room door. 2-inch minimum. Often integrates with security system for access control. Service time dominated by badge-reader hardware, not QR quality.
Trade show booth (your own)
Two QRs: Lead-capture QR at booth entrance ("scan to exchange contacts") + Follow-up QR at exit ("schedule a follow-up demo"). Purpose isn't throughput — it's capture rate. 2 × 2 inches on a pop-up banner at eye-level, 3 × 3 on the booth's back wall.
Festival / multi-day event
Wristband QR (physical RFID-embedded QR printed on tyvek wristband, scanned at entry and at vendor purchases). 1 × 1 inch minimum on wristband, H-error correction critical because wristbands crumple over 3-day wear. Integrates with cashless-payment systems.
Delivery substrate: paper, mobile, or wristband
Three ways to get a QR to a guest: printed paper ticket (email → PDF → guest prints at home), mobile-delivered ticket (email → Apple Wallet, Google Wallet, or mobile-friendly HTML page), or a physical wristband/badge distributed at a pre-event will-call window. Each has a distinct service-time profile and a distinct failure mode.
Paper tickets. Service time 8-15 seconds typical. Failure modes: guest forgot to print, guest crumpled the ticket in their pocket, printed at wrong resolution or scaled, printer ink low (pale gray QR can fail), handed to staff upside-down. Advantages: works in bad lighting, no phone battery issues, easy to hand off to staff for scanning. Best for: older demographics, outdoor events where phone screen readability is poor, events with unreliable cellular coverage. Size paper-ticket QRs 2 × 2 inches minimum and strongly recommend H error correction to survive crumpling.
Mobile tickets. Service time 5-12 seconds typical, but with wider variance than paper. Fast cases: Apple Wallet / Google Wallet ticket where the QR auto-opens on approach with NFC trigger — under 5 seconds. Slow cases: email-buried PDF the guest is scrolling through on a dying battery, 15-30 seconds. Failure modes: phone battery dead, guest can't find the email, low screen brightness, cracked screen breaks QR, screen shader on their phone case tints the QR. Advantages: no printing, easy to re-issue, analytics on who opened the ticket. Best for: younger demographics, urban events, corporate events. Recommend Apple/Google Wallet integration for any event serious about mobile delivery — the native Wallet QR renders more reliably than email-delivered images.
Wristbands and badges. Service time 3-8 seconds typical — the fastest substrate because the QR is always in a consistent location (right wrist usually), always presented in roughly the same orientation, and always the same size and quality. Failure modes: wristband cracked or torn (common at day 3 of festivals), QR printed too small to survive tyvek texture, RFID secondary scan failing if that's the primary channel. Advantages: operational efficiency, low service time, can double for payment authorization. Disadvantages: printing cost, distribution logistics (guests must pick up in advance), replacement overhead for lost/damaged wristbands. Best for: multi-day events, festivals, events with cashless payment, venues with recurring access needs.
Many events blend all three: mobile for primary delivery, paper as a backup if mobile fails, wristband issued at first check-in. This redundancy is good — the cost of a second delivery mode is low, and it catches the 5-10% of guests whose primary mode fails.
Trade-show booth QRs: a different problem (conversion, not throughput)
Exhibitor QRs at a trade show are a different game than event check-in QRs. The problem isn't throughput — there's no queue to manage. The problem is conversion: you have maybe 45 seconds of guest attention in front of your booth, and a QR scan is the low-friction way to capture their contact without making them fill out a paper card or stand while you type their email into a CRM. The design choices serve that goal.
The canonical bad booth QR: "Scan for more info" on a banner somewhere, pointing to the exhibitor's homepage. Zero contact capture. Prospects who scan never identify themselves, the booth has no idea who walked by, and the post-show nurture campaign has nothing to work with. Industry average: 8-12% of booth visitors scan this pattern, and roughly 0% convert to leads in any trackable way.
The better pattern: a two-step QR flow. QR 1 at the booth entrance: "Scan to exchange contacts" — links to a lightweight lead-form page (name, company, email, "what are you interested in?") that takes 20-30 seconds on mobile. QR 2 at exit or on take-home swag: "Schedule a follow-up demo" — links to a booking calendar. Teams using this flow report 25-45% of booth visitors submitting contact info, with 8-15% converting to demo-booked leads. The lift comes from making the contact capture feel like a two-way exchange ("I'll give you my contact, you give me something useful") rather than a one-way pitch.
Design specifics. The QR should be 3 × 3 inches on a pop-up banner at eye level, with a short, active CTA ("Scan to exchange contacts" beats "More information"). The lead-form page should be mobile-optimized, pre-fill the "event" field so the prospect doesn't have to type which show they're at, and — critically — be fast. A 4-second lead-form page loses half the prospects who start the scan.
Bonus: put a QR on your follow-up email the next week. "Remember our conversation at [Event]? Here's the deck we discussed." A QR to a personalized landing page (rather than a generic PDF) gives you scan-tracking that tells you which leads are actually engaged, which is far more useful than email open rates. The compounding effect: event QR → lead form → follow-up email QR → personalized page → booked demo. Each QR narrows the funnel and produces data for the next stage.
The 500-scan pilot: find queue failures before showtime
Event QR setups fail at scale. Small-batch testing (you scan your own ticket at your laptop, it works) misses the failure modes that show up at 8:32am on event day. The fix is a structured pre-event pilot — 500 simulated scans across the conditions you'll actually face, finding the 5-10% failure rate you didn't know you had before it matters.
Pilot design. Print or generate 100 test QRs at the exact specs you'll use on event day (same size, same printer, same paper or mobile rendering platform). Scan each QR 5 times — 2 times with your staff's phones (testing phone-scan fallback), 2 times with a dedicated handheld scanner (testing primary flow), 1 time after a "damage" simulation (crumple a paper ticket, tilt a phone screen into glare). Target: 95%+ first-attempt scan rate under the worst realistic conditions. If you're not hitting 95%, debug before showtime.
Most common failure modes the pilot surfaces: (1) printer ink too pale for reliable contrast — fix by adjusting the QR's background color to pure white and verifying with a ColorChecker or a simple grayscale test; (2) QR printed at 200 DPI instead of 300+ — modules soften at the edges and fail on older phone cameras; (3) mobile ticket screenshot auto-compressed by a messaging app — fix by distributing the QR as a Wallet pass or PDF attachment rather than an image file; (4) handheld scanner set to wrong mode (some default to barcode mode and take 3 seconds to auto-detect QR) — configure before event; (5) wristband QR printed on the wrong substrate (glossy tyvek fails where matte works) — check the print vendor's default substrate.
Beyond scan reliability, pilot your check-in staff flow. Simulate peak-cluster arrival (20 guests at the check-in table in 5 minutes) and time the service rate. If you're taking longer than your budgeted service time, debug the bottleneck: usually it's staff-phone scanning (too slow), on-demand printing (add pre-printing), or a slow registration platform (batch-pre-load attendee data locally on scanner devices so lookups don't require a network round-trip).
Do the pilot three to five days before the event, not the day before. You want time to swap printers, reconfigure scanners, or switch delivery substrates if the pilot reveals a structural problem. Day-before pilots that find issues often don't have time to fix them properly.
Event QR FAQ
How big should a QR code be on an event ticket?
For paper tickets: 2 × 2 inches minimum. For mobile tickets: 1.5 × 1.5 inches on screen. For printed badges: 2.5 × 2.5 inches. These sizes give dedicated scanners sub-second reliable scanning at the typical 6-10 inch scan distance at a check-in table. Going smaller saves almost nothing on print cost but meaningfully raises scan failure rates.
Paper tickets, mobile tickets, or wristbands — which is best?
Mobile for most modern events (fastest service time, no printing cost, easy re-issue). Paper as backup for guests without phones or where mobile delivery failed. Wristbands for multi-day events, festivals, or events with cashless payment integration. Many events blend all three: mobile primary, paper backup, wristband issued at first check-in.
How many check-in scanner stations do I need?
Apply Little's Law: peak arrivals per minute ÷ (60 ÷ service time in seconds) = scanner count. For a 500-person event with peak arrival of 15/min and 20-sec service time, that's 5 scanners. Round up, always. Undersized check-in damages the guest experience more than over-provisioned staff costs.
Should we use staff phones or dedicated handheld scanners?
Dedicated handheld scanners for any event over 200 attendees. They're 1-2 seconds faster per scan than phones, handle bright uneven lighting better, don't depend on staff battery life, and decouple from staff phone calls or notifications. The cost (~$150-400 per scanner) pays back in reduced queue times at even a single event.
What error correction level should I use for event QRs?
H (30%) for all event contexts. Event QRs get creased in pockets, printed at variable quality, viewed through dirty phone screens, and subjected to handling stress. H-level error correction tolerates about 30% of the QR being unreadable before failing, which handles most real-world damage gracefully. L or M error correction fails enough at scale to cause queue buildups.
What's the best way to deliver QR tickets to attendees?
Apple Wallet / Google Wallet pass if your ticketing platform supports it — native rendering, no screen-shader interference, scannable without opening the ticketing app. PDF attachment as fallback. Image-in-email is the lowest-reliability option because messaging apps compress images inconsistently. For printable tickets, send a high-resolution PDF with explicit print instructions.
Can one QR code be used for multiple events?
No — each event should have its own QR (and ideally each attendee should have a unique QR within an event). Multi-use QRs break the audit trail: you can't tell which event a scan belonged to, which is a registration/billing problem, and you can't detect duplicates or forward-tickets. Per-event, per-attendee QRs cost nothing extra and solve both problems.
What happens if someone's phone is dead and they can't show the QR?
Have a name-lookup fallback at every check-in station. Staff searches by last name or confirmation number, verifies identity, and manually checks the guest in. This should take 30-45 seconds — slower than QR scan, but necessary. Typical incidence: 2-5% of attendees at a 500-person event need this fallback. Staff should be trained for it; don't assume everyone arrives with a charged phone and an accessible QR.
Can I track which QR codes were scanned to see who actually attended?
Yes — any dynamic QR logs scans with timestamp and typically device type. This is useful for post-event attribution (which marketing channels drove actual attendance vs. just registrations) and for no-show tracking (helpful for weighted guest-list decisions at the next event). Don't collect more than you need — IP or precise-location logging is rarely useful and has privacy implications.
What's the best QR code for a trade-show booth?
Two QRs: a lead-capture QR at the booth entrance (links to a short form — name, company, email, interest) and a follow-up-schedule QR on swag or banner at exit (links to a booking calendar). Teams using this two-step flow capture 25-45% of booth visitors as leads, compared to 8-12% for a generic "Scan for info" QR pointing to the homepage.
How do I handle QR codes for a festival or multi-day event?
Tyvek wristband with embedded QR, issued at first check-in. The wristband carries the attendee's access credentials for all days, all stages, all vendor purchases if cashless. 1 × 1 inch QR on wristband (tyvek texture handles this size reliably) with H error correction for crumpling tolerance. Budget for 3-5% wristband-replacement rate over a 3-day event — lost or damaged wristbands are normal.
Should I run a pilot before event day?
Yes. 500 simulated scans across conditions you'll face on event day, 3-5 days before the event. Test: scan reliability across printer/mobile variants, staff workflow at peak cluster, scanner configuration (some default to barcode mode), registration platform lookup speed. Target 95%+ first-attempt scan rate. Day-before pilots find issues you can't fix in time; earlier pilots leave room to swap substrates or printers if structural issues surface.
Where to go next — linked guides & QR types
Event QRs bridge three knowledge-graph areas. On the physical side, ticket and badge printing are covered in the business cards guide (similar card-stock material, similar lamination decisions). Large-format signage (stage banners, entrance wraps) falls under the posters guide for outdoor durability and scanning-from-distance sizing. Wristband QRs are a niche substrate not yet fully covered — the closest current guide is t-shirts, which shares the "flexible substrate with body motion" consideration.
On the QR type side, the dynamic URL QR is the default for event tickets and badges. The lead-form QR is the right choice for trade-show booth contact capture. For events with structured check-in and pre-registration data, a Google Form or webhook-driven QR is often the cleanest integration — the Google Form QR type handles this.
For multi-stage events (conference with sessions across a three-day program), smart redirect rules let one QR behave differently based on time of day (the check-in QR redirects to the keynote room Monday morning, the breakout hall Tuesday afternoon, the closing reception Wednesday evening). Expire rules handle ticket QRs that should auto-deactivate after the event date.
One follow-up tactic that compounds: after the event, add a QR to the thank-you email for attendees pointing to a personalized feedback and content hub. Attendees scan the QR and land on a page customized to their session interests (tracked from their badge scans during the event). That post-event scan is your highest-value re-engagement touchpoint of the year, and the analytics give you the signal to invest in specific session tracks for the next event.
By QRLynx Team · Last updated: