Knowing which file contains a value is not the same as knowing how that value was produced. If a project film relies on a derived metric, commission a short provenance explanation that identifies the source, the relevant transformation and the resulting value. The audience should not mistake a calculated output for a direct observation.
The W3C PROV primer distinguishes information entities, activities, responsible agents and derivation relationships. A public film does not need that formal vocabulary, but it can use the underlying distinction to make a data story easier to follow.
Trace one consequential value
Ask the client to choose a value central to the approved story and provide a readable account of its origin. The production should not attempt to reconstruct an analytical pipeline from scattered screenshots or filenames.
Identify whether the input is measured, supplied, assumed or otherwise defined. The transformation may be a calculation, aggregation or another documented activity. Keep those roles separate even if the film uses a simple three-stage diagram.
The final value should retain its relevant unit, interval and scope. A provenance graphic cannot rescue a result whose public meaning remains undefined.
Make the transformation visible without teaching implementation
A named activity between source and result is often enough. Avoid decorative code or an unexplained “AI” box that suggests a capability the project did not use. If an analytical method is important, the specialist should approve its public description.
The graphic should also distinguish responsibility from causation. A person's name beside a dataset might identify its supplier, reviewer or analyst; those roles should not be collapsed into one vague ownership label.
Use authorised role labels where personal identities are unnecessary. The audience normally needs the chain of meaning, not private account details or internal usernames.
A hypothetical reporting film
Imagine a project team supplies a dashboard metric calculated from several approved records. The first film shows one sensor and makes the displayed total appear to come directly from that device.
The buyer adds a concise source-to-calculation-to-result explanation and labels the displayed value as derived. The story becomes more credible because the audience can see the relevant reasoning path. This example is hypothetical and does not validate the calculation itself.
Review the sequence by asking which part was observed and which part was produced through analysis. If the answer treats everything as direct measurement, the transformation has been hidden too effectively.
The commission should preserve the client's supported lineage account. It does not include auditing the calculation, certifying the source data or constructing a provenance system. A clear information diagram can explain the evidence chain while leaving technical validation with its proper owners.
Where a transformation has several inputs, identify their different roles instead of drawing every incoming record as equally influential.
Discuss the film
Contact Live Images to discuss whether this approach suits your brief and what production scope would be appropriate.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.