ScopeDue feature
Proof Pack
A Proof Pack turns a messy project history into one clear business record: what changed, who approved it, what payment was requested, what the client marked paid, what the freelancer confirmed received, and whether work or handoff was released. It is built for freelancers who need a calm, professional record before project closeout, not a legal guarantee or a replacement for accounting.
Indexable feature page · Primary workflow: proof export · Built for freelancers, solo studios, and small service providers
What it does
Proof Pack is the record behind the change.
Client changes often start in emails, calls, texts, shared documents, or casual comments. By the time a project ends, the important details are scattered: the original scope, the extra request, the price, the approval, the payment status, and the final handoff decision.
ScopeDue’s Proof Pack feature collects the approval trail, payment status history, uploaded proof, freelancer confirmation, and handoff status into a clean exportable record for your own business files.
Pain → Workflow → Record
A cleaner workflow when a client change needs proof.
Pain
A client asks for extra work, approves it in a thread, says they paid later, and expects final handoff. The freelancer has to reconstruct the story from messages and payment notes.
ScopeDue workflow
- Create the change request.
- Send the client approval link.
- Get the approval or response.
- Track payment status and freelancer confirmation.
- Export the Proof Pack when the work or handoff is complete.
What gets recorded
Scope, price, timeline impact, approval, payment status, payment proof, freelancer confirmation, handoff status, notes, and the Proof Pack timeline.
Record structure
What a Proof Pack can include
| Proof Pack section | What it captures | Why it helps |
|---|---|---|
| Project summary | Client, project name, original scope reference, and export timestamp. | Gives the record context without searching through the full project workspace. |
| Approved changes | Change request title, description, price, timeline impact, approval status, and client response. | Shows what changed and whether the client accepted the added work. |
| Payment timeline | Payment requested, client marked paid, proof uploaded, freelancer confirmed received, partial payment, overdue, waived, refunded, or disputed events when used. | Separates “client says paid” from “freelancer confirmed received.” |
| Handoff record | Whether work, final files, source files, or handoff were locked or released based on the required payment condition. | Clarifies why handoff continued, paused, or released. |
| Notes and proof references | Uploaded proof/receipt references, comments, and record notes tied to the relevant event. | Keeps the business record organized without relying on scattered screenshots. |
Sample timeline
How a Proof Pack tells the story
- Original scope recorded Two web pages, homepage refresh, and one revision round were included in the approved project scope.
- Client requested extra work The client asked for a booking page after the original scope was approved.
- Freelancer sent a priced approval link The change request included the added deliverable, price, timeline impact, and payment required before work.
- Client approved the request The approval event was saved to the approval trail and connected to the payment item.
- Payment moved through the ledger Payment was requested, the client marked paid, proof was uploaded, and the freelancer confirmed received.
- Work and handoff were released Once the required payment was confirmed, the change became ready to start and final handoff could be released when complete.
Best fit
Use Proof Pack when the record matters.
- A client approved extra work after the original scope.
- Payment was required before work or before final handoff.
- The client marked paid, but you still needed to confirm receipt.
- Final files, source files, or handoff were locked until payment was confirmed.
- You want a project closeout record for your own files.
Not for
Do not treat it as a legal shortcut.
- Not a contract replacement.Use proper agreements and professional advice when needed.
- Not automatic payment collection.ScopeDue records payment status; payment processing may happen outside the record.
- Not a dispute guarantee.A clear business record may reduce confusion, but it does not guarantee an outcome.
Product demo
See the proof record before you create your own.
Preview how approval, payment status history, freelancer confirmation, and handoff events can appear in one clear Proof Pack.
Before and after
Why a Proof Pack is cleaner than a screenshot folder
Scattered record
- Scope is in one email.
- Change approval is buried in chat.
- Payment note is separate from the work request.
- Final handoff decision is hard to find later.
- The freelancer has to explain the timeline manually.
Proof Pack record
- Original scope and changes stay tied to the project.
- Client approval link creates a clean approval trail.
- Payment status history shows each event.
- Freelancer confirmation is separate from client marked paid.
- Handoff status is recorded with the payment condition.
Connected workflows
Proof Pack works best when the earlier steps are clear.
Checklist
Before you export a Proof Pack
- Confirm the original scope record is attached to the project.
- Make sure each extra request has a clear description and price.
- Check whether payment was required before work or before handoff.
- Review payment events for client marked paid and freelancer confirmed received.
- Confirm handoff status is correct before project closeout.
Do not wait until a disagreement to organize the record. The best Proof Pack starts when the first change is priced, approved, and connected to payment status.
FAQ
Proof Pack questions
What is a ScopeDue Proof Pack?
A Proof Pack is an exportable business record that can include the original scope, approved changes, approval timestamps, payment status history, proof uploads, freelancer payment confirmation, handoff status, and export timestamp.
Does a Proof Pack guarantee payment or legal protection?
No. ScopeDue helps you create a clear business record of approvals, payments, and handoff events. It is not a substitute for legal, tax, or accounting advice and does not guarantee payment outcomes.
Can a client confirm that something is fully paid?
The client can mark payment as sent and upload proof. The freelancer confirms receipt before ScopeDue treats the item as paid for workflow purposes.
Is a Proof Pack public?
Public SEO pages should link only to static samples. Private client, project, approval, and user-specific Proof Pack pages should not be indexed by default.
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, read the ScopeDue disclaimer. For access and private route handling, see the security approach.
Next step
Create a clear record before the work continues.
Start with a priced approval link, track the payment condition, and export the Proof Pack when the change or handoff is complete.