Showing a design change without implying the original was defective

Establish what each version actually was

Identify whether the material represents an early concept, an option, an approved design, a later revision or a record of the completed work. Those statuses should not be collapsed into a simple “bad before, good after” story.

Ask the project information owner to confirm the date and status of each item. A file name alone may not reliably establish what was current or authorised at a particular time.

Keep superseded material identifiable. It can help explain a genuine decision, but the production team should not mistake it for an instruction or the final arrangement. Use a reference to the approved record rather than copying confidential design information into broad circulation.

Describe the reason using checked information

Write the reason for the change at the level the evidence supports. Perhaps a requirement was clarified, an option was selected or information from another project stage became available. Do not infer a technical defect or failure simply because a revision exists.

Separate the problem being considered from the choice made. A film can explain alternatives and constraints without claiming that every unselected option was unsuitable or that one party should have known the outcome earlier.

If the reason is disputed or sensitive, identify the appropriate reviewer and keep the wording unresolved. The edit should not settle a technical or contractual disagreement by compressing it into a dramatic sentence.

Attribute the decision accurately

Identify who proposed the change, who evaluated it, who approved it and who carried out the relevant work. These may be different organisations or people.

Use verbs that match the actual contribution. A contractor who coordinated installation should not be presented as having designed the change unless that is accurate. Equally, a film can show the contractor's practical contribution without diminishing the designer's role.

For a complex shared decision, select the level of detail the viewer needs. The film does not need every meeting, but it does need enough context to avoid a misleading allocation of credit or responsibility.

Build a dated decision strip

Add a review note beneath the strip:

• Does any wording imply a defect not established by the evidence?
• Could the image order suggest an unsupported cause?
• Are earlier options labelled accurately?
• What technical meaning needs specialist confirmation?
• Which material is authorised for the intended use?

A fictional revision story

A fictional project film shows an early layout option followed by the completed arrangement. The first draft calls the change a correction to a flawed design. The project record instead shows that the client's use requirements were clarified after the option was prepared.

The team changes the story to explain the confirmed requirement and subsequent decision, with the relevant contributors checking their roles. It does not present the existence of a revision as proof of a defect. This example is invented and describes no actual project.

Review the sequence, not isolated labels

Give the responsible specialist the proposed words and the images in their intended order. Ask whether an unfamiliar viewer would understand the status, reason and contribution accurately.

Use the technical explanation worksheet to simplify a checked point, and the shared-contribution worksheet where roles need further clarification. If a diagram or animation is proposed, discuss it as an additional treatment under the agreed production scope. A clear story should emerge from the verified decision record, rather than an invented contrast between failure and success.