1. Start with the exact version.
Open the file the editor should change and record its title or version. For video, include a time point. A comment about an older cut can reintroduce a problem that is already fixed.
2. Describe the change, then the reason.
“At 00:12, replace the second sentence because the service name is incorrect” is more useful than “This part feels off.” When the issue is tone or pacing, describe the intended effect and point to the moment that misses it.
3. Separate corrections from preferences.
A factual error or missing disclosure needs a clear correction. A stylistic preference benefits from a short reason or reference. Mark which is which so the editor can prioritize without guessing.
4. Resolve conflicting direction.
Collect the required reviewers’ notes in one place. If one person asks for a faster edit and another wants more detail, agree on the priority before requesting the revision.
5. Approve the finished version clearly.
Review the revised file and its caption together. An approval should identify the final version. New edits after approval need another check when they change the content or its meaning.
Bring this to your next handoff
- Exact file and version identified
- Time point or location included where relevant
- Requested change and reason are specific
- Required reviewers’ notes are consolidated
- Final asset and caption are approved together