Key Takeaways
- The master production schedule contains: the pre-production timeline (week 12 to week 1), the load-in schedule (minute by minute), the show schedule (the run of show), and the load-out schedule
- The pre-production timeline is a Gantt chart — each task has a start date, a completion date, an owner, and a dependency on which subsequent task it gates
- The load-in schedule is a vehicle and crew movement document — not an abstract task list
- The show schedule is the run of show — per our run sheet guide, cue by cue in absolute clock time
- The master schedule is owned by the show-caller from week 10 — all changes go through them
The pre-production timeline structure
The pre-production timeline is typically a Gantt chart in Google Sheets or a project management tool. The rows are tasks; the columns are weeks. Each task has: a task name, the department responsible (production company, client, venue, specific supplier), the start date, the target completion date, the dependency (which earlier task must be complete before this task can begin), and a status (not started, in progress, complete, at risk). Key milestone rows — concept approval, AV specification lock, vendor contract completion, content submission deadline, run of show issue — are highlighted as critical path items. The chart is shared with the client at the first production meeting, updated weekly, and reviewed in the production status call.
The load-in schedule structure
The load-in schedule is a minute-by-minute document covering the period from first vehicle arrival at the venue to show open. Its structure: a time column (in 30-minute increments), a task column (what is happening at that time), a responsible party column (which supplier or crew department), and a notes column (any special instructions or dependencies). The schedule must show: when each supplier's vehicle is expected at the loading dock (staggered to prevent dock congestion), when each supplier's crew begins their specific task, the sequence of interdependent tasks (staging before PA rigging, PA rigging before lighting), the breaks for crew catering, and the times for the PA line check, lighting focus, and technical rehearsal. This document is issued to all suppliers at week 2 — not on load-in morning.
The backwards planning framework
Start with the event date. Work backwards: Week 0 = event day. Week 1 = load-in begins. Week 2 = final content lock, all pre-production complete. Week 3 = run of show desk review, speaker briefings. Week 4 = content submission deadline. Week 6 = all vendors contracted. Week 8 = AV specification approved, stage design approved. Week 10 = concept presented, budget approved by client. Week 12 = brief received, site visit completed. This backwards structure makes the client's approval gates visible — if concept approval happens at week 8 instead of week 10, the vendor selection moves to week 4 and the content submission deadline moves to week 2. The compression cascades.
Client approval gates
The approval gates that consistently delay Indian corporate event productions, in order of frequency: budget approval (internal sign-off processes that take 2–3 weeks longer than anticipated); content submission from speakers (speakers miss the deadline, submitting at week 2 content that was due at week 4); and creative concept approval (design-by-committee processes where 6 stakeholders each request changes sequentially). Build each approval gate into the production schedule with a target date, a named approver, and an escalation path if the approval is late. Approvals that are assumed will happen within 2–3 days consistently take 2–3 weeks.