The Event Check-In Playbook: Move 1,000 People Through the Door in 30 Minutes

Moving 1,000 people through your doors in 30 minutes is an arithmetic problem, not a heroics problem: at a realistic 5 to 8 QR scans per minute per staffer, you need 5 to 7 scanning lanes, a layout that keeps lines moving toward them, and a fallback plan for the three things that always go wrong. We've watched hundreds of Canadian events run doors on Eventist, from 200-parent dance competitions to multi-day festivals, and the events with calm entrances all run some version of the playbook below.

How fast is QR code check-in compared to paper lists?

QR scanning is roughly 6 to 10 times faster than a paper or spreadsheet list. A trained staffer with a phone scanner processes a guest in 4 to 8 seconds — point, beep, wave through. A name lookup on a printed list takes 30 to 60 seconds per guest once you account for spelling clarifications, page flipping, and the inevitable "it might be under my partner's name."

At scale that difference is the whole ballgame:

• One QR lane: 5 to 8 guests per minute, 300 to 480 per hour
• One paper-list lane: 1 to 2 guests per minute, 60 to 120 per hour
• To admit 1,000 people in 30 minutes: 5 to 7 QR lanes — or 17+ paper lanes, which no lobby on earth has room for

If you're still on printed lists, the mechanics of switching are simpler than most organizers expect — we walk through the whole flow in how QR code check-in works at events.

How many check-in staff do you need? The lane math

Use this formula and you will never guess again:

Step 1: Estimate your peak arrival window. For ticketed shows with a hard start time, expect 60 to 70% of attendees to arrive in the 30 minutes before doors close. For a 1,000-person event, that's roughly 650 people in your peak half hour.

Step 2: Divide by lane throughput. At a conservative 5 scans per minute, one lane clears 150 guests in 30 minutes. 650 ÷ 150 = 4.3, so run 5 scanning lanes.

Step 3: Add non-scanning roles. One line marshal per 2 to 3 lanes to keep queues even and answer questions before guests reach the scanner, one floater to resolve exceptions (name changes, duplicate scans, "my ticket won't load"), and one supervisor with full admin access. For our 1,000-person example: 5 scanners + 2 marshals + 1 floater + 1 supervisor = 9 door staff.

Step 4: Brief for the exception rule. The single most important instruction: any guest issue that takes longer than 20 seconds gets stepped aside to the floater. One confused order held at a scanner stalls 150 people behind it. The lane keeps moving; the floater solves the problem.

How should you lay out the entrance?

The pattern we see across smooth entrances is that the layout does half the work before anyone scans anything:

• Signage starts at the parking lot. "Have your QR code on your screen and brightness up" signs (or a staffer with a megaphone-friendly voice) 20 metres before the door converts fumbling time into walking time.
• Split will-call and VIP from general admission. Will-call transactions take 10x longer than a scan; one will-call guest in a scan lane destroys its throughput. Give will-call its own table, off to the side, with its own staffer.
• Add an accessibility lane. A wider, step-free lane with a patient staffer, clearly signed. It's the right thing to do, and it also removes mobility devices, strollers, and guests who need extra time from the high-speed lanes — everyone moves faster.
• Pre-scan the wifi and cellular reality. Concrete lobbies and 1,000 phones murder connectivity. Test your scanning devices at the actual door, at the actual angle, an hour before doors — not on the venue office wifi.
• Set stanchions for a queue, not a crowd. A serpentine or per-lane queue with a defined entry point processes dramatically faster than a fan-shaped mob, and it feels faster to guests too.

What happens when the internet goes down? Offline fallbacks

Plan for connectivity failure at every event, because it will eventually happen at one of them. Your fallback stack, in order:

• An offline-capable check-in app. Eventist's QR check-in keeps scanning when connectivity drops and syncs when it returns, so a dead router doesn't become a stopped line. Confirm your attendee list is loaded on each device before doors — that's part of the pre-doors checklist below.
• A hotspot per zone. One charged phone hotspot per pair of lanes, tested in advance, on a different carrier than the venue wifi if possible.
• The break-glass paper list. Print one alphabetized list per lane the night before — not to use, but to exist. If every digital layer fails, you mark names with a highlighter and reconcile scans afterward. In years of events we've rarely seen it used, but the nights it was, it saved the show.

How do you handle duplicate scans and ticket disputes at the door?

A duplicate-scan alert means one of three things, and your staff should know the script for each:

• Screenshot sharing (most common). Someone forwarded their QR code to a friend; the first scan wins. The system flags the second attempt with the original scan time. The floater handles it: the second holder can buy a ticket at the door or step aside — the scan lane never adjudicates.
• Re-entry. A guest who legitimately left and returned. Decide your re-entry policy before doors and give staff a mechanism (out-scan, wristband, or hand stamp) so a duplicate alert on re-entry is expected, not an incident.
• Honest double-scan. Two staffers scanned the same guest ten seconds apart in a busy moment. The timestamps make this obvious; wave them through.

The principle underneath all three: scanners scan, floaters decide. Escalation paths keep lines moving and keep confrontations away from the crowd.

The 15-minute pre-doors checklist

Run this at T-minus 15 minutes, every event, no exceptions:

• T-15: Every scanning device charged above 80%, logged in, attendee list synced and showing the correct count. Backup battery packs at each lane.
• T-12: Test scan one real ticket and one already-scanned ticket at every lane — confirm both the green path and the duplicate alert behave.
• T-10: Hotspots on and devices confirmed connected. Paper break-glass lists placed under each lane's table.
• T-8: Staff briefing: peak-window estimate, the 20-second exception rule, who the floater is, re-entry policy, accessibility lane location.
• T-5: Stanchions final, signage visible from the approach, will-call table stocked with its own list and a card reader.
• T-2: Supervisor takes position with radio or group chat open. Doors on time — a late door start compresses your peak window and undoes all the math above.

Check-in is the first thing every attendee experiences and the last thing most organizers plan. Give it the same rigor as your pre-event checklist and the entrance becomes a non-event — which is the highest compliment door operations can earn. If you want help modelling lanes and staffing for your specific venue, book a call and we'll run the math with you.

Frequently Asked Questions

How many people can one staff member check in per hour?

With QR scanning, 300 to 480 guests per hour per lane is realistic once staff are warmed up. With paper lists, 60 to 120. Staff your doors from your peak 30-minute arrival window, not your total attendance.

Does QR check-in work without internet?

It should — verify before you commit. Eventist's check-in keeps scanning offline and syncs when connectivity returns. Whatever platform you use, load attendee lists onto devices before doors and carry a hotspot per zone as a second layer.

What stops someone from screenshotting a ticket and sharing it?

First scan wins. When a shared code is scanned a second time, staff see a duplicate alert with the original scan timestamp. Route the holder to a floater, never debate at the scan lane.

When should doors open relative to start time?

For most single-room events, 45 to 60 minutes before start; for 1,000+ attendees or events with bag checks, 90 minutes. The goal is to keep your peak arrival window inside your lane capacity — if the math says you can't clear the crowd in time, open earlier or add lanes.