How Many Revision Rounds Should Be in Your Video Editing Contract?

Every editor who has been freelancing for more than a year has a story about the project that would not end, the one where "just one more small tweak" turned into a fourth, fifth, sixth pass on a video that was supposed to wrap in two rounds, and by the time it actually shipped the effective hourly rate had dropped so low it barely covered the coffee. If that sounds familiar, the problem almost never starts with a difficult client. It starts with a contract that never said a number out loud.

Why "Reasonable Revisions" Is Not a Number

A lot of editing agreements still use language like "includes reasonable revisions" or "revisions until client satisfaction," and we get why that phrasing feels safe when you're trying to close a deal and don't want to seem rigid. The trouble is that "reasonable" is a word two people can read completely differently, and when a disagreement shows up three weeks into a project, you do not want to be negotiating the definition of a word for the first time under pressure. A contract's job is to remove ambiguity before the relationship needs it removed, and a revision clause with no number in it has not actually done that job, it has just postponed the argument to a worse moment.

We work with a lot of freelance editors and small post houses through PlayPause, and the pattern we see over and over is that the editors who never get walked over on scope are the ones who put a specific digit in writing before the kickoff call ends, not the ones with the most polished contract template.

What the Right Number Actually Is

There is no universal correct answer, but there is a range that works for most project types, and it clusters around two to three rounds. Fewer than two tends to feel stingy even to reasonable clients, because almost nobody nails a cut on the first pass, not because the editor did bad work but because the client is often seeing their own footage assembled for the first time and needs a beat to react to it. More than three, on the other hand, starts to signal that the scope was never actually locked, and it invites what we'd call revision drift, where each round reopens decisions that were supposedly closed in the round before.

Two Rounds for Straightforward Work

For social cuts, short-form content, single-camera talking head videos, and anything with a tight brief, two rounds is usually plenty. Round one addresses structure, pacing, and anything glaringly wrong. Round two is polish, small timing fixes, maybe a color or audio tweak. If you're doing this kind of volume work, Youtube Creator and Social Media workflows both live or die on how fast that two-round loop closes.

Three Rounds for Complex or Multi-Stakeholder Work

Corporate videos, brand campaigns, anything touching Corporate Video or Brand Marketing Teams, and projects where more than one person signs off usually need a third round, because the first round often surfaces internal disagreement on the client side before it surfaces feedback on your cut. We go deep on what happens when that disagreement itself becomes the bottleneck in our piece on handling conflicting stakeholder feedback, but for contract purposes, just budget the extra round up front.

What the Clause Actually Needs to Say

A revision clause that holds up is not just a number, it is a definition of what counts as a round, what counts as a request within a round, and what happens after the last one runs out. Here is the structure we recommend to editors who ask us this exact question:

That last point matters more than people think. If a client sends feedback in three separate emails over ten days, each with new notes tacked on, that is not three rounds, that is one messy round, and your contract should say so explicitly. Otherwise you end up eating the cost of their disorganization, one email at a time.

Pricing Extra Rounds So They Actually Deter

The point of charging for extra revisions is not really to make more money on overages, it's to make the included rounds feel like the fast, included path and anything beyond that feel like a deliberate choice the client is making with their eyes open. We tell editors to price additional rounds at something close to their normal hourly rate, not a token fee, because a small flat "extra round" charge does nothing to change behavior, it just becomes a line item nobody thinks twice about. At the end of the day the number needs to sting enough that a client pauses and asks themselves whether this note is actually necessary or just a preference being voiced out loud for the first time.

Building the Cap Into Your Actual Workflow, Not Just the PDF

Here's the catch: a contract clause is only as strong as your ability to actually track what round you're on and what was said in each one. If feedback is scattered across email threads, texts, and a Google Doc someone forgot to update, you have no evidence when a client insists this is only their second round of notes and you're pretty sure it's their fourth. This is exactly the gap we built PlayPause to close. Every round of feedback lives as timestamped comments on the actual frame of the actual version, so when you tell a client "this is round three, per the contract," you can pull up rounds one and two in seconds, dated, attributed, and impossible to argue with.

We built this because we watched too many editors lose these arguments not on the substance, they were usually right, but on the paperwork, because they couldn't produce a clean record fast enough to hold their ground. A Client Review Portal that logs every round automatically turns your contract's revision clause from a promise into something you can actually enforce in the moment it matters.

Handling the Client Who Pushes Back on the Cap

Some clients will ask why you're capping revisions at all, and this is worth having an answer ready for, because dodging the question makes you look like you're hiding something. The honest answer is that unlimited revisions do not produce a better final video, they produce a longer process with more cooks and more drift, and a capped structure with clear rounds actually gets them a better result faster because it forces feedback to be decisive instead of exploratory. If they push further, that's usually a sign they're worried about not getting it right in two or three tries, which is really a conversation about the creative brief, not the contract. Tightening the Creative Brief up front solves more revision problems than any clause ever will, since vague briefs are what generate vague, scattered feedback in the first place, something we go deep on in our piece about vague client feedback.

• State the round count in writing before the deposit is paid
• Define what counts as one round, not just how many
• Set a feedback deadline per round so rounds don't stall indefinitely
• Price extra rounds at a real rate, not a token fee
• Track every round in one place so you can prove where you are

What This Looks Like in Practice

A small studio we talked to runs mid-length brand documentaries and had been burning an extra 15 to 20 percent of project hours on unbilled revisions before they rewrote their contract to specify three rounds with a defined feedback window. The number itself did some of the work, but the bigger shift was that stakeholders started consolidating their notes before sending them, because they knew a scattered, drip-fed round of feedback would eat into their allotment. That's the quiet benefit of a clear cap: it changes client behavior before you ever have to enforce a penalty on anyone.

As the Motion Picture Editors Guild and other industry bodies have long pointed out, scope definition is one of the most under-negotiated parts of freelance creative work, and revisions are usually where that vagueness costs the most money over the life of a project. Getting specific here is not about being difficult with clients, it's about giving both sides a shared, written understanding of what "done" actually looks like before anyone starts working.

A Quick Word on Retainer and Ongoing Clients

Everything above assumes a single project with a defined end, but the calculation shifts a bit for retainer clients who send you a new video every week or two. In that setup, we tell teams to cap revisions per deliverable rather than per relationship, so a client on a monthly retainer covering four videos still gets, say, two rounds on each individual video rather than one giant shared pool of revisions they can spend however they like across the month. Without that distinction, a retainer client can unknowingly (or knowingly) sink six rounds into one video and leave nothing for the rest, and then you're the one explaining why video four is behind schedule for a reason that had nothing to do with your output. Publications like No Film School and StudioBinder's blog cover this same scope-management problem from the production side, and the underlying lesson translates directly to post: define the unit you're capping, not just the ceiling.

Put the Number in Writing, Then Back It With Proof

A revision cap only protects you if you can actually show what happened in each round when it matters, so pair a specific number in your contract with a workflow that timestamps and attributes every note automatically. Check PlayPause pricing to see how teams run capped, trackable revision rounds without juggling email threads, or reach out to PlayPause if you want help setting up a review flow that makes your contract's revision clause actually stick.