Skip to main content

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 approver within a stated window), and what the rate is for additional rounds. Without all three, 'revisions' becomes an open-ended obligation that eats your margin.

Anatomy of a strong revisions clause

Round cap
The number of revision rounds included in the base fee. Two is the industry default for most creative work. Write it as a specific number, not 'reasonable revisions' or 'until the client is satisfied' — those phrases have no enforceable meaning and will be read by the client as 'unlimited.'
Round definition
A single round is a single consolidated batch of feedback from the approver. Multiple conflicting emails across a week are not a round — they're a process failure. The clause should state: 'A revision round consists of consolidated feedback from [approver name or role], delivered in writing within [N days] of delivery.' This prevents drip feedback from eroding the cap.
Named approver
Name the single person whose feedback counts. Feedback from anyone else — a new stakeholder, a partner agency, a junior team member — is out of scope until the named approver incorporates it into a consolidated round. This protects you from the stakeholder gauntlet where you're rewriting for three different voices.
Overflow rate
The rate for revision rounds beyond the cap. Usually hourly, sometimes per-round. The key is that it exists — so you don't have to negotiate at the moment a fourth round arrives. Include it even if you expect never to use it; the visibility alone deters scope creep.
Scope exclusion
A one-line statement that 'revisions do not include changes to voice, tone, direction, audience, deliverable format, or strategy.' This distinguishes revisions (edits to existing work) from rewrites and re-scopes (new directions disguised as feedback). Without this line, every direction change will be framed as 'just a revision.'

Example language

Drop this into your contract and adapt the bracketed placeholders.

Revisions. Two (2) rounds of revisions are included in the base fee. A revision round consists of consolidated written feedback from [Named Approver or Role], delivered within seven (7) calendar days of delivery of the draft. Feedback received outside this window, or from other stakeholders, will be accommodated in the next round. Revisions are limited to edits within the approved direction — changes to voice, tone, audience, deliverable format, scope, or strategic direction are re-scopes, not revisions, and will be quoted separately. Additional rounds beyond the two included are billed at [$X/hour] or [$Y per round], whichever is specified in the engagement schedule.

Common mistakes

  • Writing 'reasonable revisions' or 'revisions until the client is satisfied' — both phrases have no cap and will be read as unlimited.
  • Specifying a number of rounds without defining what a round is. Clients will send daily emails and claim each feedback batch is one round.
  • Not naming an approver. When multiple stakeholders send conflicting feedback, you become the arbiter — which is unpaid work, and usually thankless.
  • Omitting the overflow rate. When a fourth round arrives, you'll be negotiating from a weak position; having the rate in the contract means the conversation is already settled.
  • Not excluding voice, tone, and direction changes from the revisions clause. Without this exclusion, 'can we try a different tone' counts as a revision, and you'll be doing full rewrites inside your round cap.
  • Treating revisions as open-ended time. Tie each round to a specific delivery, not a project phase — otherwise feedback can drift across weeks and you lose the ability to close a round.
Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

How many revision rounds should a freelance contract include by default?+

Two is the standard default for most creative work — design, copy, strategy. One round is common for short-form deliverables (social posts, ad variants, logo marks where only one direction was briefed). Three rounds can be reasonable for stakeholder-heavy projects or large deliverable sets, but more than three usually signals a scoping problem upstream — the brief wasn't clear enough.

What if the client sends revisions to a previous round after the next round has started?+

Name it in the clause: 'Feedback received after a round has closed will be accommodated in the next round, subject to availability.' This prevents feedback from ping-ponging across rounds, which is where round-count inflation actually happens. If a client really needs to reopen a closed round, quote it as an additional round.

Can I include unlimited revisions in my pricing?+

Only if you've priced the engagement as an open-ended retainer, not a fixed-scope project. 'Unlimited revisions' on a fixed-fee project is a margin trap — one difficult client will consume all your profit. If you want to offer it as a premium tier, price it at 2–3x the revision-capped version and be explicit that it buys unlimited rounds, not unlimited scope.

How do I handle revisions when the client's feedback changes direction entirely?+

Recognize it as a re-scope, not a revision. Point to the 'changes to voice, tone, audience, or direction' exclusion in your clause, and offer to incorporate the new direction as a change order. The friction here is usually lower than you expect — clients generally understand that a new direction is new work once you name it.

Should revision rounds be priced per round or per hour for overflow?+

Per-hour for deep work (design, strategy, long-form copy) where the effort per round varies. Per-round for well-bounded work (social posts, email copy, short design exports) where each round is similar in scope. Whichever you pick, put the number in the contract — vague overflow rates are worse than no overflow rate at all.

Who should be named as the approver in the revisions clause?+

The most senior person whose feedback will be binding, and who can commit the organization. Usually this is the person who signed the contract. Do not name a committee or a team — name an individual, ideally with their title, so there's no ambiguity when feedback comes from elsewhere.

Related reading

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.

Try it free →Read the scope creep guide