What to Put in Your Agency's Revision Policy So Clients Stop Asking for 'One More Small Change'

Every agency owner we talk to has some version of the same story, a client loved the cut, signed off on it in writing, and then three days later sent a message that started with "quick thing" and turned into a full afternoon of re-timing, re-grading, and swapping out a lower third that was apparently "always going to change." Nobody agreed to that work, and nobody's getting paid for it, and it happens because most agency revision policies are a single vague line in a statement of work that says something like "two rounds of revisions included," without ever defining what a round actually is. That gap is where scope creep lives, and it's expensive in a way that doesn't show up on an invoice, it shows up in editor burnout and producer overtime and the quiet resentment that builds when the same three-minute brand film has eaten six rounds of notes.

We built PlayPause because we watched this exact pattern play out across dozens of production teams, and the fix isn't a sterner client email, it's a revision policy that's specific enough to reference mid-project without an argument. This post walks through what actually needs to be in that policy, how to structure it so it protects margin without making clients feel nickel-and-dimed, and how the review tool you use enforces (or completely undermines) whatever you write down.

Why "Two Rounds Included" Doesn't Actually Stop Anything

The phrase "two rounds of revisions" feels precise because it has a number in it, but it doesn't define what counts as a round versus what counts as a single note inside a round, and it definitely doesn't define what happens when round two produces four new requests that weren't in round one's notes. A client can technically stay "within two rounds" while sending nine separate feedback emails over three weeks, each one small on its own, and your editor ends up opening the project nine separate times. For a mid-size agency running maybe fifteen active client projects at once, that kind of drift adds up to real hours, and it's the kind of cost that's nearly invisible until someone runs the numbers on billable versus actual time spent per project at the end of a quarter.

The real problem is that "revision" is doing too much work as a word. A full round should mean the client watches the complete cut and gives consolidated notes once, in one sitting, through one channel. A minor tweak, fixing a typo in a lower third, nudging a music cue by half a second, is not that, and your policy needs to say so explicitly rather than leaving it to whoever's managing the account that week to decide on the fly.

Defining a Round So It Can't Be Argued With

The clearest agencies we work with define a round using three things together: a scope boundary, a delivery format, and a response window. The scope boundary says what a round covers, for instance "one full watch-through of the current cut with all notes submitted together." The delivery format says how notes arrive, through the review tool and not scattered across email, Slack DMs, and a phone call the account manager forgot to write down. And the response window says how long the client has to consolidate their notes before the round closes and any additional feedback rolls into the next one.

This is also where a lot of agencies discover their process was never actually broken, their tooling was. If a client can leave a comment on a video by replying to an old email thread, or texting the producer, there's no way to enforce "one consolidated round" because there's no single place the round happens. That's the entire reason timecoded, threaded comments inside Video Review tools matter here, they force every note into one visible surface tied to a specific frame and a specific version, which makes "is this round two or round three" a factual question instead of a memory contest.

Small Tweak vs Full Round, Where the Line Actually Goes

We tell teams to write down a literal list of what qualifies as a minor tweak, because "small" is subjective and clients will always argue their request is small. A genuinely minor tweak is something like a spelling correction, a volume adjustment on a single clip, or swapping a still image that doesn't touch the edit's pacing or structure. Anything that touches trim points across multiple sections, changes the overall grade, swaps a VO track, or reorders scenes is a structural change and belongs inside a tracked round, full stop, even if the client phrases it as "just one small thing."

The agencies that hold this line well aren't the ones with the harshest contracts, they're the ones who can point to a specific comment thread and say "this request came in after round two closed, here's the timestamp, here's what a change order looks like." That only works if your Approval Workflow actually timestamps and versions everything automatically, because manually tracking "which email was round two" across a twelve-week campaign is a losing game.

What Scope Creep Actually Costs You Per Project

Run the math on a typical mid-size project, say a $28,000 brand campaign with a budgeted 40 editor hours built into the quote. If the revision policy is loose enough that "small asks" keep sliding in outside the two contracted rounds, and each of those asks eats even 45 minutes of an editor's time, ten of them across a project timeline erases 7.5 hours of margin that was never priced in anywhere. Multiply that across fifteen concurrent client projects and you're looking at over a hundred hours of unbilled work a quarter, which is roughly the equivalent of losing a full-time editor's output for a month, and nobody signed off on that loss because nobody was tracking where it came from. The catch here is that this cost is almost always invisible in real time, it only shows up when someone finally compares budgeted hours against actual hours at project close, and by then the client relationship has already absorbed the pattern as normal.

This is exactly why the policy needs teeth built into the tooling and not just the contract language. A round definition that lives only in a Word doc gets forgotten the moment a friendly client sends a casual message, but a round counter that's visible inside the review portal itself, showing "round 2 of 2, closes in 3 days," changes the conversation before it starts.

Where PlayPause Fits Into Enforcing This

This is basically the whole reason we built version comparison and approvals the way we did. Every cut a client watches gets a version number, every comment is timestamped against that specific version, and when a client opens round three, the system shows exactly what changed since round two closed, so nobody's relitigating whether a note was "already covered." At the end of the day a revision policy is just a set of rules, and rules only work if there's a system enforcing them, otherwise it's a paragraph in a contract nobody rereads until there's already a dispute.

We see this constantly with agencies who switch to PlayPause specifically because their old process, usually email chains, Dropbox links, or a review tool with no version history, made it impossible to point to evidence. Once every round lives inside a tracked Client Approval Workflow with real sign-off, the "one more small change" conversation basically resolves itself, because the client can see their own round count the same way you can.

Build the Policy Into the Kickoff, Not the Contract's Fine Print

The revision policy shouldn't live only in a PDF the client signed once and forgot about, it should get restated verbally in kickoff, referenced in the first review link you send, and visible somewhere inside the actual review portal, because that's the moment it's actually useful. If you're running a Multi Stakeholder Review with a brand team, a legal reviewer, and a creative director all weighing in, the round definition needs to be even tighter, since "one round" for three separate people can quietly become three rounds if nobody's tracking it as a group.

What This Looks Like Across a Real Project Timeline

• Kickoff states the round definition in writing and out loud
• Every note comes through the tracked review link, never email
• Minor tweaks list is shared before round one starts
• Change orders get logged the moment a request falls outside scope
• Sign-off is captured per version, not per "looks good" reply

If you're running review chains that also involve regional or holding-company partners, the same round logic needs to extend across offices too, which is a big enough topic that we wrote a separate piece on how holding-company agency networks handle sign-off across regional offices for one global campaign, worth a read if your revision problem isn't just client-side but also inter-agency. And if legal or brand compliance is part of your sign-off chain, it's worth reading how agencies keep that separate from creative approval rounds entirely, since mixing the two is one of the fastest ways a "two round" policy quietly becomes five.

According to StudioBinder's blog, unclear revision scoping is one of the most common sources of budget overruns on client production work, which tracks with what we hear directly from agency producers every week.

Put the Policy Somewhere It Can Actually Be Enforced

A written revision policy only protects your margin if the tool your clients review inside actually reflects it, version by version, comment by comment, sign-off by sign-off. That's what PlayPause is built for, and if you want to see how flat per-workspace pricing compares to what you're paying now for a tool that doesn't track any of this, take a look at PlayPause pricing or just contact PlayPause and we'll walk you through setting up round-based approvals for your next client project.