Late deliverables, budget overruns, and blockers land better with facts, options, and a calm plan, not apologies without structure.
11 min readCALM script
- Context (project, milestone)
- Actual issue (one sentence)
- Leverage options (2 paths)
- Move forward (new date or next step)
Template: you will miss deadline
Subject: [Project] timeline update
We targeted [date] for [deliverable]. It will move to [new date].
Reason: [blocked on login / scope grew / my estimate was short]
Options:
- New date [date] with full scope
- Ship [smaller slice] by [original date], rest [date] (change order if extra hours)
Recommend: option [X]. Reply or I will proceed.
Send as soon as you know, not day of.
Template: their delay caused slip
Milestone [X] is waiting on [asset / approval] since [date]. That pushes delivery to [new date] per our scope. Send [item] by [date] to protect [later milestone].
Factual, not blaming.
Template: you made a mistake
I sent the wrong [file / report]. Correct version attached. Cause: [brief]. Steps so it does not repeat: [checklist]. No extra charge for fix.
Own it. Fix it. Do not grovel into free weekend work unless you choose to.
Common mistakes
| Mistake | Result |
|---|---|
| Hiding until due date | Trust break |
| Sorry with no plan | Client still anxious |
| Absorbing rush free | Burnout |
| Blaming in Slack | Looks unpro |
How Salag helps
- Freelance Readiness Checker: realistic milestones upfront.
- Late Fee Calculator: if bad news involves payment delay.
- Scam Pattern Detector: clients who rage at normal delays.
Move safer. Not faster.
In short
Bad news lands best as fact + cause + options + new date.
Skip five paragraphs of sorry. Clients trust VAs who flag problems early with a plan.
Common questions
Bad news lands best as fact + cause + options + new date. Skip five paragraphs of sorry. Clients trust VAs who flag problems early with a plan.
State the fact first (deadline missed, blocker, mistake). No long apology intro. Then cause and options.
Direct but polite English. Clients prefer early bad news over surprise on due date.
Contract should say how delays and change requests affect timeline. Makes news easier to explain.
Stay factual. Offer call if emotional. Do not over-apologize into accepting free rush work.
Context, Actual issue, Leverage options, Move forward date. Email or call script.
If your mistake cost them money, propose fix and fair credit. If their delay caused slip, document chain.
Yes. Written bad news with new date protects both sides.
Scope docs show if slip is in-scope delay vs extra work.
Timeline doc, change order, Loom walkthrough of fix plan.
Fifteen minutes to draft fact + options email.
Projects: new milestone date. Retainers: reprioritize weekly list.
Still send written summary of new plan. Get reply when possible.