Event Check-In and Door Operations That Actually Scale

Great marketing dies at a slow door. Guests forget the flyer, the lineup, and the lighting. They remember standing in a queue for forty minutes while one person squinted at a phone.

Nigerian venues add their own difficulty: heat, generator noise, patchy network, and entrances that were never designed for a thousand people arriving in the same twenty minutes. Tickethub.ng check-in is built around QR first with a search fallback, but the software is the easy part. This guide is about the operation around it.

Five principles that keep a door fast

1. QR first, manual second. The moment staff start with manual search, throughput collapses.
2. More scanners beat one hero phone. Three average scanners outperform one excellent one, every time.
3. Separate ticket types when volumes differ. VIP and media need their own lane even when the numbers are small, because those guests arrive with higher expectations.
4. Train on rejects before doors open. Hesitation at a reject is what turns into an argument.
5. Protect the main line. One calm desk, slightly aside, absorbs every edge case.

Speed is a design choice, not a talent. If you brief staff five minutes before doors, you will invent process under pressure and it will be bad process. Write a one-page door plan and tape it near the entry.

Re-entry rules deserve their own line here. Whatever you told buyers must match what the scanner enforces. Ambiguous re-entry is how a night generates both arguments and duplicate tickets.

The week before

People

• Invite door leads as access managers from the event dashboard. They can scan without seeing your organiser settings, pricing, or payouts.
• Send a short briefing: what VIP looks like, what to do with a screenshot that will not scan, and exactly when to escalate rather than decide.
• Name one person who owns decisions on the night. Not the busiest scanner.

Kit

• Charge every phone. Pack power banks, and pack more than you think.
• Test scanning on the same network type you will use on site, whether that is venue Wi-Fi or mobile data.
• Confirm a used ticket rejects correctly. This one check catches most configuration mistakes.
• Print a lightweight attendee export only as a last-resort backup, and only if the venue is known for total network failure.

Geometry

Walk the physical entry the day before if you can, at the same time of day. Count how many people can stand in single file without blocking a road, a hotel lobby, or a fire exit. Bad geometry creates worse queues than bad software, and no amount of extra scanners fixes a two-metre gate.

Staffing maths

Start from one active scanner per 150 to 250 guests arriving in the same window, then add a supervisor who holds no phone and watches flow. Adjust from there:

Rotate staff so scanners stay sharp. Tired eyes misread reject states, and a misread reject is how a paying guest gets turned away. Water and a real break plan are operations, not hospitality.

Know your crowd. Campus events spike hard right after lectures. Nightlife surges late and all at once. Conferences arrive in a polite trickle then all at 08:55. Staff the surge shape, not the headcount.

Lane design at the venue

• Put signage where people naturally join the queue, which is rarely where you want them to.
• Label lanes by ticket type only when those types are large enough to justify it.
• Keep the manual desk slightly aside. This is the single highest-leverage layout decision you will make.
• Decide in advance whether table hosts enter through VIP or general, and tell security.
• Use cones or stanchions if the venue allows. Improvised human walls collapse the moment friends try to cut.

Outdoors, protect screens from glare. Indoors in a dark club, train staff to ask guests to raise brightness before anything else. And keep a path for guests who cannot stand in a packed queue. A respectful side process is part of professional door culture, not a favour.

During doors

Open scanners a little before advertised entry. Watch the first twenty scans closely, because most early problems are staff technique or guest screenshots rather than platform failures.

When a QR fails, the order is: brightness, then search by email or ticket code, then manual desk. Never invent a paper workaround that creates duplicate entry risk.

If reject volume suddenly spikes, stop and diagnose before adding phones. Rising already used rejects usually means screenshot sharing. Rising not found rejects usually means a promoter is circulating a link to the wrong event.

Keep one shared status chat for door leads and the organiser. Payment disputes go to a named person, never to whoever is holding the busiest scanner.

After the rush

Once peak entry passes, reduce scanners to one live station for late arrivals and release the rest. Then, while it is fresh:

• Review check-in logs for no-show rates and reject patterns.
• Compare actual arrival times against your advertised door time. If guests arrive an hour late every single event, change the marketing clock rather than the complaint tone.
• Note who should lead next time, and write down one concrete improvement.
• Thank the door team properly. They absorbed the hardest hour of your night.

Failure modes and what to do

A 60-second script for every scanner

Give each person the same six steps, and rehearse three rejects before doors: already used, not found, and wrong event. Confidence on rejects is what keeps a line honest.

1. Greet the guest.
2. Ask for the QR.
3. Scan.
4. Wait for the success state, then wave them through. Not before.
5. On failure: brightness, then search, then manual desk.
6. Never improvise a refund, an upgrade, or a plus-one.

Door-day checklist

• Access managers invited and briefed
• Sample ticket scanned successfully on the site network
• Used-ticket rejection confirmed
• Power banks packed and phones charged
• Lane signs printed and placed at the real join point
• Manual desk assigned and positioned aside
• Re-entry rule confirmed and matching what buyers were told
• Named decision-maker reachable all night