What to include
Keep the request short and useful. Include:
- The original deadline
- The real constraint in one sentence
- A new date you can actually meet
- Any partial deliverable or next step you can offer now
The other person should not have to guess whether you still own the work.
A clean message pattern
This basic structure works in most cases:
- A heads-up before the deadline
- The real issue in one sentence
- The revised date
- A quick offer or question
Example:
"Hi [Name], I wanted to flag that I won't be able to finish [task] by [original date]. I'm waiting on [constraint] and need a little more time to get this right. I can send a complete version by [new date]. If helpful, I can also share the current draft before then."
That reads more responsibly than a long apology or a vague "running behind."
What makes the ask stronger
- Ask as soon as you know.
- Pick a specific date, not "soon."
- Keep the reason honest but short.
- Offer something useful if you can.
Most people trust a clean reset more than a fuzzy one.
What weakens the request
- Waiting until after the deadline passes
- Asking without proposing a new date
- Padding the message with too many apologies
- Giving a reason that sounds evasive instead of real
The stronger move is usually simple: own the delay, name the new date, and stop talking.
If your exact situation is trickier than a generic template, You.one can help you shape the wording around the actual stakes, person, and timeline involved.
Use You.one when the details actually matter
This page is here to help you orient. If your situation depends on timing, money, another person, or what has already happened, You.one can walk through your version step by step.
Draft my extension request