Scope Change Request Examples (Copy-Paste for Freelancers)
Real-world scope change request examples for design, dev, and brand projects — client emails, freelancer responses, and when to issue a change order instead of revising.
Part of Scope Drift™ guides guides →
- scope change request
- scope change request examples
- scope creep
- change order
When a client asks for work outside the locked SOW, how you respond sets whether you eat the cost or get paid. These scope change request examples show in-scope revisions vs out-of-scope drift — with copy you can adapt.
For templates, see Change order template and Out-of-scope work templates.
Example 1: Design — extra formats (out of scope)
Client: "Can you also export the logo for embroidery and merchandise?"
Why it is drift: Original milestone listed web + print PDF; merchandise was not in DoD.
Response:
Happy to — embroidery and merch lockups were not in Milestone 1's locked deliverables. I'll send a short change order for [amount] covering [deliverables] and [timeline]. Work starts once both parties accept.
Example 2: Design — kerning tweak (in scope revision)
Client: "Can you tighten kerning on the wordmark?"
Why it is in scope: Refinement of agreed logo within revision round 2 of 3.
Response:
Yes — that's included in revision round 2. I'll update and re-submit for review by [date].
Example 3: Dev — new API integration (out of scope)
Client: "Can we hook this up to Salesforce too?"
Why it is drift: Milestone covered Stripe checkout only.
Response:
Salesforce integration is a new integration surface — outside Milestone 3 scope. I can quote a change order with API discovery, implementation, and testing hours. Want a one-page estimate?
Example 4: Brand — new direction (out of scope)
Client: "Actually let's explore a completely different visual direction."
Why it is drift: Not refinement — new concept phase.
Response:
A new direction is a new concept phase beyond our three revision rounds on the approved route. Options: (a) change order for 2 new concept directions, or (b) approve current direction and proceed to guidelines milestone.
Example 5: "Small" copy expansion (often drift)
Client: "Can you write all the product descriptions too?"
Why it is drift: Copywriting not in creative deliverables list.
Response:
Copy was listed as client-provided in our agreement. I can add copywriting via change order at $[rate]/page or refer a copy partner — your call.
Decision table
| Request | In scope? | Action |
|---|---|---|
| Refine locked deliverable | Usually yes (if rounds remain) | Revise |
| New deliverable type | No | Change order |
| New integration / platform | No | Change order |
| New concept direction | No | Change order |
| More revision rounds | No (if limit hit) | Change order |
Estimate creep before you say yes
Use the scope creep calculator to ballpark unpaid risk on hourly work.
In Zlaip
Scope Drift™ surfaces likely out-of-scope requests in Accountability Chat — Ignore (noise) or Create Change Order (billable expansion).
Next: Scope Drift™ guides