Production schedule

The audience sees only a small part of production activity. Equipment must arrive, rooms must become available, systems must be installed and departments must test their work together. A production schedule connects these activities to venue access and programme commitments. It should explain how the event becomes ready, not merely list supplier arrival times beside the doors opening time.

The run of show concentrates on the live programme. The production schedule provides the surrounding working framework, including technical rehearsals, presenter access and removal. Keeping that distinction clear helps planners avoid allocating the same room simultaneously to installation crews, a speaker briefing and a client walkthrough. Each activity may be reasonable individually while the combined plan remains impossible.

An activity can start only when its prerequisites are satisfied. A scheduled lighting focus is not credible if the approved installation is still incomplete, and a presentation rehearsal cannot fully test playback while the media system remains unavailable. Ask department leads what they require before starting, what they will hand over and how completion will be confirmed.

Some work can overlap; some cannot. Confirm that judgment with the responsible professionals rather than assuming simultaneous tasks always save time.

A schedule assigns resources as well as hours. The same technician cannot support two rehearsals in different rooms, and a shared loading route cannot serve unlimited deliveries at once. Include briefings, meal arrangements, shift changes and necessary rest in workforce planning. Fatigue and rushed handovers can undermine a timetable that appears efficient on paper.

Put contingency beside the uncertainty

Allow realistic recovery time where access, content readiness or complex integration creates uncertainty. An unexplained spare period at the end of the day may not help if an earlier missed handover blocks every department. Contingency should protect specific dependencies. Its presence is not permission for teams to ignore agreed starts, and using it should trigger a review of the remaining work rather than conceal an emerging delay.

For each activity, show the location, start, finish or duration, responsible lead and completion condition. Include the event date explicitly, especially when work continues overnight. A line labelled testing needs enough context to distinguish a department checking its equipment from a combined test involving several teams. State which issue controls if a venue timetable and supplier schedule disagree.

• Identify access restrictions and the contact authorized to resolve them.
• Separate crew call times from vehicle arrival and work-start permissions.
• Mark milestones that require acceptance before the next activity begins.
• Issue revised schedules with a clear version and a summary of consequential changes.

A site visit can reveal physical constraints that need to become explicit schedule assumptions rather than informal knowledge held by one planner.

Imagine an Abu Dhabi conference using a main hall and a smaller rehearsal room. Both teams request the same presentation technician during the afternoon. The first draft lists each rehearsal separately and appears feasible until the resource conflict is noticed. Meanwhile, a shared service corridor limits when equipment can move without interfering with other venue activity.

The production manager consults the venue and department leads, then staggers equipment movement and rehearsals. The main hall receives its combined test before presenters arrive, while the smaller room begins with a content review that does not require the technician. The revised schedule identifies each handover and preserves a genuine soundcheck rather than absorbing it into general setup. This hypothetical solution changes the sequence instead of asking one person to cover incompatible commitments.

When a milestone slips, assess the downstream effect before moving every remaining row forward. Some commitments may be fixed, while other tasks can be resequenced or reduced with approval. Department leads should explain the consequences of shortening their allocated work. Required inspections, competent staffing and safety procedures must not become discretionary simply because earlier activities took longer.

Record decisions that change scope, access or readiness expectations. If a rehearsal loses a segment, identify what remains untested and who accepts the resulting operational limitation. Keep the approved baseline available alongside current revisions so the team can distinguish an authorized adjustment from a forgotten task. After delivery, compare planned and actual handovers to improve future estimates without turning the review into a search for blame.