You open the door at seven, and by five past the hour twelve people are already standing in the hallway. Someone printed their ticket at home but left it in the car. Another person has the confirmation email but can't find the QR code because their phone screen is cracked. A third bought two tickets under different names and now both friends are stuck at opposite ends of the queue. Meanwhile, the people who arrived on time are getting impatient, and you haven't even said hello yet.
A slow check-in kills the mood before the event starts. The solution is not complicated, but it does require a bit of preparation and one or two decisions made ahead of time.
What actually slows down the entrance
The bottleneck is rarely the scanning itself. It's the confusion about what counts as a valid ticket, who's allowed to vouch for whom, and what to do when someone's name isn't on the list but they insist they paid.
If you're checking people in by hand with a printed spreadsheet, you'll spend time scrolling, squinting and asking people to spell their names twice. If you're using QR codes but only one person has the scanner, that person becomes the single point of failure. If the Wi-Fi is patchy and your check-in app needs to refresh the list every time, you're stuck waiting for a spinning wheel while the queue grows.
The other common problem is people who forward their ticket to a friend without telling you, or who screenshot someone else's QR code. If your system doesn't mark a ticket as used the moment it's scanned, the same code can be shown twice and you'll only notice when the room is over capacity.
Setting up QR check-in that works offline
The simplest fix is to generate a unique QR code for every ticket and store the guest list on the device you're using at the door. That way you don't depend on a live internet connection, and scanning happens in a second or two.
When someone buys a ticket on Anyza Events, they receive a PDF with a QR code tied to their order. You open the check-in page on a phone or tablet, scan the code, and the system marks that ticket as used. If someone tries to show the same code again, you'll see a warning. The whole guest list lives in the browser, so it works even if the venue has no signal.
You can also add people manually at the door—useful for last-minute walk-ins or complimentary entries—and everything syncs when you're back online. If you're running a free event with registration, the same approach applies: everyone gets a QR code when they sign up, and you scan it to confirm attendance.
Organising the entrance so one person isn't doing everything
Even with fast scanning, a single checkpoint creates a queue if you have more than twenty or thirty people arriving in the same ten-minute window. The fix is to split the work.
One person scans tickets. Another handles questions, checks IDs if you're serving alcohol, or directs people to the cloakroom. If you're expecting a crowd, set up two scanning stations and divide the alphabet or ticket types between them. Early-bird ticket holders go left, regular tickets go right, or surnames A to M use one line and N to Z use the other.
Make sure both people at the door have access to the check-in system. If you're using a phone, open the page in two browsers or on two devices signed in with the same account. Test this before the event starts, not when the first guest arrives.
What to do when the QR code doesn't work
Sometimes the code won't scan because the screen brightness is too low, the PDF got corrupted, or someone photographed their ticket at an angle. Have a backup plan that doesn't involve starting an argument.
Keep a copy of the full guest list on your phone—a simple text file or spreadsheet works—so you can search by name or email. If someone's on the list and their QR code won't cooperate, mark them as checked in manually and let them through. It's faster than making them stand aside while you troubleshoot.
If someone claims they bought a ticket but you can't find their name anywhere, ask for the confirmation email or payment receipt. If they can show you either, let them in and sort it out later. If they can't, offer to sell them a ticket at the door if you have capacity, or take their contact details and follow up after the event. Holding up the queue to investigate rarely ends well.
Rehearsing the first fifteen minutes
The difference between a smooth check-in and a chaotic one usually comes down to whether you practiced the process before people showed up. An hour before doors open, walk through the entrance with whoever is helping you.
Scan a test ticket to make sure the system is working. Decide where people will stand once they're checked in—if they cluster right in front of the door, the next person can't get through. Put up a sign that says "Have your QR code ready" so people aren't fumbling with their phones while they're at the front of the line.
If you're selling tickets at the door, set up a separate table for walk-ins so they're not blocking the main queue. Make sure you have a way to accept payment and issue a ticket on the spot, whether that's a phone with a payment link or a cash box and a receipt book.
Check the lighting. If the entrance is dim, the scanner might struggle to read the codes. A cheap clip-on phone light solves this.
Trying it at your next event
If you haven't used QR check-in before, start with a small event where you can afford to experiment. A meetup with fifteen people is a good test case—you'll learn how the system behaves without the pressure of a ticketed event where people paid in advance.
Set up an event page on Anyza Events, send the ticket link to your guests, and practice scanning a few codes before they arrive. You'll know within five minutes whether your phone handles it well or whether you need a tablet with a bigger screen.
Once you've done it once, the next event will be faster. And the queue at the door will be shorter, which means you can spend the first fifteen minutes talking to people instead of apologising for the wait.
Comments