A large-scale event is a distributed system of interdependent decisions — and like any distributed system, its reliability is determined not by its best-performing component but by its worst. The show management workflow is the architecture that prevents a weak link in one department from cascading into a systemic failure across the production. Building this architecture well is a discipline that combines production management, project management, and operational systems thinking in a way that few single-discipline professionals fully master.
The Show Bible: Building a Single Source of Truth
The foundational tool of large event show management is the show bible — a living document that contains every confirmed operational decision, technical specification, timeline, and contact that any production team member might need. In contemporary production, it lives in a cloud-based project management platform — typically Notion, Airtable, or the event-specific platform ShowSync — accessible to all departments from desktop and mobile.
The show bible structure for a large event should include: show timeline with minute-by-minute running order, technical specifications for every department, contact hierarchy including emergency contacts for every vendor, venue rules and restrictions, catering schedules, artist and speaker technical riders with change log, risk assessment and safety documentation, and contingency protocols for every identified failure scenario.
Departmental Integration
The structural challenge of large event production is that each technical department — audio, lighting, video, staging, automation, rigging, broadcast — develops deep expertise within its own domain and necessarily focuses on its own deliverables. This departmental specialisation is essential for technical quality but creates integration blind spots where critical interdependencies go unmanaged. The lighting department’s power draw schedule may conflict with the audio department’s generator allocation; the video department’s cable routes may clash with the staging department’s deck layout.
The solution is structured cross-departmental briefings at defined production milestones: initial design review six to eight weeks out, technical design freeze three weeks out, site preparation review one week out, and daily production meetings from load-in through show day. Each briefing should explicitly cover integration points — the moments where departments’ work intersects and could create conflict.
Runsheet Design That Departments Can Use
The show runsheet is the document every department uses to organise their on-site work. Modern show management practice favours departmental runsheet views — tailored subsets of the master timeline filtered to show each department the information relevant to them, while maintaining a master view for the production manager. Tools like Lumi Events and ShowFlow provide multi-view runsheet platforms where a single master document generates department-specific feeds, eliminating the version control problem that plagues Excel-based runsheet management.
Real-Time Communication Infrastructure
On the day of a large event, the communication infrastructure is as important as any technical system on site. A well-designed production communications stack typically includes: a channelled radio system using Motorola MOTOTRBO or Hytera DMR with department channels, a programme interrupt system via Clear-Com for cued content, a group messaging platform like Slack for non-urgent communication, and a dedicated production office with hardwired telephone backup.
Risk Registers and Decision Trees
Every large event production carries operational risks that can be anticipated and mitigated in advance. The risk register — a systematic inventory of potential failures, their likelihood, their impact, and the pre-planned response — provides the production team with pre-authorised decision trees that dramatically speed up response time when an issue occurs during a live show. Covering technical failures, personnel risks, weather contingencies, and content delivery failures transforms reactive scrambling into managed response.
Post-Show Review and Institutional Learning
The show management workflow doesn’t end when the last guest leaves. The post-show debrief — conducted within 48 hours of the event while experiences are fresh — is the mechanism through which production organisations convert live experience into institutional knowledge. A structured debrief covers what went to plan, what didn’t, what corrective actions were taken, and what process changes would prevent recurrence. Productions that invest in this cycle build compounding operational advantage over those that treat every show as a standalone event.