HOME › HOW TO SAY IT

How to push back on a deadline without losing trust

The delay is rarely the problem. Finding out late is the problem.

The situation

The date is not going to happen. You knew a few days ago, and every day you wait makes the message harder to send and worse to receive.

The email that works does three things quickly: names the new date, says what the extra time buys, and confirms what has not changed. Vagueness here reads as trouble, even when there is none.

Why it is hard

A slipped deadline threatens what politeness theory calls negative face — the other person’s freedom to plan. That is why late notice stings more than the delay itself: it removes their options rather than the outcome. The repair is to hand options back. A specific new date, a reason that shows the time is being spent on their behalf, and an explicit list of what is unaffected restores the ability to plan, which is what was actually taken.

What to actually write

Two versions of the same message. Same facts, different posture — which one is right depends on the relationship, not on which is “better”.

THE DIPLOMATClient or someone senior who will be disappointed

Subject: Meridian launch — moving to Wednesday 27th

Hi Sarah,

I want to flag this early rather than on Friday: the launch is moving from the 22nd to Wednesday the 27th.

The five days are going into QA on the mobile checkout flow. Nothing is wrong — we found two edge cases and I would rather catch them now than in your customers' hands.

Budget and scope are unchanged. I can have a private preview link with you Thursday, and I am glad to walk you through it if that is useful.

— Sam

THE VETERANInternal team, no diplomacy tax needed

Subject: Launch moves to Wed 27th

Quick one: launch is Wednesday the 27th, not Friday the 22nd.

The extra days go to mobile checkout QA — two edge cases we would rather not ship.

Scope and budget unchanged. Preview link Thursday.

— Sam

What to avoid

Waiting for certainty. A heads-up with a rough date beats a precise one sent late.
Blaming named people. "Two of our devs were out" reads as an excuse and exposes your team.
Leaving the new date open. "Early next week" invites a second conversation you do not want.

Common questions

How much notice is enough?

As soon as you believe it more likely than not. People forgive a delay flagged early and remember one flagged late.

Should I apologise?

Once, and briefly. The reassurance that scope and budget are unchanged does more work than an apology does.