A useful boundary email does not argue about whether the client should have asked. It makes the new decision visible: what changed, what it affects, and which option the client wants to approve.
Free reference
Keep seven calm replies nearby.
Get the concise PDF and the automated follow-up sequence.
Use this four-part structure
- Anchor. Name the approved deliverable or limit.
- Delta. Describe the new request without blame.
- Impact. State effort, fee, dependencies, or date movement.
- Choice. Offer concrete options and wait for written approval.
01
Short and direct
Thanks for the request. It sits outside the deliverables we approved for this phase. I can quote it as an addition, trade it for an existing deliverable, or keep the current plan unchanged. Which option would you like me to prepare?
02
Add it for a fee
I compared this request with the approved scope. It adds [work] and approximately [effort]. I can include it for [fee], with delivery moving from [current date] to [new date]. Please confirm that option in writing and I will update the production plan.
03
Trade scope instead of increasing budget
We can keep the current fee and deadline if we replace [approved deliverable] with [new request]. That keeps the workload balanced. Please confirm which item should remain in the plan before I proceed.
04
Schedule it for a later phase
This is a reasonable addition, but including it now would put the approved milestone at risk. I can scope it as phase two for [date], or price the extra capacity needed to add it to the current phase.
05
Hold until approval arrives
I have logged the request and its impact, but I do not yet have written approval for the fee and timing change. I will keep it outside the production queue and continue with the approved plan until you confirm the selected option.
06
Decline without blaming the client
I cannot add this request inside the current engagement without putting the agreed work at risk. I can recommend a separate phase or another specialist, while keeping this project focused on the approved deliverables.
Why choices work better than a defensive no
A single yes-or-no boundary can feel like a dead end. A small choice set restores agency: pay for the addition, trade something, schedule it later, or keep the current plan. Each option protects the project while letting the client control the business decision.
Do not negotiate against yourself
Avoid apologizing for a documented boundary or beginning “just this once.” If you choose to absorb work, record that as a deliberate commercial decision so the cost does not disappear.
Prepare the evidence before you send
Keep the approved baseline, request, estimate, proposed fee, schedule impact, and approval in one record. Start with the scope of work template, then use the change request workflow when the project changes.
Frequently asked questions
How do I tell a client work is out of scope politely?
Refer to the approved deliverable, describe what changed, explain the fee or timing impact, and offer two or three practical options before asking for written approval.
Should I start the extra work before the client approves it?
No. Keep the request outside the production queue until the client confirms the selected fee, trade, schedule change, or later phase in writing.
What if the client says the request is small?
Discuss impact rather than size. A visible edit can still add research, dependencies, testing, review time, or risk to the approved deadline.