How to Give Timestamped Feedback on Video for a Whole Section, Not One Frame
A single frame comment cannot carry a note about ninety seconds of pacing, so this is how I use range comments in PlayPause and write them so an editor can act on them in one pass.
The client feedback on Founder_Story_MV2.mp4 is one comment at 00:02:14 that reads "this whole middle bit drags", pinned to a single frame where the founder happens to be mid blink. So I am basically sitting with a blinking man in a browser tab while being told that roughly ninety seconds around him are slow, right, and nobody has told me where those ninety seconds start or end. That is the exact spot where timestamped feedback on video quietly falls over, and the client did nothing wrong, because the note was about a section and the comment box only knew how to hold one frame.
I run a video editing agency and I also build PlayPause, so I watch this from both chairs, and to be very honest the editor chair is the more annoying one, because I am the person who has to guess an in point and an out point and reverse engineer what "the middle bit" meant to somebody who watched the cut once at midnight. What would have saved that round is a comment that carries a start and an end.
That is what range comments are for, they sit on every PlayPause plan, and they have quietly become the feature I lean on most in a review round. So let me walk through when a section note beats a frame note, how clients leave one, how I word them, and how they get used once the cut opens in Adobe Premiere Pro.
Single frame notes versus section notes
A single frame comment is the right tool when the problem lives at one moment, for instance a jump cut at 00:00:47, a logo two shades off at 00:01:12, a misspelled lower third, a pop on a splice, and so on. For all of that the frame is the whole message, which is what I mean by frame-accurate video feedback, because the editor lands on the frame, sees the problem and fixes it without a single message going back and forth.
A section note is a different animal, because the problem lives in the relationship between frames. Pacing works like that, and so does a b-roll run that starts fine and then outstays its welcome. If you pin "drags" to 00:02:14, the editor opens a perfectly reasonable frame, the note contradicts what they are looking at, and you get the polite reply asking what exactly you meant.
One frame gets a note about ninety seconds, and the editor guesses the in and out points from a sentence.
The comment carries a start and an end, so the editor sees exactly which stretch the note is about.
So the split I use in my agency is simple, right. If I can point at one frame and say "that", it is a frame comment, and if I have to say "from about here to about there", I mark a range instead. Does that make sense, right, the note should carry the shape of the problem, and some problems are shaped like a point while others are shaped like a line.
When timestamped feedback on video needs a range
Four kinds of notes come up again and again in my agency, and I have basically stopped squeezing any of them into a single frame.
Pacing is the obvious one. "This section drags" only means something if the section has edges, and the difference between 00:02:05 to 00:02:50 and 00:02:05 to 00:04:10 is the difference between trimming four shots and restructuring an act. My piece on pacing notes without words makes the same case, that a selected range does more work than three paragraphs of adjectives.
Music beds are the second. A track fighting the voiceover fights it across a whole passage, right, so "duck the music from 00:03:12 to 00:03:48" is a note an editor can execute in one pass.
Pacing, music beds, b-roll runs, and any note about a section of dialogue that needs tightening. Everything else is usually fine as a frame comment.
B-roll runs are the third, because "too much of this" is a duration, and you can only describe a duration with two points. The fourth is dialogue, where a client wants an interview stretch tightened but really does not want to pick which sentence dies, so they hand over the stretch and the editor proposes the trims. In all four, the range gives the problem edges, right, and edges let an editor start without booking a call. At the end of the day, when a round stalls in my shop it is usually because two people pictured a different starting point for the same problem.
How range comments work for clients
Here is the part I care about commercially, right. A feature only editors can use does nothing for the client side of a review, and range comments matter to us because a client can leave one from a link, with no account to make and nothing to install.
I send one share link, the client opens it in whatever browser is already open, and the video plays from a streaming copy so the original stays untouched. To leave a section note they mark where the stretch starts and ends, then type. That is why I built the time-coded annotations for video review side of PlayPause this way, because the second a client has to create a password, a good chunk of them drift back to WhatsApp, and I am reading "the bit after the drone shot" again.
There is a quieter benefit too, because the comment records the position itself, so I am not working from a time a client typed off a phone player that only shows seconds. At a frame rate of 25 or 30, a rounded second can leave me up to thirty frames away from what they meant.
Comments are threaded, so my producer can reply "so we are cutting the second half of that, confirming", @mention the editor, and the decision lives on the card instead of in email. Late stakeholder opinions are their own problem, which my post on stopping late executive notes covers, although a range at least removes the excuse that nobody knew which part was being discussed.
Writing range notes an editor can act on
A range without a sentence is still a guess, right, and since I give notes as the client on my own channel's videos and receive them as an agency, I have had plenty of chances to get this wrong from both sides.
My pattern has three parts. The boundary is the range, set slightly wider than the problem, because narrowing is easier for an editor than hunting. The second part is what I felt, in plain words, like "I checked out here". The third is the permission, which almost everybody skips, so I say something like "happy to lose about twenty seconds anywhere in this".
A range tells the editor where to work, the sentence tells them what hurt, and the permission tells them how far they are allowed to go.
A worked example on one cut
Here is roughly how my notes on that founder video would read, with frame comments and ranges left in the same pass.
- 00:00:47, frame comment: "This jump cut feels accidental, can we cover it with the workshop b-roll?"
- 00:01:58 to 00:02:52, range: "I checked out through here. Happy to lose twenty seconds anywhere, but keep the line about the first hire."
- 00:03:12 to 00:03:48, range: "The music sits on top of her voice through this whole stretch, please duck it."
- 00:04:05 to 00:04:13, range plus a box drawn on the frame: "The pack sits too low for the entire hold, can we reframe it up?"
- 00:05:20, frame comment: "Surname is misspelled in the lower third."
Two are single frames and three are sections, and every one can be picked up by an editor at 8am without a call, which is the test I hold a note to. The pacing range also gives a target and a protected line, so the editor has a budget and a line they must not touch, and the calls in between are theirs.
What I avoid is stacking six problems into one range, because the thread turns into a to do list nobody can tick off, so I keep one problem per comment. If the same forty seconds has a pacing issue and a colour issue, that is two comments on the same stretch, each resolved on its own.
- Set the range wider than the problem
- Say what you felt, not what to do
- Give the editor permission and a rough target
- Keep one problem per comment
If your team still collects notes on a document, my piece on the video feedback form template explains why a form makes people write more and say less, and why one range with one good sentence beats twelve fields nearly every time.
Combining range comments with drawings
Sometimes a note is about a section and a spot on screen at once, for instance packaging sitting too low for a whole eight second hold, or a subtitle block covering a hand gesture through an entire answer.
Drawing on the frame is on every plan, so I set the range across the section and draw on the frame that best represents it, and between the two the editor gets both the duration and the geography. They see the box around the packaging, see the range covering the full hold, and know it is a reframe across a section. That combination is most of what I cover in how to annotate a video, and I am pretty sure it saves more back and forth than any other habit we have.
The catch here is that a drawing alone implies a single frame, so if a client draws once and means "the whole scene", you are back to guessing, right. In the kickoff call I give new clients one line, which is that if it lasts you mark the range, if it is a spot you draw on it, and if it is both you do both, and that takes about twenty seconds.
Working through range notes in the edit
Now the editor side, right, because a comment only counts if it survives the trip into the timeline. When notes come in on a rough cut, I no longer read them in the browser and retype them into a notepad, because trust me on any level, that habit eats a huge chunk of review time.
With the Premiere Pro panel, the comments show up inside Premiere, and clicking one jumps the playhead to that frame, so I land on the note's timecode and play through the stretch it describes with the text beside me. I can upload the next version straight from the timeline too, which matters because the moment uploading becomes a separate errand, versions drift out of order. My post on syncing comments to Premiere timecode covers that loop in detail.
If you cut in DaVinci Resolve, Final Cut Pro or After Effects, the route is export, upload, review, then work from the notes in your editor, and range comments on a second screen still beat a document. Either way the new version stacks on the same card as MV3 rather than becoming a fresh file with its own link. On Agency and up, side-by-side version compare settles the "did you actually change it" conversation, and AI transcription with a clickable transcript lets a producer find the exact sentence inside a dialogue range in a few seconds.
For the wider picture, the video feedback and review page walks through a whole round, and my write up on presenting a rough cut to clients covers the conversation before the notes arrive.
Frequently asked questions
Can a client leave a range comment without an account?
Every plan allows it. The client opens the share link in a browser, plays the video, marks where the section starts and ends, and types the note, with nothing to install. You can password protect the link if the project is sensitive, and revoke it instantly if the wrong person ends up with it, which happens more often than anybody admits, right.
What is the difference between a range comment and two timestamps?
Two timestamps are two separate comments a human has to mentally staple together, and they drift apart the moment somebody resolves one and forgets the other. A range is one comment with a start and an end, so the section gets discussed and resolved as a single note. You see what I mean here, one object is far easier to track than two.
How do range notes get into Premiere Pro?
They come in through the Premiere Pro panel. The review comments show up inside Premiere, and clicking one jumps the playhead to that frame, so you start on the note's timecode with the text right there and play through the section it describes. You can also upload the next version from the timeline, so the new cut stacks on the same card.
How is this different from Frame.io for a small team?
Frame.io charges per seat, from $15 per user per month, so a small team with freelancers and clients gets expensive quickly. PlayPause is flat per workspace, so Creator is $9 a month with room for 10 members and Agency is $19 with room for 50, and on Agency and up a guest can upload a version with just a name and email, which Frame.io does not allow without an account.
Should every note be a range comment then?
No, and overusing them is its own mess. If you can point at one frame and say "that", leave a frame comment, because a range around a single moment makes the timeline look busier than the edit is. I use ranges for pacing, music, b-roll runs and dialogue trims, and frame comments for everything else.
If you want to try this on a real cut, every plan has a 7-day free trial, so put your next rough cut up, send the link to one client and see how many round trips disappear when notes arrive with edges on them. The PlayPause pricing page has the breakdown, and range comments, drawing and commenting without an account are on all three plans, so even Creator covers the core of what I described, with compare and transcription waiting on Agency.
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