Two records can look identical when a software demonstration first creates them, yet behave differently when one changes. A linked reference may continue to point to a source; an independent copy may have its own subsequent life. A film that shows only the initial appearance leaves that distinction unresolved.
Before commissioning the sequence, ask the product owner which relationship the demonstrated action creates. Avoid using duplicate, clone, link and copy as interchangeable narration. The approved explanation should follow the actual product terminology while making the relationship understandable to someone who has not used the system.
Make the later change part of the story
Choose a harmless field whose change can reveal the relationship. A fictional project title, descriptive note or display label may be suitable. Do not use a sensitive account setting or a live business transaction merely because its effect is dramatic.
Show the source and destination with recognisable identities. If the screen recording uses two nearly identical tabs, add clear editorial labels that do not resemble native product controls. The viewer should know which record is being edited and which is being inspected afterwards.
Distinguish shared content from shared location
A record appearing in two places does not, by itself, tell the audience whether two objects exist. Ask the product owner to describe the actual relationship in one sentence. The film can then choose the smallest useful visual demonstration of that sentence.
For a fictional supplier portal, a specification summary might be referenced from several project pages. An update to the source appears wherever that reference is displayed. A separate copied summary in another project remains unchanged. Showing those outcomes side by side would explain the distinction more clearly than repeatedly zooming into the action menu.
Only include that comparison if both behaviours genuinely exist in the demonstrated product. A hypothetical storyboard is useful for planning, but it must not become a claim about an unverified feature.
Keep permissions out of the inference
A relationship between records does not automatically establish who may edit each one. If the demonstration needs to explain permissions, identify that as a separate question. Do not let a successful source edit imply that every person viewing a linked record has the same authority.
Likewise, do not imply that deleting a visible reference deletes the source unless the product owner confirms that behaviour. The current film may need only to explain the continuing connection; adding several destructive cases can obscure the central idea.
Review the change rather than the resemblance
At approval, ask what would happen if the source label changed tomorrow. The answer should follow the relationship the sequence has established. If reviewers rely only on the fact that the records originally looked alike, the film has not yet done its job.
Retain the demonstrated source and destination identifiers with the recording notes. That allows later revisions to reproduce the same relationship instead of replacing it with a superficially similar pair of records. The result is a clearer explanation of reuse, not merely a polished animation of a copy command.
Discuss the proposed explanation with Live Images and confirm suitability, production scope and the content owner’s review responsibilities. This unpublished draft uses a fictional example, not a claimed client project.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.