01
Separate the record from each interpretation
A fictional client says a business priority has changed and asks to stop a project halfway through. The freelancer has completed some work and has partially finished other files.
The client may have a legitimate reason to stop, and the freelancer may have legitimate completion, payment, or handover questions. Cancellation should become a structured wind-down, not one ambiguous message.
Documented facts
- The client sent a written request to stop future work.
- Some deliverables are complete, some are in progress, and some have not started.
- Payments, licenses, access, files, and retention have not yet been reconciled.
What the freelancer believes
- Completed and committed work should be identified and handled under the agreed termination and payment terms.
- A rushed handover could expose unfinished material or third-party assets without the right context.
What the client believes
- Stopping now should limit further cost and effort because the business no longer needs the full project.
- Useful paid-for work and client-owned materials should be returned promptly.
What remains unknown
- The effective stop date, authorized notice method, and any required notice or cure period.
- Which amounts are funded, paid, invoiced, refundable, disputed, or tied to incomplete triggers.
- What may be handed over, used, retained, deleted, or accessed after termination.
02
Consider both perspectives without assuming fault
Different concerns can be reasonable at the same time. Neither list proves a disputed fact; it shows what a workable response must address.
Freelancer perspective
Practical concerns from the freelancer’s side
- Acknowledge the stop request, pause avoidable new work, preserve the record, and prepare a neutral status inventory.
- Do not withhold, delete, publish, or transfer material based on assumptions about rights or leverage.
Client perspective
Practical concerns from the client’s side
- Use the agreed notice route and identify the desired stop date, immediate safety or access needs, and business priority.
- Review completed work and payment records fairly rather than treating all unfinished work as valueless.
03
Check these records before deciding what happened
Start with the material both parties can inspect. Preserve original messages and files; work from copies when adding notes.
- Termination, notice, payment, refund, ownership, license, confidentiality, retention, and dispute wording.
- Platform cancellation, escrow, milestone, review, and support procedures if applicable.
- A deliverable inventory showing complete, in-progress, blocked, and not-started work.
- Funded, paid, invoiced, committed, and third-party amounts with supporting records.
- Client materials, freelancer materials, access, backups, credentials, licenses, and secure return or deletion needs.
04
Choose the smallest proportionate next step
These steps are possibilities, not a required legal sequence. Adapt them to the actual risk, agreement, platform, and communication record.
Confirm the pause
Acknowledge the request, identify the proposed effective point, and stop avoidable new work while urgent risks are addressed.
Create a wind-down inventory
List work status, files, payments, licenses, data, access, and decisions without asserting disputed outcomes.
Apply the controlling process
Use the agreement and platform steps for notice, review, payment, refund, delivery, and disputes.
Close each record separately
Confirm final work status, money, handover, retention or deletion, access removal, and continuing obligations.
05
Adapt a neutral, answerable message
Replace every bracketed detail and verify the record before sending. Do not turn the example into a threat or claim a consequence you have not checked.
06
Know when the situation needs qualified help
Termination, refund, ownership, license, confidentiality, and possession questions can carry legal consequences. Use qualified advice and the applicable platform process when the record does not clearly support an agreed wind-down.
Get qualified help promptly when there is
- a threat to anyone’s physical safety or credible harassment or discrimination concerns;
- suspected crime, fraud, unauthorized account access, or a material exposure of personal or confidential data;
- a large potential loss, an imminent filing or response deadline, or a demand that depends on jurisdiction-specific rights; and
- a platform restriction, court order, insurance requirement, or other process with a deadline you cannot confidently interpret.
07
Use Lucy only after removing sensitive details
Lucy can structure the timeline, work status, payments, files, access, and open questions. She does not determine termination rights or amounts owed. Following this link opens the ordinary blank tool. It does not load this example, transmit content, or make an AI request until you choose to submit the tool form.
Organize a redacted cancellation record →
Read how Lucy handles a request before submitting real project material.
Keep going
Continue from the actual record
Close-out record
Final Delivery Checklist
Adapt the file, access, approval, payment, and retention fields to an early wind-down.
Project terms
Statement of Work outline
Review termination, payment, ownership, confidentiality, and dispute wording together.
Client learning path
Close access and preserve records
Use the ordinary close-out sequence as a checklist, while recognizing that cancellation may leave disputes.
Related situation
Freelancer ends the engagement early
Compare the responsibilities when the freelancer initiates the wind-down.