QR Codes for Events in 2026: Check-In, Tickets, and the Line-Killing Playbook

It was hour two of the registration line at a SaaS conference in Austin last November. The hotel ballroom doors were closed because the opening keynote had already started. Outside, four hundred founders, half of them jet-lagged from Seattle or Boston, shuffled forward toward a single table where two volunteers were typing names into a laptop that kept losing the venue Wi-Fi. A VC I knew from San Francisco gave up at minute forty and went to drink at the pool bar. He told me later he learned more there than he would have in the keynote, which is probably true and entirely beside the point. The event sold itself on access. The line broke the promise before he ever got in the room.

Event check-in is a solved problem. I have been running event operations for conferences, product launches, and a fair number of weddings since 2014, and the technology that makes a thirty-second check-in possible has been cheap and reliable for at least five of those years. The reason lines still exist in 2026 is that the check-in flow gets designed last, by someone who has never worked a door, in the week before the show. This is the playbook for not being that organizer.

The thirty-second check-in versus the five-minute one

Here is the actual stopwatch difference. A QR-based check-in with a phone scanner, a charged battery, and a printed badge sheet sorted by last name as backup runs eighteen to thirty seconds per attendee. A laptop-and-spreadsheet check-in where the volunteer searches the registrant list, asks how to spell the company name, and prints a badge on the spot runs three to five minutes per attendee. At a four hundred person event with two stations, that is the difference between a six-minute average wait and a fifty-minute one. The attendees blame you for the second number even though the math is just throughput.

Eventbrite, Bizzabo, and Cvent all ship serviceable scanner apps now. Most of the production teams I work with at the mid-market end use Eventbrite for sub thousand-person shows, Bizzabo when there is a sponsor activation layer that needs structured lead capture, and Cvent only when corporate procurement mandates it. For weddings I have built more than one workflow on Airtable plus a Zapier hook plus a free QR generator. The platform matters less than the operator does.

What is actually inside a ticket QR

A ticket QR contains a string. The string is one of two things. Most platforms use a random UUID, usually a v4, that the server looks up in its tickets table to confirm validity and mark the ticket as redeemed. A smaller number of platforms use a signed JWT, which carries the ticket ID and a signature so the scanner can validate it offline if the network drops. Eventbrite uses the UUID lookup approach. Some of the corporate event platforms use signed tokens.

The practical implication for you as an organizer is this. Never put attendee personal data inside the QR payload itself. If a guest screenshots the ticket and posts it on Instagram, which they will, you do not want their email address or phone number readable to anyone with a scanning app. The QR should be opaque. The personal information lives in your registration database, keyed to the ID inside the QR. You will also want server-side validation that flags any ticket ID that is scanned twice, which is how you catch the screenshot resale problem. More on that in a minute.

Scanner phone or scanner kiosk: pick one and train for it

For events under a thousand people, scanner phones beat dedicated kiosks every time. A volunteer with an iPhone running the platform app can move down a line, scanning badges in attendees hands, which doubles your effective throughput because you are not bottlenecked at a fixed station. For events over a thousand, a mixed setup works best. Two self-service kiosks for the early arrivals who want to be efficient, four staffed phone scanners for the rush between minute fifteen and minute forty-five of the doors-open window.

The training matters more than the hardware. Every volunteer at the door needs to know three things cold. How to scan a QR. How to mark a ticket as checked in manually when the scan fails. How to handle the polite but escalating attendee whose name is not in the system. I run a fifteen-minute drill the night before every event where I make the volunteers process me through each of those three flows under a stopwatch. It feels excessive until the day-of when nobody freezes.

Redundancy is not optional. At minimum you need two charged backup phones in a drawer behind the desk, a printed alphabetical attendee list with a checkbox column, and one volunteer whose sole job is to keep the scanner phones plugged into a power strip when they are not in active use. The scanner phones will die. Not might. Will. The screen brightness is at max, the camera is running continuously, and the network radio is hammering. Plan for ninety minutes of battery per phone, not the four hours their spec sheet claims.

The dead-battery scenario and the printed-ticket backup

An attendee will arrive at every event with a dead phone. Sometimes it is genuine, sometimes they forgot to charge in the cab, sometimes they handed it to a child during the Uber ride. The polite thing to do, the thing that keeps the line moving, is to print the QR on the ticket confirmation email in addition to attaching the Apple Wallet or Google Wallet pass. The attendee who printed the email at home has a paper backup. The attendee who did not is no worse off, because they have the wallet pass. Both groups get through the door in thirty seconds.

I always argue with platform vendors about this. Most of them push you to use wallet-only passes because it is cleaner and on-brand. It is also fragile. The print fallback costs you nothing and saves you the fifteen-percent of attendees who, for one reason or another, cannot present a working phone at the door.

Schedule changes mid-event: dynamic QRs earn their keep here

The printed program is wrong by lunch on day one. A keynote speaker misses their flight. A workshop oversells and a second session gets added. The panel moderator gets food poisoning at the welcome dinner and a senior partner volunteers to fill in. This happens at every event I have ever worked.

One dynamic QR on every piece of signage and on the back of every badge solves it. The QR points to a single page that you control, served behind a CDN, which renders the current program from a Google Sheet or a Notion database that your program manager can edit from her phone. When the speaker drops out at 10:47, she updates the sheet, the page refreshes, and the next attendee who scans the QR sees the new schedule. No reprints, no apology emails, no taped-over printed boards. Static QRs cannot do this. Use dynamic.

Networking vCards on every table at every event

The conference dinner is where deals get made and contacts get lost. The ritual is familiar. Eight people at a round table, three of them fishing for business cards in a wallet, two more typing names into LinkedIn under the table, the rest pretending to listen to the founder pitch happening across the centerpiece. By dessert nobody remembers who said what about which round.

Print a small vCard QR tent for each attendee at check-in. Each tent has the attendee name, company, and a QR that, when scanned, drops a fully populated contact card straight into the scanning phone. Two seconds, no typing, no spelling out an unusual surname for the third time that evening. I have seen this single intervention cut the post-event LinkedIn-connection lag by about a week, because the contacts are saved in the phone the same night, while the conversation is fresh.

For large weddings, the vCard pattern extends further than you might think. The invite QR scanned by the recipient leads to an RSVP form, then to a meal preference picker, then to a seat assignment confirmation, all in one flow. I built this for a wedding in Atlanta last December with five hundred guests and the family planner told me it saved her roughly thirty hours of text-message back-and-forth in the two weeks before the reception. The same QR on the reception entry desk doubles as the check-in.

Sponsor QRs and the prize-draw lead capture trick

Sponsors pay you for access to attendees. The worst thing you can do is hand them a fishbowl for business cards. The best thing you can do is give every sponsor booth a structured lead-capture flow that uses the same scanner app your registration team uses. The attendee scans the sponsor QR, the sponsor gets a structured record with the attendee company and role, and the attendee is entered into whatever giveaway the sponsor is running.

The prize-draw incentive is not optional. Without it, attendees skip the booths. With a meaningful prize, an Apple Watch or a $200 Amazon gift card, the booth traffic and the lead quality both go up noticeably. The sponsor renewal conversation the following year is much easier when you can show them four hundred structured leads instead of a shoebox of paper.

The badge-as-QR pattern at large conferences

At SaaStr, TechCrunch Disrupt, Web Summit, and most of the large enterprise events, the attendee badge itself is a QR. The QR encodes the attendee ID, and any other attendee can scan it to exchange contact details through the event app. This is now table stakes for any conference over fifteen hundred people. The cost is a slightly more expensive badge stock, maybe thirty cents more per attendee, and one extra field on the registration platform export. The benefit is that networking stops being an exchange-cards ritual and starts being a tap-and-move-on interaction.

The version of this pattern I most often see done badly is when the event app the QR opens has a six-screen onboarding flow before the attendee can save the contact. The app does not need to be good. It needs to save the contact in one tap. Push back on your event-app vendor on this exact interaction. It is the only one that matters.

The pre-conference QR pack

The week before the event, send registrants one email with three QRs in it. First, the venue location QR. Second, the speaker-bio page QR. Third, the hotel-Wi-Fi QR for the conference block, if you have negotiated one. This tiny pre-arrival pack does more for attendee mood than any swag bag I have ever ordered, because it removes three small frictions before they become complaints at the registration desk.

What I would skip

NFC for events under a thousand people. Every event-tech vendor pitches NFC badges as the next thing. For a five hundred person conference, NFC is overkill. The badges cost three to four times more, the scanning hardware is more expensive, and the failure modes are worse, because an NFC read failure is invisible whereas a QR read failure shows you what went wrong on the camera screen. Save NFC for events where you need access control to specific rooms, like a multi-track conference with paid and free tracks running in parallel.

Branded QR codes with the sponsor logo in the center for ticket check-in. The marketing team will ask for this. The branded QR scans slightly slower because the error-correction budget is being spent on hiding the logo behind the image overlay. For a ticket scan that happens once and is throwaway, do not pay the throughput cost. Use plain black-on-white. Save the branded version for the after-event commemorative poster.

The event app for everything. Event apps have their place, mostly for the schedule and the in-app networking. Do not force check-in through the app. Half the attendees will not download it. The ones who do will not have logged in. The QR in the confirmation email is faster than the app every time.

The five event QR mistakes I keep seeing

Tickets resold via screenshot with no unique-scan validation.This is the biggest one. A friend buys two tickets, screenshots one, sells it on a WhatsApp group, and now two people show up with the same QR. The first one through the door gets in, the second causes a scene. The fix is dead simple, and most platforms have it built in: flag any ticket ID that gets scanned a second time and require a manual override. Check that the setting is on. At a wedding last year I worked, this flag is what caught the cousin who tried to bring his unannounced plus-five.

No paper backup of the attendee list. The Wi-Fi dies, the cellular network at the venue is overloaded, the registration platform has a regional outage. All three have happened to me on event days. The printed list with a checkbox column is the thing that keeps the doors moving while you call the platform vendor.

Scanner phones not charged. See above. Three power strips behind the desk, one volunteer whose job is to rotate phones onto chargers between waves.

No offline fallback in the scanner app. Some of the cheaper platforms require an internet connection for every scan. When the venue Wi-Fi drops, the line stops. Before you commit to a platform, ask whether the scanner app caches the attendee list locally and syncs scans later. If the answer is no, pick a different platform.

No QR on the conference badge itself. The badge is hanging around the attendee neck for two days. It is the easiest networking surface you have. Print a vCard QR on the back. The attendees who use it will thank you. The ones who do not will not notice.

The pattern, summarized

The pattern at events with smooth check-in is the same. The QR is in the wallet and in the email body and printable on a fallback page. The scanner app caches the attendee list. The volunteers have run a fifteen-minute drill the night before. The schedule QR is dynamic. The vCard tents are at every table. The sponsor lead capture is structured. The badge has a QR on the back.

The pattern at events with broken check-in is also the same. The QR is buried six clicks deep in an event app the attendees never installed. The single scanner station has one volunteer who has never seen the platform before. The fallback is a panicked search through a Gmail inbox. The schedule is printed and outdated by 11 AM. The networking surface is paper business cards.

You can move from one pattern to the other in about three hours of preparation. The events hub has a printable check-in checklist you can hand to your door lead and a sample vCard tent template you can adapt. The FAQ covers print sizing for badges and the contrast rules that make scans reliable in low venue lighting. For sponsor lead tracking and post-event attribution, the print marketing QR guide has the UTM and A/B test patterns that work equally well at a sponsor booth.

Last updated June 2026 by David Kumar.