Who this is for: Motion producers, technical reviewers and teams approving encoded deliverables.
What to prepare
- Original and revised encoded files with identifiers
- Exact timestamps or frame indices and frame-rate convention
- Approved references and source revisions
- Actual inspection notes and named sign-off owners
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative job format: investigate a heading accent that appears clipped during an entrance. Require the original encoded clip, affected frame and adjacent frames before treating the symptom as real. Record a mask-bound hypothesis separately from the observation. After a source correction, obtain a new encode and compare the equivalent visual state, then replay the interval. Assemble a 30-second review outline: defect evidence at 0–6, hypothesis at 6–13, corrected artifact comparison at 13–22 and actual retest status at 22–30. Deliver the issue register, captured evidence, source revision and sign-off fields. This example specifies a method; it does not assert that any defect was found or fixed.
Make it your own
- ISSUE_RECORDS
- List observed symptoms with exact artifact and location.
- COMPARISON_STATES
- Provide matched original, expected and revised evidence.
- RETEST_PROCEDURE
- State the checks actually performed and their scope.
- SIGNOFF_FIELDS
- Record reviewer, artifact, decision, date and unresolved concerns.
Select review material that proves something
Suitable material includes exact encodes, reproducible source versions and a visible difference the team can inspect. A design preview without the final encode cannot prove a delivery defect is resolved. A vague comment such as “something flickers” needs a location and observed behavior before it becomes an actionable record.
Capture the frame before, affected frame and frame after. Keep a short playback segment when the issue is temporal. Record whether the symptom appears in the file itself or only in a particular player, because those findings lead to different checks.
Organize observation and investigation
Use fields for symptom, expected appearance, suspected cause, proposed check, implemented change and retest evidence. Clipping may suggest masks or bounds; a one-frame jump may suggest timing or scene joins. These are hypotheses, not diagnoses until supported.
Change one plausible cause at a time where practical. If several settings change together, explain that the evidence does not isolate which change mattered. Preserve unresolved questions so the next producer does not mistake an assumption for a verified cause.
Compare equivalent states
Show original and revised artifacts with exact version labels. If timing changed, compare the same visual state as well as the old timestamp. A clean final hold cannot disprove a defect that occurred during entrance. Inspect the relevant neighboring frames and play the interval at ordinary speed.
If the correction affects a shared mask or global scale, inspect other scenes that use it. Keep that regression scope connected to the change. Avoid a generic success stamp that claims every deliverable was checked when only one interval was reviewed.
Make sign-off traceable
A sign-off row needs reviewer, file identifier, checks performed, result and remaining limitations. Include captions, audio, loop seams or alternate formats only when they were actually inspected. Keep the final reel and its evidence register together in the handoff.
This workflow is tool-neutral and can support a production process in Animro or any other tool. The page does not promise automatic defect detection or certify an uninspected render; the evidence must come from the real output.
Review checklist
- Every issue identifies a real artifact and location.
- Observed symptoms are separate from suspected causes.
- Corrections are checked in new encoded evidence.
- Sign-off names the actual inspection scope and remaining concerns.