How to Tell a Client Something Is Out of Scope

The "while you're at it, could you also…" request is one of the most uncomfortable moments in freelancing. The work is beyond what you agreed, but the client does not know that — to them it is one small extra — and saying so feels like picking a fight over something they think is already included. The good news is that this is a script problem, not a confrontation. Handled well, flagging an out-of-scope request is a normal, calm part of the job that clients respect.

Here is exactly how we would say it, plus the scripts to copy.

What to say when a request is out of scope

Name it as a scope question, not a refusal: acknowledge the request warmly, say plainly that it sits outside what you both agreed, and offer the path to a yes in the same breath. The move is "happy to do that — since it is beyond our original scope, let me write it up as a quick add-on." You are not saying no. You are saying yes, with a small step in front of it.

That single sentence does three things at once. It keeps the relationship friendly ("happy to do that"), it states the boundary as a shared fact rather than an accusation ("our original scope," not "your request"), and it hands the client a clear, low-drama way forward (a written add-on). Lead with the yes, follow with the paperwork, and almost nobody bristles.

Why "no" is the wrong frame — and "not included" is the right one

Frame the request as outside the agreement, never as something you are unwilling to do. "I can't do that" invites an argument about whether you should; "that isn't part of what we scoped" points at a document you both agreed to, and there is nothing to argue with. The distinction is small in words and enormous in effect.

The reason this works is that a boundary set on day one is a term, while a boundary reached for on day forty feels like a threat. If your original agreement named the deliverables — and named what was not included — then flagging an extra is simply reading back a decision the client already made. That is why the real fix for these moments happens at kickoff, before any of them arrive:

• Name the concrete deliverables in the agreement, and name what is explicitly excluded.
• Set a revision limit, and say what happens once it is reached.
• Get it signed, so "what did we agree to?" always has a documented answer.

If you want the up-front side of this in full, our freelance project kickoff checklist walks through the five things to settle before a minute of billable work.

You are not the bad guy for protecting the scope. The agreement is doing the asking; you are just reading it back.

Copy-paste scripts for the awkward moment

Use a warm opener, a plain statement that the request is outside scope, and an immediate offer to add it as a change order. Here are three versions for the situations that come up most — adapt the bracketed parts to your voice.

For a genuinely new deliverable:

Hi [Name] — happy to take this on. Since a [second landing page / extra logo variation / new section] is beyond what we scoped in the original agreement, we'll write it up as a quick change order so the cost and timeline are clear before we start. Sound good?

For "just a few more" revisions past the agreed limit:

Thanks for the notes! We're now past the [two] revision rounds we included, so this next round would be a small add-on. We'll send it over as a change order — same easy sign-off — and then dive straight in.

For a request that quietly changes direction on already-approved work:

Good news is this is very doable. Because it reworks the [homepage] we'd already signed off on, it counts as new work rather than a tweak — so we'll capture it as a change order with the extra time and cost spelled out, and go from there.

Notice the shared shape: every script opens with warmth, states the boundary as a matter of fact, and treats the change order as ordinary procedure rather than a penalty. The tone is "this is just how we work," which is exactly what makes it land.

Handle the pushback calmly

If a client pushes back with "I thought that was included," do not defend — point to the agreement and stay neutral. Something like: "Totally fair to check — here's what we scoped, and this falls just outside it. Happy to add it; here's the change order." You are not litigating; you are showing the shared document and moving on.

Most pushback is not bad faith. It is a client who genuinely lost track of where the line was, which is precisely why a written, signed scope is worth so much: it replaces two conflicting memories with one record. When the boundary lives in a document the client agreed to, the conversation stops being your word against theirs. For more on why unbilled extras pile up in the first place, our guide on what scope creep is and how to stop it goes deeper on the pattern.

Turn the yes into a change order

The cleanest way to say yes to an out-of-scope request is to convert it into a change order — a short written add-on that names the new work, its cost, and its effect on the timeline, which the client approves before you start. It turns a fuzzy "is this extra?" into a documented decision, so the extra is priced and agreed rather than quietly absorbed. If you have never written one, how to write a change order for a freelance client has a full copy-paste template.

This is the seam Drift Catch is built for. When a request lands outside the signed scope, you turn it into a change order in the same place the original agreement lives, the client e-signs it, and it attaches to the project with a full audit trail — a simple electronic signature recognized under modern e-signature laws such as the U.S. E-SIGN Act and UETA, and Canada's PIPEDA Part 2. Change orders are part of the Solo plan and up. On the Pro plan, once you connect Stripe, you can also collect payment on a change order inside Drift Catch — and require the extra to be paid before that work opens, so "I'll settle up later" simply means the add-on waits until it is paid. You can see that flow in our guide to stopping scope creep with e-signed change orders.

The short version

Telling a client something is out of scope is not a "no" — it is a warm yes with a small step in front of it. Acknowledge the request, name it as outside the agreement rather than as a refusal, and offer to capture it as a change order in the same breath. Keep the tone matter-of-fact, point to the signed scope when anyone is unsure, and let the document do the asking. Do that consistently and the "one more thing" moment stops being a source of dread — it becomes a normal, billable part of the work.

This is general business information, not legal advice. For agreement and change-order language that fits your specific situation, check the rules in your region or have a professional review it.