Event Check-In Operating Runbook
Prepare gates, devices, operators, validation outcomes, offline policy, escalation, and post-event review.
Why this work needs a system
Gate pressure turns small ambiguities into inconsistent admission decisions. A runbook gives operators one response path while reserving policy exceptions for supervisors.
The useful test is whether another authorised team member can see what happened, what should happen next, and which exception still needs attention. A tool helps only when the operating rule is clear enough for people to follow under pressure.
A practical workflow
From preparation to review
- 01Prepare
Confirm event data, ticket groups, gates, devices, batteries, accounts, and network conditions.
- 02Brief
Train operators on valid, duplicate, expired, invalid, wrong-group, and override outcomes.
- 03Open
Run test scans at every gate and verify time, sound, display, and assignment.
- 04Operate
Monitor queues, device health, pending syncs, and supervisor requests.
- 05Close
Stop admission, synchronise devices, export results, and record unresolved exceptions.
Operating checklist
Use this before rollout
- Gate map and ticket-group policy are current
- Devices are approved and charged
- Operators use individual access
- Test tickets cover every outcome
- Offline and reconnect drill is complete
- Supervisor channel is staffed
- Post-event owner and export location are named
Limits and failure modes
Where Nox-Tickets fits
Nox-Tickets provides the product surface for this workflow, but configuration does not replace ownership, training, exception policy, or live verification. Review the current capability and status pages before relying on it in production.
