Demo tool · Proof Pack sample

Proof Pack Sample

Updated

A Proof Pack is a clear business record of what changed, who approved it, what payment status events happened, whether the freelancer confirmed receipt, and whether handoff was released. This sample shows how ScopeDue turns a priced change request, payment ledger, handoff status, and export timestamp into one organized record before confusion spreads across email, chat, files, and invoices.

Sample/demo data only · Built for freelancers, solo studios, and small service providers in the United States · Last reviewed: May 26, 2026

Create proof record See the Proof Pack feature
This is sample data. The record below is fictional and is provided only to show the structure of a ScopeDue Proof Pack. It is not a real customer record, not payment confirmation, and not legal, tax, or accounting advice.

What this demo shows

A proof record that is easier to read than scattered messages

Freelancers often have approvals in one place, payment notes in another place, and final handoff details somewhere else. The sample Proof Pack below shows the record as one timeline: original scope, approved change, payment requested, client marked paid, proof uploaded, freelancer confirmed received, and final handoff released.

  • Approval trail: the change was reviewed and approved before extra work continued.
  • Payment status history: client action and freelancer confirmation are separate events.
  • Handoff record: final files were released only after the required payment condition was met.
  • Export-ready summary: the record can be saved as a Proof Pack for business records or project closeout.

Approved change

The client requested an additional booking page outside the original scope. The freelancer created a priced approval link before starting the work.

Payment separated from approval

The client could mark payment sent and upload proof, but only the freelancer could confirm the payment was received.

Handoff status recorded

Final handoff stayed locked until the required payment was confirmed, then the handoff release event was added to the record.

Pain → ScopeDue workflow → What gets recorded

The Proof Pack workflow

Pain

A client approves extra work in chat, later says they thought it was included, and payment proof is mixed across screenshots, emails, and file messages.

ScopeDue workflow

  1. Create the proof record or request.
  2. Send the client approval link or message.
  3. Get approval or a clear response.
  4. Track payment status and handoff conditions.
  5. Save the Proof Pack timeline.

What gets recorded

Scope, price, timeline impact, approval, payment status, payment proof, freelancer confirmation, handoff status, and the Proof Pack export timestamp.

Create proof record View sample Proof Pack

Sample timeline

What the Proof Pack timeline can include

This sample timeline is intentionally plain: it shows the sequence of decisions instead of trying to sound like a legal document. The value is clarity—what happened, when it happened, who acted, and what condition changed.

Original scope saved

Original project scope listed a five-page website, two revision rounds, and final handoff after confirmed final payment.

Change request created

Additional booking page added as a priced change request with a $450 fee and a two-business-day timeline impact.

Client approved

Client approved the change through the approval link. Payment was required before the extra work could be marked ready to start.

Payment requested

Payment item opened in the payment ledger. Status moved from not requested to payment requested.

Client marked paid

Client marked payment sent and uploaded proof. Status became paid pending confirmation, not final paid.

Freelancer confirmed received

Freelancer confirmed the payment was received. Change request became ready to start.

Handoff released

Work was completed and final handoff was released after the required payment condition was already confirmed.

Freelancer controls

What the freelancer controls

  • Original scope summary and included deliverables.
  • Change request title, description, price, and timeline impact.
  • Whether payment is required before work starts.
  • Whether payment is required before final handoff.
  • Payment status confirmation after the client marks payment sent.
  • Which sections appear in the Proof Pack export.

Client view

What the client sees

  • What changed and why it is separate from the current scope.
  • The price, timeline impact, and payment requirement.
  • Approve, decline, or ask a question actions.
  • Payment request details after approval when payment is required.
  • Ability to mark paid and upload proof, without self-confirming final paid status.

Payment status history

Sample payment ledger inside the Proof Pack

The payment ledger is not just a paid/unpaid checkbox. It separates client statements from freelancer confirmation, which helps reduce confusion when a client says payment was sent but the freelancer has not received it yet.

Payment itemAdditional booking page
Amount due$450.00
Payment requirementPayment required before work
Client actionClient marked paid
Proof referenceReceipt image uploaded · Sample only
Freelancer actionConfirmed received
Final payment statusPaid

Handoff condition

Sample handoff rule recorded in the Proof Pack

Rule: final handoff stays locked until the required payment is confirmed by the freelancer. In this sample, the handoff release event appears after the freelancer confirms receipt, not when the client simply marks payment sent.

See handoff lock See payment ledger

Copyable sample output

Proof Pack summary you can model

Use this sample structure to think through your own project record. In ScopeDue, the saved version would be tied to real project events instead of a manual note.

Proof Pack summary — sample/demo only

Project: Website launch update
Original scope: Five-page website, two revision rounds, final handoff after confirmed final payment
Approved change: Add booking page
Price: $450.00
Timeline impact: +2 business days
Approval status: Client approved through approval link
Payment status: Paid — freelancer confirmed received
Client marked paid: Yes
Payment proof: Uploaded by client; sample reference only
Handoff status: Released after payment confirmation
Export timestamp: 2026-05-26 10:15 AM CT

Business record note:
This Proof Pack summarizes approvals, payment events, and handoff status. It does not replace legal, tax, or accounting advice.

Proof Pack sections

What gets saved to the record

Record section What it answers Why it matters for freelancers
Project summary What client/project is this tied to? Keeps the Proof Pack connected to one project instead of scattered messages.
Original scope record What was included before the change? Helps show why a new request was treated as extra work.
Approved change What changed, what did it cost, and who approved it? Turns vague “can you also add this?” work into a clear approval trail.
Payment ledger Was payment requested, marked paid, uploaded as proof, and confirmed received? Separates client marked paid from freelancer confirmed received.
Handoff status Was final handoff locked or released? Shows whether the required payment condition was met before final files were released.
Export timestamp When was this Proof Pack generated? Creates a clean closeout record for business organization.

Good fit

Use this sample when

  • A client asked for extra work and you want one clear record.
  • A change was approved but payment status needs to be tracked separately.
  • Final files, source files, or handoff depend on confirmed payment.
  • You need a project closeout record with approvals, payment events, and handoff status.

Not a fit

Do not use it as

  • A guarantee that a client will pay.
  • A replacement for a contract, lawyer, accountant, or tax advisor.
  • A payment processor or automatic collection system.
  • A place to publish private client records on the public web.

Step-by-step walkthrough

How to create a cleaner proof record before work continues

  1. Start with the approved scope

    Record the original scope, included deliverables, revision limit, payment terms, and handoff rule before the next change gets mixed into chat.

  2. Create the priced change request

    Add the new request, the price, the timeline impact, and whether payment is required before work or before handoff.

  3. Send the client approval link

    The client reviews the request in one place and can approve, decline, or ask a question. For a static preview, see a sample approval link.

  4. Track payment without skipping confirmation

    If payment is required, the client can mark paid and upload proof. The freelancer still confirms receipt before the item becomes paid.

  5. Export the Proof Pack

    When the work or handoff is complete, save the approval trail, payment status history, and handoff event as a Proof Pack.

Client-friendly wording

A short message to pair with a proof record

Hi [Client Name], I created a clear record for this additional request so we both have the details in one place: what changed, the price, the timeline impact, and the payment condition. Please review the approval link before I continue. Once the required payment is confirmed, I can move the work forward and keep the proof record updated.

Related ScopeDue workflows

Proof Pack feature — see how approval and payment events become an exportable record. Change request approval — create a priced approval link before the extra work starts. Payment ledger — track requested, client marked paid, proof uploaded, and freelancer confirmed received. Client approval — document client decisions in a cleaner approval trail. Proof of work — learn how proof records fit into project closeout. Freelance project closeout — close projects with a final checklist and record.

Create the record before confusion starts

Turn the next approved change into a proof record

Use ScopeDue to create a priced change request, send a client approval link, track payment status, confirm receipt, control handoff, and save the Proof Pack timeline.

Create proof record Start with a change request

Related workflow links

Use these supporting pages to move from the current topic into the next approval, payment, proof, or handoff step.