Try the demo(opens in a new tab)
Menu
Try the demo(opens in a new tab) Start free(opens in a new tab) Log in(opens in a new tab)

Running the door: offline lists, re-entry, scanning and what fails

Scanners, the printed list, re-entry, and every decision that takes seconds.

By NightHall · Published 2026-10-14 · 6 min read · door, event-day

Doors opened at 22:00 and there are 2,000 people in the queue. One person scans, another handles what the scanner refuses. That is a screenshot of somebody else's ticket, a name that does not match, or a person who was already admitted an hour ago. Each decision takes seconds and each one has to survive being asked about in June. This article is about that hour.

The scanner is the fast path, not the only path

Every ticket opens the door without an app and without an account. The buyer shows the code on their phone or on paper. The scanner reads it, and the admission lands on the fan record with the gate and the time. That record is what the organizer reads the next morning: who came, through which gate, and when.

The scanner asks NightHall about every code it reads. That keeps the answer current across gates: a ticket scanned at the main entrance reads as used at the side entrance a minute later. Two devices admitting the same ticket while neither can see the other is the failure this design exists to prevent.

The night the network drops

The connection at the venue drops at 23:10 and comes back at 23:40. This happens often enough that the plan assumes it. The door admits buyers with no network, through the scanner and a printed door list. Every pilot event keeps a printed door list as the fallback.

Print the list before doors, per gate, sorted so a name is found in seconds. Mark admissions on paper while the network is down, and reconcile against the system when it returns. When the signal comes back, both attempts on one ticket are real. One of them is wrong, and the door lead is the one who says which. That decision needs the paper record. Memory does not survive the night.

Re-entry, decided before doors

Re-entry is a policy, not a scanner setting. Decide it before the night and print it on the ticket. Does a scanned-out guest come back in on the same code, with a stamp, or not at all? The scanner enforces whatever the organizer set. The queue does not wait while staff debate it.

Festivals with camp sites need re-entry across days. Club nights usually do not. Either way the rule is the same for every gate, and the door lead can state it in one sentence. A guest who hears one rule at the main entrance and another at the side entrance stops believing both.

Guest lists live beside the tickets

The guest list is not a second system. Names, plus-ones, crew, press and the artist's contact sit on the same door view as scanned tickets. The door lead sees one queue rather than two. The reference cast keeps it concrete. The artist's contact, first aid and production each hold a place on the list. Each scans or signs the same way.

Keep the list closed at a stated time. A guest list that grows during the night is a queue that never moves. Publish the closing time to everyone who holds list places before doors.

What fails on the night

  1. A screenshot of somebody else's ticket. Refuse it, and point at the

transfer: the holder changes the name before the night.

  1. A name that does not match. Check the order with the order number and

the email address, then decide.

  1. A duplicate scan. One admission stands, the other does not, and the

door lead records which.

  1. A dead device. The printed list takes over that gate until a charged

replacement arrives. Bring chargers and one spare device per gate.

  1. A queue that stops moving. Open the paper lane: list check while the

scanner lane clears.

None of these is a software problem on the night. Each is a staffing and paper problem the software supports. The organizer who prints the list, charges the spares and briefs the door lead has handled most of the night before 22:00.

Brief the team in ten minutes

Ten minutes before doors, the door lead states five things. Which gates are open, the re-entry rule in one sentence, and where the printed list sits. Who decides duplicates, and when the guest list closes. Five sentences, then positions. Staff who heard the rule state it to guests. Staff who did not invent one per guest.

Keep one radio channel for the door and one decision-maker on it. The scanner lane, the paper lane and the guest lane each report problems to the same person. Two decision-makers admit the same duplicate twice.

After the doors close

Every scan lands on the fan record, so the organizer knows who came and through which gate. That record feeds the next presale: it opens first to the fans scanned in that night. The no-show list feeds the re-engagement. The door is not the end of the event cycle. It is where the audience for the next one is recorded.

Ticket Tailor treats its check-in app the same way, as event-day tooling with its own product notes rather than a feature bullet. The pretix blog publishes post-mortems when its own event tooling breaks, with the cause and the fix. Both habits are worth copying: the door deserves its own notes, and failures deserve a written cause.

What NightHall runs at the door

The scanner, the gates, guest lists, the live door view and the printed door list. The door works with no network and every conflict stays visible. The door lead opens the gates, hands out the scanners and decides the awkward cases.

Sources

All articles