Charging for extra revisions: how to tell the client (templates)

Every freelancer hits this moment eventually: the project included two rounds of revisions, you are on round four, and the client is asking for "just one more small thing." The work itself might be small. The pattern is not. If you do not say something, round five and six will follow, unpaid, and the project quietly stops being profitable.

The hard part is rarely the math. It is finding words that charge fairly without sounding like you are punishing the client for having opinions. Below is how to think about pricing extra revisions, and messages you can send when the moment comes.

Why this conversation feels harder than it is

Freelancers often delay this message because it feels like confrontation. It usually is not, for two reasons. First, if revisions were specified in your scope or quote, you are not inventing a new rule — you are referencing one the client already agreed to. Second, most clients genuinely do not track how many rounds they have used; they are not trying to get free work, they just lost count. A clear message usually resolves this calmly, because it gives them the missing information rather than accusing them of anything.

Decide your rate before the conversation, not during it

Walking into this message without a number ready is what makes it stressful. Pick one of these approaches ahead of time, for every project:

• Hourly rate for extra rounds. Simple and transparent, works well for revisions that vary a lot in size.
• Flat fee per extra round. Easier for the client to budget for, works well when revision rounds tend to be similar in scope.
• Percentage of project fee per round. Common for design and video work, scales naturally with project size.

Whichever you choose, write it into your contract or quote up front: "Includes [2] rounds of revisions. Additional rounds are billed at [rate]." That single sentence does most of the work for you later — the message you send when the moment comes just points back to it.

Template 1: the first time the limit is reached

Use this when the client is about to start a revision round beyond what was included. Lead with willingness to help, then state the number.

Happy to make these changes. Just flagging that this would be round [4] — the project included [3] rounds, so this one would be billed at [rate]. Let me know if you'd like me to go ahead, and I'll get started as soon as you confirm.

Template 2: when the client did not realize they were over the limit

Some clients are surprised to hear a limit existed at all, especially if time has passed since the quote. Be specific about where it was agreed.

No problem on the changes — quick note before I start: our agreement included [3] rounds of revisions (see the scope section of the proposal from [date]), and we're now on round [4]. I'd bill this round at [rate] on top of the original quote. Happy to proceed on that basis, just wanted to confirm first.

Template 3: offering a choice instead of a flat "no"

Giving the client a decision to make, rather than a rule to accept, usually gets a faster and friendlier response.

For this round, there are two ways to handle it: I can bill it at [rate] as an extra round, or we can treat it as the start of a second, smaller phase with its own short scope. Either works on my end — let me know which you'd prefer.

Template 4: when the "small" request keeps growing

Sometimes a single revision request balloons as you work on it. Flag the moment it starts, rather than absorbing the extra time quietly.

I started on this and it's turning into more than a quick tweak — closer to [X hours / a half day] of work rather than a small fix. I can keep going at [rate], or we can scope it down to fit inside the current round. Your call — just didn't want to go ahead without checking first.

Template 5: confirming the extra charge in writing after a verbal yes

If the client agreed on a call or in chat, put it in writing immediately so there is a record for the invoice later.

Confirming from our chat: round [4] of revisions on [Project] will be billed at [rate], in addition to the original [price]. I'll include this on the next invoice. Let me know if anything here doesn't match what you understood.

What to do if the client pushes back

A client who disputes the extra charge is usually disputing one of two things: whether the limit really existed, or whether this round really counts as "extra." Resolve both with the same move — point to the written record. If you sent a scope document, quote it. If you did not, this is the moment to start keeping one, so the next project does not repeat the ambiguity. Our guide on scope creep messages covers the related case of new requests that were never part of the project at all, which uses a similar approach: be specific, give the client a choice, and put the answer in writing.

Keep the count, not just the conversation

The actual friction in these conversations rarely comes from the client disagreeing with your rate. It comes from both sides being unsure how many rounds have actually happened. A simple log that marks each round "in scope" or "extra" the moment it starts removes the guesswork, so the message above becomes a formality instead of an argument.

The Client Approval Log + 50 Client Messages pack includes a revisions tracker built for exactly this, plus ten ready-to-paste messages for scope creep and extra revisions. See it on Gumroad: Client Approval Log + 50 Client Messages.