Use the structure below for freelance projects, consulting engagements, retainers, and small-agency work. Keep it short enough to read in one sitting, but specific enough that the decision can still be understood months later.
Copy this change request structure
Project: [project name]
Request ID and date: [CR-001 · date]
Requested by: [name and role]
Original baseline: [the approved deliverable, assumption, or limit]
Requested change: [plain-language description of the new request]
Reason: [business need or context supplied by the client]
Impact: [effort, dependencies, cost, risk, and schedule effect]
Options: [add for a fee] · [trade another deliverable] · [schedule later] · [keep original plan]
Recommended option: [your recommendation and why]
Decision required by: [date]
Approval: [selected option, approver, date, and written confirmation]
How to use the template
- Anchor to the baseline. Quote the relevant deliverable, assumption, or constraint from the approved scope.
- Describe the delta. Explain exactly what is new or different.
- Quantify before pricing. Estimate the actual effort and downstream effect.
- Present choices. A change request should help the client decide, not corner them.
- Record written approval. Save the selected option before work enters production.
What counts as a change?
A request usually deserves review when it adds a deliverable, changes an approved direction, introduces a new stakeholder, expands the audience, moves a deadline, increases review rounds, or changes an assumption your estimate depended on. “Small” is not a useful classification; impact is.
Operational template, not legal advice
A change record supports clearer decisions, but it does not replace a properly drafted agreement. Adapt the language to your contracts, jurisdiction, and professional advice.
Change request email
Thanks for the request. I compared it with the approved scope and it changes [baseline item]. I have outlined the effort, timing, and options below. Please confirm your preferred option in writing before [decision date], and I will update the production plan.
Why a ledger is better than scattered forms
Individual documents help with approval, but a ledger shows the pattern: how many requests arrive, how much value is identified, what gets absorbed, which fees are approved, and where margin is leaking. The Scope Ledger System combines the client-ready change notice with that operating record.