QR Code Check-In Without an App: Setup, Offline, Staffing

Guests show a QR code, door staff scan it with a phone browser, and nobody installs anything. Here is how no-app check-in works, what happens when the wifi drops, and how to staff the door.

The short answer

QR check-in without an app runs in the web browser. Each confirmed guest gets a unique QR ticket by email, and door staff open a scanner page in their phone's browser and point the camera at it. There is nothing to download for guests or staff and no hardware to buy. On Event Flo it is free, with no limit on guests or door staff, and if the wifi drops, scanning keeps working and syncs when the connection comes back.

The rest of this guide is the planning around that: which check-in model suits your event, what to expect when the venue has no signal, how many scanners the door needs, and what to do for the guest who arrives without a code. For the scanner itself, step by step, see the QR code event check-in guide.

How browser-based QR check-in works

1. The guest registers. They RSVP on the event page, and each confirmed registration gets a unique code.

2. The ticket arrives by email. The QR code opens on any phone screen, and guests can also print it.

3. Staff open the scanner. Door staff sign in and open the scanner page in the phone's browser. The browser asks once for camera access.

4. The scan is checked. The server confirms the ticket belongs to this event, is still valid and has not already been used, and the phone shows "Checked in" or the reason it was refused.

5. The count updates. The check-in is recorded once on the server, so the organizer's live headcount moves, and if a second phone scans the same ticket it shows "Already checked in" with the time.

The browser is the reason no app is needed. Modern phone browsers can use the camera and store data on the device, which covers everything a door scanner needs.

Self-scan or staff scan: pick the right model

"QR check-in" describes two different setups, and they solve different problems.

Self-scan: one code at the entrance

A single QR code sits on a poster or screen at the door. Each guest scans it with their own phone and confirms their name on a form. It needs no door staff and suits trainings, classes and internal meetings where everyone is known and you only want an attendance record.

The catch: anyone can scan a poster. Self-scan records who says they came; it does not stop someone who was not invited from walking in, and it slows down when a crowd arrives at once because every guest fills in a form.

Staff scan: one code per guest

Every guest carries their own code, and a staff member scans it at the door. Because each code is unique, a forwarded screenshot works once and the second scan shows as already checked in. It is the right model for ticketed events, parties and anything open to strangers, and it is faster at a busy door because the guest only holds up a phone.

Event Flo uses staff scan. If you want an attendance record for a closed group, it still works: everyone on the list gets a code, and one person at the door scans them in.

What happens when the wifi drops

Venue wifi fails often: basements, rooftops, parks and packed halls are all hard on a signal. A browser scanner deals with it by loading the guest list onto the device before doors open.

1. Before doors: open the scanner while you have a connection and leave the page open, so each phone stores the current guest list.

2. Offline: staff keep scanning. Each scan is checked against the stored list, marked as pending sync and saved on the phone with its time. Name lookup works offline too.

3. Back online: the saved scans sync to the server, which records each check-in at the time it happened at the door.

4. Afterwards: any offline admit the server refuses, such as a ticket cancelled while the phone was offline, is flagged on the scanner so you can follow up.

Know the limit. An offline admit is provisional. The phone only knows the list as it was at its last refresh, so it cannot see a ticket cancelled or a guest blocked after that, and it cannot enforce a capacity limit. Two phones that are both offline cannot see each other's scans either, so one ticket could get in at two doors. Refresh the scanner right before doors, and keep offline stretches short.

Two cheap backups cover the rest: one phone with a mobile hotspot for the door team, and a printed or downloaded guest list in case a device dies.

How many scanners do you need?

Size the door for the rush, not the total. Most guests arrive in the half hour after doors open, so plan around that window.

As planning arithmetic: the scan itself takes a moment, but a guest finding their ticket, saying hello and getting a wristband takes longer. Assume about 30 seconds per guest at a busy door. One scanner then clears about two guests a minute, or about 60 in that first half hour.

Adjust for your crowd. A run club where everyone turns up at 5:55 AM needs more scanners per head than a dinner where guests drift in over an hour. Add one spare phone at any door with more than one scanner. Past a few hundred guests, staggered entry times or a second entrance usually do more than adding scanners at one door.

When a guest has no QR code

Someone will arrive with a dead phone or a deleted email. Decide the fallback before doors open so staff do not improvise in front of a queue.

• Look them up by name. Type the name into the scanner's manual box, check it against their ID, and check them in from the result.

• Send the ticket again. If they have their phone but cannot find the email, the organizer can resend the ticket from the attendee list. Guests who can sign in can also open the ticket on the website.

• Pull them out of the line. Send no-code guests to one person at the side so the scanners keep moving.

• Decide on walk-ins in advance. If you will admit people who are not on the list, decide who can approve it and keep a count, so your attendance numbers stay true.

Set it up the day before

A no-app system takes minutes to set up. Doing it the day before, not at doors, is what makes the night go smoothly.

1. Create the event and confirm your guest list. If guests registered somewhere else, import the list from Excel or CSV so each one gets a QR entry pass, then send the passes.

2. Invite your door staff by email. Each person needs a free Event Flo account and accepts the invite, then scans from their own phone.

3. Do a test scan with two phones: one valid ticket, the same ticket again, and one name lookup.

4. Remind guests in the event message to have their QR code ready at the door.

5. On the night, open the scanner on every phone while you still have signal, and check the battery.

For the door itself, from lighting to queue layout, see how to scan tickets at events.

After the event

Export the attendance report once doors close. Check-in times tell you when the rush happened, which tells you how many scanners to bring next time, and the gap between RSVPs and check-ins is your real no-show rate. Follow up with the people who came, and decide what to do about the ones who did not.

When another tool fits better

A browser scanner covers most doors, but not all of them. If you need printed name badges at the door, a dedicated badge tool such as Eventleaf, RSVPify or OneTap fits better, because Event Flo does not print badges. If you want card payments taken at checkout, Eventbrite does that; on Event Flo, guests pay the host directly. For large multi-day conferences with session tracking, a conference suite like Cvent or Whova is built for the job. The full comparison, with prices, is in event check-in apps compared.

Run your door on Event Flo

Event Flo gives every confirmed guest a QR ticket and lets your door team scan from their own phones in the browser, with a live headcount on the organizer's check-in screen, scanning that keeps going when the wifi drops, and an attendance report afterwards. It is free event check-in software with 0% platform fees and no limit on guests or door staff. To compare it with paper lists, spreadsheets and kiosks, read how to check in guests at an event.