Reusable source footage libraries

The working approach

Store the complete recording with a stable identifier.
Index useful scene timestamps.
Save the brief and output version beside each edit.

Make provenance easy to inspect

A useful source record includes the capture date, product identity, viewport, full duration and a stable file key. A scene record adds start and end times, a description and the state it proves. An output record connects its brief and selected scenes to an exported file. This structure lets an editor answer a simple but important question: which real recording supports this particular claim?

Do not silently replace old originals when re-recording. A mobile retry can improve one source while existing desktop edits remain valid. Mark older material as superseded when the interface changes, but preserve the connection between historical outputs and their inputs. For long-term reuse, inspect whether the product behaviour is still current; a well-organised archive makes that judgement easier but does not remove the need to make it.

A concrete example

Name a scene “filtered-library-results” and record its source interval, viewport and product version.

Before recording this scenario, write down what the starting screen contains and what should be different at the end. This gives the reviewer an observable result to check, rather than asking them to approve a general impression.

The mistake to avoid

Editing from an already shortened teaser compounds quality loss and removes context.

If the source cannot support the intended message, narrow the claim or capture the missing evidence. A transition, caption or voiceover can explain a real change; it should not manufacture one.

Put it into a production brief

Replace the bracketed fields before using this brief. The scenario is illustrative; keep only the actions your product actually supports.

EDITABLE PRODUCTION BRIEF

Purpose: Reusable source footage libraries.
Audience: [specify the viewer and their familiarity with the product].
Decision: [what should the viewer understand or do next?].
Approach: The original recording is a production asset. Keep it separate from short exports so new hooks and formats do not require a new capture every time.

Required evidence:
1. Store the complete recording with a stable identifier. Show the relevant entry state, action and completed result.
2. Index useful scene timestamps. Show the relevant entry state, action and completed result.
3. Save the brief and output version beside each edit. Show the relevant entry state, action and completed result.

Reference scenario: Name a scene “filtered-library-results” and record its source interval, viewport and product version.
Avoid: Editing from an already shortened teaser compounds quality loss and removes context.

Deliverable: [duration], [format], [placement].
Use only recorded product behaviour. Preserve the full original.
Acceptance: check each claim against its visible scene, review at actual viewing size, and test the final file.

Review before delivery

Evidence: can a new viewer identify the result described in the example without being told where to look?
Reading distance: are the relevant controls and labels understandable at the intended placement size?
Continuity: does each cut preserve the relationship between the action and its result?
Accuracy: does the final caption describe the visible product state, including any limits?

Using this with Demovela

The automatic URL workflow currently supports Postraid and Adfolio. Other product scenarios on this page are production-planning examples, not compatibility claims. Adapt the brief to your own recorder or editor. Demovela preserves originals and creates separate outputs; review the resulting file before publishing.

Check the current preview scope →

Keep the workflow moving

Choose the next resource based on the decision you still need to make.

Browse the complete resource library →