Source
Which proposal, contract, message, invoice, or delivery record supports this action?
Template
Change Request Draft
A calm message for turning an extra client request into a clear tradeoff instead of silent unpaid work.
Use it when
Start from a clear structure, then check the facts.
These templates are deliberately plain. The value comes from pairing the message with the source records that support it.
scope creep
Change Request Draft
Subject: Quick confirmation on [new request]
Hi [Client name],
I can help with [new request]. I want to separate it from the original scope so budget and timing stay clear.
Original scope: [scope summary]
New request: [request summary]
Impact: [timeline / budget / deliverable impact]
Options:
1. Add it as a change request for [fee/timeline]
2. Swap it for [existing item]
3. Schedule it for a later phase
Which option would you prefer?Before sending
Review the evidence first.
Status
Is the project confirmed, unclear, overdue, or blocked by a missing record?
Tone
Does the message fit the client relationship and the current state of the work?
Related
Continue with the matching workflow.
FAQ
Who should use Change Request Draft?
Independent professionals and small teams who need a calm, source-aware starting point before sending a client message.
Should I copy it exactly?
Use it as a structure, then adjust the facts, tone, and relationship context before sending.
What should I check first?
Check the relevant approval, scope, delivery, invoice, or payment record before using the template.
Early access
Bring this template into real client work.
Early access helps us test these workflows against actual project records.