Before proposing a difficult lesson for publication, separate the experience, the evidence and the takeaway. This card helps a buyer decide what can be explained responsibly, what needs review and what should remain outside the film. It is an editorial planning tool, not advice on a dispute or contractual liability.
Describe the learning without naming a culprit
Begin with what your team learned about its own decisions or coordination. “We now confirm this interface earlier” is a different proposition from “another party failed to tell us”. The first can often be explored through your team’s experience; the second may make a consequential allegation requiring a different review process.
This does not mean disguising material facts or presenting a false account. It means identifying the point the audience actually needs before deciding how much sensitive history is necessary to explain it.
If a claim about another party is central, refer it to the appropriate project and legal decision-makers. Do not ask an editor to settle a contested account through tone, music or selective quotations.
Separate observation, interpretation and outcome
Write three lines. What did the speaker directly observe? What did they infer? What changed afterwards? Keep them distinct until the relevant people confirm the connection.
A participant may accurately remember feeling that a handover was unclear without knowing why another organisation acted as it did. A revised process may have been introduced without evidence that it caused a later performance improvement. Those limits should shape the wording.
The film may still contain a valuable lesson when a broad outcome cannot be established. Describe the decision or practice the team adopted, subject to confirmation, rather than adding a result because the ending otherwise feels incomplete.
Establish what the team actually changed
Separate an adopted practice from an interviewee’s suggestion about what might help next time. Ask who owns the practice, when it was adopted and what record or knowledgeable person can confirm that account. If it remains a proposal, describe it as a proposal rather than evidence of organisational learning already put into use.
Then identify the circumstances in which the lesson is relevant and a limit on transferring it elsewhere. A useful takeaway can explain a question to ask earlier on similar work without prescribing a method for every project. This gives the viewer a bounded learning point, even where no later performance improvement has been measured.
Complete the lesson review card
- Specific audience question this lesson answers:
- Experience the speaker can describe first-hand:
- Project fact and source reference:
- Interpretation that needs checking:
- Other party mentioned or implied:
- Information that is confidential, contested or outside the speaker’s role:
- Practical takeaway, stated narrowly:
- Adopted practice or proposed change, confirmed by:
- Practice owner and evidence of adoption, if claimed:
- Circumstances where the lesson is relevant, and limits on transfer:
- Outcome claim, if any, and its evidence:
- Responsible factual reviewer:
- Additional publication or legal review required:
- Proposed wording, alternative wording or decision to omit:
Avoid copying sensitive correspondence into a widely shared production worksheet. Refer the responsible reviewer to the relevant record through the organisation’s approved process.
Test the pictures as well as the words
An apparently neutral interview can acquire a different meaning when cut against a contractor’s logo, an identifiable worker or footage of unfinished work. Ask what the combined sequence suggests about responsibility.
A shot recorded on one day should not silently stand in for an event it did not depict. If suitable supporting material does not exist, discuss another explanation or leave the point out. Dramatic illustration is not a reason to imply an unverified event occurred.
The ACCC’s guidance on misleading claims is a useful reminder to check the overall impression, not isolated words. It does not determine the facts or legal position of a particular project.
A fictional lesson that becomes narrower
A project manager initially proposes saying that a supplier’s mistake delayed the work. The supporting information is incomplete and the explanation is disputed. The actual learning the team wants to share concerns how it now confirms interface information before scheduling a particular activity.
The proposed film is narrowed to that checked internal decision, without claiming to establish who caused a delay or promising that the revised process eliminates future problems. The publication owner still reviews the context. This is an invented example, not a report of a Live Images client or an instruction to conceal a material fact.
Give reviewers a decision they can answer
Send the relevant passage and the intended pictures together. Ask whether the facts are correct, the attribution is fair and the proposed takeaway is supported. A broad request to “approve the video” may hide the exact point that needs judgement.
If reviewers cannot resolve a material issue, mark the passage as held or omitted. Do not treat the absence of a reply as approval. Keep the decision with the current edit record so a later short version does not restore the disputed wording.
A worthwhile lesson gives the audience something specific to understand without overstating what the film can establish. Bring the checked lesson card to the production discussion; the feedback worksheet can help communicate any resulting changes.
Sources and editorial note
ACCC — False or misleading claims — claim accuracy and overall impression. Checked 29 October 2026.
The worksheet and fictional example are original editorial planning guidance. Confirm project facts, permissions and the written production scope with the responsible people. Prepared with AI assistance for Live Images.