Request a Short Extension on a Professional Deliverable

Ask before the deadline becomes a surprise

Send the request when you have a credible reason to think the deliverable will be late—not after the deadline has passed if you can avoid it. Early notice gives the recipient a chance to adjust review plans, coordinate with others, or decide whether a partial delivery would help.

You do not need to wait until every detail is known. If the risk is real, explain what you know, state when you will provide a firmer update if needed, and avoid presenting uncertainty as a confirmed new deadline. For urgent work, use the communication method your team normally relies on, then follow up by email so the dates and agreement are clear.

Check the date before proposing it

Choose a date based on the work remaining, not simply the first date that sounds more comfortable. List the unfinished pieces, estimate the time each needs, and account for reviews, dependencies, and your other committed work. Leave room to address likely feedback if the deliverable will be reviewed before it is considered complete.

Check whether the proposed date falls on a working day for the people involved and whether a meeting, handoff, or approval must happen first. If another person’s input is required, ask about their availability before treating that date as dependable. A precise but unrealistic promise can create a second missed deadline; a slightly later date you can meet is usually more useful.

• What remains, and what must happen before the work is ready to send?
• Are there reviews, dependencies, or other commitments that affect the timeline?
• Can you deliver by the proposed date without relying on an unconfirmed assumption?

Keep the reason brief and useful

Give enough context for the recipient to understand the request, but do not turn the email into a lengthy defense. State the relevant constraint plainly: for example, a required source file arrived later than expected, or a higher-priority issue needs attention. Use a reason that is accurate and appropriate to share.

Then make clear what you are doing about the work. If it helps, mention the next concrete step, such as completing a review or sending a draft. Do not blame a colleague, disclose confidential details, or promise a level of polish or scope that you have not checked. If the deliverable’s scope will change, say so and ask whether that change is acceptable.

Editable email template

Replace every bracketed field before sending. If you do not know the exact original deadline, check the agreed schedule rather than guessing. Address the recipient by the name they use at work, and keep the subject specific enough to identify the deliverable.

• If a partial item is not useful or feasible, remove that sentence rather than offering it automatically.
• If the request affects a client commitment, approval, or handoff, identify that impact clearly and ask about the needed decision.

To: [recipient@example.com]
Subject: Extension request: [deliverable]

Hi [Name],

I’m writing about [deliverable], originally due [original date and time]. Because [brief, accurate reason], I need a little more time to complete it.

Could I send it by [specific new date and time]? I have checked the remaining work and [brief next step or relevant dependency], and this date is realistic for me.

I’m sorry for the change. Please let me know if this timing works or if you’d prefer that I send [useful partial item] by the original deadline. I’ll continue with [next action] in the meantime.

Best,
[Your name]

Make the request, not an assumption

Use wording such as “Could I send it by [date]?” unless the recipient has already authorized the change. Do not update a shared schedule or tell other stakeholders that the deadline moved before the person responsible has agreed.

If the original date is close, make the subject line easy to recognize and send the message through an appropriate work channel. For a time-sensitive deliverable, a brief conversation may be useful, but still record the agreed date in writing. This helps everyone distinguish a request from a confirmed change.

Confirm what happens next

When the recipient replies, check that you have the same new date, time, and time zone if those details matter. Confirm whether the deliverable’s scope, format, or review process has changed. A short reply—“Thanks, I’ll send [deliverable] by [confirmed date and time]”—creates a clear shared understanding.

If the proposed date is declined, do not simply repeat it. Ask which timing or partial delivery would be most useful, then check what you can realistically commit to before answering. After agreement, update any relevant task or calendar entry you are responsible for and work toward the confirmed date. The request has worked when the responsible person has responded and both sides understand the revised expectation—not merely when the email has been sent.