Product Video Consistency Checklist: Viewers Shouldn't Spot Errors for Us
Product video errors are not limited to a single color discrepancy. They can also be factual conflicts between appearance, actions, interfaces, and versions. This checklist follows the shot order to verify sample states and continuity, returning issues to the responsible stage before delivery.
Project Production Guide
Go to the relevant chapter based on the actual project issue.
- 01
Establish the product baseline for this film first
- 02
Record state changes in shooting order
- 03
For continuous actions, check the starting point and result first
- 04
The master and derivative versions share the same factual baseline
- 05
Return continuity errors only to the responsible stage
In brief
Turn appearance states into explicit confirmation checkpoints so the team can move forward according to the project process.
Six Key Steps in Project Execution
- Common Misconception
Establish the product baseline for this film first
Consistency checks begin by establishing a baseline for the current model's appearance, color, accessories, interface, and functional state, rather than relying on everyone agreeing that it looks close enough. Baseline images and reference materials are dated, so every subsequent asset can be traced back to the same reference. The team shares one set of product information that can be checked by eye.
- Requirement Divergence
Record state changes in shooting order
Cleaning, assembly and disassembly, charging, interface updates, and contact with props can all change the sample, so record its state on set in shot order. Mark different bodies or software versions separately so editing does not quietly switch products within a single action. Asset labels must include the body number, software version, shot number, and shooting time.
- Production Principle
For continuous actions, check the starting point and result first
Check the person's hand gestures, product position, opening and closing direction, screen feedback, and object count between adjacent shots, rather than checking color alone. The shorter the footage, the more easily cause and effect can be hidden by jump cuts, so key operations should retain enough context before and after. Continuity is treated as product accuracy, not merely an art detail.
- Confirmation Checkpoint
The master and derivative versions share the same factual baseline
Horizontal and vertical crops, short cuts, subtitled versions, and versions for different markets can change the pacing, but they cannot change the model, operating conditions, or product conclusion. Review each version against the master baseline item by item. When a conflict is found, locate it in the specific asset. The difference log should state the market, aspect ratio, model, shot number, and person responsible for processing.
- Project Risk
Return continuity errors only to the responsible stage
When an issue comes from the sample, camera position, performance, graphics, or editing, send it to the corresponding stage for correction instead of reopening the entire film. Keep sections that are already stable locked. The repair record should explain why the previous version cannot continue to be used, and rework items should specify the filename, timecode, responsible stage, and reviewer.
- Getting Started
Ask an unfamiliar viewer to conduct a factual review
Before delivery, have someone unfamiliar with the shooting process watch the film continuously and record what changes they believe have occurred to the product. Any change that cannot be explained by the script should be checked against the baseline until viewers no longer discover factual contradictions for the team. The final viewing gives real understanding the opportunity to validate the internal baseline.
Put the Key Choices in One Table
| Item | Description |
|---|---|
| Point 01 | Turn appearance state, action continuity, and version consistency into separate project confirmation checkpoints. |
| Point 02 | When a difference in one detail could break the entire timeline, confirm the Brief, responsible owner, and approval criteria for this stage. |
What to Confirm Before Project Kickoff
What project issues is the product video consistency checklist mainly suited to addressing?
It helps the project lead organize the brand, product, sales, procurement, and production teams around appearance states, and turn the discussion into a defined scope of work and deliverables.
Can the action continuity checklist be used directly as a production plan?
No. The checklist is used to confirm sample states, action transitions, on-set verification records, and missing materials. The specific creative concept, production resources, scope of work, and schedule still need to be determined based on this Brief.
What situations can affect continued progress on version consistency?
When the issue is only discovered during editing and there is very little room for remediation, when the responsible owner has not yet confirmed, or when the required materials are incomplete, complete the Brief first. Then schedule on-set confirmation, determine whether additional shooting is needed, and proceed with version consistency work.
For appearance states, we will organize action continuity and version consistency into responsible owners, key checkpoints, and approval criteria so the project can move forward in stages.
The decision-makers and material providers for this round should attend a short meeting and record their answers and deadlines separately in the failure sample log.
