Setting Revision Round Limits in Your Agency's SOW (and Actually Enforcing Them)

Somewhere in almost every agency's history there's a project that started as a tidy three-round engagement and ended up eating eleven rounds of notes, three change-of-heart briefs, and a client relationship that never quite recovered its warmth. We hear this story from agency owners constantly, and it's almost never framed as a creative problem, it's framed as a margin problem, because the crew is still getting paid the same day rate whether they're on round two or round nine, and somewhere around round five the project stops being profitable and nobody noticed exactly when that happened.

Why "Unlimited Revisions" Creeps Into Every SOW

Nobody writes "unlimited revisions" into a statement of work on purpose, at least not usually. It creeps in through vague language, phrases like "we'll revise until you're happy" or "feedback rounds as needed," which sound generous and client-friendly at the pitch stage and become a genuine liability six weeks later when a client is on their eighth round of notes and still not happy, because the brief itself was never locked down clearly enough for happiness to be a reachable target. We built the revision tracking inside PlayPause because we kept seeing agencies discover, usually mid-project, that they had no contractual language protecting them from exactly this scenario.

The catch here is that revision creep is rarely one dramatic moment, it's death by a thousand small asks, a client asking for "just one more tiny tweak" seven separate times, each one reasonable in isolation and each one technically a new round that nobody logged as such.

Writing A Revision Cap That Actually Holds Up

A workable revision clause needs to define what counts as a round in the first place, and this is where a lot of SOWs fall apart before they even get to the number. Does a round mean one consolidated batch of notes from the client, or does every individual comment thread count separately? Does a round that only touches color grading count the same as a round that requests a full recut? We tell agencies to define a round as a single, consolidated set of notes delivered by a specific date, with all further tweaks to that same note batch counted inside the same round rather than as new ones, because otherwise clients will naturally drip-feed feedback and blow past your cap without ever technically requesting "another round."

The Language That Works In Practice

The SOWs that hold up in practice tend to include three specific numbers: how many rounds are included in the base fee, what a round costs beyond that cap, and how many business days a client has to consolidate their notes into a single round before it rolls into a new one automatically. That third number matters more than agencies expect, because open-ended feedback windows are exactly how a single round quietly turns into three.

Enforcing The Cap Without Feeling Like The Bad Guy

Here's the part that's genuinely hard, and it's not the writing, it's the enforcing. Account managers hate being the person who tells a client "that's round four, this one's billable," especially mid-relationship with a client they like and want to keep happy long term. At the end of the day though, the agencies that enforce caps consistently are the ones that protect their own margins and, somewhat counterintuitively, end up with better client relationships, because clients respect a partner who runs a tight, professional process more than one who lets scope quietly balloon and then gets resentful about it later.

The step people skip is the automatic flag, and it's the one that makes the whole system work without anyone having to remember to check. If your team is manually tallying rounds in a spreadsheet, you know exactly what I mean if you've ever watched a project quietly slide from round three to round six because nobody was tracking it in real time. That's a workflow problem, not a discipline problem, and it's solvable with tooling rather than with asking your AMs to be more vigilant, which never really works long term.

Where Revision Tracking Actually Lives

This is really the crux of why revision-round enforcement needs to be built into the review tool itself rather than tracked separately in a project management app. If your feedback happens inside PlayPause, every round is timestamped automatically against the actual video, every comment is tied to the specific version it was left on, and the round count is visible to the AM without anyone opening a spreadsheet. We go deeper on the mechanics of that live tracking in how account managers track revision-round SLAs across a dozen active campaigns, which is worth reading alongside this piece if you're the one actually watching the dashboard day to day.

What Happens When A Client Pushes Past The Cap

Eventually a client will push past whatever cap you've set, and how that conversation goes depends entirely on whether you have a clean, timestamped record to point to or just a vague sense that "this project's gone on a while." The agencies that handle this best don't wait until round eight to bring it up, they flag it the moment a project crosses into round four of a three-round cap, calmly, with the actual dates and round numbers in hand, which turns a potentially awkward conversation into a straightforward, documented fact. We've written specifically about how to turn that documentation into an actual invoice without damaging the relationship in charging clients for extra revision rounds without damaging the relationship, since the tracking and the billing are really two halves of the same problem.

Different Clients Need Different Caps, And That's Fine

Not every account should run on the same revision cap, and agencies that try to force a one-size-fits-all number into every SOW usually end up either overpromising to their biggest, highest-touch clients or underdelivering on smaller retainers where three rounds is genuinely more than enough. A large brand marketing account running a big seasonal campaign might reasonably need four or five included rounds given the number of internal stakeholders they're routing notes through, while a quick social cutdown for a smaller client should probably cap at two. The mistake isn't having different numbers for different accounts, it's failing to write each one down explicitly per SOW and then trying to enforce a mental average that nobody agreed to.

Matching The Cap To The Project Type

This gets even more important once you're running a mix of project types under one client relationship, a hero commercial spot alongside a batch of quick social cuts, for instance. The commercial spot might reasonably warrant more rounds given its cost and visibility, while the social cutdowns should move fast on a tight cap or they'll eat the margin on work that was never priced to support extended back-and-forth. Teams juggling Multi Projects under a single account benefit from setting the cap at the project level rather than the account level, so nobody's arguing over whether "the account gets three rounds" means three rounds total or three rounds per deliverable, which is a surprisingly common and surprisingly expensive point of confusion.

What Good Onboarding Looks Like For This

The clients who push back hardest on revision caps are almost always the ones who were never told the cap existed until they'd already blown through it, and that's an onboarding failure, not a client character flaw. Walking a new client through their actual review workspace during kickoff, showing them exactly where their round count will live and what happens when they approach the cap, does more to prevent disputes later than any amount of contract language buried in an appendix. It takes maybe ten minutes at the start of an engagement and it changes the entire tone of the round-four conversation months later, because the client isn't hearing about the cap for the first time under pressure, they're being reminded of something they already saw and agreed to.

Building This Into Your Client Approval Workflow From Day One

The agencies that never have this problem in the first place are the ones that bake the revision cap into their Client Approval Workflow before a single frame gets cut, not as a legal formality buried in page nine of the contract but as something the client actually sees and acknowledges at kickoff. Pairing that with a Client Review Portal where the round count is visible to the client themselves, not just your internal team, tends to reduce pushback dramatically, because nobody argues with a number they can see updating in real time next to their own comments. According to the Content Marketing Institute, agencies that formalize scope boundaries in writing at the proposal stage report meaningfully fewer disputed invoices than those who handle scope verbally, and revision rounds are one of the clearest places that discipline pays off.

Basically, the fix here isn't a harder negotiation with clients, it's better infrastructure so the negotiation barely needs to happen. If you're tired of finding out a project blew past scope after the fact instead of in real time, see how PlayPause handles round tracking, or check PlayPause pricing to see how a flat per-workspace plan compares to what you're paying now for tools that don't track any of this for you.