Practical guide

Make the exception desk a decision point, not another queue with no owner

Last materially reviewed 2026-09-28

Quick answerGive uncertain cases a named owner, a minimum handoff and a clear return instruction.
What to know

Define the boundary

List which cases should leave the ordinary scanning position: unclear entitlement, wrong occurrence, a disputed earlier check-in or a requested order change. The exact list belongs to the organizer. Do not ask volunteers to make decisions outside their training or permissions. The exception route should explain where the person goes and how the next responsible operator learns what has already been checked.

What to know

Pass useful context

A concise handoff can include event scope, the observed message and the checks already performed. It should not include an unnecessary public copy of the ticket or payment details. Use the organization’s private method where identifiers are needed. The receiving person needs enough context to avoid starting the investigation again, but the entire door team does not need access to every customer record.

What to know

Close the handoff explicitly

After a decision, tell the ordinary entrance what outcome they should act on through an agreed channel. Avoid vague statements such as “someone said it was fine.” Record who made the decision in the appropriate private operational record. The website cannot authorize admission or resolve disputes; it supplies a structure for the organizer’s own process. Any financial correction remains a separate authorized task. Agree how the lead returns an answer to the original operator; an unresolved case should not circulate between volunteers without an owner.

What to know

A fictional unclear-order case

A volunteer locates a possible order but cannot determine which member has arrived. They pass the case with the event, observed status and reason for uncertainty. The lead resolves it under the actual policy and returns a clear instruction. Afterward, an anonymous issue category helps improve the briefing. The attendee’s full history does not need to appear in a public lessons-learned document or our local planning tools.

Continue when useful

Next: Door-team roles

Assign scanning, exception handling and administration separately, then verify each person can do their actual job.

Open Door-team roles →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Ticket Tailor: attendee check-in — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
  2. Ticket Tailor: assigning the team to an event — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
DOOR-TEAM BRIEFING

One route for each kind of decision.

SituationImmediate taskOwner or next step
Ordinary valid arrivalApply the event's agreed check-in procedurePrepared door volunteer
Wrong date, absent record or disputed statusKeep uncertainty separate from permission to enterNamed exception lead
Conflicting records after an outagePreserve the scope and explain what remains unknownOrganizer's reconciliation

An editorial workflow, not a substitute for venue safety plans or event policy.