Event day runbook

What belongs in an event day runbook

Your event day runbook is the single source for time-stamped contacts, lane maps, and decision trees. It should fit on a laminated card per supervisor and a PDF in every group chat. Include load-in times, power locations, Wi-Fi SSIDs (if any), and explicit event gate supervisor phone order—who answers when line one goes dark.

Gate staffing plan and crowd math

Derive gate staffing plan from peak ingress, not average queue length. For Indian outdoor shows, add hydration and shade roles adjacent to scanning lanes so medical incidents do not masquerade as ticket disputes. Rotate scanners every 60–90 minutes—fatigue drives misreads and rude tone, which sparks viral clips.

• One “debug” lane for exceptions so VIP lanes do not absorb chaos.
• Radio discipline: codewords for medical, security, and tech.

Ticket scan failure protocol

Document a ticket scan failure protocol: retry scan, adjust brightness, try paper backup, verify ID against purchase name, then escalate to supervisor with order ID. Never let a volunteer invent refunds—only finance-approved roles. Log device IDs when failures cluster; that is how you spot dying batteries or bad firmware.

Duplicate QR ticket handling

A duplicate QR ticket event triggers when the same entitlement enters twice—sometimes fraud, sometimes a couple sharing a screenshot. Policy should distinguish “already redeemed” from “counterfeit.” Train staff to de-escalate: offer box-office research, not public shaming. If your platform supports live revocation, supervisors should know the exact taps.

Scanner failover plan and offline behaviour

Your scanner failover plan must include spare hardware, power banks, and SIM swaps. If the system runs offline, define how long sync can lag before you pause sales at the window. On-site event operations teams should rehearse this the night before—not during soundcheck confusion.

Briefing and volunteer clarity

Event volunteer briefing should be under 30 minutes with role play on red/yellow scans. Provide Hindi and English cheat sheets at each lane. Thank volunteers with food and shade—caring for them is part of crowd control ticketing because calm staff calm crowds.

Finlo customers often centralise these workflows digitally; whether paper or pixels, the principle is the same: predictable steps beat heroics. Use this structure as your Finlo gate operations baseline and adapt per venue.