Ticket Scans

A ticket scan links a ticket code to an event and organization. It can record scan time, admission count, decision time and check-in time. Its status begins in Draft, moves to Submitted for review, and reaches Approved, Rejected or Completed according to the decision and completion checks. The revision helps the reviewer decide on the same scan that the operator submitted.

The admission operator first identifies the parent event. The submission check compares capacity and evidence separately. A scan with a valid ticket code can still exceed available capacity; a scan within capacity can still lack verified provider payment evidence. An independent reviewer records a decision for the submitted revision. Completion waits for persisted capacity and verified provider payment effects. That order makes the scan record useful at a busy entrance and in later review.

• Submission. Freeze the scan revision after checking the event and admission count.
• Decision. Attach an independent review decision to the matching parent and revision.
• Completion. Record the check-in only when the capacity and payment effects are present.

Agree where ticket codes originate and how staff identify duplicates at the entrance. Decide who may submit a scan and which independent reviewer covers each event. The reviewer should see the linked event, capacity, admission count and provider evidence before deciding. A rejected scan needs a clear reason, and the operator should know whether to correct it through a new revision or leave it rejected.

Practice a network retry. The same operation key should not produce two completed check-ins. An operation receipt with a pending or uncertain result should go to reconciliation before someone repeats an external action. The admission count should remain traceable to the event’s reserved and admitted quantities.

At a theater entrance, an operator scans a ticket that admits two people. The operator checks the selected open event, records the ticket code and admission count, then submits the scan. The independent reviewer sees the submitted revision and payment evidence. If the evidence is verified and capacity remains, the reviewer approves it. The operator completes check-in after the effects persist. A second scan of the same ticket prompts investigation of the earlier operation receipt rather than a second admission. If the scan is rejected, its decision and reason remain linked to the event.

• Ticket scan review queue — Submitted scans awaiting a decision.
• Ticket scan board — Scans grouped by their current lifecycle state.
• Completed scans — Check-ins with their recorded admission count and time.

Walk through admission and scans and review and evidence.