How to Charge for Out-of-Scope Work (Without the Awkwardness)
Quick answer
When a client asks for something outside the agreed scope, the move is: acknowledge it, name it as extra, and quote it — in that order, in one calm sentence. Something like: "Happy to help with that — it's outside what we originally scoped, so let me put together a quick quote for the extra work." This isn't confrontational. It says yes in spirit, states the boundary as a fact rather than an accusation, and turns the moment into a business decision the client gets to make, rather than an argument you have to win. The awkwardness most freelancers feel here isn't really about the money — it's about not having a script ready. Here's the script, the pricing method, and what to do when it doesn't go smoothly.
Key takeaways
- Use one consistent script. Acknowledge → name it as out of scope → offer a quote.
- Say yes in spirit, price it separately. You're not refusing the client — you're pricing the addition.
- Price it in real numbers, not "that'll cost extra." A specific figure is easier to say yes to than a vague warning.
- Point to the written scope, not your own judgment, when a client disputes it.
- It's fine to occasionally do it free — as a deliberate choice, not a default.
- Frame it around quality, not money, for small requests: "so this gets done properly."
- Honor verbal agreements you already made, then reset the pattern going forward.
- Repeated pushback on fair charges is information about the relationship, not just the invoice.
The core script
This single structure covers the overwhelming majority of out-of-scope requests:
"Happy to help with that — it's outside what we originally scoped, so let me put together a quick quote for the extra work. Want me to send that over?"
Why it works: it opens with agreement ("happy to help"), states the boundary as a neutral fact rather than a complaint, and ends by handing the decision back to the client. Most clients say yes and move on. The ones who push back are usually the same ones who would have kept expanding scope indefinitely if the sentence had never been said — which is useful information in itself.
Variations for different situations
For a small, quick addition: "That's a small one — I can add it for a flat $[X]. Let me know if you'd like me to go ahead." Framing tiny requests around process rather than a big negotiation keeps things light.
For a client who seems to expect it's included: "Our agreement covered [X] — this request is for [Y], which is a bit outside that. I'm glad to add it for [price]." This calmly redirects to the written scope instead of your personal judgment call, which is far less likely to feel like an accusation.
For a recurring pattern of small requests: "I've noticed a few requests coming in outside our original scope — totally understandable as the project evolves. Want me to put together a short addendum so we're both clear on what's included from here?" This addresses the pattern instead of relitigating every individual instance.
How do I actually price it?
Use the same rate basis as your original quote. If your project was priced at an effective $75/hour, price the addition the same way — estimate the hours honestly and multiply. Consistency here matters: pricing the extra work at a wildly different rate than the original project invites suspicion.
Give a specific number, not a warning. "That'll cost extra" leaves the client anxious about an unknown amount and less likely to say yes. "That's an additional $150" is concrete and easy to approve. If you need a quick way to build that number, the Project Quote Estimator turns hours and a buffer into a defensible figure.
For very small additions, use a flat add-on fee rather than itemizing 15-minute increments — it's simpler for both sides and avoids the awkwardness of charging $12.50 for a tiny fix.
What if the client disputes it?
Point to the written scope, not your memory. "Our proposal specified [X pages / Y revisions / Z deliverables] — this request is additional to that" is a fact, not an opinion, and it's very hard to argue with a document both sides signed. This is exactly why a precisely worded scope matters so much upfront — see what causes scope creep and how to prevent it for the contract language that makes this conversation short instead of long.
If there's genuine ambiguity — the original scope really was vague — that's a lesson for the next contract, not necessarily a battle worth fighting on this one. Note it, absorb it if needed, and tighten the scope language for future projects.
Is it ever fine to just do it for free?
Yes — occasionally, and as a conscious choice. A five-minute tweak for a client you value, or a small gesture of goodwill early in a relationship, can be a reasonable investment. The problem isn't doing this sometimes; it's doing it every time, by default, because asking for payment feels uncomfortable. Keep a simple log of what you give away for free, even when you're choosing not to charge — over a few months, that log tells you whether you're being occasionally generous or consistently taken advantage of.
If you already agreed verbally to something for free, honor it for that instance — don't renege — but reset expectations for what comes next: "Happy to include this one, and going forward I'll flag anything outside scope with a quick quote so we're both clear." This fixes the pattern without breaking your word.
What if they push back on every charge?
A client who disputes fair, well-documented out-of-scope charges every single time is telling you something about the relationship, not just about one invoice. It's worth honestly asking whether the account is still profitable once you count the time spent negotiating every add-on, and whether continuing on the same terms makes sense — the same evaluation covered in when to raise your rates or reconsider a client.
Frequently asked questions
What do I say for an out-of-scope request? "Happy to help — it's outside our original scope, so let me quote the extra work." Acknowledge, name it, quote it.
How do I price it? Same rate basis as your original quote, given as a specific number rather than a vague warning.
What if they say it should be included? Point to the written scope document, not your own judgment — it's harder to dispute a shared document.
Should I ever do it free? Sometimes, as a deliberate choice — but log it so you can see the pattern, not do it by default.
How do I avoid sounding petty on small requests? Frame it around getting it done properly, not the dollar amount.
What if I already agreed verbally to free work? Honor that instance, then reset expectations for what comes next.
What if they push back every time? That's information about the relationship — evaluate whether it's still worth the terms.
Does a written scope really help? Yes — it turns most of these conversations from arguments into short, factual exchanges.
Conclusion
Charging for out-of-scope work feels awkward mostly because freelancers wing it in the moment instead of having a script ready. The fix is almost embarrassingly simple: one calm sentence, said the same way every time, that acknowledges the request and quotes the extra work as a normal, unremarkable part of doing business.
Say it early, say it the same way every time, and point to your written scope when there's any dispute. Do that consistently, and "can you also just quickly..." stops being the moment your income quietly leaks away, and starts being a normal, well-paid part of the job.
Quote the extra work in seconds →