Freelancer approval templates
Templates Directory
Use ScopeDue templates when a client change needs a clear record: what changed, what it costs, who approved it, whether payment is required, whether payment was confirmed, and what proof exists before work or handoff continues.
For freelancers, solo studios, and small service providers in the U.S. · Directory page · Updated for launch
Start here
Choose the template by workflow, not by wording
Most client-change problems start with the same messy moment: a client asks for something extra in email, chat, a call, or a casual comment. The safest next step is not a long argument or a vague “sure.” Pick the template that turns the request into a documented workflow.
Template clusters
Browse templates by client-change situation
Each cluster is built around a practical ScopeDue record: approval, payment status, handoff, or Proof Pack. Use the template text as a client-friendly message, then turn the outcome into a saved approval trail when the work should not continue from chat alone.
Extra work
Change request templates
Use these when the client asks for a new deliverable, feature, page, asset, or task that was not part of the original scope record.
- Freelance change request templateTurn extra work into a priced approval request.
- Change order email templateSend a professional change-order message before starting.
- Client change request form templateCollect the details needed to price and approve a change.
Boundaries
Scope creep templates
Use these when you need to respond calmly without doing unpaid work from a vague chat message.
- Scope creep email templateExplain that the request is outside scope and needs approval.
- Outside scope email templateUse a softer boundary message when the relationship needs care.
Payment status
Payment reminder templates
Use these when approval is not enough: payment needs to be requested, tracked, and confirmed before work or handoff moves forward.
- Payment before work templateExplain that the approved change starts after payment is confirmed.
- Payment before work starts templateUse when extra work is approved but unpaid.
- Overdue invoice email templateFollow up without sounding accusatory.
- Final payment reminder templateAsk for final payment before final handoff.
Revision limits
Revision templates
Use these when the client asks for one more round after the included revision limit, or when you need to make revision boundaries clear up front.
- Extra revision fee templateState the cost and turnaround for additional revision work.
- Revision limit clauseClarify included revision rounds before scope confusion starts.
- Extra revision email templateSend a friendly approval message for an added revision round.
Handoff
Source file and handoff templates
Use these when a client requests editable files, final files, or source assets before payment, approval, or release terms are clear.
- Source file release templateExplain what is being released, the fee, and the payment condition.
- Source file fee clauseClarify whether editable files are included or priced separately.
- Final file handoff checklistConfirm what is ready, what is paid, and what can be released.
Proof record
Client approval and proof templates
Use these when the important part is not just the message, but the record of who approved what and how the project closed out.
- Client approval email templateAsk the client to approve a clear request instead of replying vaguely.
- Approval record templateCapture what changed, who approved it, and when.
- Project closeout proof templateSummarize approvals, payment events, and handoff at the end.
Decision guide
Which template should you use first?
Use this table when you are not sure whether the situation is a scope issue, payment issue, revision issue, or handoff issue. The goal is to choose the template that creates the cleanest business record before the next action happens.
| Client situation | Use this template | Best ScopeDue record | Do not skip |
|---|---|---|---|
| “Can you also add this?” | Freelance change request template | Priced change request with approval status | Price, timeline impact, payment requirement |
| “This should be included, right?” | Outside scope email template | Scope boundary note and approval trail | Reference to original scope record |
| “Can we do one more revision?” | Extra revision email template | Extra revision approval | Revision round number and fee |
| Client approved but has not paid | Payment before work starts template | Approved but unpaid payment item | Freelancer confirmation before work starts |
| Client says they paid | Payment status tracker template | Payment ledger status history | Client marked paid is not the same as freelancer confirmed received |
| Client wants source files | Source file release template | Source file release request | Release terms and payment confirmation |
| Project is ready to close out | Project closeout proof template | Proof Pack timeline | Approvals, payment events, and handoff status |
Directory workflow
Use a template, then turn it into a clear record
Pain: A client message can feel harmless at first, but “one quick change” often turns into extra unpaid work, late payment confusion, or a handoff disagreement.
ScopeDue workflow: Use the right template to write the message, then create a priced approval link or payment-tracked record when the work needs approval, payment, or handoff rules.
- Create the request, payment reminder, revision note, or handoff message.
- Send the client a link or message that explains the price, timeline impact, and next step.
- Get approval, decline, or a question before work continues.
- Track payment status when payment is required before work or final handoff.
- Save the approval trail, payment status history, handoff status, and Proof Pack timeline.
Information gain
A copy-ready starter message for most templates
Use this short message when you need to move from casual conversation into a clear approval record. Replace the bracketed details, then use the matching template cluster above for a more specific version.
Hi [Client Name], I can help with [requested change]. Since this is outside the currently approved scope, I created a clear request with the details, price, timeline impact, and payment requirement. Please review it here: [Approval Link] Once it is approved and any required payment is confirmed, I’ll know we are aligned before I continue.
Professional boundary: The template should not accuse the client or turn the conversation into a dispute. It should make the next step clear: approve, decline, ask a question, or complete the required payment step.
What gets recorded
What a template should become inside ScopeDue
A template is useful because it helps you communicate. A ScopeDue record is useful because it keeps the approval, payment, and handoff trail organized after the message is sent.
Approval trail
- What changed from the original scope
- Who approved or declined
- When the client responded
- Questions or requested changes
Payment status history
- Payment requested
- Client marked paid
- Payment proof uploaded
- Freelancer confirmed received
Handoff and Proof Pack
- Work-ready or handoff-locked status
- Source file release decision
- Final handoff status
- Exportable Proof Pack timeline
Use templates to reduce confusion, not to overpromise
ScopeDue helps freelancers create a clear business record of approvals, payment events, and handoff decisions. It is not a substitute for legal, tax, or accounting advice.
For product boundaries and safe use, read the ScopeDue legal disclaimer.
Related tools
When a template should become a workflow
Use a template when you need words. Use a tool when you need output that can turn into an approval link, payment status item, checklist, or proof record.
Next step
Use a template before the work continues
The next time a client asks for extra work, an extra revision, early source files, or final handoff before payment is confirmed, start with the matching template and turn the result into a clear ScopeDue record.
Questions
Template directory FAQ
What ScopeDue template should I use when a client asks for extra work?
Start with the freelance change request template when the work is outside the original scope and needs a price, timeline impact, approval, and payment condition before work continues.
Are ScopeDue templates legal contracts?
No. They are practical business-record templates for approvals, payment events, and handoff decisions. They do not replace legal, tax, or accounting advice.
Can a client confirm final payment status?
Clients can mark payment as sent and upload proof. The freelancer confirms whether payment was actually received before work starts or handoff unlocks.
Should template pages link to private client records?
No. Public templates can link to static samples like the sample approval link and sample Proof Pack. Private client, project, and proof pages should not be publicly indexable by default.
This directory is based on ScopeDue’s product workflow: priced change requests, client approval links, payment status history, freelancer-confirmed receipt, handoff control, and Proof Pack records.
New templates
Scope, revision, closeout, and persona templates
Scope of work change clause template
Add a clear change clause for out-of-scope work, pricing, payment, and approval.
Revision and scope boundary clause
Set revision boundaries and explain when extra revision approval is needed.
Project completion approval template
Confirm final approval, payment status, handoff conditions, and proof before project closeout.
Copywriter extra revision request template
Use a copywriter-specific message when extra rewrite rounds are outside the included scope.
Social media manager extra post request template
Use a social-media-specific message when extra posts, captions, or platform versions are outside the approved calendar.