Audit a final MP4

The working approach

Play and decode the whole file.
Check dimensions and audio tracks.
Test seeking and downloading from the hosted URL.

A concrete example

Verify that a portrait export reports 1080 by 1920 and that its public link supports seeking without a workspace cookie.

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

A render job reporting success does not prove a playable hosted file.

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: Audit a final MP4.
Audience: [specify the viewer and their familiarity with the product].
Decision: [what should the viewer understand or do next?].
Approach: Treat export validation as a separate check from editing. Inspect the actual file that viewers will receive.

Required evidence:
1. Play and decode the whole file. Show the relevant entry state, action and completed result.
2. Check dimensions and audio tracks. Show the relevant entry state, action and completed result.
3. Test seeking and downloading from the hosted URL. Show the relevant entry state, action and completed result.

Reference scenario: Verify that a portrait export reports 1080 by 1920 and that its public link supports seeking without a workspace cookie.
Avoid: A render job reporting success does not prove a playable hosted file.

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 →