Video Editing Feedback Examples: 12 Vague Notes Rewritten Into Fixes
Twelve vague notes I see every week, from make it pop to the logo feels off, each rewritten as a timestamped, range or drawn comment an editor can fix in one pass.
A 90-second video cut at 25 frames a second has 2,250 frames in it, and when a client writes back "the middle drags a bit", the middle third alone is 750 of those frames. So the note is basically pointing at 750 frames at once and asking the editor to guess which ones felt slow, right, and then everyone acts surprised when the next version misses too.
Feedback like that reaches my editing agency almost every week, and to be very honest the client is rarely wrong about the feeling, because something really does sag. The note carries the feeling without the location, right, so my editor burns a whole round hunting for it. I've already argued why that hurts in the piece on vague client feedback, so this time I wanted the thing I actually send people, a bank of examples where each vague note sits next to a version an editor can act on in one pass.
These are the video editing feedback examples I keep coming back to, 12 of them across pacing, color, audio, and text or logos, each rewritten as a frame-accurate timestamped comment, a range comment, or a drawing on the frame. All 12 sit on one imaginary cut, a 90-second coffee launch video with the founder talking to camera, B-roll, a music bed and a logo end card, so the timecodes stay consistent. Whether you're the editor pasting these into a kickoff message or the marketer giving the notes, I'm pretty sure your second cut will come back closer than your first ever did.
What makes video editing feedback usable
That frame math is just frame rate multiplied by duration, but it changes how you read a note. I think about a note the way a workshop thinks about a technical drawing, where a line with no dimension on it is still a sketch, right, and nobody on a shop floor cuts metal from a sketch. A usable note carries four dimensions, the place, what you felt as a viewer, what you'd like instead, and the reason, which almost always ties back to the goal of the video, like reaching the price sooner or keeping the logo readable on a phone.
- Where it happens, as a timestamp, a range or a drawing
- What you felt while watching
- What you would like instead, even roughly
- Why it matters for the goal of the video
- One issue per comment, never a list
Professionally the place gets written as SMPTE timecode, hours, minutes, seconds and frames, so 00:00:31:12 means 31 seconds and 12 frames into the cut. The catch here is that no client should ever have to type that, right, and on a proper review link they don't, because they pause on the moment and the comment gets stamped to that exact frame on its own, which is the whole idea behind time-coded annotations. So below I write plain times like 0:31.
At this moment I felt this, because of what I saw, could we try that, so the video gets closer to its goal. Every one of the twelve rewrites below follows this one sentence.
Pacing feedback examples, before and after
Pacing notes come out the vaguest of all, because pace is felt across time rather than seen in one frame, which is basically why rhythm sits right next to emotion and story in writing on film editing, so most of the good versions here end up as ranges.
1. The middle drags
When a client says the middle drags, they usually mean the video says the same thing twice. On our coffee cut two customers in a row say it tastes smooth, so the viewer feels that repetition as slowness, right, even though neither clip is slow on its own.
Range comment, 0:31 to 0:43: Both customer clips here say the coffee tastes smooth, so it feels like we're repeating ourselves, can we keep the second one, drop the first, and get to the price sooner?
2. It feels slow at the start
Holding on an empty kitchen looks lovely in the edit suite and loses people on a phone, and for YouTube or Reels the retention drop points behind editor notes show exactly where viewers leave.
Range comment, 0:00 to 0:04: We sit on the empty kitchen before anyone speaks and I think people scrolling will leave here, so could the founder's first line start by 0:01 with the kitchen shot moved under her voice?
3. The ending is abrupt
Timestamped comment at 1:26: The logo card cuts in on the last word of "order today", so it feels like the video got chopped off, can we hold on the founder for about a second after she finishes and then fade to the logo?
The middle drags a bit, can you tighten it up somehow
From 0:31 to 0:43 the smooth taste point repeats, keep the second clip and reach the price sooner
None of these rewrites tells the editor which frame to cut on. They give the place, how it felt and what the video needs, and leave the craft to the editor, which is the right split, because a client who writes "cut at exactly 0:33:08" is usually wrong about the frame and right about the problem.
Visual and color feedback examples you can copy
Color is where clients feel least qualified, so they write the vaguest words, because grading is a whole craft with its own vocabulary. A client only has to point at the thing and compare it to something real, like the actual product or the shot just before.
4. Make it pop
"Make it pop" can mean brighter, more saturated, faster, louder, more text and so on, so the first thing I ask is, pop compared to what? For instance, in most product videos it turns out the client means the product.
Timestamped comment at 0:12: The coffee bag looks greyish against the white counter, but the real bag is a deep red, can the product shots match the packaging so it stands out?
5. The colors look off
Range comment, 0:22 to 0:29: The founder's skin looks a lot more orange here than in the shot just before at 0:21, can these two shots match so it doesn't feel like a different day? I'm watching on an iPhone.
That last line about the device matters, because plenty of color notes I've chased came from a phone with a warm night filter on, and knowing the device tells the editor whether to regrade the shot or just reassure the client.
6. This shot looks cheap
"Cheap" rarely points at the camera, and far more often it means something in the frame is pulling focus from what the shot is for.
Drawing on the frame at 1:10, circling the cable on the left edge and the half-open drawer behind the founder: These two things keep pulling my eye away from the cup she's holding, can we crop in past them or use the other take?
Audio and music feedback examples
Audio notes are tricky because you can't draw on a sound, so the timecode and the spoken words carry the whole note. On the Agency and Enterprise plans, AI transcription adds a clickable transcript, which pairs really really well with notes like these.
7. The music is too loud
Range comment, 0:05 to 0:18: The music covers the founder when she says "single origin" and I had to replay it to catch the words, can the music dip under her voice through here and come back up after?
8. The music doesn't feel like us
Taste notes are completely fine, right, they just need an anchor that isn't another adjective.
Timestamped comment at 0:00: This track feels like a gym ad to me, while our brand is more slow Sunday morning, so something closer to soft acoustic guitar would fit, and I've pasted two reference tracks in the reply below.
9. Something sounds weird
"Something sounds weird" sends an editor through all 90 seconds with headphones on, while the rewrite sends them straight to one frame.
Timestamped comment at 0:58: There's a click right after she says "roasted", I hear it on headphones but not on my laptop speakers, can we clean that up?
Frame-accurate note, everyone sees the exact same thing.
Text, graphics and logo feedback examples
10. The logo feels off
Drawing on the frame at 1:28, with a line where the Instagram caption bar sits: The logo is too close to the bottom edge and the caption will cover it, can we move it above this line and make it about 20% smaller?
The "about 20%" is the part most people skip, and it's the part that saves the round, because without a degree the editor nudges, you nudge back and the logo does laps. A note like this should only ever be given once, right, so in my agency it goes into the client's brand Playbook, which sits on the Agency and Enterprise plans, as a permanent rule every editor reads before that client's next video.
11. The text is hard to read
Timestamped comment at 0:48: The white price text sits on the light counter and I can't read it on my phone, could it move to the darker left side or get a dark bar behind it?
12. Fix the typos
A note that just says fix the typos makes the editor proofread every caption again, while the client already knows which ones they saw, so the rule is one typo per comment, and each fix gets answered in its own thread.
Timestamped comment at 0:52: The caption reads "freshly grounded" and it should say "freshly ground", and at 1:04 I've left a separate comment because "Sumtra" is missing a letter.
When a range comment beats a single timestamp
Across these examples of video edit notes, the rule I give my editors is simple, if the problem has a duration use a range, and if it's an event use a single timestamp. Notes 1, 2, 5 and 7 are ranges because repetition, slow openings, color mismatches and music levels live across time, and a single mark at 0:31 tells the editor where the trouble started but never where it stopped. Notes 3, 9, 11 and 12 are single moments where a range would just be noise, does that make sense, right?
The pitfall is a 40-second range, which is just a vague note wearing a timecode, and my rough rule is that anything past about 15 seconds is two notes pretending to be one. On the editor's side the loop closes in the same thread, right, you reply "trimmed in MV2, have a look from 0:31", the new cut stacks onto the same card, and on the Agency and Enterprise plans you can play MV1 against MV2 side by side so the client sees the fix. That loop is most of what cutting revision rounds comes down to, and trust me on any level, it's why the slow part of video editing turnaround time is almost never the editing itself.
When drawing on the frame says it better than words
Anything about where something is, position, framing, a crop, a distracting object, reads faster as a drawing than as a paragraph, which is why notes 6 and 10 were drawn. Writing "the thing slightly left of the cup, behind her shoulder" still gets misread, while a circle takes one second.
A circle on the frame tells the editor where to look, and one sentence under it tells them what to do about it.
A drawing on its own is still ambiguous, right, because a circle could mean remove it, brighten it, move it or keep it, so I ask clients to add one sentence under the mark, which is how drawing and markup works best. With the Premiere Pro panel the editor then sees that comment inside Premiere, clicks it and the playhead jumps to the exact frame. Some editors even write "notes must be pinned to a moment" into the feedback clause of their video editing contract template, and you see what I mean here, at that point these examples stop being a nice idea and become the agreed standard.
Frequently asked questions
What do good video feedback examples have in common?
Good video feedback examples name the place, the feeling, the ask and the reason, for instance "0:31 to 0:43, both clips say it tastes smooth, keep the second and reach the price sooner". Bad video feedback examples carry only the feeling, like "the middle drags", which is honest but gives the editor nothing to aim at, and at the end of the day the test is whether the editor could fix it without asking what you meant.
How do I write video feedback if I'm not an editor?
Watch once without stopping, then go back and pause wherever you felt something, and describe that feeling in plain words, because nobody expects you to say J-cut or color temperature. Then say roughly what you'd like and why it matters for the goal. My longer walkthrough on how to give feedback on a video goes deeper, but honestly place, feeling, ask and reason covers most of it.
What does a timestamped feedback example look like?
It looks like "At 0:58, there's a click right after she says roasted, I hear it on headphones but not on laptop speakers, can we clean that up?" The time comes first, so the editor jumps straight there, and the detail about headphones tells them exactly what to listen for once they arrive.
How many notes should one round of feedback have?
There's no magic number, but I'd rather see 15 small pinned notes than 3 big vague ones, because each pinned note can be fixed and answered on its own. What I push against is one comment holding a list of six issues, since the editor fixes five of them, the sixth slips through, and the round comes back. The older post on why bad feedback kills an edit goes into that cost properly.
If you want to try these on your next cut, every PlayPause plan starts with a 7-day free trial, and you can see the Creator, Agency and Enterprise plans side by side on the pricing page. Send the client one link, paste two of these rewrites into the first comment as a sample, and just watch how different round two feels.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free