Event operationsTemplateGated

Live Issue Log Template

Record material operational issues as they arise, route them to escalation contacts and monitor status through a live Dashboard. The editable workbook includes reference data, contacts and one dedicated issue log. It supports event operations and handover, but it is not a statutory incident report, emergency record or substitute for required reporting to authorities, insurers, employers or other responsible bodies.

Browse event operations resources

Format
XLSX
Difficulty
Intermediate
Time
30 min
Stage
Run

What this resource helps you do

  • Capture the essential live issue log template inputs in one place
  • Hand off a consistent template across event operations owners
  • Reduce last-minute gaps before the run milestone
  • Reuse the structure for the next event operations cycle

When to use this resource

  • Before doors to preload areas and escalation contacts
  • During event delivery when a material issue is identified
  • At handover or debrief to review unresolved items

What is included

  • live-issue-log-template.xlsx
  • XLSX download package
  • Instructions: Guidance for consistent live logging.
  • Reference Data: Controlled values used in the issue log.
  • Escalation Contacts: Named contacts for routing material issues.
  • Live Issue Log: Working operational issue record.
  • Dashboard: Summary of issue status for command review.

Information required before starting

  • Operational areas and reference values
  • Escalation contacts
  • Issue details, time, owner and current status

What you produce

  • Live issue register
  • Escalation contact reference
  • Dashboard view of issue status

Who this is for

This resource is designed for Event organisers and Operations managers who need a practical, reusable document for event operations.

  • operations manager

    Owns issue quality, escalation and handover.

  • event organiser

    Uses the Dashboard to understand live operational exposure.

Event-type use cases

  • festival

    Tracks issues across zones and operational areas.

  • conference

    Supports central logging of venue, programme and attendee-impacting issues.

How to use this resource

  1. 1

    Prepare reference data and contacts

    Load operational areas, status values and current escalation contacts before opening.

  2. 2

    Create one row per material issue

    Record clear facts as soon as an issue is identified.

  3. 3

    Assign and escalate

    Name an owner and route urgent matters through the agreed escalation path.

  4. 4

    Update status and resolution

    Keep the row current so the Dashboard and handover remain useful.

  5. 5

    Separate statutory reporting

    Follow required incident or emergency procedures outside this operational log.

Common mistakes to avoid

  • Combining unrelated issues in one row — Create a separate record for each issue needing its own owner or outcome.
  • Treating the log as a statutory incident report — Use the organisation's required reporting process for reportable incidents.

Download files

Unlock this resource above to download every included file. Companion files do not need a separate form.

Live event operational issue log — editable XLSX

Editable workbook with Reference Data, Escalation Contacts, Live Issue Log and Dashboard sheets for show-day issue coordination.

When to choose it: Use at the operations or command desk as the maintained log of material live issues.

XLSX · 15 KBLocked

Frequently asked questions

Frequently Asked Questions

What counts as a material issue?+

Log matters needing ownership, escalation, cross-team visibility or a recorded resolution.

Is this an accident or incident form?+

No. It is an operational issue tracker and does not satisfy statutory or organisational reporting duties.

Can it be used without the command-centre runbook?+

Yes. It stands alone, while the runbook adds wider roles, decisions, contacts and handover context.

When should an issue be closed?+

Close it only when the resolution, decision or transfer is recorded and the accountable owner confirms the next state. Keep follow-ups open.

Tell me more