How to Sort Client Video Notes Into Fixes, Tweaks, and New Requests Before You Touch the Timeline

Sort every client note into one of three buckets before you open your editing software: fixes, tweaks, and new requests. Fixes are errors that must be corrected, tweaks are creative adjustments inside the agreed scope, and new requests are ideas that were never part of the original brief. That single pass is the difference between a revision round that takes an afternoon and one that quietly eats a whole week, because it tells you what to do first, what to discuss, and what to price separately.

Most revision chaos is not caused by difficult clients. It is caused by treating every note as equal. A misspelled name and a request to reshoot a scene land in the same list with the same urgency, so the editor bounces between tiny corrections and major rethinks and sends back a cut that fixes the wrong things. Sorting first restores order, and it gives you a reply you can send before you change a single frame.

What counts as a fix, a tweak, or a new request?

A fix is anything factually wrong or broken: wrong spelling in a caption, an outdated price, a logo from a previous campaign, a clip showing the wrong product, or audio that drops out for two seconds. Fixes are not creative opinions. If the note points at something incorrect, it goes in this bucket and gets done in the next round without discussion.

A tweak is a creative adjustment that stays inside the agreed brief: trim a pause, swap two shots, raise the music under the voiceover, warm up the color on one scene, or tighten the ending by three seconds. Tweaks are the normal work of a revision round, and most projects include two rounds of them in the quoted fee. They change how the agreed idea feels, not what the idea is.

A new request changes the idea itself: a scene that was never shot, a new message, a different licensed track replacing the approved music, or a format nobody discussed. New requests are often good ideas, but they are new scope. Treating them as free tweaks is how a three week project becomes a six week project while the fee stays exactly the same.

How do you sort a full round of notes in 20 minutes?

Start by reading every note once without editing anything. Resist the urge to fix the easy ones as you go, because early fixes hide the shape of the round. On the second pass, label each note with one word: fix, tweak, or new. If a note contains two ideas, split it in two. A comment like “fix the typo and also can we add a testimonial section” is really one fix and one new request, and they deserve different responses.

Then order your work: fixes first, tweaks second, new requests only after they are approved and priced. Fixes first clears errors that would embarrass everyone if they shipped. Tweaks second delivers the creative polish the client is waiting to see. New requests last, because they may change once the client sees the fixed and tweaked cut, and editing them early often means editing them twice. If new requests dominate the round, stop and reply before you edit at all, because that round needs a scope conversation, not a timeline session.

What do you say to the client before you start?

Send a short sorted summary, not a point by point argument. List the fixes and tweaks you are making, and the new requests with a price or a question attached. A message like this takes five minutes and prevents most revision disputes: “I have sorted your notes into 4 fixes and 6 tweaks, which I am doing in this round, plus 2 new requests, which I have priced below. Let me know if you would like me to add those.” Clients rarely argue with that structure, because it shows their notes were read carefully and nothing was silently dropped.

How do you handle vague notes after sorting?

Vague notes still get sorted, but with a question attached. “Make it pop” is probably a tweak, but you cannot act on it until you know whether the client means brighter color, faster cuts, or bolder music. Reply with one clarifying question tied to a timestamp, and keep the note in the tweak bucket while you wait. Never guess at a vague note, and never let it block the fixes you can already do with certainty.

Timecoded comments make this system dramatically easier. When every note is pinned to the exact second it refers to, sorting takes minutes instead of an afternoon scrubbing the timeline for “the bit near the middle.” You work from a single list instead of reconstructing feedback from email threads, chat messages, and phone calls. With File Approved, clients need no account to leave those timecoded comments, and every approval produces a timestamped certificate recording the reviewer, the time, the file, and the version.

Make sorting a habit, not a rescue plan

Sorting works best when clients know about it before the first cut arrives. Tell them at kickoff that you sort notes into fixes, tweaks, and new requests, and that new requests get priced separately. Set a review window of 24 to 48 hours so notes arrive in one consolidated round instead of dribbling in over a week.

The Free plan at $0 covers 1 active review link with 10 GB of storage, timecoded comments, and one-click approval with a certificate, and Pro at $25 per month adds unlimited review links and 5 TB of storage. Whatever tool you use, the discipline is the same: sort, reply, edit.

How many revision rounds should a project include?

Two rounds is the standard most freelance editors build into a project fee, with extra rounds priced separately. State that number in writing before work starts, so a new request in round three is clearly new scope, not a continuation of round one.

What if a client insists a new request is just a tweak?

Point back to the agreed brief, not to your opinion. If the brief says nothing about a testimonial section, that section is new scope even if it feels small. Offer to price it quickly and fairly, and most clients will accept the distinction once they see it applied consistently.

Should you sort notes from multiple reviewers separately?

Sort them into one combined list, but flag contradictions for the named approver before editing. One consolidated list keeps you from doing the same fix twice or undoing one reviewer’s approved change to please another.