Clauses  ›  Revision limits

Revision limits.
The clause that defines what "done" means.

"Just one more tweak" — six times. Without a revision limits clause, every iteration is free, and the project never ends.

Draft an agreement with revision limits

Free. No registration. No card. No catch.

In plain English.

A revision limits clause specifies how many rounds of feedback are included in the project price, what constitutes a "round" (a single consolidated batch of feedback, not individual comments), and what happens when the client exceeds the limit — typically a per-round fee.

Plain English definition

Two rounds of revisions means the client gets two chances to submit consolidated feedback after each delivery. Not two tweaks. Not two emails. Two complete feedback cycles — each with all requested changes gathered into one submission before you begin revising.

When you need it

Any project involving creative deliverables: design, writing, video, web development, photography, marketing. If the client will have an opinion about the output — and they always do — you need a revision limit clause.

What happens without it

Without a defined limit, every revision request is in scope. The project has no end state. You revise until the client is happy — and happy is an infinitely moving target. Your effective hourly rate drops with every round.

Every freelancer has a revision horror story. Most still don't include the clause.

Why missed

Counting rounds feels stingy

Telling a client they get "two rounds" sounds like you're rationing your time. The reality is that two consolidated rounds is generous and professionally normal — it's the unlimited approach that's the anomaly.

Why missed

What counts as a round isn't obvious

One email with five feedback items: one round or five? If the contract doesn't define "round," the client will count each item separately. You'll never agree on when the limit is reached.

Why missed

They plan to negotiate when it comes up

Many providers skip the clause thinking they'll handle it case by case. But in the moment, with a client asking for "just one more pass," saying no is awkward without a contract to point at.

The downstream consequences.

Endless iterations

The project that was scoped at 20 hours turns into 50 hours because the client sends one more round of feedback every time you deliver. Without a limit, you have no mechanism to stop.

Direction changes disguised as revisions

The client changes their mind about the direction entirely. They call it a "revision." Without a clause defining what a revision is vs. a change in direction, you absorb a restart as if it were a tweak.

Payment held hostage

When "done" is undefined, final payment is tied to a moving target. The client keeps revising, the project never ends, the final invoice never lands. Cash flow stalls indefinitely.

Scope creep via the back door

Without revision limits, scope creep doesn't need to come through new feature requests. It comes through the revision process — new requirements submitted as "feedback" round after round.

Revision language that invites unlimited work.

These phrases appear commonly in templates. Each one removes the boundary that makes the clause worth having.

Red flag

"Unlimited revisions"

The single most dangerous phrase in a creative services contract. It sounds like a feature. It's an open-ended obligation that can consume the entire project margin.

Red flag

"Until client is satisfied"

Satisfaction has no objective standard. This is unlimited revisions with extra steps.

Red flag

"Reasonable revisions included"

Whose reasonable? No number, no definition, no mechanism to know when the limit is reached.

Red flag

"Minor revisions at no charge"

Every client considers every revision "minor." The word does no definitional work.

Red flag

"Revisions included per project"

No number. No definition. The phrase signals awareness of the issue but addresses none of it.

A revision limits clause that works.

A strong revision limits clause defines the number of rounds, defines what a round is (consolidated feedback), sets a deadline for feedback submission, and specifies the fee for additional rounds. All four elements are necessary.

BizDraft includes revision limit language calibrated to your deliverable type and industry — from two rounds for design to one structured feedback cycle for copy.

The pattern

  • Name the number of rounds. "Two rounds of revisions are included per deliverable."
  • Define what a round is. "A revision round consists of one consolidated list of feedback submitted by Client in writing. Multiple emails or messages about the same deliverable count as one round if submitted within 48 hours of delivery."
  • Set a feedback deadline. "Client must submit feedback within 5 business days of delivery. Failure to submit within this window constitutes acceptance."
  • Price additional rounds. "Additional revision rounds beyond the included two are available at $[rate] per round, billed in advance."
  • Define what isn't a revision. "Changes in direction, new requirements, or requests that materially alter the approved concept are not revisions and require a change order."

Agreement types where revision limits matter most.

Generate an agreement with revision limits
already calibrated to your project type.

Free. Five minutes. Yours to keep.

Draft your agreement

Clauses that work alongside revision limits.

⚠ Legal disclaimer: Agreements generated by BizDraft are AI-produced for informational purposes only. They do not constitute legal advice and do not create an attorney-client relationship. For any agreement of significant legal or financial importance, consult a qualified attorney before signing.