Skip to content

Still improving UX Peeker — full access is free for now.

All posts
August 20, 2026·8 min read

How to Give Feedback on Video Editing (So Your Editor Can Actually Use It)

A practical guide to giving video editing feedback that gets acted on — for YouTube creators working with editors, and for video agencies collecting notes from clients. Timestamps, phrasing, round limits, and the questions to settle before the first cut.

Learning how to give feedback on video editing is the difference between a cut that lands in two rounds and one that limps through six. The notes themselves are rarely the problem — most people know what they dislike. The problem is that video feedback is usually delivered in a format an editor cannot act on: a paragraph in a WhatsApp message, a voice note, or a call where someone describes a moment they cannot quite find again.

This guide is for both sides of that exchange. If you are a YouTube creator sending notes to an editor, it will get your revisions turned around faster. If you run a video agency and your clients send you notes, it doubles as something you can forward to them at the start of a project.

Why video feedback is harder than feedback on anything else

Give someone a document and they can highlight a sentence. Give them a design and they can point at a button. Both of those live in space — you can indicate a location and both people are looking at the same thing.

Video lives in time. To point at something, you have to describe when it happens, and humans are genuinely poor at this. The moment you noticed the music swelling is not the moment it started swelling. By the time you reached for the keyboard to note the timestamp, two seconds had passed. So you write “around 0:47,” the editor scrubs to 0:47, hears nothing wrong, and now you are both annoyed.

Everything below is a way of working around that one structural problem.

The four rules of usable video feedback

1. Anchor every note to a timestamp

A note without a timestamp is not a note, it is a mood. If your tool does not attach timestamps automatically, write them by hand in mm:ss and err early rather than late — an editor would rather rewind two seconds than hunt forward through a scene.

✗ Vague

The intro feels a bit slow.

✓ Clear

0:00–0:12 — the intro runs about four seconds long before the first hook lands. Can we cut straight from the cold open to the title card?

2. Say what is wrong, not what to do

This one is counterintuitive, and it is where most creators go wrong. Prescribing a fix (“add a zoom here”) locks your editor into your solution, which is usually not the best one available — they have the timeline open and can see three options you cannot. Describing the problem (“this shot sits too long and the energy drops”) lets them solve it properly.

Prescribe only when the fix is non-negotiable: brand rules, a legal disclaimer, a sponsor requirement. Everything else is a symptom to report, not a repair to specify.

✗ Vague

Put a whoosh sound effect at 1:20.

✓ Clear

1:20 — the cut between the two scenes feels abrupt and I lose the thread. Something to smooth the transition?

3. Separate errors from taste, and say which is which

An error is objectively wrong: a misspelled lower third, audio that clips, a jump cut that was not intentional, the wrong logo. Taste is a preference: pacing, music choice, colour grade, how long a joke breathes.

Editors treat these completely differently. Errors get fixed without discussion. Taste notes are a conversation, and an experienced editor may well push back — that is what you are paying them for. Mixing both into one undifferentiated list forces them to guess which of your notes are open to debate, and most will simply do all of them, including the ones where they were right and you were wrong.

Labelling each note “fix” or “preference” takes three seconds and changes how the whole round is handled.

4. Send all of it at once

Drip-feeding notes across an afternoon is the single most expensive habit in video review. Every message restarts the editor’s context, and worse, later notes routinely contradict earlier ones — you ask for a tighter intro at 2pm and a longer establishing shot at 4pm, and by then the first change is already made.

Watch the whole cut. Take notes as you go, but send nothing. Watch it a second time before sending, because roughly a third of first-pass notes resolve themselves once you have seen the full arc. Then send the list.

Bad notes and better versions of the same note

These are the phrasings that come up constantly, and what the editor actually needs instead.

✗ Vague

Can you make it more punchy?

✓ Clear

2:10–2:40 — this section drags. The cuts are around four seconds each; can we tighten to two and drop the second B-roll shot?

✗ Vague

The audio sounds off.

✓ Clear

3:05 — the voiceover is noticeably quieter than the previous section, and the music is competing with it.

✗ Vague

I don’t love the colours.

✓ Clear

1:30 onwards — skin tones look orange compared to the earlier interior shots. Can we match them to the 0:40 setup?

✗ Vague

Something feels wrong at the end.

✓ Clear

8:12 — the outro card appears before the last sentence finishes, so the sign-off gets cut off mid-word.

The pattern is the same every time: a timestamp, an observable fact, and the reason it matters. If a note has all three, an editor can act on it without replying to ask what you meant.

Questions to settle before the first cut

Most painful revision rounds are traceable to something nobody agreed on at the start. If you are an agency, these belong in your intake form. If you are a creator hiring an editor, ask them yourself before any footage is handed over.

  • 1How many revision rounds are included, and what counts as a round? A round is a batch of notes, not a single note.
  • 2What is the target length, and is it a hard limit or a rough aim?
  • 3Who supplies music, and is it licensed for the platform this is going on?
  • 4Which platform and aspect ratio is the master for — and are vertical cutdowns in scope or a separate job?
  • 5Are captions or subtitles included, and burned in or as a separate file?
  • 6What is the turnaround time for each round, and does the clock start when notes are sent or when they are complete?
  • 7Who has final sign-off? Name one person. Feedback from a committee with no decider is the most reliable way to reach round six.

That last one matters more than the rest combined. When three people send conflicting notes and none of them can overrule the others, the editor is not editing any more — they are negotiating.

How many rounds should a video actually take?

For a straightforward edit against a clear brief, two rounds is a reasonable target: one substantive pass on structure and pacing, one polish pass on detail. Anything beyond three usually indicates a brief problem rather than an editing problem, and the fix is upstream — a clearer reference, a tighter script, or a named decision-maker.

If you are an agency, write the round count into the quote and define what a round is. “Unlimited revisions” sounds generous in a proposal and reliably becomes the least profitable line on your invoice.

Fixing the format, not just the phrasing

Every rule above is a workaround for the same underlying issue: the person giving feedback has to manually describe where in time they are pointing. Get rid of that step and most of the problem disappears on its own.

That is what timestamped video review does. Instead of typing “around 0:47,” the reviewer clicks the frame where the problem is, and the comment attaches to that exact second. The editor opens the note and the playhead is already there. No scrubbing, no rewatching, no “can you send me a screenshot of what you mean” — which is, when you think about it, you asking your client to do your job.

It also fixes the batching problem quietly, because notes accumulate in one place rather than arriving as a stream of messages, and it fixes the accountability problem, because every note carries the name of whoever left it.

See how timestamped comments work on a real cut — upload a file or paste a link, and clients review without an account. Video review tool

For YouTube creators working with an editor

A few things specific to the creator–editor relationship, which is usually ongoing rather than project-based.

  • Build a reference folder, not a reference sentence. “Like MrBeast” means nothing; three specific clips with the exact moments you like means everything.
  • Send your notes in one document per video, kept in the same place every time. Editors working with several creators cannot hold your preferences in their head.
  • Repeat notes are a systems problem. If you have asked for the same thing three videos running, it belongs in a style guide, not in a revision round.
  • Say what worked. Editors calibrate on positive signal as much as negative, and an all-criticism note list teaches them nothing about what to keep doing.
  • Give the thumbnail and title their own review pass. They are a separate craft from the edit and get lost when bundled into a list about pacing.

For agencies collecting client notes

Your problem is the reverse: you are receiving the feedback, and you cannot dictate how a client behaves. What you can control is the format you hand them.

  • Never ask for notes over email or chat. You are guaranteeing untimestamped, drip-fed, unattributed feedback and you will absorb the cost of that.
  • Send one review link and make it the only channel. If notes arrive elsewhere, politely redirect them into the link rather than transcribing them yourself.
  • Do not make the client create an account. A signup wall between a client and a two-word note means the note does not get left, and it resurfaces later as a phone call.
  • Confirm the round is complete before starting work. “Is that everything?” prevents the note that lands twenty minutes after you have begun.
  • Keep the thread attached to the timestamp after the fix, so the next round has the history rather than relitigating a decision from two weeks ago.

The short version

Good video editing feedback is timestamped, describes the problem instead of prescribing the fix, marks the difference between an error and a preference, and arrives all at once from one named decision-maker. Everything else is detail.

If you take one thing from this: the note “around 0:47 the music gets weird” costs your editor four minutes of scrubbing and one reply asking what you meant. The note “0:51 — music jumps up under the voiceover and I lose the line” costs them nothing. Same observation, same effort to write, entirely different outcome.

See it in action

UX Peeker lets you pin feedback right on the live site — free to start.

Start reviewing free