How many revisions should a freelancer include? Wording for a revision limit clients actually accept

"How many revisions should I include?" is a question almost every freelancer has to answer before sending a quote. You'll often hear two or three rounds. That's a reasonable starting point, but the number alone won't protect you.

Here's an invented example of how a limit fails. You promise "two rounds of revisions". The client sends feedback on Monday, adds three more notes on Wednesday, and their manager weighs in the following week. Is that one round or three? Is "can we try a completely different layout?" a revision at all? Nobody agreed, so you end up doing whatever is asked.

A revision limit that works answers four questions, and the number is only one of them:

  1. How many rounds?
  2. What counts as one round?
  3. How long does the client have to send feedback?
  4. What happens after the last round?

This article covers each one. Then it gives you copy-paste revision-policy wording for design, writing and development work, plus a reply for when the rounds are used up.

1. How many rounds: a convention, not a rule

Two or three rounds per deliverable is a popular starting point. It isn't an industry standard, and no rule says you have to offer it.

Use it as a default, then adjust:

Whatever you pick, put it in writing. A limit the client never saw isn't really a limit.

What about "unlimited revisions"?

Some freelancers offer unlimited revisions to win work. If you do, you still need two limits around it: a time window ("revisions requested within 14 days of delivery") and a definition of what a revision is. Otherwise "unlimited" can quietly grow to cover new work.

2. What counts as a round (and what doesn't)

This is the line that does the most work. A good default:

A round is all of the client's changes for one draft, gathered into a single list and sent by one named person.

You get one considered set of notes instead of a trickle, and the client's team settles its own disagreements before the list reaches you.

Just as important is what isn't a revision. A revision changes something you already agreed to make. A new request changes what you're making. Some examples:

Service Revision (counts as part of a round) New request (quote it separately)
Design Change the button colour, swap a photo, tighten the spacing A new concept after one was approved, an extra page size, a social version of the banner
Writing Rephrase the intro, cut 100 words, change the tone in one section A different angle or audience, a second article, a rewrite after the outline was approved
Development Fix a bug against the agreed spec, adjust layout to match the approved design A new feature, a new integration, a redesign of a page that was signed off

Bug fixes deserve a note. Fixing something that doesn't work as agreed is your job, and shouldn't use up a round. Say so in your policy. It's fair, and it makes the rest of the limit easier to accept.

If a request falls in the "new request" column, it's a change, not a revision. The out-of-scope request email guide has a triage table and replies for exactly that situation.

3. The feedback window

A feedback window says how long the client has to respond to a draft, for example three or five working days. It's mainly about your schedule. Without it, a project can stall for weeks and then expect the original deadline to hold.

Add one plain sentence that links late feedback to dates: "Each working day that feedback runs late pushes the next milestone back by a working day." It's not a fee or a punishment. It just makes clear that the schedule depends on both of you.

4. After the last round

Decide this before the project starts, so it's a process rather than an argument. Common options:

Pick one, put the price or rate in your proposal, and the conversation later is just "as agreed".

Copy-paste revision policy wording

Three versions to adapt. Replace the bracketed parts with your own numbers and terms. Not legal advice and not a contract: these are plain-language summaries to sit alongside your contract. If your contract says something different, the contract wins, so make them match.

Design

Revisions. This project includes [2] rounds of revisions on the initial concepts and [1] round on the final files. Each round is a single list covering all your changes to that draft, sent by [CLIENT CONTACT]. Please send feedback within [3] working days of each draft. Late feedback pushes the next milestone back by the same number of working days.

A revision changes something in the agreed design. New concepts after a concept is approved, extra sizes or formats, and new deliverables aren't revisions. I'll quote them separately before starting. Extra rounds are [PRICE] each.

Writing

Revisions. Each piece includes [2] rounds of edits. Each round is one set of comments, in one document, from [CLIENT CONTACT]. Please return comments within [5] working days. Later comments move the delivery date by the same number of working days.

Edits cover wording, structure, length and tone within the agreed brief. A new angle, a new audience, or a rewrite after the outline was approved counts as new work and will be quoted first. Extra rounds are [PRICE] per piece.

Development

Changes and fixes. Bugs, meaning anything that doesn't work as described in the agreed spec, are fixed at no charge until [DATE / X days after launch]. Bug fixes don't count as revision rounds.

The build includes [2] rounds of changes to the agreed features and layout. Each round is a single list or ticket from [CLIENT CONTACT], sent within [3] working days of each review build. New features, integrations or redesigns of approved pages are changes to the scope. I'll estimate them before starting, at [HOURLY RATE] or a fixed quote.

The "you've used your rounds" reply

When the next round of feedback arrives after the included rounds are used, reply before doing any work. Keep it short and friendly, and give the client a choice.

Hi [NAME],

Thanks for these notes. Before I start: we've used the [2] revision rounds included in the project, so this would be an extra round.

A few options:

  • Extra round: [PRICE], and I'd send the update by [DATE].
  • Just the essentials: if only one or two of these matter for launch, tell me which and I'll check whether they fit as small final fixes.
  • Leave it as is: I'll send the final files on [DATE] as planned.

If you go with the extra round, sending everything in one list helps me get it right first time. Which would you like?

Best, [YOUR NAME]

Note what this reply doesn't do. It doesn't apologise, quote the contract or say no. It names the situation, gives options and asks for a decision.

How to get clients to accept a limit

A limit the client saw before signing is much easier to accept than one that first appears halfway through. So:

The client onboarding checklist shows where the revision limit fits among the other steps before kickoff.

If you'd rather not set this up from scratch: the Scope Guard & Client Onboarding Kit (coming soon) includes a one-page scope summary with fields for revision rounds, what counts as a round, and the feedback window, plus ten email scripts for the moments where scope usually slips.

Want the full set?

This article covers revision limits. The Scope Guard & Client Onboarding Kit covers the whole path from first brief to kickoff:

The templates come as .docx and .md, with CSV checklists for Google Sheets or Notion. It isn't a contract and it isn't legal advice: it's the process around your contract.

The kit isn't on sale yet. See what's in the kit

← All posts