THE DIRECT ANSWER

Tell the affected person as soon as you know the deadline has been missed. Name the deliverable, acknowledge the impact you can verify, separate completed work from remaining work, and propose a specific recovery checkpoint. If recovery requires changing scope, timing, or someone else’s priorities, ask the person with authority to choose instead of quietly making that decision yourself.

Start with the missed commitment

A useful update makes the situation easy to understand before it explains the background. Say which commitment was missed and when the person will hear from you next. Avoid calling a document nearly finished when the missing validation or handoff prevents someone from using it. Acknowledge the missed commitment directly without turning the message into a judgment about your character.

If you know a downstream activity is blocked, name it. If you do not know the impact, ask which dependency needs attention first. Do not invent an impact to make the apology sound more serious.

Make the recovery estimate inspectable

List the remaining tasks and their estimated time separately from the time you actually have available. Include checking and handoff. A recovery promise that omits the final transfer can create another missed commitment. If the estimate is uncertain, identify what you will check and give a short checkpoint for updating it rather than presenting a guess as a guaranteed completion time.

  • Completed: what another person can already use.
  • Remaining: specific work, dependencies, and validation.
  • Available: time you can actually allocate before the proposed checkpoint.

Ask for the decision you cannot make alone

A deadline has already passed, so resetting your personal schedule does not automatically repair the agreement. Offer a workable next step and ask whether it meets the receiver’s need. The owner of the deadline may need to approve a new delivery time; a project lead may need to authorize removing work. State which decision you need and by when. If nobody responds, report the absence of agreement rather than describing your proposal as approved.

Adapt the message to your role

An employee can identify competing assignments and ask a manager to resolve priority conflicts. A freelancer can propose a revised delivery arrangement while checking the agreed scope and acceptance process. Someone working across several roles can disclose the relevant availability limit without explaining unrelated clients or personal commitments. In every role, avoid volunteering another person’s time to make your recovery promise possible.

Close the loop after the repair

Once a recovery plan is agreed, send a compact written recap with the owner, deliverable, checkpoint, and open dependency. At the checkpoint, report whether the promised usable output exists. After delivery, discuss one practical prevention change: an earlier risk signal, an explicit handoff allowance, or a smaller review milestone. Keep that discussion separate from the immediate request for a decision so the urgent message remains easy to act on.

AUTHORED FICTIONAL EXAMPLE

A conversation you can rehearse

Authored fictional example, the Fixed Deadline case: Friday noon was fixed. There were five hours available; the core took three hours, the mandatory handoff one, and optional polish three. The full seven-hour version did not fit. Noon has now passed without a usable handoff.

A first reaction

Sorry, things got hectic. I will finish everything as soon as possible.

A more specific response

I missed the Friday-noon delivery, and the handoff is not ready. I am checking the remaining core and handoff work now and will give you a recovery estimate at 12:20. Optional polish stays outside that estimate. Which downstream dependency needs attention first, and who can approve the revised delivery time?

The better response does not reuse the original four-hour estimate as though no work had happened. It acknowledges the miss, creates a near-term checkpoint, and asks for the impact and decision authority needed to agree recovery.

Before you act

  • Name the missed commitment plainly.
  • Distinguish usable work from work merely started.
  • Estimate the remaining work afresh.
  • Include validation and handoff.
  • Get agreement to any revised commitment.

Common questions

Should I explain why the deadline was missed?

Yes, when the explanation helps the receiver make a decision or prevent a repeat. Put the status and recovery request first. Use observable facts, and do not assign blame or speculate about another person’s motives.

What if I cannot yet give a reliable new completion time?

Give a specific time for the next verified update and explain what you will check before then. A checkpoint is a commitment you can make without pretending the final estimate is settled.

Original conversation-practice guidance using an authored fictional case. It cannot determine your actual remaining workload, organizational authority, or contractual consequences.

Source basis: an original scenario-based practice framework. The example is fictional, and no external research finding or measured effectiveness is claimed. Read the editorial method.