Feedback That Actually Makes Your Editor Better

Give timestamped notes tied to the viewer, send them in one batch, and your outsourcing editing costs fall every round because the same mistake stops repeating. Vague feedback is the expensive kind, since it forces the editor to interpret you and interpretation drifts.

Good feedback is a training signal disguised as a correction. Each note either changes this video or changes every video your editor touches for you from now on, and the second kind of note is worth ten times the first.

If you have explained the same note three times, the note is not the problem. Your system for storing notes is.

Timestamps beat adjectives

'The energy dips here' tells an editor nothing they can act on. 'At 04:12 the pause before the answer is two seconds too long' tells them exactly where to click, and they can fix it while your note is still open in the other window.

Pair the timestamp with the reason, always. A reason lets the editor solve the next similar problem alone, which is the entire point of hiring someone. Corrections without reasons keep you in the loop forever.

Write the note while the cut is still playing in your head, then edit the note for clarity before sending. The first version is a reaction, the second version is an instruction, and only one of them is worth paying for.

Talk about the viewer, not your mood

Frames like 'this confused me' invite arguments about your taste. Frames like 'a first-time viewer will not know what that reference means' give the editor a target they can hit without asking how you felt that morning.

Viewer language also survives handoffs. If a second editor or a thumbnail designer reads your notes later, they will understand the goal instead of decoding your preferences. Write notes that age well and stay useful after you forget the conversation.

Send one batch per round

Drip feedback is the habit that quietly doubles your bill. Ten small messages spread over two days produce ten passes of uncertainty, while one list produces one focused revision. Batch it, then leave the editor alone to work.

• Watch the whole cut before writing anything, so your notes describe patterns rather than reactions.
• Group notes by segment, intro, middle, outro, so the editor works down one list.
• Mark each note as required or optional, because priority prevents accidental rewrites.
• Send notes once per round, then wait for the next cut before adding more.

Close the loop

When a note lands well, say so in one line. Positive notes are information too, because they tell the editor which of your rules already stuck and which need repeating in the brief.

Track recurring notes in a shared document. Three repeats of the same correction means the instruction is unclear or the editor is not the fit, and both answers are useful to know before your next upload.

Praise the specifics too. Saying exactly which timestamp worked tells the editor which instinct to trust on the next cut.

Key takeaways

• Timestamp the problem and always state the viewer-facing reason.
• Mark notes as required or optional so priority is never a mystery.
• Send feedback in a single batch per round, never in drips.
• Log repeated notes, since they reveal unclear instructions or a poor fit.