Give Your Editor a Review Note They Can Act On
A useful review note tells the editor where to look, what you noticed and what needs to change. I would separate those three parts before sending feedback. Our explainer uses a simple sequence: start with the timestamp, describe the issue and give a clear next step.
Start with a timestamp
Point to the moment you mean instead of making the editor search the entire piece. For example, a note could begin with ‘At 00:14’. That is an example of how to write a note, rather than a timestamp from a particular client project.
Describe what you noticed
Name the issue in that moment. ‘The name is difficult to read’ gives a clearer observation than ‘something feels wrong’. Then explain the intended change, such as making that name easier to read. Keeping the observation and the requested result together gives the editor a useful target.
Keep one note per issue
If the title and the sound both need attention, give them separate notes. That makes it easier to see which issue each instruction addresses. Before sending the review, I would read each note once more: does it identify the place, explain the issue and say what needs to change? The short animated video gives the same checklist without turning feedback into a long conversation about an unspecified problem.
Optional camera resource from my filming kit. This is a general kit resource, not equipment required to apply the checklist.
Affiliate disclosure: I may earn a commission from qualifying purchases. As an Amazon Associate I earn from qualifying purchases.
Comments