Product features
Features directory
Explore the ScopeDue features that help freelancers turn client changes into clear records: what changed, what it costs, who approved it, whether payment is required, whether payment was confirmed, and what proof exists before work or handoff continues.
Last reviewed: May 26, 2026 · Built for freelancers, solo studios, and small service providers in the United States.
Use this directory by workflow, not by software category. ScopeDue is not a marketplace, CRM, accounting app, or contract platform. It is a focused approval, payment-status, handoff, and proof workspace for the client-change moments that often happen inside email, chat, calls, or casual comments.
Core ScopeDue features
These four pages explain the foundation of the product: a client asks for extra work, you send a priced approval link, payment status is tracked, and the final record is saved for your business files.
Change Request Approval
Turn “can you also add this?” into a client approval link with the change, price, timeline impact, and payment condition in one place.
View change request approval- Best for extra pages, extra deliverables, rush changes, out-of-scope requests, and client-requested additions.
- Shows the client what they are approving before the freelancer starts the extra work.
- Connects naturally to the change request generator and the sample approval link.
Payment Ledger
Track payment requested, client marked paid, proof uploaded, freelancer confirmed received, overdue, partial, waived, refunded, or disputed payment events.
View payment ledger- Best for approved but unpaid changes, payment before work, and final payment confusion.
- The client can mark payment sent or upload proof, but the freelancer confirms final receipt.
- Pairs well with the payment before work template and future payment follow-up workflows.
Proof Pack
Export a clean business record of scope, approved changes, payment events, uploaded proof, handoff status, notes, and timeline history.
View Proof Pack- Best for project closeout, approval history, payment history, and keeping a professional record after delivery.
- Helps reduce confusion without claiming to replace legal, tax, or accounting advice.
- Preview the concept with a static sample Proof Pack.
Handoff Lock
Keep final handoff, source files, or final deliverables locked until the required payment condition is confirmed by the freelancer.
View handoff lock- Best for final files, high-resolution exports, editable files, source files, or project handoff after final payment.
- Uses payment status history instead of a vague paid/unpaid note.
- Pairs with the final handoff checklist builder when that workflow is live.
Choose the feature by the client-change problem
The fastest way to pick the right ScopeDue feature is to start with what is blocking the work: approval, payment, handoff, source files, revisions, or proof.
| Client situation | Use this feature | What the client sees | What gets recorded |
|---|---|---|---|
| A client asks for additional work outside the original scope. | Change Request Approval | Change, price, timeline impact, approve, decline, or ask a question. | Approval status, approval event, price, timeline impact, and request history. |
| A change is approved, but payment is required before work starts. | Payment Ledger | Payment request, due date, mark paid, upload proof, ask a question. | Payment requested, client marked paid, proof uploaded, freelancer confirmed received. |
| Final files are ready, but final payment has not been confirmed. | Handoff Lock | Handoff status and the payment condition required before release. | Handoff locked, payment status, freelancer confirmation, handoff released. |
| The project needs a clear closeout record. | Proof Pack | A readable proof timeline or exported record when shared by the freelancer. | Scope, approved changes, payment status history, proof files, handoff timeline. |
| The client asks for editable source files or final project assets. | Handoff Lock | A source file or final handoff request with the required condition. | Source file release request, approval, payment condition, release event. |
| The client asks for another revision after the included rounds. | Change Request Approval | Extra revision scope, fee, timeline, and approval options. | Revision request, price, approval, payment status, completion note. |
Pain → ScopeDue workflow → What gets recorded
Pain
A client makes a casual extra request in chat, email, a call, or a quick comment. The freelancer wants to help, but the change has a price, timeline impact, or payment condition that is not clearly documented.
ScopeDue workflow
- Create the request or record.
- Send the client approval link or message.
- Get approval, decline, or question response.
- Track payment or handoff condition if needed.
- Save the proof record.
Pick the shortest path to a clear record
I need the client to approve extra work
Start with the feature that turns out-of-scope work into a priced approval link before the work begins.
Explore change request approvalThe change is approved but unpaid
Use payment statuses that distinguish client marked paid from freelancer confirmed received.
Track payment statusFinal files should not go out yet
Use a handoff condition so final files or source files are released only after the required payment is confirmed.
Lock final handoff until payment is confirmedI need a clean record later
Use Proof Pack to keep the approval, payment, and handoff timeline together for your business records.
See the Proof Pack featureI want to see the client experience
Preview a static approval page before sending a real client a link.
Try a sample approval linkI want a practical first action
Generate a simple client-ready request and turn the situation into a clear approval workflow.
Use the change request generatorBrowse by workflow category
Approval
Document what changed and get a clear response before the work continues.
- Change request approval — priced requests, approve/decline/question response, and approval history.
- Sample approval link — see what a client-facing request can look like.
Payment
Track payment status without letting a client self-confirm the final paid state.
- Payment ledger — requested, marked paid, proof uploaded, freelancer confirmed received.
- Payment before work template — a client-friendly message for payment-required changes.
Handoff and source files
Keep final deliverables, editable files, and source files tied to the right payment or approval condition.
- Handoff lock — final handoff released after required payment is confirmed.
- Source file release template — a structured way to explain editable file release.
Proof and closeout
Keep the story of the project readable after the work is complete.
- Proof Pack — a project or change request record with approval, payment, and handoff history.
- Sample Proof Pack — preview the timeline-style record.
Create a clear record before the work continues.
The next time a client asks for an extra page, another revision, a source file, or final handoff before payment is confirmed, start with a ScopeDue approval workflow instead of a scattered chat thread.
Use ScopeDue when the issue needs a record
Use this when
- A client asks for extra work that changes price, timeline, or scope.
- Payment is required before work starts or before handoff.
- The client says they paid and you need to confirm receipt on your side.
- Final files, source files, or editable assets should wait for confirmed payment.
- You want a Proof Pack-style record for project closeout.
Do not use this as
- A replacement for a contract, attorney, tax advisor, accountant, or payment processor.
- A promise that every client will pay or that every dispute will be resolved.
- A full CRM, project management suite, marketplace, or accounting system.
- A place to publish private client approval links or user-specific project pages.
Clear records without overclaiming
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.
Clients review the request without learning a complex portal.
The freelancer confirms when payment is actually received.
Client-specific project pages and generated proof records should not be public index pages.
Approval, payment, and handoff events stay together for business records.
Security approach · Privacy Policy · Terms of Service · Product disclaimer