QR Code Event Check-In: How It Works and How to Set It Up
Half of your attendees are going to turn up in the 30 minutes prior to the opening session. It's that 30-minute window (not the total number on your registration list) that will ultimately determine whether you end up with a queue. QR code event check-in can be a great way to keep things progressing. Each delegate gets a code, you quickly scan it, and their record appears, their badge prints out, and you're all good. With a little bit of planning, you can be ready for the things that occasionally go wrong (phone dies, duplicate scan, station just stops working, etc.). This guide walks you through the full setup and tells you what to do if a scan doesn't work.

Key Takeaways
- Give each attendee their own code. You can't just use one shared code to let people in.
- Set the rules prior to the doors opening as to what constitutes a scan and what happens on a repeat scan.
- Have a fallback ready. Name lookup and a confirmation number can keep the line moving when a code fails.
- Size your stations for the busiest 30 minutes, not the total headcount.
- Monitor scan rates live during arrivals so you can spot a stalled station within minutes, not after lunch.
What Is QR Code Event Check-In?
QR code event check-in sees each delegate given a scannable code which is linked to their registration. You simply scan that at the door to check them in.
The code itself contains almost nothing useful; it’s just a pointer. Its value comes from the record it points to and the rules the system applies as soon as it’s scanned. That record determines whether the person is registered, whether they’ve paid, which sessions they can attend, and what appears on their badge.
This matters because it changes what you’re buying. You’re not buying a code generator; you’re buying the logic that runs behind the scan.
Unique QR Codes vs. One Shared QR Code
A single shared code is quick to produce. Print it on a poster, let everyone scan it, and you're done. It also tells you nothing.
A shared code in no way allows you to know who scanned it. It gives you no way of stopping a ticket from being used twice. It doesn't print a name on a badge, and it doesn't stop someone from attending a session they haven't paid for. All you get is a headcount, and an unreliable one.
A unique QR code per attendee is the answer to all of that. Each scan resolves to one individual, so you end up with an accurate arrival list, the correct name on the badges, access rules that actually work, and a record you can refer to afterward. If you're printing badges or running gate sessions in any scenario, then unique codes are the only viable option. Shared codes have their place for free walk-in events where you just need a rough figure.
Registration QR Code vs Check-In QR Code
These two are often confused, and they serve opposite purposes.
A registration QR code is an invitation. You put it on a flyer, a poster, a social post, etc and it opens your sign-up form. It's the same code for everyone, and anyone who scans it can register. Its job is to get people onto your list.
A check-in QR code is a credential. It's generated after registration; it's theirs; it's their proof that they're on the list. Those are the QR codes that your attendees bring to the door. One gets them into the database; the other gets them through the door.
Static vs Dynamic QR Codes for Events
A static code has the destination hardwired into the code itself. Once it's printed it can't be altered. If the link dies or the venue changes, every instance of the code is now dead.
A dynamic QR code for events will point to a short redirect URL that you control. You can change where it goes after you've printed it and you can see when and how many times it's been scanned.
For check-in itself the question doesn't really arise as the check-in code will have a unique registration reference rather than a web link. Dynamic codes are the ones that go on the printed material (signage, direction cards, programme inserts etc). That's the bit where you may well need to change the destination after a print run has gone out.
QR Code Check-In vs Manual Check-In
The difference is not only speed. Manual check-in and QR code check-in produce different data, fail in different ways, and need different staffing.
Manual check-in has one real advantage worth naming. It never depends on a battery, a signal, or a screen. That is why the best setups keep a manual fallback on the help lane rather than removing it entirely.
How to Set Up QR Code Event Check-In (Step-by-Step)
Nine steps, in the order you should do them. The first four happen weeks out. The last five decide how the morning goes.
1. Set Up Your Event in a Reliable Check-In Platform
Create the event in your event check-in solution and enter the basics (dates, venue, sessions, ticket/registration types and the access each type has). Everything that comes after in this list is read from what you've entered here so if you have the wrong session name in there now you're going to have the wrong access rules on the day.
2. Collect Accurate Attendee Information
Your badge is only as good as your registration form. You need to decide right at the outset which fields are going to print on the badge (typically name, company and job title) and make those required. You can also set rules for those fields. Free text company names end up as ACME, Acme Inc and acme inc and all three get printed.
Clean the list prior to code generation, not after. If you fix a record after the code has gone out, you're going to have to re-issue the code.
3. Automatically Generate Unique QR Codes
Let the platform generate one code per registration. Don't build them by hand in a spreadsheet and a free code generator, as hand-built codes have no link back to a live record. A code that can't be cross-checked against a database is just a picture, not a credential.
4. Distribute QR Codes via Email or Event App
Include the code in the confirmation email, then resend it in a reminder message two days beforehand.
The confirmation email should carry five things:
- The QR code as an image in the body, not as an attachment people never open.
- One line telling them what to do with it: have it open and ready at the entrance.
- A validation or booking number in simple text, as the fallback when the code will not scan.
- The event name, date, and arrival window.
- The venue address and which entrance to use.
Offer a mobile wallet pass as well. A pass sits in Apple Wallet or Google Wallet, survives a buried inbox, and opens without a signal. It is the single cheapest fix for the most common problem you will face on the day.
5. Configure Check-In Rules
This is the step most teams skip, and it is the one that decides what your staff spend the morning doing. Before the doors open, define what a scan triggers and what the system does when something is wrong.
A good scan should do three things at the same time: record the attendee as present, send the badge to the printer and apply the attendee's session access (and any VIP or restricted zone access).
Then set the exceptions. A duplicate QR scan will require a pre-determined decision as to whether it reprints the badge or alerts the operator. Reprint on request is generally the right answer, as lost badges are the norm and queue arguments are the exception.
A code from a different event should fail in a very clear way rather than just fail silently. An unpaid or incomplete registration should go to the help lane rather than the main line. Walk-ins need a registration route at the station.
6. Plan Check-In Stations for Peak Arrival
Plan your check-in for the rush, not the total crowd. A 1,000-person event doesn’t trickle in. About half of them show up in the 30 minutes before the first talk.
The maths is easy. Count how many people you expect in that rush, then work out how many that is per hour. Divide by what one station can handle. Then add one more.
Use a real number, not a guess. fielddrive, for example, says each of its kiosks can check in up to 200 people an hour, and that includes printing badges. So if 500 people come in 30 minutes, that’s 1,000 an hour. You’d need five stations, plus one spare. That spare isn’t extra fluff. If a printer jams or a screen freezes, it keeps the line moving.
Mix up your lanes, too. Self-service kiosks work well for most guests, who arrive with their code ready. Staffed lanes are for people who need a bit of help. Then set up one help desk on its own, with a clear sign. That’s where lost codes, name changes and tricky questions go. Skip it, and one confused guest can hold up the whole queue.
7. Test the Full Flow at the Venue
Test on site, on the real hardware, in the real room. A test that passed in the office proves very little.
- Scan from an iPhone and an Android phone, at the screen brightness people actually use.
- Scan a printed code and an on-screen code.
- Load the venue Wi-Fi with every device you plan to run, at once.
- Pull the network and confirm check-in keeps working, then confirm it syncs when the network returns.
- Print a real badge and check the alignment, the cut, and the spelling.
Note what offline mode actually covers. On fielddrive, offline supports QR scanning and name lookup. It is worth knowing which methods keep working before the network decides to test it for you.
8. Train Staff on Exceptions
The main line mostly runs on its own. Your staff are there for the people it can’t handle. So train them on those cases, and tell each person which ones are their lanes.
Go through every common problem before the doors open. A guest’s phone has died. Their email is lost in their inbox. They’ve lost their badge. They didn’t register. Their name is wrong. Or they’ve come to the wrong venue.
The rule is the same for all of them. Don’t fix it in the main line. Walk the guest over to the help desk and keep scanning. A problem that takes 15 seconds to sort out still holds up the 40 people behind it, and each of them loses a minute.
9. Scan and Monitor Check-Ins Using Devices or Kiosks
On that day someone should be monitoring the numbers rather than just scanning them. The real time check-in data is only going to be of any use if someone is actually looking at it and there's still time to act.
Watch three things. Scan rate per station tells you whether the floor is coping. A station that goes quiet whilst the others are still busy is broken not idle and that's the one thing that will save you the most time. Queue length against your plan tells you whether to open the spare lane you've kept in reserve.And the number of people being sent to the help lane tells you whether something systemic has gone wrong, because a sudden spike there usually means a bad batch of codes rather than a run of unlucky attendees.
The same scan data becomes your attendance tracking record afterward: who arrived, when they arrived, who never came, and which sessions filled.
What to Look For in a QR Code Event Check-In System
The vast majority of vendors will list the same features so the real test is how the system performs under load rather than what the page says. Six things in particular will determine that.
- Speed at peak, with a published number. Ask for throughput per station per hour, with badge printing included, not a scan time in isolation.
- Offline operation and its limitations. Which check-in methods work when you're offline, and how does the data get reconciled afterward? Most of the systems that claim to support offline operation only support a subset of the methods.
- On-demand [badge printing](https://www.fielddrive.com/solution/badging). Printing at the moment of scan removes alphabetical sorting, pre-print waste, and the walk-in problem in one move.
- Access rules that operate on the same record. Session and zone permissions should be checked as part of the same scan that is used to check the attendee in, rather than being managed in a separate system.
- Registration platform integrations. If the check-in layer cannot read your existing registration data, someone will be exporting spreadsheets at midnight.
- Onsite support on the day. Ask whether a person is on site or on the phone, and what the response time is during the arrival window.
If you're doing a detailed vendor comparison, then a scored breakdown of the various event check-in systems will show you how they differ on these points.
Common QR Check-In Problems and How to Fix Them
Almost every QR code check-in issue falls into one of six categories. Print out that table and give it to the person who runs the help lane.
Two of these are actually prevented rather than cured. Wallet passes deal with the majority of the lost code cases and a properly tested offline mode deals with the network case. The remainder require a help lane and a trained person in that lane.
QR Code Placement on Badges and Emails
A code that scans on the second go costs you the same as one that never scans at all. The queue is totally indifferent to the reason. Three specs are of course the important ones and all three are measurable.
Size: the minimum printable size for an ISO/IEC 18004 compliant code is 1cm x 1cm and 2cm x 2cm is the safer working minimum. The usual rule of thumb is a 10:1 distance to size ratio so a code to be scanned at 20cm would want to be about 2cm across.
Quiet zone. ISO/IEC 18004 requires a clear space of four modules on each side of the code (a module being one of the little squares in the pattern). Logos, borders and badge text which get pushed into that margin are a very common cause of slow scans.
Contrast. Dark pattern on a light background only (never the other way around). Don't ever print code over a photo, a gradient or a dark branded colour.
On the badge the QR code goes on the front, below the name block, well clear of the lanyard slot and the fold line. A code placed behind a holder's seam or crease will fail. In the email the code goes in the body at a sensible size and the confirmation number in text directly underneath it.
QR Code Event Check-In Best Practices
Five practices that change the arrival experience more than any setting in the software.
- Send a notice two days out which states where the code is. You can't find a confirmation from six weeks ago. Retransmitting it is the cheapest queue reduction you can do.
- Sign the queue before people get to it. Have a sign up saying "Have your QR code open and ready" and that gets the codes onto the screens whilst people are still walking.
- Have a completely separate and clearly signposted help lane. Keep all exceptions out of the main queue. That's the single most important thing in terms of how the queue feels.
- Give walk-ins their own station. Onsite registration takes several times longer than a scan, so it should never sit behind a scanning lane.
- Keep one station in reserve and watch the live data. The spare covers the station that fails. The live scan rate tells you when to open it.
Wrapping Up
QR code event check-in is simple to switch on and easy to get wrong. The code generation is the simple part. The work is in the decisions around it: one code per attendee, rules set before the doors open, and a tested fallback for failed scans. Add enough stations for the half hour when everyone arrives at once.
Get those four right and the technology mostly disappears, which is the point. Nobody remembers a check-in that worked.
fielddrive runs QR check-in, on-demand badge printing, and session access from a single attendee record, online or offline, reading from 35 or more registration platforms. If you want to see it against your own attendee file and your own arrival numbers, book a demo.
Frequently Asked Questions
The code itself adds no security. The security comes from what sits behind it: a unique record per attendee, validation at the moment of scan, and a duplicate flag on the second use. That combination makes a shared or copied ticket visible, which a printed list cannot do.
Yes. Access is set on the attendee record, not the code, so VIP, staff, press and exhibitor types can each carry different permissions. The same scan that checks them in will also apply their session and zone access and the badge can print a different design depending on the types, and the badge can print a different design per type.
Move the attendee to the help lane and keep the main line scanning. Staff then fall back in order: name lookup, confirmation number, then photo ID. A trained fallback takes under a minute. The failure only becomes a problem when someone tries to solve it in the main queue.
Every scan is time-stamped, so you get arrival patterns, no-show rates, and session attendance without anyone typing them up. That tells you when your real peak was, which sessions filled, and how many registrations never turned into arrivals.
Yes, provided each event has its own code set and its own access rules. The thing to confirm is how the system reacts to a code from the wrong event. It should fail clearly and tell the operator which event the code belongs to.
Use a platform that reads your existing registration data, generates the codes, and prints badges at the scan. That removes the three manual steps teams usually build themselves. Set your check-in rules and test on site before the day.
Want to learn how fielddrive can help you elevate your events?
Book a call with our experts today
.webp)

