Client Keeps Asking for Revisions? Write the Rules Down Once
When the same retainer client sends the same logo, caption and pacing notes on every video, I stop fixing them one round at a time and write them down once as rules my editors tick before uploading.
A repeat client revision note derailed a review call for one of the retainer clients at my video-editing agency, and three minutes into the cut the client stopped playback and told my editor that the logo was coming in too early again, and the captions were too big again. My editor went completely blank, right, because he had joined that account two weeks earlier and had no idea there was any "again" to begin with.
That call is basically what it looks like when a client keeps asking for revisions on the same handful of things. Moving a logo by a second is a five-minute fix, but he had given that exact note on the previous three videos to two different editors, and each time we fixed it inside one video and then lost it. To be very honest, I stopped blaming clients for this a while ago, because the real problem was that we kept the client's rules in people's heads and old WhatsApp threads.
So this is the system I use now, and it is really really simple on paper, right, you pull the repeat notes out of old feedback, write the permanent ones down once, give editors a checklist they tick before every upload, and get the client to confirm the rules.
Why the client keeps asking for revisions with the same note
In almost every agency I have seen, including mine, it happens the same way. A client says the logo is too early, the editor fixes it, the video gets approved, and the fix lives inside that one project file and nowhere else, right, so when the next video starts with a different editor, the same logo shows up at the same wrong moment.
On a retainer this gets worse with every new face on the account, because editors rotate and freelancers leave and the knowledge walks out with them, which I wrote about in the post on feedback lost when contractors leave. The client only sees that they said something clearly and it came back wrong, so they get sharper on the next review, and I'm pretty sure every agency owner reading this has a client like that in mind.
Before fixing anything, look at what the revisions actually are, because a client asking for revisions again and again can mean different things. If the notes are new every round because nobody agreed what the video was for, that is a brief problem, and our page on why review is a workflow problem starts there. If the client approves and then reopens things, see how to stop clients changing approved feedback, and if there is no limit on rounds, you need an agency revision policy. If the same few notes come back on every new video, though, that is a memory problem, and it is the one this post fixes.
The catch here is that a memory problem feels like a difficult client from the inside, so agencies add caps or push back harder, and a cap does nothing about why the rounds exist. Left alone, repeated client feedback becomes unbilled rework that behaves a lot like scope creep, because the job grows past what was agreed without anybody deciding it should. Our page on how to reduce video revision rounds covers the wider workflow.
Every repeat note is a rule that was fixed once inside one video and then lost the moment the next project started.
Separating one-off notes from permanent preferences
Before you write anything down, be a bit ruthless about what counts as a rule, right, because if every note goes in you end up with a forty-page mess that no editor reads. My test is very very simple, I ask whether the note would still be true on the next video, and if yes it is a permanent preference, and if no it is a one-off that dies with this cut.
For instance, swapping the shot at the product reveal is a one-off because it is about this footage, whereas the logo landing after the hook is permanent because it is about how the brand shows up everywhere. Caption size, fonts, lower third colors, pacing on talking heads, music under the voice, words the founder never wants on screen and so on all sit on the permanent side. Does that make sense, right, the question is always about the next video.
Repetition is the other signal I trust, so if a note shows up on two different videos I treat it as a rule, because clients rarely announce brand rules, they just repeat themselves, slightly more annoyed each time. When I am unsure, I ask at the next review whether a note is for this video or every video, which is one of the prompts in our post on the questions to ask clients at each review stage.
Swap the shot at the product reveal in this video only
The logo lands after the hook on every video and never in the first two seconds
Building a client playbook from past feedback
Now for the actual work, which to be very honest takes one focused afternoon per client. Say a retainer client has a dozen videos delivered, so you go back through every review comment, WhatsApp message and email that carried feedback, and copy each note into one plain list with the video it came from.
In PlayPause this part is easier, because comments are frame-accurate and stay attached to each version on the same card, so you can open MV1, MV2 and MV3 of an old video and see what the client said at which frame, right, instead of scrolling through chat. If your notes are scattered, our guide on how to organize revision notes by timecode gets them into a sortable shape.
Then you sort and count, and here is an illustrative tally, made up but typical of what I see. Twelve videos might give you a little over a hundred notes, and once they are grouped, logo too early sits on five videos, captions too big on four, music fighting the voice on three and the founder's job title written wrong on two, while almost everything else shows up once. Those four repeat notes are basically your playbook.
The step people skip is rewriting each repeat note as a rule an editor can check without guessing. A note like "keep captions clean" is too vague, right, because two editors will read it two ways, whereas "captions in the lower third, two lines maximum, white with a soft shadow" can be checked against a frame. A style guide in publishing works the same way, and our post on a brand style guide editors use goes deeper. In PlayPause those rules go into a Playbook, the per-client document of creative style and direction that comes with the Agency plan and up.
Brand rules versus per-project instructions
The next mistake is putting every rule in one place. PlayPause splits this into brand playbooks for permanent rules and folder playbooks for each folder, and the brand playbook holds whatever survives a change of campaign, so logo timing, fonts, colors, caption styling, music taste and banned words, which is really the video side of brand management written for editors.
The folder playbook holds instructions for one project or series. For instance, a client might run a podcast clip series and a paid ads series at once, where the clips need a hook in the first line and a standard intro card, while the ads need a specific call to action and a product name spelled one way for this launch. Put all of that in the brand playbook and each editor wades through the other series' rules, and within a month nobody reads any of it, you see what I mean here.
My rule of thumb, right, is that if a rule would survive the client changing campaigns it goes in the brand playbook, and if it would die with the campaign it goes in the folder playbook, which keeps the brand playbook short enough for a new editor to remember.
Frame-accurate note, everyone sees the exact same thing.
Checklists editors tick before every upload
A playbook that editors read once and forget is only slightly better than none, right, so the part that actually changes behavior is the checklist. Playbook checklists in PlayPause are not done until each item is ticked, and in my agency the rule is plain, before an editor uploads a new version they tick every line against the actual cut, and if a line cannot be ticked the version does not go out.
The catch here is length, because with thirty items editors start ticking without looking, and then you have a record saying something was checked when it was not. I keep the list to the rules the client has actually repeated, and trust me on any level, a short checklist ticked honestly beats a long one that gets skimmed.
- Logo lands after the hook and never in the first two seconds
- Captions sit in the lower third with two lines maximum
- Brand fonts and colors on every title card
- Music sits under the voice and never over it
- Banned words checked against the transcript
I also add a custom status like Checklist done, so a Manager or Admin can see which versions went through the check. Premiere Pro editors can use the PlayPause Premiere Pro panel, where client comments show inside Premiere and a click jumps the playhead to that frame, while editors on DaVinci Resolve, Final Cut Pro or After Effects export, upload, check the cut in PlayPause and carry the notes back into their editor.
Getting the client to confirm their own rules
Most agencies skip this step, and it is the one I like best. PlayPause lets you share a Playbook with the client as a clean page they open without logging in, so once the brand playbook is written I send it over and ask what is wrong or missing, the same one-link experience as in our post on getting client feedback without a login.
Two good things tend to happen, right. The client corrects the rules, often telling you the logo is really about landing after their name is said, which beats the rule you guessed, and the client now owns those rules, so when the same note shows up again you point at a line they approved instead of defending your editor.
That makes pushing back far less awkward, because you are asking whether they want to change their own rule instead of arguing about taste, which is the approach in our post on pushing back on client feedback. If a boss tends to appear at the last minute, share the playbook with them too, because a lot of late executive notes are rules nobody ever asked that person about, and at the end of the day a rule the client confirmed is worth ten you wrote alone.
Once the client signs off on their own rules, a repeat note becomes a quick pointer to a line they approved instead of an argument about taste.
How to handle client revision requests after the playbook exists
With the playbook in place, the way you handle client revision requests gets calmer on both sides. When a frame-accurate comment matches a rule, the editor replies in the thread, points to the line and fixes it in the next version. The reply is short and boring on purpose, something like "Thanks for flagging, this is rule 2 in your brand playbook, captions two lines maximum in the lower third, it slipped past our check and it is fixed in MV3." On the Agency plan and up, side-by-side version compare puts MV2 next to MV3, so the client sees the fix for themselves.
A new note goes into the playbook and the checklist straight away, and I tell the client it was added, so they know saying something once is enough. When a note contradicts a rule, the editor asks in the thread whether the rule is changing or this is a one-off, and the answer gets written down. In my agency, the accounts where we did this properly stopped feeling like never-ending client revisions, and their notes are now mostly about new footage, which is really really what feedback should be about.
You still want a limit on rounds, covered in our post on capping revision rounds for retainers, but the playbook stops you burning those rounds on notes you already knew about. If you run many clients at once, our page on PlayPause for advertising agencies shows how this fits a multi-client setup.
Frequently asked questions
Why does my client keep asking for revisions we already made?
In my experience it is almost always because the fix was saved inside one video and never written down as a rule, right, so the next editor on the account never saw it. The client repeats the note a little louder and starts to look difficult, when the real gap is that the agency has no shared memory for that client, which a brand playbook and a short checklist go a long way to fixing.
How do I stop endless client revisions without annoying the client?
I make the client part of the fix, so I share the playbook as a page they open without logging in, ask them to correct it, and from then on every repeat note points at a rule they approved. Pushback becomes a quick question about whether they want to change their own rule, and most clients enjoy being asked, because it shows you were listening.
What goes in a brand playbook versus a folder playbook?
The brand playbook holds anything that would survive a change of campaign, like logo timing, fonts, colors, caption style and banned words. The folder playbook holds instructions for one project or series, like a campaign's call to action or the intro format for a podcast clip series. If you are unsure, ask whether the rule would still apply next quarter, and if it would, it belongs in the brand playbook.
Which PlayPause plan includes Playbooks?
Playbooks come with the Agency plan and up, so Agency at $19 a month or Enterprise at $27 a month, both flat pricing per workspace rather than per member. Agency also includes side-by-side version compare, AI transcription and guest version upload, and every plan has a 7-day free trial, so you can build one client playbook and test it on a real video first.
Where I would start this week
Pick the one retainer client who has sent you the same note more than twice, block an afternoon, pull the repeat notes out of their old reviews, write their first brand playbook with a short checklist, and share it so they can correct it. If you want that next to your reviews, have a look at PlayPause pricing, where Agency is the plan with Playbooks, and every plan comes with a 7-day free trial so you can try it on a real account first.
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