Client change approval & payment proof workspace

Stop unpaid
scope creep.

Turn every client change into a priced, approved, payment-tracked record — before the work continues.

No payment processing Free tools included For U.S. freelancers
scopedue.com/approve/k9x2m
Change Request · Pending Approval
Additional booking page for website
Price $350.00
Timeline impact +2 business days
Payment condition 🔒 Required before work starts
Add one booking/scheduling page not in the original scope. Custom form, calendar integration, and confirmation email.
Payment confirmed · $350
🔓 Handoff unlocked
📄 Proof Pack saved
1
Create change recordPrice it, set the condition
2
Send approval linkClient reviews & decides
3
Track payment statusClient marks paid, you confirm
4
Export Proof PackFull record, one export
The problem

Client changes are easy to lose
when they happen in messy places.

Extra work starts in email, Slack, texts, calls, comments. The client thinks it's included. You keep working to be helpful. Later, the price, approval, and payment status are scattered — and impossible to prove.

💬

"Can you also add this?"

A casual chat message becomes out-of-scope work with no price, no approval, and no record anywhere.

💸

"I already paid."

The client says payment was sent, but there's no clear record of when you actually confirmed it received.

📁

"Send the files first."

Final deliverables leave your hands before payment is confirmed — with nothing documented either way.

Core workflow

One clear path from request to proof.

Built around the exact moment a client asks for extra work — and you need a professional way to define it before continuing.

1

Create the change record

Describe the extra work, price it, set the timeline impact, and choose whether payment is required before work starts.

2

Send the approval link

The client gets one clean page to approve, decline, or ask a question — timestamped and automatically saved.

3

Track payment status

Client marks paid and uploads proof. You confirm payment received separately — keeping both events distinct.

4

Save the Proof Pack

Approval trail, payment events, freelancer confirmation, and handoff status — one exportable record.

Features

A lightweight workflow for paid client changes.

Not a CRM, not an accounting tool. Just the exact workflow you need when a client asks for extra work.

📋

Priced Change Requests

Turn "can you also add this?" into a clear record with price, timeline impact, and payment requirement — before you start.

Explore change requests
🔗

Client Approval Links

Give clients a simple page to approve, decline, or ask a question — no heavy portal, no confusion.

Preview a sample link
💳

Payment Ledger

Separate "client says paid" from "payment received." Track every status from requested through confirmed.

Track payment status
🔒

Handoff Lock

Keep final files locked until payment is confirmed. Nothing leaves until the condition is actually met.

Lock final handoff
📄

Proof Pack

Export every approval, payment event, confirmation, and handoff decision as one clean business record.

View Proof Pack
🔁

Extra Revision Approval

Make revision limits clear without awkwardness. Turn extra rounds into priced, approved requests.

Create a revision approval
Live samples

What the approval link and Proof Pack look like.

Both are client-readable records that keep your approval trail and payment history in one place.

Sample Approval Link

Sample data
Change
Add one booking page not included in the original website scope.
Price
$350 — manual payment item for the approved change.
Timeline
Adds 2 business days after payment is confirmed.
Client actions
Approve, decline, ask a question, mark paid, or upload proof.
View sample approval link

Sample Proof Pack

Export preview

Original project scope recorded with deliverables, revision limit, and handoff rule.

Client approved the priced change request through the approval link.

Client marked paid and uploaded proof; freelancer confirmed payment received.

Final handoff available after required condition was met.

View sample Proof Pack
Who it's for

Built for freelancers who sell custom work.

Intentionally narrow — for service providers who need cleaner boundaries around extra requests, approvals, and payment.

Design

Web & Graphic Designers

Extra pages, revision rounds, source files, alternate formats — price and document every added request.

Designer workflow →
Video

Video Editors

Extra cuts, vertical versions, captions, exports — turn each new deliverable into an approved, tracked record.

Video editor workflow →
Development

Freelance Developers

Extra features, integrations, deployment changes — make out-of-scope work clear before you build.

Developer workflow →
Writing

Copywriters

Extra pages, rewrites, rush edits — send a calm approval link instead of renegotiating over email.

Copywriter workflow →
Marketing

SEO & Social Media

Extra posts, reports, campaign assets — keep every add-on tied to price, approval, payment, proof.

SEO freelancer workflow →
All types

Solo Studios

Any service-based work where client changes, payment status, and handoff decisions need a clear record.

Browse all use cases →
Fit matrix

When to use ScopeDue.

When a client says…Use ScopeDue forBest next step
"Can you add one more page?"A priced change request with timeline impact.Generate a change request
"Can we do one more revision?"An extra revision approval with a fee and turnaround.Calculate revision fee
"I already paid."A payment status history where client marks paid and freelancer confirms received.Use the payment ledger
"Send the final files first."A final handoff lock until required payment is confirmed.Create a handoff lock
"Can I get the source files?"A source file release request tied to approval and payment.Source file release template
"I thought that was included."An original scope record, change approval trail, and Proof Pack.View Proof Pack workflow
🔐

Client can't self-confirm payment

Client marks paid and uploads proof. Only the freelancer confirms payment was actually received.

🔒

Private records stay private

Approval pages, project records, and Proof Packs are not public search pages by default.

📑

Designed as a business record

Documents approvals, payment events, and handoff decisions together in one place.

⚖️

Not legal or accounting advice

Use alongside your own contracts, payment tools, and professional advisors when needed.

Free tools

Start with a tool, template, or sample.

Free tool

Change Request Generator

Turn extra client work into a client-ready request with price, timeline impact, and payment condition.

Use the generator →
Template

Scope Creep Email Template

Write a firm but friendly response when a request is outside the current project scope.

Use the template →
Sample

Proof Pack Sample

See how approvals, payment events, and handoff decisions appear in one exportable record.

View the sample →
A clear record before the work continues

The next client change doesn't have to start from a vague message.

Create your first approval link, show the client what changed, track payment status, confirm receipt, and save the proof record — before the work or handoff moves forward.

No payment processing · For U.S. freelancers and solo studios · Last reviewed May 2026

FAQ

Frequently asked questions

Quick answers about what ScopeDue is, what it isn't, and how it fits into your workflow.

What is ScopeDue?
+
ScopeDue is a lightweight client change approval and payment proof workspace for freelancers, solo studios, and small service providers. It helps turn extra client requests into approved, priced, payment-tracked records — before the work continues.
Is ScopeDue a CRM or project management tool?
+
No. ScopeDue is intentionally narrow. It focuses on approval links, payment status history, handoff rules, and Proof Pack records for client changes — not full project or client relationship management.
Can the client mark something fully paid?
+
The client can mark that payment was sent and upload proof, but the freelancer confirms when payment was actually received. That keeps "client marked paid" separate from "freelancer confirmed received" — an important distinction for your records.
Does ScopeDue process payments?
+
No. The core workflow is a payment status ledger and proof record, not a payment processor. ScopeDue does not replace an accounting system or act as a tax tool.
Does this replace legal advice or contracts?
+
No. ScopeDue helps create a clear business record of approvals, payment events, and handoff decisions. It is not a substitute for legal, tax, or accounting advice. Use it alongside your own contracts and professional advisors.
Should private client approval pages be indexed by search engines?
+
No. Public SEO pages can show static samples, but private app dashboards, client-specific approval links, and user-specific Proof Packs should not be indexable by default.