01
Separate the record from each interpretation
A fictional fixed-fee project is entering its eighth week after an initial six-week plan. Both parties agree the work is not finished, but they describe the reason differently.
Elapsed time alone does not reveal who caused the delay or what remedy is sensible. The project needs a timeline of work, decisions, dependencies, changes, rework, and remaining acceptance steps.
Documented facts
- The initial plan described six weeks, and the project is now in week eight.
- Several client input dates, freelancer estimates, and requested adjustments appear in the record.
- No complete revised schedule and responsibility summary has been approved.
What the freelancer believes
- Late inputs and evolving requests account for most of the added elapsed time.
- The remaining work can be completed if decisions stop changing.
What the client believes
- The freelancer underestimated the work and has not made progress easy to verify.
- Some adjustments were normal clarification rather than added scope.
What remains unknown
- How much time came from active work, waiting, defects, added work, or revised decisions.
- Which remaining outputs are critical and what evidence shows their current state.
- Whether the original objective, fee, team availability, and target date still make sense together.
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
- Replace general percentage-complete claims with a deliverable-by-deliverable status and realistic remaining estimate.
- Own estimating or quality errors where supported, while separately recording client dependencies and added work.
Client perspective
Practical concerns from the client’s side
- Prioritize the business outcome and identify which work can be deferred rather than insisting that every idea remain urgent.
- Evaluate the timeline against the actual record, including client waiting time and approved changes.
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.
- Original estimate assumptions, target versus binding dates, and current deliverable status.
- A dated timeline of inputs, approvals, work submissions, defects, changes, and waiting periods.
- Fixed-fee or hourly terms and how added work or schedule changes are handled.
- Remaining critical work, realistic effort, owners, dependencies, and acceptance sequence.
- Whether reducing scope, adding resources, revising dates, or ending work creates the least harmful path.
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.
Build one shared timeline
List material events and classify each as work, waiting, correction, change, or decision.
Reforecast the remainder
Use deliverables, owners, dependencies, and review points rather than one completion percentage.
Choose a recovery shape
Consider reducing scope, sequencing a minimum usable release, revising dates, or approving a true change.
Set a decision checkpoint
Record how progress will be verified and when the parties will reassess if the plan fails.
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
A recovery plan is not a waiver or legal allocation of delay. Get qualified help before making material termination, refund, suspension, or damages decisions when responsibility and the governing terms remain disputed.
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 organize a redacted remainder into deliverables, dependencies, assumptions, and decisions. Use the dispute tool instead when the primary need is a contested record or wind-down. 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.
Reframe the remaining project scope →
Read how Lucy handles a request before submitting real project material.
Keep going
Continue from the actual record
Planning guide
Freelance Pricing and Project Budgeting
Revisit estimate assumptions, fixed-fee risk, milestones, revisions, and change effects.
Change record
Project Change Request
Record changed facts, scope, dates, price, and acceptance if recovery requires a formal change.
Worked example
See a project revise its schedule
Follow Harbor Street from a new request to a recorded December launch date.
Related situation
Freelancer missed a deadline
Use the missed-date guide when one specific delivery event needs immediate recovery.