Use email for the decision, not for blame
The client may not recognize the change. Quote the original agreement rather than describing the request as unreasonable. If the disagreement is about work that was already promised, clarify that first; this email is not a reason to charge again for an included obligation.
Escalate material changes to a change order
When a change alters several milestones, dependencies, or deliverables, use this email to introduce a separately numbered change order. Keep both the discussion and the approval record.
Copy-and-customize preview
Free editable sample
No purchase or email required.
Subject: Approval needed — [requested addition] Hi [Client], The approved scope dated [date] covers [included work]. Your request for [addition] adds [specific difference]. Option A: add it for [fee], with delivery on [date]. Option B: replace [included item] with [addition] for [revised fee and date]. Please confirm your preferred option in writing. Until then, I will continue with the approved scope. [Name]
| Field | Why it matters | Example |
|---|---|---|
| Scope reference | Makes the boundary verifiable. | Proposal v2, approved September 4: three pages. |
| Difference | Names the new work. | A fourth page with a separate review round. |
| Decision | Prevents ambiguous permission. | Approve option A and the revised delivery date. |
Use it in four steps
- Open the approved scope and locate the relevant exclusion
- Describe the new outcome without blame
- Estimate the addition or a viable swap
- Send the options and record approval before starting
Customization checklist
- Use the actual approved document version
- Remove any swap you cannot deliver within the original budget
- Name the authorized decision-maker
Common mistakes to avoid
- Calling a request out of scope without identifying the agreed boundary
- Offering a swap that still increases effort
- Assuming a friendly acknowledgement approves the fee
Frequently asked questions
- Can a reply approve the addition?
- A clear written reply may provide a practical approval record, subject to your agreement and applicable law. Specify the option, amount, and revised delivery date; use a formal change order where required.
- Should I stop the entire project?
- Not automatically. Continue unaffected approved work where practical and identify any task that must pause pending the decision.
Continue with the next decision
How to Tell a Client a Request Is Out of Scope
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.
Free editable artifactFreelance Change Order Form Template
A freelance change-order form records the original agreement, requested difference, added and removed work, price adjustment, revised milestones, dependencies, and authorized approval. Give each change an identifier so the client can approve a specific version.
Publisher comparisonRevision vs Scope Change: How to Tell the Difference
A revision refines an included deliverable against the approved brief. A scope change alters the brief, quantity, direction, format, audience, or other agreed requirements. Corrections needed to meet existing acceptance criteria should not automatically be treated as new billable scope.
Change Order TemplatesFollow Up When a Client Does Not Approve an Out-of-Scope Estimate
Follow up by restating the pending option and its scheduling dependency. Silence is not approval. Continue unaffected work and reconfirm availability if the original estimate window has passed.