Review product update videos against the actual release

Start with factual claims: behavior, scope, role, availability and timing. Then inspect whether the final composition communicates those facts clearly. A claim can be accurate in the script but misleading when its condition is hidden behind a small label or cut too quickly.

Give reviewers specific responsibilities. The release owner confirms product truth. The production reviewer inspects frames, sound and readability. A publication owner verifies destinations and surrounding copy. One person may hold several roles, but the checks should remain explicit.

• For each scene: time range, claim, evidence reference and verdict.
• For each qualifier: placement, reading opportunity and relationship to the claim.
• For each action: exact interface label and correct role.
• For each result: observed confirmation rather than an invented success state.

This illustrative audit concerns a fictional 30-second update about personal saved views. It describes review findings that could occur; it does not claim a video was rendered or tested.

• 0–5: title says “Save team views.” Evidence says personal only. Required correction: change the title and check the thumbnail for the same claim.
• 5–14: save action uses the approved screen. Reviewer still checks the role and sample-data label.
• 14–23: reopened view shows different filters. Required correction: use the matching example or explain a real state change.
• 23–30: availability card says “All accounts” while rollout is limited. Required correction: use the current eligibility statement.
• Publication note: recheck the corrected encoded file, not only the editing timeline.

Watch the encoded file at normal speed, pause the important frames and inspect it in a compact viewport. Read captions, qualifiers and interface labels where the audience will see them. Listen for narration or audio edits that change the meaning of a sentence.

Open every destination from the publication copy. Check that the linked release note describes the same version and contains the promised details. A valid URL can still point to stale or irrelevant instructions.

Write a finding as an observable issue, its consequence and the required correction. “Make it clearer” leaves the author to guess. “At the saved-view result, retain the Personal label because the current frame implies team sharing” is actionable.

After edits, identify the new file revision and recheck the affected scenes plus any dependent surfaces. Do not carry approval from an earlier export automatically. Record what was actually reviewed and any remaining limitation.