Help · First approval link
Getting started with ScopeDue
Create your first ScopeDue request by turning one client change into a priced approval link. Add what changed, the cost, timeline impact, and payment condition before work continues. The client can approve, decline, ask a question, or mark payment sent; you confirm receipt before the request becomes ready to start.
Last reviewed: May 26, 2026 · Support guide for U.S. freelancers, solo studios, and small service providers
Use ScopeDue when a client asks for extra work
The fastest way to understand ScopeDue is to use it for one real client change. Instead of replying from a scattered email, call, text, or chat thread, create a short approval record that says what the client asked for, what it costs, how it affects timing, and whether payment is required before work or handoff.
That record becomes the start of your approval trail, payment status history, and future Proof Pack.
Before you start
What you need for your first request
Client and project
Choose the client and project where the request belongs. A short original scope record is enough to explain what was already included.
The change
Write the added work in plain language. For example: “Add a booking page,” “Create one extra revision round,” or “Release editable source files.”
Price and condition
Add the fee, timeline impact, and whether payment is required before work starts or before final handoff is released.
Step-by-step
How to create your first approval link
-
Create or choose the project
Open the client project, or create a new project if this is your first ScopeDue record. Add a brief original scope summary so the new request has context: what was included, what was excluded, any revision limit, and the current handoff rule.
-
Add the client’s request
Create a new change request. Use the same language the client used, then clarify it into a clean deliverable. This helps reduce confusion later because the request is no longer only a casual message.
-
Set price, timing, and payment rule
Add the price, currency, and timeline impact. Then choose the condition that fits the work: payment required before work, payment required before handoff, or no payment required for this specific request.
-
Preview the client approval link
Check the client-facing page before you send it. The client should see the request title, description, price, timeline impact, payment requirement, and actions to approve, decline, or ask a question.
-
Send the link and wait for a response
Send the client approval link by email or message. You can also use the change request generator first if you want help turning the request into a clearer client-ready message.
-
Track payment and confirm receipt
If payment is required, the client can mark payment sent and upload proof. The payment remains pending until you confirm receipt. This protects the difference between “client says paid” and “freelancer confirmed received.”
-
Save the approval and payment history
Once the request is approved and any required payment is confirmed, ScopeDue keeps the approval trail, payment status history, freelancer confirmation, and handoff status ready for your project record or Proof Pack.
Example
What your first request might look like
Demo data only · Not a real customer record
- Project
- Small business website refresh
- Client request
- Add one new booking page and connect it to the existing navigation.
- Price
- $180
- Timeline impact
- Adds 2 business days after approval and payment confirmation.
- Payment rule
- Payment required before work starts.
- Client actions
- Approve · Decline · Ask a question · Mark payment sent after approval
Product workflow
Pain → ScopeDue workflow → what gets recorded
Pain
A client asks for “one quick change” in a message thread. The freelancer wants to help, but the change has a cost, timing impact, or payment condition that needs to be clear before the work continues.
ScopeDue workflow
- Create the request.
- Send the client approval link.
- Get approval or a question.
- Track payment if required.
- Confirm receipt and save the record.
What gets recorded
- Scope and change description
- Price and timeline impact
- Approval response
- Payment status and proof
- Freelancer confirmation
- Handoff or Proof Pack timeline
Status basics
Common statuses you may see
| Status | What it means | What to do next |
|---|---|---|
| Draft | The request has not been sent to the client yet. | Review the price, timeline impact, and payment requirement before sending. |
| Sent | The client approval link has been created and shared. | Wait for the client to approve, decline, or ask a question. |
| Approved, payment required | The client approved, but the request requires payment before work starts. | Send or confirm the payment request. Do not mark the work ready yet. |
| Paid pending confirmation | The client marked paid or uploaded proof, but you have not confirmed receipt. | Check your account or payment method, then confirm received if accurate. |
| Ready to start | The request is approved and required payment has been confirmed. | Begin the approved work and keep future changes in the same record trail. |
| Handoff locked | The work may be ready, but final files or source files should not be released until the required payment is confirmed. | Use the handoff lock workflow to wait for confirmation before release. |
For a deeper explanation, see the payment ledger feature and the help article for payment statuses when available.
Checklist
First request quality check
Include before you send
- Clear request title
- Plain-language description of what changed
- Price or fee, if billable
- Timeline impact
- Payment required before work or before handoff, if applicable
- Client-facing note that stays calm and professional
Avoid in your first request
- Starting work from a vague chat approval alone
- Letting the client self-confirm final paid status
- Combining unrelated changes into one unclear request
- Using hostile language when a clear price and condition would work better
- Releasing final or source files before a required payment is confirmed
Troubleshooting
If something does not look right
The client says the price is wrong
Keep the request in a pending state, edit the draft or create a revised request, and send the updated link. Avoid treating a disputed price as approved.
The client approved but has not paid
If payment is required before work, keep the request as approved but unpaid. Use the payment ledger to track the payment request and confirmation.
The client says they paid
The client can mark payment sent or upload proof, but you should confirm receipt on your side before the item becomes paid.
You need a clean example first
Open the sample approval link to see how a client-facing request should look before sending your own.
Create a clear record before the work continues
Your first request does not need to be complicated. Start with one client change, add the price and payment condition, then send the approval link before you continue the work.
Related help and product pages
Next places to learn
FAQ
Getting started questions
What should I create first in ScopeDue?
For most freelancers, the best first step is a priced change request tied to a client project. It gives the client a clear approval link before extra work continues.
Do I need a full project setup before sending one approval link?
No. A short project record with the client name, project name, and original scope summary is enough for your first request. You can add more project detail later.
Can a client confirm that a payment is fully paid?
No. A client can mark payment as sent and upload proof, but the freelancer confirms receipt before the payment status becomes paid.
Should I use ScopeDue instead of an invoice or contract?
No. ScopeDue is a client change approval and payment proof workspace. It helps create a clear business record, but it does not replace legal, tax, accounting, invoicing, or contract advice.
Support note: 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.
Need help? Visit the Help Center or contact ScopeDue support.