Template · Change request approval
Freelance Change Request Template
Use this freelance change request template when a client asks for extra work that was not part of the approved scope. It helps you describe the change, show the price, explain any timeline impact, state whether payment is required before work starts, and ask the client to approve before you continue.
For US freelancers, solo studios, and small service providers · Primary workflow: paid change request
Use this when the client’s request changes the scope, price, or timeline.
A strong change request should answer five questions: what changed, why it is outside the current scope, what it costs, how the timeline changes, and what approval or payment is needed before work continues. If you want a structured record instead of a loose email, turn the message into a priced approval link.
Use case
Who this template is for
Freelancers handling extra client work
Use it when a client says “can you also add this?” and the request needs a price, timeline impact, or approval before you continue.
Solo studios that need a clear record
Use it when you want the approval trail to show what was requested, what was approved, and whether payment was required.
Creative and service providers
It works well for web design changes, extra pages, revisions, copy updates, source file requests, video edits, and small rush changes.
This page is a template and workflow resource, not legal advice. ScopeDue helps freelancers create a clear business record of approvals, payments, and handoff events. It is not a substitute for legal, tax, or accounting advice.
When to send it
When a change request is better than a casual yes
| Client request | Why it needs a change request | What to record |
|---|---|---|
| “Can you add one more page?” | New deliverable, added time, possible extra fee. | Page scope, price, timeline impact, payment condition. |
| “Can we do another revision round?” | May exceed the included revision limit. | Revision round, fee, turnaround, approval status. |
| “Can you send the source files too?” | Source files may not be included in the original scope. | Release terms, source file fee, payment status, handoff event. |
| “Can you make this rush update today?” | Timeline changes may affect other work. | Rush scope, price, revised deadline, client approval. |
If the request is mainly about unpaid extra work, the scope creep guide and scope creep email template can help you soften the wording before you send the formal request.
Copy-ready version
Freelance change request template
Copy the version below and replace the bracketed details. Keep the message short enough for the client to understand quickly, but specific enough to create a clear record.
Subject: Approval needed: additional work for [Project Name] Hi [Client Name], I can help with this additional request. Since it is outside the currently approved scope, I created a change request so we can confirm the details before I begin. Requested change: [Briefly describe the extra work] Reason it is outside scope: [Explain what was originally included and what is new] Price: [$ Amount] Timeline impact: [No change / adds X business days / changes delivery date to X] Payment requirement: [Payment required before work starts / payment due before final handoff / no upfront payment required] Please review and approve the change here: [Approval Link] Once it is approved and any required payment is confirmed, I’ll add it to the work queue. Thanks, [Your Name]
Tone options
Choose the version that fits the client relationship
Hi [Client Name], Yes, I can help with [requested change]. Because this is outside the approved scope for [Project Name], I’ve separated it into a change request with the price and timeline impact. You can review and approve it here: [Approval Link] Once approved and payment is confirmed if required, I’ll move it into the work queue.
Hi [Client Name], I can help with that. Since it is outside the approved scope, I created a short change request with the price, timeline impact, and approval step: [Approval Link] Once approved, I’ll know we’re aligned before I begin.
Hi [Client Name], To keep the project record clear, I’ve documented this additional request as a change request. The request includes the added work, price, timeline impact, and payment condition. Please review the details and approve or ask a question here: [Approval Link] I will wait for approval before beginning this additional work.
Hi [Client Name], Thanks for confirming that you want to move forward with [requested change]. This item requires payment before work begins, so I created a request that includes both the approval and payment status. Please review it here: [Approval Link] Once payment is received and confirmed on my side, I’ll start the approved change.
Product workflow
Pain → ScopeDue workflow → what gets recorded
Pain
A client asks for extra work in a chat, call, or email. If you say yes immediately, the price, payment condition, and timeline impact can stay vague. That is how a small request becomes unpaid scope creep.
- Create a change request with the requested work, price, and timeline impact.
- Send the client a clear approval link instead of relying on a scattered message thread.
- Let the client approve, decline, or ask a question before work continues.
- If payment is required before work, track the payment request and confirmation.
- Save the approval and payment history as part of the project’s Proof Pack.
Sample client page
What the approval link should make clear
A good approval link should not feel like a legal document or a complex client portal. It should show the practical decision the client is being asked to make.
Add booking page to website project
What changed: Add one new booking page, connect the scheduling link, and update the main navigation.
Why it is outside scope: The approved scope included five site pages. This adds a sixth page and an additional integration check.
- Price: $350
- Timeline impact: Adds 2 business days
- Payment condition: Payment required before work starts
- Next step: Approve, decline, or ask a question
Customize before sending
What to change in the template
Be specific about the original scope
Replace vague phrases like “not included” with a clear reference to the approved scope: deliverables, revision limits, pages, files, rounds, dates, or milestones.
State the payment rule plainly
Use language such as “payment required before work starts” or “payment required before handoff.” Avoid sounding punitive; keep it procedural.
Add timeline impact
Even a small change can affect delivery. Add “no timeline change,” “adds two business days,” or “moves final delivery to [date].”
Give the client a clean response path
Ask them to approve, decline, or ask a question. A sample approval link shows the decision more clearly than a long email thread.
Payment status
Do not treat “approved” as “ready to work” when payment is required
If the change requires payment before work, approval is only one step. The payment status should show what happened after the approval.
ScopeDue’s product rule is simple: approved but unpaid does not mean ready to work when payment is required.
Common mistakes
Mistakes to avoid when asking for change approval
| Mistake | Why it creates confusion | Better wording |
|---|---|---|
| “Sure, I can do that.” | The client may assume the work is included. | “I can help with that. Since it is outside the approved scope, I created a change request.” |
| Only mentioning the price | The timeline and payment condition are still unclear. | “The added work is $350, adds two business days, and requires payment before work starts.” |
| Starting before approval | You lose the chance to confirm the scope and payment rule first. | “I’ll begin once the change request is approved and payment is confirmed if required.” |
| Letting the client self-confirm final paid status | A client saying they paid is not the same as the freelancer confirming receipt. | “Thanks for marking payment sent. I’ll confirm once it appears on my side.” |
HowTo
How to use this template with a client
- Paste the template into your message. Replace the project name, client name, requested change, price, timeline impact, and payment rule.
- Attach or link the approval record. For a cleaner workflow, use the change request generator to create a client-ready approval link.
- Wait for approval before doing the extra work. The client should approve, decline, or ask a question before you continue.
- Track payment separately from approval. If payment is required before work, use the payment ledger to record payment requested, client marked paid, proof uploaded, and freelancer confirmed received.
- Save the record. Keep the approval, payment status history, and work/handoff status so they can appear in a Proof Pack.
Related resources
Useful next steps
Generate the request
Turn the template into a structured request with price, timeline impact, payment rule, and client approval status.
Use the change request generatorUnderstand the workflow
Learn how ScopeDue handles client approval links for extra work, revisions, source files, and paid changes.
Explore change request approvalFormalize extra work
Use the topic hub when you need a broader process for client changes, payment status, and proof records.
Read the freelance change request guideCreate a clear record before the work continues.
Use the template when you need a message. Use ScopeDue when you want the request, approval, payment status, freelancer confirmation, and proof timeline saved in one place.
FAQ
Freelance change request template FAQs
Is this the same as a contract?
No. This template helps you create a clear business record for an extra client request. It is not a substitute for a contract or legal advice. For legal questions, review the ScopeDue product disclaimer and contact a professional.
Should I send a change request for small changes?
Use judgment. If the request changes scope, price, timeline, payment timing, final handoff, or source file release, it is usually worth documenting before work continues.
What if the client approves but does not pay?
If payment is required before work, keep the status as approved but unpaid until payment is confirmed on your side. The payment ledger keeps approval separate from payment confirmation.
Can I use this for extra revisions?
Yes. Replace the change description with the extra revision round, price, turnaround time, and payment rule. For revision-specific pricing, use the extra revision workflow when it is available.