ScopeDue Feature
Handoff Lock
ScopeDue Handoff Lock helps freelancers keep final files, source files, exports, launch access, or completed deliverables locked until the required payment is confirmed. Instead of releasing work from a messy chat promise, you create a clear handoff checklist, connect it to the payment ledger, and record when the client marked paid, when proof was uploaded, when you confirmed receipt, and when handoff was released.
Last reviewed: May 26, 2026 · Built for U.S. freelancers, solo studios, designers, video editors, and developers
What it does
Release final work only after the required condition is met.
Handoff Lock is for the moment when the work is finished, the client wants the final deliverables, and payment status is still unclear. It gives you a professional way to say: final handoff is ready, but release happens after payment is confirmed on your side.
Use it when final payment, a source file fee, an extra revision charge, or a milestone payment must be confirmed before the next handoff step. For a broader source-file workflow, pair it with the source file handoff guide.
Product workflow
Pain → ScopeDue workflow → What gets recorded
Pain
The client asks for final files, source files, a high-resolution export, a site transfer, or launch access before the final payment is actually confirmed. You do not want to sound difficult, but releasing too early can create payment confusion.
ScopeDue workflow
- Create the handoff checklist.
- Set the payment-required-before-handoff condition.
- Send the client link or payment message.
- Client marks paid or uploads proof.
- Freelancer confirms received and releases handoff.
What gets recorded
- handoff item;
- payment status;
- payment proof;
- freelancer confirmation;
- release timestamp;
- Proof Pack timeline.
Best-fit scenarios
Built for designers, video editors, developers, and service providers who hand off valuable final work.
Designers
Use Handoff Lock before releasing editable logo files, brand assets, source files, final PDFs, packaging files, or alternate formats that were tied to final payment.
Video editors
Use it before sending high-resolution exports, final cuts, captions, project files, vertical versions, or extra deliverable bundles after a payment-required approval.
Developers
Use it before transferring code, credentials, deployment access, website ownership, repository access, or launch handoff after the remaining payment is confirmed.
Practical checklist
What to include before final handoff
A good handoff record should make the next step obvious to both sides. The client should see what is ready, what is still locked, what payment condition applies, and what happens after payment is confirmed.
- Name each final deliverable or file package.
- State whether the item is included, an add-on, or tied to a final payment.
- Connect the handoff item to the correct payment item.
- Show whether the client has marked payment as sent.
- Require freelancer confirmation before the handoff becomes released.
- Save the handoff event to the Proof Pack timeline.
Payment status logic
Approved, marked paid, and confirmed received are not the same thing.
Handoff Lock works with the payment ledger so you do not treat a client’s “I paid” message as final confirmation. The client can mark payment as sent and upload proof; the freelancer confirms whether payment was actually received.
| Status | What it means | Handoff result |
|---|---|---|
| Payment requested | The freelancer has asked for the required payment. | Handoff remains locked. |
| Client marked paid | The client says payment was sent, optionally with proof attached. | Handoff remains locked until freelancer confirmation. |
| Paid pending confirmation | The payment event exists, but receipt has not been confirmed on the freelancer side. | Handoff remains locked. |
| Freelancer confirmed received | The freelancer confirms payment was received or confirms the required partial amount. | Handoff can be released and recorded. |
| Disputed or overdue | Payment is not resolved or the due date has passed. | Handoff remains locked unless the freelancer changes the condition. |
Client-friendly wording
A calm message you can send
Use this as a business workflow message, not as legal or accounting advice. You can adapt the wording based on your contract, client relationship, and payment method.
When to use it
Use Handoff Lock when the deliverable has leverage.
- Final artwork, video exports, copy packages, code, or website access are ready.
- Final payment, milestone payment, or source file fee is still not confirmed.
- The client says they paid, but you still need to verify receipt.
- You want the release decision recorded in the same Proof Pack as approvals and payments.
Sample timeline
How a clean handoff record looks
- Final files marked readyThe freelancer marks the deliverable ready but not released.
- Handoff lock appliedThe record says final handoff requires confirmed final payment.
- Payment requestedThe payment item is connected to the final deliverable.
- Client marked paidThe client says payment was sent and may upload proof.
- Freelancer confirmed receivedThe freelancer verifies receipt and updates the ledger.
- Handoff releasedThe final files, source files, export, access, or launch handoff can be released and saved to the Proof Pack.
Proof Pack connection
The handoff decision becomes part of the project record.
- Original handoff rule
- Final payment item
- Client marked paid event
- Payment proof reference
- Freelancer confirmed received event
- Handoff released timestamp
Why this matters
Freelance handoff problems often become confusing because the approval, payment, and release decision live in different places. Handoff Lock keeps those events connected so the record tells a simple story: what was ready, what was required, when payment was confirmed, and when the deliverable was released.
For proof-focused workflows, review the Proof Pack feature or preview a sample Proof Pack.
Decision guide
Use this when / do not use this when
| Situation | Use Handoff Lock? | Better next step |
|---|---|---|
| Final files are ready, but final payment is not confirmed. | Yes | Create handoff checklist and request payment. |
| Client asked for source files that were not included in the original scope. | Yes | Use a source file release template or source file request. |
| The client approved extra work, but payment is required before delivery. | Yes | Connect the change request to payment status and handoff release. |
| You are only sharing a low-risk preview or watermarked draft. | Maybe not | Use your normal review process and keep the final handoff locked. |
| You need legal advice about withholding deliverables. | No | Read the product limits and consult a qualified professional for legal guidance. |
Next step
Create a clear handoff record before the files go out.
Use a handoff checklist to define what is ready, what payment is required, who marked paid, whether proof exists, and when you confirm receipt. That keeps the conversation professional without turning final delivery into a guessing game.
Related workflows
Keep handoff connected to approval, payment, and proof.
Important: 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.
FAQ
Handoff Lock questions
What is a handoff lock?
A handoff lock is a rule that keeps final files, source files, exports, or launch access unreleased until the required payment is confirmed by the freelancer.
Can a client confirm final paid status?
No. The client can mark payment as sent and upload proof. The freelancer confirms whether the payment was actually received.
Is this only for source files?
No. Use it for source files, final artwork, high-resolution exports, code transfer, website launch access, final copy packages, or any deliverable that should wait for payment confirmation.
Does this replace my contract?
No. ScopeDue creates a clear business record of approvals, payment events, and handoff decisions. It does not replace a contract or legal advice.