Finish the review without losing the thread.

Agree on what this round is for

A rough-cut review and a final approval need different kinds of feedback. Say which decisions are open before you send the link. For a first cut, ask about story and structure. For a final pass, ask the client to check names, text, legal details, and the agreed changes. Name one person who will combine the client team’s notes.

Run one clear round

1. Prepare: the editor checks the cut internally and attaches the correct version to the task.
2. Request: send the review link with a short purpose, deadline, and decision maker.
3. Collect: reviewers leave timecoded comments and annotations on the cut.
4. Triage: the producer resolves conflicting notes and confirms what belongs in this round.
5. Revise: the editor works from the agreed feedback and adds a new version.
6. Close: the decision maker confirms approval or lists the remaining changes.

Write feedback an editor can act on

Use the timecode, the problem, and the requested change. For example: “At 00:18, the title is hard to read over the white shirt. Please add a darker backing.” If you are unsure about the solution, name the problem and let the editor suggest a fix. Avoid scattering the same request across chat, email, and the review.

Make approval lead somewhere

After approval, assign the delivery or publishing step. Confirm the export version and destination before closing the task. If a new request arrives after approval, record it as a new change with an owner and date so it does not quietly replace the agreed final cut.