RCRAIN CITY
PRODUCTION NOTES

Clear thinking for small productions.

About the publication ↗
Post-production

Give an Editor Video Notes They Can Act On

Use one approved version, precise references and a single decision owner to turn competing reactions into a workable revision list.

“Make it more dynamic” may describe a reaction, but it does not tell an editor which problem to solve. Good review notes connect the reaction to a moment and the project’s purpose. Begin by confirming that everyone is watching the same version. A team discussing different exports can spend an hour disagreeing about a change that has already been made. Put the version name and review deadline in the invitation.

State what this round is for. A first edit may need decisions about structure and message; a later round may focus on spelling, graphics, sound and final details. Ask reviewers to separate those levels. There is little value in polishing a lower-third animation while the group has not agreed whether the interview section belongs in the film. Keep the original brief available so feedback can return to the intended audience and purpose.

Refer to a moment and explain the issue

Use a timestamp or time range and describe what the viewer experiences. “At 00:18, the product name disappears before I can read it” is more actionable than “graphics too fast.” Explain the desired result without prescribing a technical solution unless there is a real requirement. The editor may find a better way to address the problem when the note identifies the communication issue rather than dictating an arbitrary cut.

Tools can help keep those references together. Vimeo’s review-link documentation describes time-coded comments and review management. Check the current features and permissions for the account being used. Whatever tool you choose, test access with a reviewer before the deadline and make sure private material is shared only with the intended people. The process should not depend on everyone guessing how to leave a usable note.

Resolve contradictions before sending revisions

Give one person responsibility for consolidating the client’s response. That person should identify conflicting requests and obtain a decision. An editor should not have to choose between two executives who want opposite opening scenes. Keep genuine alternatives visible while the decision is pending, but send a clear instruction once it is resolved. Mark which notes are required corrections and which are suggestions the editor may interpret.

Separate factual errors from preferences. A misspelled name, incorrect product detail or unsupported claim needs correction. A preference for a different shot needs to be weighed against the brief, continuity and available footage. When requesting a new fact or line, provide the approved wording and its responsible checker. Do not ask the editor to invent a stronger business claim merely because the current phrase feels less exciting.

Keep the history useful

Maintain a record of the note, decision and resolution. Avoid deleting the earlier discussion in a way that makes the next round impossible to follow. If a request is withdrawn, mark it as such. When a new export arrives, review the affected sections and watch the full film once for unintended consequences. A small timing change can affect a caption, music transition or the relationship between a statement and its supporting image.

Ask reviewers to watch with suitable sound and at a useful size, then include a separate check for the intended real viewing conditions. A phone review can reveal small text, while a desktop view may expose different issues. Do not treat either device as the sole truth when the campaign has several destinations. Specify which version and context a note concerns so the editor can apply the change appropriately.

Close the round with an explicit approval or a consolidated remaining list. Silence is not a clear approval record. Name who approved the version and what deliverables that approval covers. Keep that record with the export package. The aim is not to eliminate creative discussion; it is to make the discussion produce decisions the editor can implement without decoding contradictory messages across several channels.