ScopeDue Support
Help Center
Search ScopeDue help for approval links, payment statuses, Proof Packs, handoff locks, source file release requests, templates, privacy, and support. Start with the situation you are trying to fix, then move to the workflow page that explains what the freelancer records, what the client sees, and what happens before work or handoff continues.
Start here
Choose the support path that matches the record you are trying to create
ScopeDue support is organized around the product workflow: create a clear record, send a client approval link, track the payment status, confirm receipt as the freelancer, and save proof for the project. Use the paths below when a client change, payment, revision, source file request, or final handoff feels unclear.
Support paths
Getting started
Create your first client change record, understand the basic workflow, and learn what should be included before you send a link.
Approval links
Learn what the client sees, how approve, decline, and question responses work, and how an approval trail is saved.
Read approval link help
Payment statuses
Understand payment requested, client marked paid, proof uploaded, paid pending confirmation, freelancer confirmed received, overdue, and disputed.
Review payment status help
Proof Packs
See what can be included in a project proof record: original scope, approved changes, payment events, uploaded proof, and handoff history.
Learn about Proof Packs
Handoff locks
Use handoff guidance when final files, source files, high-resolution exports, or deliverables should wait until required payment is confirmed.
Security and privacy
Review how ScopeDue thinks about approval links, private project records, uploads, proof records, and safe product limitations.
Core workflow
From client change to clear record
Create the request or record
Describe what changed, what it costs, whether the timeline changes, and whether payment is required before work or handoff.
Send the client link
The client reviews the approval link and can approve, decline, or ask a question without learning a large client portal.
Track payment status
The client can mark paid or upload proof, but only the freelancer confirms payment received. Approved but unpaid does not mean ready to work.
Continue work or release handoff only when ready
If payment is required before work or final handoff, keep the status clear until the freelancer confirms receipt.
Save the proof record
Approval, payment, proof upload, freelancer confirmation, and handoff events can be organized into a Proof Pack for business records.
Help by situation
| Situation | Use this path | What ScopeDue records |
|---|---|---|
| A client asks for extra work outside the original scope. | Generate a change request or read the freelance change request workflow. | Change description, price, timeline impact, approval response, payment condition, and status history. |
| The client approved the change, but payment is still required. | Track payment status and use payment status help. | Payment requested, client marked paid, proof uploaded, freelancer confirmed received, overdue, or disputed events. |
| You need to respond professionally to scope creep. | Generate a scope creep response or use the scope creep email template. | The message can become a clear approval request instead of a loose chat promise. |
| Extra revisions go beyond the included revision limit. | Create an extra revision approval or use the extra revision fee calculator. | Revision round, price, turnaround, client approval, and payment requirement. |
| The client wants source files, editable files, or final files. | Review source file handoff guidance or use the source file release template. | Source file request, approval, fee, payment status, and release event. |
| You need a clean project record after completion. | Learn about Proof Packs or view a sample Proof Pack. | Original scope, approved changes, payment events, uploaded proof, handoff history, and export timestamp. |
Popular help topics
Approvals
Client approval links
Use approval links when the client needs to review a priced change request, understand the timeline impact, and choose approve, decline, or ask a question.
Payments
Payment ledger statuses
Use the payment ledger when the difference between “client says they paid” and “freelancer confirmed received” matters for whether work or handoff should continue.
- Read about the payment ledger
- Start a payment status tracker
- Generate a late payment reminder
Handoff
Final files and source file release
Use handoff support when the client asks for final files, editable files, source files, exports, or site transfer before required payment is confirmed.
- Understand handoff lock
- Build a final handoff checklist
- Create a source file release request
Proof
Proof Packs and project records
Use Proof Pack help when you need a business record showing what was approved, what was paid, what proof was uploaded, and when handoff was released.
- See what a Proof Pack contains
- View a sample Proof Pack
- Document client approval
Common terms you may see in ScopeDue
- Approved but unpaid
- The client approved the change, but a required payment has not been confirmed by the freelancer. This should not be treated as ready to work when payment is required before work starts.
- Client marked paid
- The client says payment was sent. This is useful information, but it is not the final paid status.
- Freelancer confirmed received
- The freelancer checked their side and confirmed the payment was received. Required work or handoff conditions can use this status.
- Handoff locked
- Final files, source files, or other deliverables are ready but should not be released until the required payment condition is met.
- Proof Pack
- A clean business record of scope, approvals, change requests, payment events, uploaded proof, handoff actions, and export timing.
Use ScopeDue as a business record, not a legal guarantee
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, and it does not guarantee payment or replace a contract.
Read the product disclaimer if you need the full boundary before using approval, payment, proof, or handoff workflows.
Contact support
Before you contact support
Include the product area, the record type, and what you expected to happen. Do not send private client payment details in a public message.
- Project or change request context
- Whether the issue involves approval, payment, proof, handoff, source files, or templates
- Current status shown in ScopeDue
- What the client already approved or marked
- Whether you are trying to continue work, confirm payment, or release handoff
Choose the right support route
Next step
Create a clear record before the work continues
The most useful ScopeDue help path is the one that turns a vague client request into a clear record: what changed, what it costs, who approved it, whether payment is required, whether payment was confirmed, and what proof exists.