How to Review the Impact of a Production Change

Establish the current agreement

A request to change the event can arrive as a message, a revised programme or a new file. Before acting on it, establish what the team is currently preparing to deliver.

Identify the current brief, programme, supplier scopes, working schedule and relevant departmental documents. Record the versions and the decisions they represent. Where the documents disagree, resolve the baseline with their owners rather than selecting whichever version makes the request easiest to accommodate.

The baseline can contain open items. Keep those visible so the review can distinguish a new consequence from uncertainty that already existed.

This work sits within production advance. A change review focuses that coordination on the difference between the current arrangement and a particular request.

Describe what is being requested

Record who requested the change, what they want to achieve and when a decision is needed. Be specific about the difference: a presentation becoming a live remote conversation creates a different requirement from replacing a slide in the same presentation.

A request identifies the desired result. Supplier availability describes what could be provided. Approval records who has accepted a particular arrangement and its consequences. Keep those states separate throughout the review.

If someone says a change is approved, ask which decision that approval covers. Agreement to the programme idea may leave additional work, cost, venue permission and technical assessment unresolved.

Trace the consequences across the event

Start with the changed requirement and ask what must be different for it to happen. Follow each dependency into the work of other teams.

A remote conversation may affect programme duration, incoming video, room audio, what the remote participant hears, content ownership, supplier operation, participant availability and rehearsal. The person receiving the request needs those interfaces assessed together, even when separate teams deliver them.

Review the production schedule against the revised work. A task needs its inputs before it can be checked, and a rehearsal may need several teams and participants together. Moving one programme row does not establish that the preparation can happen.

Ask each affected owner whether their current scope still applies, what changes and what they need from others. Record a reason when an item is assessed as unaffected. An old confirmation should not silently become confirmation of a new requirement.

Obtain decisions within the right authority

Agree who provides, delivers, coordinates and approves the work. These functions may belong to different people.

The programme owner may approve the audience-facing choice. A budget owner may accept a revised cost. Suppliers must confirm their delivery scope. Relevant specialists assess the technical arrangements within their competence, and the venue confirms matters within its authority.

The coordinator brings these decisions together. A coordination record does not grant technical design authority, certify capacity or replace an inspection. If a change needs specialist assessment or venue approval, retain that dependency until the responsible party supplies the required decision.

For an artist requirement, use How to Advance an Artist Technical Rider to manage the artist documents and approval route. Then trace any consequences for the wider event through this review.

Work through a change from recorded content to a live conversation

Consider a fictional conference preparing from brief version 3, run of show version 4, production schedule version 2 and agreed supplier scope version 2. The programme includes an approved recorded interview. The video supplier's agreed work covers playback; the audio supplier's scope describes playback sound in the room. A rehearsal is planned, but no remote guest test or call operator is included in the working arrangement.

The programme lead requests a live conversation with the same guest instead. The intended audience segment remains in the same position. The client has approved exploring the idea, but has not approved additional supplier work or a revised cost. The recorded interview remains the current agreed segment while the request is reviewed.

The coordinator records the request against that baseline and asks the affected teams to assess the consequences:

One suggested response is to replace the recorded segment with the live call and use the existing rehearsal allocation without a joint test. The programme lead rejects this option after the coordinator makes the unresolved guest availability, operation and audio/video interface visible. Changing the programme label would leave preparation-critical questions unanswered.

The team instead develops an option with an owned call operation scope and a joint test opportunity. The suppliers describe the additional work, and the client budget owner approves the quoted addition. Each supplier accepts its revised delivery scope. Those decisions authorize the agreed work and spending; they do not establish that the live conversation has passed its checks.

The programme owner approves the live conversation as a conditional programme option. The condition is that the guest's test availability is confirmed and the responsible teams complete the agreed checks. The recorded interview remains the agreed alternative. The programme owner will decide which segment is used at the recorded decision point before the final programme handover.

The coordinator issues a preparation revision identifying the additional accepted work, conditional programme option and open items. The brief, supplier scopes, responsibility record, schedule and run of show each reference the same change record. The run of show retains the recorded segment as the current delivery instruction until the programme owner's selection is issued. The live option is identified as pending, so recipients can distinguish preparation authorization from an instruction to use it during the show.

The audio and video leads identify the checks needed for the changed arrangement. These include the intended picture and conversation audio, what the guest receives, call operation and the handover to the next programme segment. The content owner confirms which recorded file is the current alternative. The coordinator tracks the test arrangement and outcomes without declaring the systems accepted on behalf of those teams.

At the end of this worked record, guest availability and venue access remain unresolved and the checks have not happened. The next action is to obtain those answers, then record the responsible teams' results for the programme owner's selection. If the live option cannot meet the agreed decision conditions, the programme owner can issue the recorded choice and the teams must confirm its current content and preparation. Neither choice becomes ready merely because its paperwork has changed.

ILLUSTRATIVE SCENARIO

Issue a handover that can be acted on

Give each affected team the current requirement, accepted scope, applicable approval and remaining dependencies. Identify the documents superseded and the version recipients should use. Include rejected options where they explain why a tempting shortcut should not reappear in preparation.

Record who received the revision and who has confirmed the effect on their work. Receipt shows that information arrived; it does not prove that the revised work has been accepted or checked. Follow up separately where either remains outstanding.

Use a compact record containing the baseline, request, affected work, decisions and conditions, open actions with owners and deadlines, revised documents, recipients and rechecks. The detail should be enough for a delivery team to understand its task without reconstructing several conversations.

Recheck what the change has affected

Ask the responsible teams which earlier checks or confirmations no longer apply. Identify what must be repeated, what new checks are needed and what evidence will close each item. Do not prescribe a universal test sequence or shorten checks to preserve a preferred programme time.

Record results against the actual revised arrangement. If a check exposes another change, bring it back through the relevant assessment and decision route before updating the handover.

A change review is useful when the team can distinguish what was requested, what was accepted, what remains open and what still needs verification before use.