A package-by-package seminar can leave viewers with a list of disciplines but little understanding of how their work connects. Commission an explanation that follows one information dependency across the packages. The subject is what one contributor needs from another and why the status of that information matters.
This differs from filming a project programme presentation. Dates may provide context, but the useful editorial question concerns the content of the handover. A coloured arrow between package names is not enough if nobody explains what the arrow represents.
Name the input precisely enough to discuss
Ask the receiving contributor to describe the information they need in ordinary language. Then ask the supplying contributor what they can provide at the stage being discussed. Check the terms with both parties before turning the relationship into a graphic.
Identify whether the seminar concerns an agreed input, a provisional assumption or a request still being defined. These states should remain visible. A polished diagram can otherwise make an uncertain relationship appear settled simply because every box has a label.
Select evidence that supports the explanation without exposing unnecessary project detail. An approved extract or simplified example may be adequate. The subject owners must confirm that the simplification retains the dependency that matters.
Show the consequence of a changed input
Ask the receiving speaker what question would need reconsideration if the input changed. The answer should explain the relationship, not offer technical instructions for redesigning the package. A bounded consequence gives the audience a reason to remember the dependency.
The supplying speaker can then explain what status information accompanies the input. Avoid turning that discussion into an unsupported promise about delivery dates or completeness. The film should reflect the authorised account available for the seminar, with unresolved matters stated as such.
If the dependency cannot be explained without a long chain of other packages, narrow the commission. One intelligible connection is more useful than a network graphic whose complexity conceals every actual exchange.
A hypothetical multidisciplinary review
A hypothetical design seminar considers how a room-use requirement informs several packages. The initial presentation follows the organisation chart. The buyer instead commissions a sequence in which the client states the requirement, one discipline explains the input it develops and another identifies the part it relies on. A possible change is discussed only to show which question would reopen. The film does not become a release schedule or a direction to proceed.
The viewer now understands why an apparently small unresolved input attracts attention across the team.
Accept the connection between contributors
Have a reviewer draw the selected dependency after viewing and label what passes across it. If they can reproduce only the names of the organisations, the substantive explanation is still missing.
Ask both subject owners to approve the final relationship and its stated status. Keep any programme commitments in their authorised project source. The recording should make the information exchange understandable while leaving formal release and change decisions where they belong.
Discuss suitability
Contact Live Images with the proposed subject, audience and intended use to discuss suitability, scope and availability.
Editorial note
Original commissioning guidance prepared with AI assistance. Hypothetical examples are invented, not Live Images projects. This unpublished resource makes no engineering, legal or performance guarantee.