Product video quality assurance

The working approach

Decode the complete export.
Inspect each scene at normal playback size.
Match every headline to an action or state in the footage.

Separate three kinds of approval

Technical approval checks that the complete file decodes, the expected audio exists, the dimensions match the deliverable and the hosted link supports normal playback. Factual approval checks that captions and narration describe the visible product state. Editorial approval checks whether the sequence is understandable and worth watching. These reviews catch different failures; passing one does not substitute for the others.

Inspect each selected scene around its cut boundaries as well as at its midpoint. A midpoint can look clean while the first frame contains a menu or a flash of sensitive information. Then watch the whole export without stopping. Look for narration overruns, abrupt music endings and transitions that make a successful action ambiguous. Keep corrections tied to timestamps and test the final delivered version after any re-render.

A concrete example

Review the first frame, each transition and the final frame, then watch once without pausing and once without sound.

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 contact sheet misses timing problems and audio collisions.

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: Product video quality assurance.
Audience: [specify the viewer and their familiarity with the product].
Decision: [what should the viewer understand or do next?].
Approach: Quality review should test the file, the story and the claims independently. A video that plays successfully can still show the wrong thing.

Required evidence:
1. Decode the complete export. Show the relevant entry state, action and completed result.
2. Inspect each scene at normal playback size. Show the relevant entry state, action and completed result.
3. Match every headline to an action or state in the footage. Show the relevant entry state, action and completed result.

Reference scenario: Review the first frame, each transition and the final frame, then watch once without pausing and once without sound.
Avoid: A contact sheet misses timing problems and audio collisions.

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 →