01
Separate the record from each interpretation
A fictional freelancer was due to deliver a staging version on Tuesday. Tuesday passes without the agreed output, and the freelancer sends a short note the next morning saying the work needs more time.
A missed date is documented, but the cause, material effect, available cure, and authority to revise the schedule still need to be established.
Documented facts
- The project record names Tuesday as the staging delivery date.
- The staging output was not delivered by that date.
- The freelancer gave notice after the deadline and has not yet supplied a detailed recovery plan.
What the freelancer believes
- An unexpected technical issue can be corrected within several working days.
- Some earlier client content changes also reduced the available build time.
What the client believes
- The missed date puts a planned internal review and launch at risk.
- The freelancer should have raised the risk before the deadline rather than afterward.
What remains unknown
- Which work is complete, blocked, or still untested and what evidence supports that status.
- Whether client dependencies changed the controlling date under the agreement.
- Whether a realistic revised plan can protect the important business outcome.
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
- Give a candid status by deliverable, identify the cause without obscuring responsibility, and propose dates you can support.
- Do not promise an aggressive cure merely to reduce immediate discomfort.
Client perspective
Practical concerns from the client’s side
- State the concrete effect of the missed date and ask for a recovery plan rather than assuming abandonment or bad faith.
- Use the agreed notice, cure, approval, and escalation process before inventing a new one.
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.
- The controlling delivery date, time zone, deliverable, and definition of submission.
- Dependency, extension, notice, cure, and schedule-change wording.
- Prior status reports, risk notices, supplied inputs, approvals, and requested changes.
- The material effect on downstream review, launch, staffing, or third parties.
- What has been completed and whether a smaller verified delivery can reduce uncertainty.
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.
Request a factual status
Ask what is complete, incomplete, blocked, and ready to inspect, with dates rather than percentages alone.
Test a recovery plan
Identify the critical deliverable, realistic sequence, owner, check-in, and revised approval point.
Record any revised date
Only the authorized parties should change the schedule, and related review or payment effects should be explicit.
Escalate proportionately
If the plan is not credible or communication stops, follow the agreement or platform process and preserve the record.
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 missed date does not by itself answer questions about termination, refund, damages, or other rights. Seek qualified help when the commercial impact is material or the controlling contract, platform process, insurance notice, or local law is unclear.
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 separate dates, notices, dependencies, impact, and proposed next steps. Keep names, account details, and confidential project material out. 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 deadline record →
Read how Lucy handles a request before submitting real project material.
Keep going
Continue from the actual record
Agreement record
Statement of Work outline
Review dates, dependencies, notices, milestones, and change handling in one place.
Client learning path
Manage timing and blockers
See how a client can provide decisions, consolidate feedback, and respond to schedule risk.
Worked example
Read Harbor Street status updates
See how a project records progress, dependencies, and a possible change before dates move.
Related situation
Project taking longer than expected
Separate elapsed-time growth from a single missed delivery event.