Tell reviewers what is ready to judge
An internal team may inspect a rough scene to find continuity errors before anyone approves the visual style. A client may need to choose between two visual directions without judging temporary dialogue. If the review purpose is unstated, both audiences can provide reasonable but incompatible feedback.
Wrong Opera documents collaborators, client review rooms, comments, change requests and delivery rounds. Those tools can keep feedback near the work. The production team still needs to agree who resolves conflicting notes and what an approval covers; a review room does not create that agreement by itself.
Define the review contract
Each round should name the version, the decision and the intended next action. Invite the people who can contribute to that decision rather than distributing an undifferentiated request for thoughts.
| Element | Internal review | Client review |
|---|---|---|
| Primary question | Does the work function as intended? | Does it meet the agreed brief? |
| Typical detail | Continuity, performance, edit boundaries | Message, direction, suitability for delivery |
| Useful output | Specific repair or recommendation | Approval or bounded change request |
| Escalation | Creative lead resolves production trade-offs | Named stakeholder resolves brief changes |
Review a thirty-second launch scene
Imagine a fictional product film whose brief is to show a lamp making a reading corner inviting. Internally, reviewers find that the lamp changes shape between shots and the actor looks toward the wrong side. Repair or clearly flag those defects before asking the client to approve the mood.
The client round then asks whether the warm, quiet atmosphere matches the brief and whether the product is recognisable. If a reviewer requests a fast comedy scene instead, classify it as a direction change with consequences for story, boards and performance. Do not bury it among minor colour notes.
Close the round with an intelligible decision
Produce a short response to the feedback: accepted changes, questions that need a decision and the version that will be reviewed next. Where comments conflict, record the chosen direction and its owner. Keep the language concrete enough that a new collaborator can understand the decision without reading every discussion.
Before moving forward, check whether any approved upstream decision has changed. A new message can require returning to Story; a different character design can require revisiting Look and subsequent shots. Agree the revised review scope before doing dependent work. This protects the usefulness of an approval without pretending that creative work never changes.
Questions & answers
Should clients see rough material?
Yes, when the roughness is explained and the requested decision is appropriate, such as choosing story direction or reviewing boards.
Does an approval mean no later revisions are possible?
No. It records a decision for a particular version and scope. A later change should identify the affected work and establish a new review decision.
Evaluate the workflow with your production team.