Agree what this review is meant to decide
State whether the team is reviewing story, boards, performance, a rough cut or final delivery. Include known limitations so placeholders do not generate unnecessary work. Name the person who resolves conflicting feedback and the place where the decision record will be maintained.
Ask reviewers to describe what they experienced before prescribing a change. “I cannot tell why the character leaves” identifies a story problem. “Add another close-up” proposes one possible answer but may not explain what that image needs to accomplish.
Copy the review header and individual note
Use the header once for the round and repeat the note block for each issue. Keep a stable scene or shot reference alongside a time reference, since timings can move after edits. Mark priority according to its effect on approval, not how strongly someone prefers the change.
Include a preservation field for successful choices that a revision could accidentally remove. Useful praise can be an instruction to keep an effective pause, reaction or transition.
PROJECT / REVIEW ROUND:
MATERIAL AND VERSION:
REVIEW PURPOSE / KNOWN LIMITATIONS:
REVIEWER / DECISION OWNER:
NOTE ID:
SCENE / SHOT / TIME REFERENCE:
OBSERVATION - WHAT I SAW OR HEARD:
INTENDED VIEWER EFFECT:
PROPOSED SOLUTION (if any):
PRIORITY - BLOCKER / REFINEMENT / OPTIONAL TEST:
WHAT SHOULD BE PRESERVED:
ACCEPTANCE CHECK:
DECISION / REVISION OWNER:
STATUS - OPEN / RESOLVED / DEFERRED:
RESOLUTION NOTE:Worked illustration: an unclear story detail
The fictional note below identifies why the envelope matters, while leaving room for the editor to choose the most effective correction. It also protects the existing hesitation, which could disappear if the scene were simply shortened.
The acceptance check can be used on the next cut. It does not require the team to adopt the first proposed solution if another change communicates the intended information more clearly.
Consolidate requests and close the loop
Before assigning revisions, combine duplicate notes and resolve contradictions through the decision owner. If one reviewer asks for a longer pause and another asks for a faster scene, identify the audience effect each wants before issuing instructions.
After revision, record whether the original issue is resolved, deferred or still open. Check enough surrounding context to catch new problems created by the change. A closed note should explain the decision briefly so a later reviewer can understand why the work looks the way it does.
Questions & answers
Should all feedback become a revision?
No. Record it, assess its effect on the agreed goal and make an explicit decision. Optional preferences and changes to the brief need different treatment from errors that prevent approval.
What if a client sends feedback in several places?
Consolidate the relevant notes into one current record and confirm unresolved contradictions before work begins. Keep the source context available so the summary does not change the intended request.
Evaluate the workflow with your production team.