Demo conversion asset
Sample Approval Link
This sample shows what a client sees when a freelancer sends a ScopeDue approval link for extra work: the request title, price, timeline impact, payment requirement, and approve/decline/question actions. It turns a vague “can you also add this?” message into a clear record before the work continues.
Client-facing preview
A realistic approval link for one priced change request
This is demo data, not a real client record. The goal is to preview the calm, professional client experience before you send your own approval link.
Change request
Add booking page to website refresh
Hi Morgan, this request adds a new booking page to the approved website refresh. It includes page layout, booking embed setup, responsive styling, and one review pass for this page.
What changed
The original scope included five standard pages. This adds one new booking page with embedded scheduling instructions.
Timeline impact
Estimated launch moves from Friday to the following Wednesday if approved today.
In a real approval link, these actions create approval events in the record. This static page is only a public sample.
Why this exists
Stop turning vague requests into unpaid work
When a client asks for extra work in email, chat, a call, or a casual comment, the freelancer needs a professional way to say yes without making the boundary feel personal. A client approval link keeps the conversation focused on the request, price, timeline, and next step.
- The client sees what is being added before approving.
- The price and timeline impact are visible in one place.
- The payment requirement is clear before work starts.
- The approval event becomes part of the approval trail.
Create a clear record before the work continues.
Use ScopeDue to turn the next extra client request into a priced approval link instead of starting from a scattered chat message.
Pain → workflow → record
The approval link demo workflow
The sample is built around one primary workflow: a freelancer sends a client-friendly approval link for a priced change request.
Pain
A client asks for something outside the original scope, and the freelancer does not want to sound difficult or start unpaid work.
ScopeDue workflow
- Create the change request.
- Add price and timeline impact.
- Send the client approval link.
- Track payment if required.
- Save the proof record.
What gets recorded
Scope, price, timeline impact, client approval, payment status, uploaded payment proof, freelancer confirmation, and the Proof Pack timeline.
Record details
What this sample approval link would save
The useful part is not just the approval button. It is the business record around the decision.
| Record element | Sample value shown | Why it helps |
|---|---|---|
| Change title | Add booking page to website refresh | Gives the approval a clear name instead of relying on a chat thread. |
| Original scope reference | Original scope included five standard pages | Shows why the new request is outside the current agreement. |
| Price | $450 sample fee | Makes the extra work paid and explicit before work starts. |
| Timeline impact | Launch moves to the following Wednesday | Prevents surprise when the added work changes the schedule. |
| Payment requirement | Payment required before work | Keeps the request approved but not ready until payment is confirmed. |
| Client response | Approve, decline, or ask a question | Creates a cleaner approval trail than scattered messages. |
Payment status history
Approval does not automatically mean ready to work
For payment-required changes, ScopeDue separates client approval from freelancer-confirmed payment. That distinction matters when a client says they paid, but the freelancer has not received the money yet.
The freelancer sends the approval link with price, timeline impact, and payment condition.
The change is approved, but the status is still approved but unpaid if payment is required before work.
The client receives payment instructions and can mark payment sent or upload proof.
Only the freelancer confirms final paid status. After confirmation, the work can become ready to start.
Freelancer controls
What you control before sending
- Request title and description.
- Why the work is outside the approved scope.
- Price, currency, and due date.
- Timeline impact.
- Whether payment is required before work starts.
- Whether handoff should stay locked until payment is confirmed.
Client experience
What the client sees
- Clear request details without learning a complex portal.
- Price and timeline impact in plain language.
- Approve, decline, or ask a question actions.
- Payment status steps after approval if payment is required.
- A professional record instead of a messy message thread.
Decision guide
Use an approval link when the request changes scope, payment, or handoff
| Client request | Use an approval link? | Reason |
|---|---|---|
| “Can you add one more page?” | Yes | It changes deliverables, price, and likely timeline. |
| “Can you do a third revision round?” | Yes | It may be an extra revision approval with a separate fee. |
| “Can you send editable source files?” | Yes | It may require a source file release request or payment-before-handoff rule. |
| “Can you fix the typo I just found?” | Maybe | If it is clearly included, a formal approval link may be unnecessary. If it changes scope, document it. |
| “Can we review the payment status?” | Use the payment ledger | The client can mark paid, upload proof, and wait for freelancer confirmation. |
Next steps
Turn this sample into your own client workflow
Start with one client change. Create the request, send the approval link, and keep the payment and proof events attached to the same record.
Generate the request
Use the change request generator to turn extra work into a priced approval record.
Track payment status
Use the payment ledger to separate client marked paid from freelancer confirmed received.
Save the proof trail
Preview how approvals and payment events can become a sample Proof Pack.
Trust and privacy note
This page is a static public sample. Real client approval links, project pages, payment proof, and user-specific Proof Packs should be private or noindex by default. 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.
Read the product disclaimer or review the security approach.
FAQ
Questions about the sample approval link
Is this real client data?
No. The project name, client name, price, and timeline are sample data so you can preview the client experience safely.
Can the client mark the request as paid?
The client can mark payment sent and upload proof. The freelancer must confirm payment received before final paid status is recorded.
Should every small request need a link?
Not always. Use an approval link when the request changes scope, price, timeline, payment requirement, source file release, or final handoff condition.
Can I use this instead of a contract?
No. ScopeDue helps create a clear business record. It does not replace legal, tax, accounting, or contract advice.
Create the record first
The next client change does not have to start from a vague chat message.
Create a priced approval link, show what changed, make the payment condition clear, and save the approval trail before the work continues.