A client asks for something extra. You both agree, over email or in a quick call, that it is outside the original scope and will cost more. The work gets done. Then, weeks later, the invoice arrives with a new line item on it — and the client is confused, because they do not remember agreeing to a specific number, or they remember agreeing to "something small" and the line item does not match what they pictured.
This is not usually a dishonest client. It is a gap between when scope changes get agreed (quickly, informally, often in a different place than where the contract lives) and when they show up on paper (the invoice, much later). Closing that gap is less about the invoice itself and more about one short email sent right when the change is agreed, before the memory of the conversation fades.
Why the invoice is the wrong place to introduce a scope change
By the time a client opens an invoice, they are in a different mental mode: checking a total against what they expected to pay, not reviewing a decision. If a scope change shows up there for the first time, even a change they genuinely agreed to, it reads as a surprise rather than a confirmation. The invoice should only ever repeat something the client has already approved in writing. Your job is to make sure that written approval exists before the invoice does.
The fix: confirm the change in writing, the same day
Whenever a scope change gets agreed verbally or in chat, send a short confirmation email the same day. It takes thirty seconds and it is the single biggest thing that prevents invoice disputes later.
Template 1: confirming a scope change right after it's agreed
Use this immediately after a call or chat where extra work was approved.
Subject: Confirming the extra work on [Project Name]
Hi [Name],
Just confirming what we discussed: [describe the extra work] is outside the original scope of [project], and I'll bill it separately at [price]. This will appear as its own line item on the next invoice, alongside the original [amount].
Let me know if anything here doesn't match what you had in mind.
[Your name]
Template 2: when the scope change is a rate instead of a flat price
Useful when the extra work is open-ended enough that an hourly rate makes more sense than a flat fee.
Subject: Re: [the request] — scope and rate
Hi [Name],
Happy to take this on. Since it's outside the original scope of [project], I'll track the time separately and bill it at [hourly rate], with a quick summary of hours on the invoice. I'll flag if it looks like running past [estimate] hours before continuing.
Sound good?
[Your name]
Template 3: bundling several small approved changes into one line
When a project accumulates a handful of small extras, list them together so the client can see the whole picture at once, rather than being surprised by several unfamiliar lines on the invoice.
Subject: Summary of extra items for [Project Name]
Hi [Name],
Before I send the invoice, here is a quick summary of the extras we agreed on this round, outside the original scope:
- [Item 1] — [price]
- [Item 2] — [price]
- [Item 3] — [price]
Total extra: [amount], added to the original [amount] for a final invoice of [total]. Let me know if any of these don't match your understanding before I send it.
[Your name]
Template 4: when the client pushes back on an invoiced item they don't remember agreeing to
This is exactly the situation the templates above are meant to prevent — but it still happens on older threads or quick verbal check-ins that were never written down. Point to whatever record you have, and if there isn't one, settle it generously rather than over an invoice.
Subject: Re: Invoice question
Hi [Name],
Good question — this is for [describe the work], which came up on [date] when [brief context]. [If you have a written record:] Here's the message where we confirmed it: [quote or link]. [If you don't:] I don't have this one in writing on my end either, so let's go with your recollection — I'll remove it from this invoice and we can revisit if it comes up again.
[Your name]
Template 5: setting the expectation up front, before any extras happen
The easiest version of this problem to solve is the one that never happens. Set the expectation at the start of the project, so the first scope change does not feel like a new rule being introduced mid-way.
Subject: A quick note on scope changes
Hi [Name],
One thing I like to flag at the start of every project: if anything comes up that's outside the agreed scope, I'll always confirm it with you in writing — what it is and what it costs — before doing the work or adding it to an invoice. That way there are never any surprises on either side.
Looking forward to getting started!
[Your name]
Keep a running record, not just a thread of emails
Confirmation emails solve the immediate dispute, but they still leave the information scattered across a long project thread. A simple log — one row per approved extra, with the date, the price agreed and a link back to the confirmation — turns "did we actually agree to this?" from a search through old emails into a single lookup, and makes the final invoice something you can build directly from the log instead of from memory.
The Client Approval Log + 50 Client Messages pack includes a Revisions sheet built for exactly this — mark each extra as in scope or billable, record the rate, and see the unbilled total at a glance — plus ready-to-paste messages for scope creep and extra revisions. See it on Gumroad: Client Approval Log + 50 Client Messages.
Client Approval Log + 50 Client Messages
Keep a written record of every approval, and ask for it politely. $5.
Get it on Gumroad