When to use a change request
Any time a client asks for something that was not in the original scope. Not after the work is done. Before you start. The change request is not a confrontation. It is a professional communication that says: “I can do this. Here is what it costs.” For the full breakdown of scope creep patterns and their costs, see The Hidden Cost of Scope Creep.
Template 1: Simple scope addition
The client asks for one additional deliverable or feature that was not in the original scope. This is the most common scenario.
Subject: Scope addition for [Project Name]
Hi [Client Name],
Thanks for the direction on [specific request]. I can definitely include this.
This addition is outside the original project scope, so I want to flag the impact before I start: it adds approximately [X] hours to the project, which brings the total from [original fee] to [new fee]. The timeline extends by [X] business days.
If you would like to proceed, I will get started right away. If you would prefer to defer it to a follow-up phase, that works too.
Let me know how you would like to proceed.
[Your Name]
Template 2: Scope expansion with options
The client’s request is large enough to warrant options. Giving the client choices shifts the conversation from “yes or no” to “which option works best,” which almost always leads to a productive outcome.
Subject: Options for [specific request] on [Project Name]
Hi [Client Name],
Great idea on [specific request]. There are a few ways we can approach this:
Option A: Add it to the current project. This adds [X] hours and brings the total to [new fee]. Timeline extends by [X] days.
Option B: Defer to a follow-up phase. We complete the current project as scoped, then tackle this as a separate engagement with its own timeline and fee.
Option C: Swap it for [lower-priority deliverable]. We replace [deliverable] with [new request] at no additional cost, keeping the project on budget and timeline.
I am happy with any of these. Which direction works best for you?
[Your Name]
Template 3: Revision round exceeded
The client has used all included revision rounds and needs additional changes. This template acknowledges the quality goal while establishing the commercial boundary.
Subject: Revision status on [Project Name]
Hi [Client Name],
We have completed the [X] revision rounds included in the project scope. The work is looking great and I want to make sure we get it exactly right.
Additional revision rounds are available at [fee] per round. Each round includes one consolidated set of feedback. If you would like to proceed with another round, just send your feedback and I will confirm the addition.
If you are happy with the current version, we can move to final delivery.
[Your Name]
Template 4: Scope boundary clarification (for Slack/chat)
When a client messages “can you also...” in Slack or chat, you need a response that is fast, friendly, and clear. This one-liner does the job without slowing down the conversation.
“Absolutely, I can look into that. Just flagging that it is outside the current project scope, so I will send a quick estimate before I start. Want me to go ahead and scope it out?”
Template 5: Retainer scope expansion
For retainer clients whose monthly scope has gradually expanded beyond the original agreement. This template uses data to make the case without making it personal.
Subject: Retainer scope review for [month/quarter]
Hi [Client Name],
I wanted to share a quick update on our retainer workload. Over the past [X] months, the monthly hours have averaged [actual hours] against the [agreed hours] hours in our agreement.
I am glad the scope has grown because it means the work is generating value for you. I would like to realign the scope and fee to match the actual workload so we are both clear on expectations.
Option A: Increase the retainer to [new fee]/month to cover the current workload ([actual hours] hours/month).
Option B: Adjust the scope back to [agreed hours] hours/month by prioritizing [core deliverables] and moving [expanded deliverables] to an as-needed basis.
I am happy to discuss either direction. Would next week work for a quick call?
[Your Name]
How to include change request clauses in your proposals
The best time to establish a change request process is before the project starts. Include one or more of these clauses in every proposal or statement of work. They set expectations upfront so that sending a change request later feels like following the agreed process, not introducing a new boundary.
“Work outside the scope described in this proposal will be estimated and approved in writing before it begins.”
“This proposal includes [X] revision rounds per deliverable. Additional revision rounds are available at [fee] per round. A revision round consists of one consolidated set of feedback submitted within [X] business days of delivery.”
“Changes to project scope, timeline, or deliverables requested after project kickoff will be documented as a change request with associated cost and timeline impact for approval before work begins.”
The effective hourly rate math behind change requests
A $3,000 project with 5 hours of unscoped additions at $150/hr is a $750 gift to the client and a 25% reduction in your effective hourly rate. A single change request email costs 5 minutes to send and recovers $750. The ROI on change request documentation is approximately 9,000%.
Use the scope creep calculator to calculate your own numbers. For more on tracking your effective rate, see the complete guide to effective hourly rate.
Change request templates: FAQ
How do I send a change request without being confrontational?
Frame the change request as information, not a boundary. Use language like "I can definitely do this, here is the impact on scope and timeline" rather than "that is not in scope." The templates in this article are designed to be collaborative, not adversarial. Most clients appreciate the transparency.
What if the client pushes back on a change request?
Offer options: add it at additional cost, defer it to a follow-up phase, or swap it for a lower-priority deliverable. Clients push back on price increases but rarely push back on choices. If the client insists on absorbing the addition at no cost, you now have clear data on the effective hourly rate impact for future pricing decisions with that client.
Should I charge for small scope additions?
Track them even if you do not charge for them individually. Small additions accumulate. If a project absorbs five "small" additions of 1 to 2 hours each, that is 5 to 10 hours of uncompensated work. At $150/hr, that is $750 to $1,500. Document every addition and review the total at project end to inform future pricing.
How do I track scope changes during a project?
Log every client request that falls outside the original scope, whether you charge for it or not. At project end, calculate the total additional hours and the effective hourly rate impact. This data is essential for accurate quoting on future projects. Sengi’s project tracking and budget alerts automate this process. Learn more about Sengi’s features.
What is the difference between a change request and a revision?
A revision is a modification to existing deliverables within the agreed scope (changing the color of a header, rewriting a paragraph). A change request is new work that was not in the original scope (adding a new page, creating an additional deliverable). Revision limits and change request processes serve different functions. See Client Revision Policy Examples for revision-specific policies.