The request always arrives mid-project, always politely, and always framed as small. "One more thing while you're in there." How you answer the first one decides how many more arrive.
This post gives you three ready-to-send versions of the out-of-scope email: friendly, firm, and formal. Each fits a different situation. Copy the one you need, adapt two lines, send it.
The Anatomy: Acknowledge, Classify, Route
All three templates share the same skeleton. Learn it once and you can improvise the rest of your career:
- Acknowledge. One positive sentence about the request itself. You are not the scope police, you are a professional who likes good ideas.
- Classify. One neutral sentence placing the request against the agreed scope. Not "you're asking for too much," but "this sits outside what we scoped."
- Route. The path forward: a price for doing it now, a slot in phase two, or a change order for sign-off. The client always leaves the email with an action available, never with a flat no.
The classification step only works if there is a written scope to classify against. If your projects start without one, that is the first hole to fix: see the scope of work template.
Version 1: Friendly (Single Small Request)
The situation: a good client, first offense, a request that would take an hour or two. The relationship is worth more than the hours, but the precedent still needs marking.
The scenario: you are building a marketing site; the client asks if you can "quickly add" a testimonials section that was not in the page list.
Subject: Re: testimonials section
Love this idea, testimonials will pull their weight on this page.
Quick flag: it's not in the page list we scoped, so I want to handle it properly rather than squeeze it in quietly. Two options:
A. I add it now: 2 hours at my usual rate ($150), design consistent with the rest, and it ships with the current milestone.
B. We park it for the post-launch batch and I'll quote it with whatever else has collected by then.
Just reply A or B and I'll take it from there. Either way, good call on this.
Why it works: the tone costs you nothing, but the structure does everything. The request got priced, the "quietly squeeze it in" norm got rejected out loud, and the client got two easy paths instead of a refusal. Most clients pick A without blinking, and you just got paid for work you would otherwise have absorbed.
The "just a quick thing" pattern this defuses is worth understanding on its own: the just-a-quick-thing problem.
Version 2: Firm (Small Addition, Real Hours)
The situation: the request means a day or more of work, or it is the third "small thing" this month. Friendly did its job; now the boundary needs weight.
The scenario: mid-way through an app build, the client asks for a settings screen that was explicitly not in the feature list.
Subject: Settings screen: scope check before we proceed
Thanks for the detail on the settings screen, the requirements are clear.
Checking it against our signed brief: the feature list covers onboarding, dashboard, and reports, and the settings screen is listed under "out of scope / phase 2." So this is new work, and I want to be upfront about what it involves rather than let it blur into the current build.
Scoping it roughly: design plus build plus testing is 12-16 hours, which at my project rate is $1,400-$1,900. It would also move delivery back about one week, since the current milestones are full.
If it's a priority, I'll write it up as a one-page change order today and we can slot it in cleanly. If it can wait, phase 2 is the natural home for it and the current deadline holds.
Which way do you want to go?
Why it works: it quotes the brief verbatim, which moves the conversation from opinion ("that feels out of scope") to record ("it is listed under out of scope"). The cost lands as a range, the deadline impact is named, and the client decides with full information. No apology appears anywhere in the email, because nothing needs apologizing for.
If pushback comes, do not renegotiate in defensive fragments. The scripts in scope creep email templates cover the second round.
Version 3: Formal (Major Expansion)
The situation: the request is not an addition, it is a different project wearing the same invoice. Multi-week impact, new deliverable categories, possibly a new stakeholder behind it.
The scenario: you were hired to design and build a brochure site. Six weeks in, the client asks to "also add a members area with login, saved content, and payments."
Subject: Members area request: change order required
Hi [Name],
Thanks for outlining the members area concept. I can see the business case, and it's buildable.
I need to be clear about what it is contractually: this is a substantial expansion beyond our agreement dated [date], which covers a marketing site with no user accounts or payment functionality. A members area with authentication, saved content, and payments is a separate build with its own architecture, security, and testing requirements.
Rather than estimate it casually, I've prepared a change order covering:
- Scope: account creation and login, member dashboard, saved content, payment integration
- Cost: $8,500-$11,000 depending on the payment provider and content permissions model
- Timeline: 4-5 weeks, beginning after current site launch
- Impact on current work: none, the existing scope and launch date hold as agreed
The change order is attached. If you'd like to proceed, sign and return it and I'll schedule the work. If the budget or timing doesn't fit right now, the current project continues exactly as planned and we can revisit this next quarter.
Happy to walk through the numbers on a call if useful.
[Your name]
Why it works: the formality is the message. A casual reply to a request this size signals that scope is negotiable by email. Referencing the agreement date, attaching a real document, and explicitly protecting the current deadline ("none, the existing scope holds") tells the client the process is solid, and processes are what enterprises and serious founders actually trust.
Which Version When
| Signal | Friendly | Firm | Formal | |---|---|---|---| | Effort involved | Under ~3 hours | Half a day to 2 days | Multi-week | | Frequency | First ask | Repeat pattern | Any | | Deadline impact | None | Days | Weeks or restructuring | | Paper trail needed | Email is enough | Email quoting the brief | Signed change order | | Relationship stage | New or good standing | Any | Any, especially with new stakeholders |
When in doubt, go one level more formal than feels natural. Nobody ever lost a client by writing down what was agreed; plenty have lost margins by not doing so.
The Three Mistakes That Undo All of This
Apologizing. "Sorry, but I think this might be out of scope..." frames the scope as your inconvenient personality trait. The scope is a shared document both parties signed. Reference it like one.
Saying no without a route. A bare "that's not in scope" leaves the client stuck holding a need with no path. Every template above ends with a decision the client can make. That is the difference between a boundary and a wall.
Absorbing the first one silently. The first free favor sets the price of every following favor at zero. If you choose to gift something small, name it as a gift. Visibility is what keeps generosity from becoming precedent, a dynamic covered in nine real scope creep examples.
Classify every mid-project request out loud, price it or park it, and the "one more thing" emails stop being a threat to your margin. They become order forms.
Try the free tool
This article walks through the problem; the free tool turns the answer into a copy-pasteable output in 30 seconds. No account, no signup.
→ Use the Change Request Letter Generator
Want this across every project?
Briefance saves every brief, scope check, change order, and revision counter against the client and project. Free plan: 3 briefs/month.