Track live incidents with time, location, owner, severity, status, escalation, and resolution notes — so production, security, and vendors share one event-day issue timeline.
“If it is not on the issue log, it did not happen for debrief — one timeline beats five parallel chat threads.”
A short preview of the fields and sections included in the full template pack.
Use this spreadsheet at the command desk to log every material incident during show day: who reported it, where it happened, who owns resolution, and how it escalates. It is built for showcallers, production managers, security and vendor desks, and agency producers who need one shared issue timeline — not parallel threads.
An editable XLSX live issue log with priority guide, escalation contacts, zone list, live resolution summary, and post-event review — the incident spine beside your run-of-show, not a substitute for medical or legal reporting packs.
• Showcallers and deputy showcallers tracking programme-impacting issues • Production managers coordinating vendors, crew, and site services • Security and access leads logging crowd or perimeter incidents • Agency producers accountable for client debrief and follow-up owners
Before doors, complete Escalation Contacts and Areas / Zones. During the show, add one row per material issue — assign Owner and Escalation contact immediately. Review Resolution Summary at each showcaller sync: open count, P1 open, overdue rows, and follow-ups. After close, export open items into Post-Event Review.
The Event-Day Command Centre Runbook defines desk roles, comms channels, and escalation matrix. This template is where those paths become timestamps: the runbook tells you who to call; the issue log proves what happened and when. Use the same zone codes and escalation names in both.
EventSuite Production Ops connects schedules, tasks, vendors, workforce, and reporting so live issues reference one programme model. Download the template for the desk ritual; explore production ops software or book a demo to run digital ops sheets and audit trails alongside your XLSX.
Connect checklist rows to the product modules teams use for live delivery.
Venue handover context when live issues affect front-of-house and booking teams.
Explore module →Connect live issue triage to ticketing support and front-of-house handoff.
Explore module →See how show-day coordination fits planning, staffing, and reporting.
Explore module →Link incident owners to shift coverage and supervisor escalation paths.
Explore module →Resolve access exceptions with credential and zone context during show day.
Explore module →More practical resources from the EventSuite library.
Use this event production checklist to plan run sheets, crew tasks, suppliers, venue and site readiness, accreditation checks, live handovers, issue tracking, and post-event reconciliation before the show goes live.
View resource →Run sheet template for show-flow timings, cues, crew owners, supplier notes, and handovers — the live timeline production teams use from load-in through strike.
View resource →A runbook for showcaller and ops desks: roles, comms channels, escalation matrix, live change protocol, vendor and crew touchpoints, and handoff to strike — one spine for event-day command.
View resource →It is a structured spreadsheet to record incidents during an event: time, zone, category, priority, owner, escalation, resolution, and follow-up. The downloadable XLSX includes summary formulas for open, overdue, and P1 counts.
The runbook is the desk reference for roles, comms, and escalation paths. The issue log is the live timeline of incidents. You use both together on show day.
The workbook includes a Priority & Severity Guide with P1 (critical), P2 (material), and P3 (local) definitions. Align these with your site escalation matrix before doors.
Many teams start with the XLSX at the desk, then move live issue tracking into EventSuite Production Ops for shared visibility and reporting. The template remains useful for offline backup and debrief export.
Connect resource owners to ticketing, vendors, payments, and reporting modules so operational work stays tied to live delivery.
