01
Separate the record from each interpretation
A fictional freelancer experiences an unexpected capacity problem and cannot responsibly complete the project on the current schedule. The client has a near-term business need and depends on access to current work.
The freelancer should not disappear or promise work they cannot safely perform. The client also needs a factual transition record rather than a vague apology.
Documented facts
- The freelancer has determined that continuing under the current plan is not realistic.
- The project contains completed, in-progress, and not-started work.
- The client’s files, access, payments, and transition needs have not been fully reconciled.
What the freelancer believes
- Prompt notice and a bounded handover can reduce harm even if the project cannot be completed.
- Private health, family, or safety details need not be disclosed beyond what is necessary to manage the project.
What the client believes
- The early exit may threaten an important deadline and create replacement cost or continuity risk.
- The client needs usable files, current status, and access information quickly enough to evaluate alternatives.
What remains unknown
- Whether the problem requires immediate cessation or permits a limited transition period.
- What notice, cure, substitution, refund, delivery, or assistance terms control.
- Which work and accounts can be transferred safely and what remains disputed.
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
- Protect immediate safety first, then give the earliest responsible notice without unnecessary personal disclosure.
- Prepare a precise status and handover inventory and avoid representing unfinished work as complete.
Client perspective
Practical concerns from the client’s side
- Ask for operational facts, not private personal details, and prioritize continuity, security, and the most critical outcome.
- Review replacement, reduced-scope, or staged-transition options while preserving rights through the agreed process.
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.
- Immediate safety, security, data, or account risks that require action before ordinary notice.
- Termination, notice, cure, substitution, payment, refund, handover, confidentiality, and access terms.
- The exact state of each deliverable, repository or file location, documentation, and known defect.
- Client-owned accounts, temporary permissions, secrets, devices, data, backups, and removal steps.
- Platform support or emergency process if the engagement is platform-based.
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.
Give responsible notice
State the capacity decision, proposed work stop or transition point, and when the client will receive a status record.
Reduce immediate risk
Secure accounts and data, preserve evidence, and address urgent access without sharing credentials in messages.
Prepare the transition
Inventory work, files, instructions, open decisions, payments, and permissions using the agreed process.
Confirm the wind-down
Record what transferred, what did not, payment or refund status, access removal, retention, and unresolved issues.
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
Safety can require immediate action; contractual questions can require qualified advice. Get prompt help when threats, harassment, health or disability rights, protected information, insolvency, crime, data exposure, or a material legal deadline may be involved.
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 help organize neutral notice, status, handover, and open questions. Do not submit health details, credentials, client data, or privileged advice. 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.
Structure a redacted transition 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 handover, access, payment, licenses, and retention fields to the early transition.
Project terms
Statement of Work outline
Check notice, termination, handover, payment, confidentiality, and dispute language.
Freelancer learning path
Close work explicitly
Review the ordinary close-out responsibilities that still need attention during an early exit.
Related situation
Client cancels the project
Compare the wind-down record when the client initiates the stop.