How to Tell a Client Their Request Is Out of Scope (Word-for-Word Scripts)

The reason freelancers absorb free work isn't greed on the client's side. It's that saying "that's out of scope" feels like starting a fight. It isn't — if you use the frame that professionals use: a scope flag is not a refusal. It's a quote.

You are not saying no. You are saying "yes, and here's the price." That reframing turns the scariest email in freelancing into a line item.

These scripts assume you already have something written down to cite. If you don't, start with what scope creep is and the six clauses that make the check possible.

The master script

"Good news — this is doable. Checking it against our agreement, it falls outside the current scope [optionally: specifically the X clause], so I'll put together a change order. Based on what's involved, it should be around $X and would add about Y days. Want me to send that over?"

Why this works: it leads with willingness, cites the agreement as a neutral third party (the contract says it, not you), prices the work instead of dramatising it, and ends with a trivially easy yes.

Variations for the five classic situations

The "quick favour":

"I can definitely do that. It's not in the current scope, so I'll send a quick change order — should be about $X. If it's urgent I can start as soon as that's signed off."

The revision overrun:

"We've used the two included revision rounds, so this round would be billed at $X/hr per the agreement — likely around $Y total. Alternatively I can hold these until you have a bigger batch."

(Full clause and math: can you charge for extra revisions?.)

The assumed retainer:

"Maintenance after delivery isn't included in this project — but I do offer a care plan at $X/month if you'd like ongoing updates handled. Happy to send details."

The definitional stretch ("that's still the contact form, right?"):

"The form as scoped delivers submissions to your email. Connecting it to Mailchimp is an integration, which is a separate piece of work — I'd price that at about $X. Want me to write it up?"

The retroactive agreement ("we agreed customers could order online"):

"Let me check what we both signed. The SOW lists an informational Order Info page and explicitly excludes e-commerce. If we discussed online ordering earlier, that didn't make it into the signed scope — happy to scope it properly now and send a change order."

Notice that one is careful: you don't call the client a liar, you go to the document. This is also the moment where having the written scope and the client's message side by side matters — Stria keeps both on the record and quotes the relevant clause back to you, so the reply writes itself.

What if they push back?

Then you learn something valuable about the client at the cost of one awkward email instead of a thousand dollars of free work. The clients worth keeping respect a priced boundary. The ones who don't were never going to pay for the extra work anyway.

When they say yes to the price, send a short change order the same day — template here. When you want the check automated before you type the reply, start a 14-day trial or try scope-check with no account.

Frequently asked questions

How do you tell a client something is out of scope?

Lead with willingness, cite the agreement as a neutral third party, price the work instead of dramatising the refusal, and end with an easy yes. The frame professionals use: a scope flag is not a refusal — it is a quote. You are saying yes, and here is the price.

What if the client pushes back on a change order?

Then you learn something valuable about the client at the cost of one awkward email instead of a thousand dollars of free work. Clients worth keeping respect a priced boundary. The ones who do not were never going to pay for the extra work anyway.

Should you argue about what was discussed verbally?

No. Go to the document. "Let me check what we both signed" is careful and professional; calling the client a liar is not. If earlier discussion did not make it into the signed scope, say so plainly and offer to scope the new work properly with a change order.

How does Stria help write the out-of-scope reply?

Stria keeps the written scope and the client's message side by side and quotes the relevant clause back to you, so the reply writes itself from the record rather than from memory. Forward the email; you choose what is sent — there is no mailbox to connect.