Demo · Proof Pack export
Sample Proof Pack
This sample shows how ScopeDue turns a priced change request into a clear proof record: what changed, who approved it, the payment status history, the client’s payment proof, the freelancer’s confirmation, and whether handoff was released.
Last reviewed: May 26, 2026 · Sample/demo page · All project details below are demo data.
Sample data only. The proof record below is not a real client file, receipt, customer story, or legal document. It is a visual example of the kind of approval trail, payment ledger, and handoff status a freelancer can keep when client changes are documented before work continues.
What this demo shows
A proof record for an approved, paid, and handed-off change
A Proof Pack is useful when a freelancer wants one clean place to review the business record for a project or change request. Instead of hunting through email, chat, screenshots, invoice notes, and file links, the record shows the sequence of events in one export-ready view.
For this sample, the client asked for an extra landing page after the original scope was approved. The freelancer created a priced change request, sent a client approval link, required payment before work, confirmed the payment after the client marked it paid, then released the final handoff.
- Primary workflow: proof pack export for a paid change request.
- Best for: freelancers, solo studios, web designers, developers, designers, video editors, and service providers who need a clear record of approvals and payment events.
- Not for: replacing legal advice, tax records, bookkeeping software, or a formal contract review.
ScopeDue Proof Pack · Demo
Project proof record
Exported sample · Not real customer data
Export timestamp
May 26, 2026 · 10:40 AM CT
Project summary
| Field | Sample value | Why it matters |
|---|---|---|
| Original scope record | Homepage refresh, services page update, mobile layout QA | Shows what was already included before the extra change was requested. |
| Client request | Add one campaign landing page after the original scope was approved | Separates the new request from the previously approved work. |
| Price and timeline impact | $450 sample amount · adds 2 business days | Gives the client a clear choice before the freelancer starts. |
| Payment condition | Payment required before work starts | Prevents an approved but unpaid change from being treated as ready to work. |
Approval and payment timeline
- Original scope approved Sample client approved the original project scope, deliverables, timeline, and included revisions.
- Change request created Freelancer added the extra landing page request, price, timeline impact, and payment-before-work rule.
- Client approved the change The client reviewed the approval link and approved the additional work.
- Payment requested ScopeDue recorded that payment was required before the approved work could begin.
- Client marked paid and uploaded proof The client indicated payment was sent and attached a sample proof reference.
- Freelancer confirmed received The freelancer confirmed the payment appeared on their side. The change became ready to start.
- Work completed and handoff released The final deliverable was released after the required payment was confirmed.
Payment status history
What gets recorded
The parts of the record a freelancer should not have to reconstruct later
Approval trail
ScopeDue records the original scope, the new change request, the client approval response, and the timeline of important approval events.
Payment status history
The payment ledger can show payment requested, client marked paid, proof uploaded, freelancer confirmed received, partial payment, overdue, or disputed states.
Handoff status
When payment is required before handoff, the record shows whether the final handoff or source file release was locked or released.
Pain → Workflow → Record
A cleaner workflow than scattered screenshots
Pain
A client asks for extra work in a casual message. The freelancer wants to help, but the price, timeline impact, approval, payment, and handoff condition are not written in one place.
ScopeDue workflow
- Create the change record.
- Send the client approval link.
- Get approval or a question.
- Track payment and freelancer confirmation.
- Export the Proof Pack.
What gets recorded
Scope, price, timeline impact, approval, payment status, payment proof, freelancer confirmation, handoff status, and Proof Pack timeline.
What the freelancer controls
Before the client approves
- Describe what changed and why it is outside the current scope.
- Add the price, currency, due date, and timeline impact.
- Choose whether payment is required before work starts.
- Choose whether handoff or source files stay locked until payment is confirmed.
After the client responds
- Review whether the client approved, declined, or asked a question.
- Request payment for the approved change when required.
- Confirm received payment after checking the freelancer’s side.
- Export a Proof Pack after work, payment, and handoff events are complete.
What the client sees before the record is complete
The client experience should be simple. They do not need a complex portal to understand the request. A client approval link can show the change, price, payment requirement, and next step in plain language.
Review the request
The client sees what is being added, how it affects the timeline, and what is required before work starts.
Approve, decline, or ask
The client can approve the request, decline it, or ask a question before the freelancer continues.
Mark payment sent
The client can mark payment as sent and upload proof, but the freelancer still confirms final receipt.
Payment status table shown in a Proof Pack
The key rule is simple: a client can say payment was sent, but the freelancer confirms whether payment was actually received. That distinction keeps the payment status history clearer.
| Status | Who can trigger it | How it appears in the record |
|---|---|---|
| Payment requested | Freelancer | The payment item exists and the client has been asked to pay. |
| Client marked paid | Client | The client says payment was sent; this is not the final paid status. |
| Proof uploaded | Client or freelancer | A receipt, screenshot, or reference can be attached as supporting proof. |
| Freelancer confirmed received | Freelancer | The freelancer confirms the money appeared on their side. |
| Handoff released | Freelancer or system rule | The Proof Pack shows that the required payment condition was met before handoff. |
Use a Proof Pack when the record matters
Use this when
- A client approved extra work after the original scope.
- Payment was required before work or final handoff.
- The client marked paid and the freelancer needs to confirm receipt.
- Source files or final files were released after payment confirmation.
- You want a clean project closeout record for your own files.
Do not use this as
- A guarantee that a client will pay.
- A replacement for legal advice, tax advice, accounting, or contracts.
- A fake receipt or proof of payment that did not happen.
- A public page for private client or project details.
- A way to publish sensitive client information.
How to create a Proof Pack like this
- Create the project record. Add the client, original scope, deliverables, timeline, revision limit, and handoff rules.
- Create a priced change request. Describe the extra work, add the price, show timeline impact, and set the payment requirement.
- Send the client approval link. Let the client approve, decline, or ask a question before the work continues.
- Track the payment event history. Record payment requested, client marked paid, proof uploaded, and freelancer confirmed received.
- Release work or handoff only after the condition is met. When payment is required, avoid treating approved but unpaid work as ready to start.
- Export the Proof Pack. Save the project summary, approval trail, payment ledger, proof references, and handoff status in one record.
Create a clear record before the work continues
When the next client change affects price, timeline, payment, or handoff, do not rely on a vague chat message. Put the change in a record, send a client approval link, track payment status, and export a Proof Pack when the work is complete.
Related ScopeDue resources
FAQ
Is a ScopeDue Proof Pack a legal document?
No. It is a clear business record of approvals, payment events, handoff decisions, and related proof. It is not a substitute for legal, tax, or accounting advice.
Can a client confirm final payment?
No. The client can mark payment as sent and upload proof. The freelancer confirms when payment has been received on the freelancer’s side.
Should private Proof Packs be indexed?
No. User-specific client pages, private project records, and generated one-off Proof Packs should stay private or noindex by default. This sample page is public because it uses demo data.
What does this sample Proof Pack show?
It shows a project summary, approved change, payment timeline, proof reference, freelancer confirmation, handoff status, and export timestamp using sample data.
Editorial note: This page explains a ScopeDue product workflow using sample data. It does not make legal, tax, accounting, payment processor, customer, or competitor claims.