Door scan playbook: how to run scanning at small to mid-size events

May 24, 2026 · 10 min read · Intermediate

The door scan is where every prior decision in your event becomes physically real — buyers either get in or they don't, lines either move or they pile up, and the difference between a smooth night and a chaos night is usually 30 minutes of preparation no one made.

This guide is the operational playbook for door scanning at small to mid-size events (anything from a 50-cap bar to a 500-cap club). Larger venues with dedicated security operations need more, but the fundamentals are the same.

1. Hardware

You need three pieces of hardware, in this order of priority:

1. One scanner phone (primary). Any iPhone or Android from the last 5 years. Browser supports the camera, that's the only requirement.
2. One scanner phone (backup). Different staff member. If primary phone dies / breaks / freezes, backup is ready.
3. Paper list of all buyer names (alphabetical). Last resort if both phones fail. Print 24 hours before event.

What you don't need: a dedicated scanner gun, a tablet, a ticket printer, a card reader (you're not selling at door via the scanner — separate concern), a "scanning kiosk." All overkill for <500 cap events.

Phone-specific setup

• Charge to 100% before doors open. Camera + browser drains battery fast.
• Lock orientation to portrait. Prevents accidental rotation during scan.
• Enable Do Not Disturb. Notifications interrupt camera focus.
• Bookmark the scanner URL on home screen so it's one tap away.
• Pre-load with WiFi 30+ minutes before doors. Lets the page cache valid tokens.

2. Staffing the door

For under 100 capacity: 1 person can run scan + greeting solo if line trickles in.

For 100-300 capacity: 2 people minimum — one scans, one greets + manages line + handles questions. Splits the cognitive load so the scanner can focus on the camera.

For 300+ capacity: 2 scanners running in parallel + 1 floater for questions + 1 person inside the door confirming wristbands if you use them. Lines build fast.

Brief your staff on the 4 things they'll see:

3. Physical door layout

Spend 10 minutes day-of thinking about flow:

• Line forms outside, scan happens at threshold. Buyer holds phone up before reaching scanner, scanner sees it ready.
• One side scans, opposite side is exit + walk-up sales. Don't mix entry and exit traffic through the same door.
• Visible signage. "Have ticket ready" sign 10 feet before door. Reduces fumbling at scan point.
• Bathroom + bar visibility from line position. Helps buyers orient themselves once they're in.

4. The actual scan flow (per buyer)

Optimal flow per buyer is 5-8 seconds:

1. Buyer holds phone up at chest height, screen facing scanner (1 second)
2. Scanner aims phone camera at QR, 6-12 inches away (1-2 seconds)
3. Green tick appears (instant)
4. Scanner says "Welcome, head right in" (2 seconds)
5. Buyer walks through, scanner readies for next person (2 seconds)

Bottleneck is usually buyers who haven't opened the email — they're fishing in their inbox while a line forms behind them. Solutions:

• Pre-event email reminder 4 hours before doors: "Open your ticket email now so you're ready at the door."
• Signage at line: "Have your ticket QR open before reaching the door."
• Train staff to gently ask "Got your ticket ready?" to buyers 3 spots back in line.

5. Edge cases

"I bought a ticket but can't find the email"

Have them search their email for the event name. If still nothing, have them try "find my tickets" on your event platform (POCtix has this at /find-tickets). If that fails too, look them up in the admin orders list by their name or email. If they're in the system, manually mark them admitted in the admin and let them through.

"I tried to buy a ticket and it didn't go through but I see it on my card"

Common Stripe scenario: charge succeeded but webhook failed to create the pass. Look them up by email; if no order exists, refund the Stripe charge directly and have them buy fresh. If order exists but no pass, create a manual comp pass.

Pass shows "Already scanned"

Either: (a) two people are trying to use the same screenshot of one ticket (fraud) or (b) the buyer accidentally got scanned twice (bouncer's mistake). Quick triage: ask the buyer's name, check against the original purchase. If names match, let them in (it was a double-scan error). If not, polite challenge.

Phone camera won't focus

Either too close (move back to 6-12 inches) or low light (turn on phone flashlight, point at buyer's QR from above). Most modern phones auto-focus within 1-2 seconds.

6. Offline mode

If your venue's WiFi or cell signal flakes mid-event, a good scanner keeps working off cached tokens. POCtix's scanner pre-loads all valid passes for the event when first opened with connectivity, then validates locally. Scans sync back to the server when network returns.

For platforms without built-in offline mode: print a paper list of every buyer's first + last name + order ID. If WiFi dies, you check names manually against the list.

7. Wristbands + re-entry

If buyers leave and come back (cigarette breaks, food truck runs, late-night smokers), you have two patterns:

• Wristband on first entry. Scanner gives green tick, staff applies wristband. Re-entry = wristband visible, no re-scan needed. Best for events >100 cap with re-entry common.
• Re-scan allowed. Scanner lets the same pass through multiple times. Best for very small events or events where you don't care about exact in/out tracking. Doesn't catch double-use if buyer hands their phone to a friend outside.

POCtix supports both modes — set in event config whether passes are single-scan or multi-scan.

8. What to track + measure

After the event, pull these from your admin:

• Total passes sold vs total scanned. Tells you actual attendance rate. Typical bar/club events run 75-90% of pre-sold buyers actually showing.
• Peak scan rate (per minute). Tells you whether you need 1 or 2 scanners next time.
• Time-distribution of scans. Most events have 60% of scans in the first 30 minutes after doors. Useful for staffing.
• Refund / void rate. If >5% of tickets get refunded pre-event, there's a marketing-message-mismatch problem.