Deadline extension request

How to use it well

• →Send it before the deadline, always — an extension asked for after the date has passed is an apology, not a request.
• →Describe what happened, not why it wasn't your fault; a reason that sounds like an excuse undercuts the ask.
• →Commit to a specific new date, not "a bit more time" — a vague ask just hands the scheduling work back to your manager.

Part by part

before {{original_deadline}} arrives rather than after

States the timing explicitly, because early notice is the entire difference between a request and an apology.

I'd like to commit to {{new_deadline}}

A specific new date rather than a vague delay. Commit is the word doing the work — it is a proposal you are accountable to.

which gives me room to {{plan}}

Says what the extra time buys. Without it the request reads as needing longer rather than as a plan with a schedule.

or if we need to talk through a different approach

Leaves room for the alternative where the deadline holds and the scope changes, which is often the better outcome.

Common mistakes

• I don't think I'll make the deadline.

  States a problem and hands the whole thing over. A request without a proposed date and a plan makes your manager do the work of deciding what happens next.

• Sorry, this is taking longer than expected. Can I have more time?

  More time is not a date. An open-ended extension cannot be planned around, and it invites the follow-up question you should have answered in the first message.

• Sending it the day the deadline lands.

  Timing is most of what is being judged. The same message a week early is a plan; on the day it is a notification that something has already gone wrong.

Questions