Is one extra revision round in scope?
Ambiguous — one extra round is one of the most context-dependent scope questions. If your contract lists a specific number of rounds, anything past that is out of scope. If it uses softer language like 'reasonable revisions,' you have room to negotiate.
Why this answer
The revisions clause is where most scope-creep disputes actually happen. Contracts typically take one of three forms. The cleanest is a count ('two rounds of revisions included'), which gives both sides a hard number to point at. Past that count, anything is new work. The second form is a cap on the activity itself ('revisions to the approved direction, up to final delivery'), which is vaguer and usually stretches further. The third is the dangerous one: 'reasonable revisions' with no bound. In that case, the question becomes what 'reasonable' means in your profession and for this project's complexity, and the answer depends on norms you and the client may not share.
When the answer flips
The verdict is clearly Out of Scope when your contract specifies a revision count and the current request exceeds it. It's clearly In Scope when your contract specifies 'unlimited revisions until approval' (rare, and usually a red flag you accepted too eagerly). The most common middle case: the contract lists a count, but the client frames the current feedback as a 'consolidated round' combining several small changes. The fair read is to count that as one round regardless of how the feedback is batched. The other edge case: the scope of a round itself matters. A 'revision round' is typically one pass of feedback, not one comment — if a client sends three separate emails of feedback between delivery and your response, that's still one round.
What to do next
Start by naming the clause. Quote the exact revision language from your contract and count what's happened so far. If you're genuinely at the contract limit, offer a change order for additional rounds at a per-round rate (not hourly, which invites grinding). If the contract language is vague, acknowledge that vagueness directly: 'The contract says reasonable revisions, and we're past what I'd call reasonable for a project of this size — here's what I propose.' Most clients respond well to being shown the clause, not told about it. If the client pushes back, don't escalate — offer the choice: stop here with the current version, or proceed with paid revisions. The power of a clear choice is underrated.
Frequently asked questions
What counts as one revision round if the client sends feedback piecemeal?
One round is one consolidated pass of feedback leading to one implementation pass from you. If the client keeps adding comments after you've started work, you can either wait to collect them before starting (cleanest) or count it as the same round and add a note about consolidated feedback windows in your next contract.
Can I bill the extra round at an hourly rate?
You can, but a fixed per-round rate is usually better for both sides. Hourly billing incentivizes you to grind and disincentivizes the client to send clean feedback. A fixed rate ($X per additional round) makes the cost predictable and the expectation clean.
What if the client says they didn't understand the revision limit?
That's a 'calibrate and move forward' moment. Acknowledge the miscommunication, do not re-litigate the contract, and offer a reasonable path forward — typically one discounted additional round, then a firm stop. Document the new agreement so it's not ambiguous on the next round.
Is there a profession-standard number of revision rounds I should be using?
Two is the most common baseline across design, copywriting, and video work. Three is typical for heavier brand or development work. One is defensible for tightly scoped projects like a single social asset. Whatever you pick, say it in the contract explicitly.
What if the client's feedback is genuinely correcting an error I made?
Fixes to your own work — you delivered the wrong file format, you misspelled a name, you built the wrong variant — don't count as a revision round. A revision round is directional feedback on the deliverable. Bug fixes are part of delivering the work correctly in the first place.
How do I write a revision clause that doesn't create these disputes?
Specify (1) the count, (2) what a round is (one consolidated pass of feedback), (3) the turnaround time for the client to give feedback before a round is considered used, and (4) the per-round rate for additional work. Four specific sentences prevents most scope fights.
Related reading
- The full guide
The scope creep guide for freelancers
How to spot scope creep, why clients do it, what it costs you, and how to respond professionally.
- Scenario
Is a full logo redesign out of scope mid-project?
Yes — in nearly every freelance design contract, a logo redesign introduced after the original logo has been approved is a separate engagem…
- Clause guide
What a revisions clause should include in freelance contracts
A strong revisions clause defines three things: how many rounds are included, what counts as a round (consolidated feedback from a named ap…
- Profession guide
Scope creep for freelance designers: the patterns that cost you most
Design scope creep rarely arrives as a single big ask. It arrives as a drip of tweaks, added deliverables, new stakeholders, and 'can you j…
- Profession guide
Scope creep for web developers: where projects actually break
Web development scope creep usually hides in the gap between 'build this feature' and 'make it work in production.' Clients think the featu…
- Scenario
Is a second round of stakeholder review in scope?
Ambiguous — a new stakeholder reviewing already-approved work usually introduces new feedback that exceeds the original scope, but the revi…
Answer scope creep from your actual contract — not a template.
Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.