Client script library
Tell the client what the approved scope covers, identify the added request neutrally, and offer a priced or swapped next step instead of a blunt refusal.
Direct answer
Tell the client what the approved scope covers, identify the added request neutrally, and offer a priced or swapped next step instead of a blunt refusal.
Definition: An out-of-scope request changes a deliverable, quantity, revision, dependency, stakeholder group, channel, or schedule beyond the approved plan.
Start with the project fact: what was approved, what changed, and who can authorize the next step. Customize the wording so it matches your agreement and normal client channel.
State any fee and schedule impact together. Do not begin changed work until the client gives written approval and the current project plan reflects the decision.
Use this as a practical starting point. Replace every placeholder with a fact from the approved project.
I can help with that. The approved scope covers [included work], while this adds [new work]. I can add it for [fee] with delivery moving to [date], or swap [item] to keep the current plan.
Use it before ambiguity turns into unplanned work. For contract language, include it before kickoff; for a client script, send it as soon as a request changes the approved plan.
No. This is practical business wording, not legal advice. Adapt it to your agreement and ask a qualified lawyer about legal requirements in your jurisdiction.
Professional boundary language connects a scope fact to a helpful next step.
Contract clause libraryAn additional-work clause separates helpful incidental discussion from billable services and requires approval before extras begin.
Free templateA ready-to-customize out of scope email template with practical guidance for using it professionally and keeping the client relationship intact.
Educational information only; not legal advice. Review contract language for your jurisdiction and circumstances.
ScopeShield
$39 · instant access