Two deadlines just landed on the same week, and neither one is negotiable on your end. One is a client deliverable. The other is an internal review that three other people are waiting on. You cannot do both at full quality, and pretending otherwise is how people end up missing both.
An email informing your manager of overlapping deadlines is not a complaint. It is a risk report that arrives early enough for someone to act on it. The difference between a manager who helps you reprioritize and a manager who questions your time management usually comes down to when you sent the message and how you framed it.
Most people wait too long, bury the conflict in a status update, or present the problem without a recommendation. The result is a manager who has to do the triage themselves, which is exactly the outcome you were trying to avoid. The templates and timing rules below fix that.
Why Waiting Until the Last Minute Makes It Worse
A deadline conflict is only a problem when it is discovered late. Found early, it is a scheduling decision. Found on the day something is due, it is a failure with your name on it.
Managers can move deadlines, reassign work, bring in help, or reduce scope. Every one of those options shrinks as the calendar compresses. At two weeks out, there are five ways to solve the problem. At two days out, there is one, and it usually involves someone working a weekend.
There is also a trust dimension that is easy to underestimate. A manager who hears about a conflict early learns that you flag risks before they become emergencies. A manager who hears about it on the due date learns something else entirely, even if the conflict was genuinely outside your control.
The Mistakes That Turn a Deadline Conflict Into a Performance Issue
These are the specific errors that convert a solvable scheduling problem into a conversation about your reliability.
- Burying it in a status update. If the conflict appears in paragraph four of a weekly report, it does not count as a notification. It counts as a mention.
- Presenting the problem with no recommendation. Managers want a proposed priority order, not a question mark. Bring an opinion even if it is wrong.
- Using urgency language that sounds like panic. "Everything is on fire" makes people defensive. State dates, deliverables, and impact instead.
- Apologizing for having a conflict. You do not control the calendar of every stakeholder. Over-apologizing makes it look like you mismanaged something you did not.
- Assuming your manager already knows the other project's deadlines. They may not. Spell out both commitments in full.
- Framing it as a complaint about workload. This is a priority question, not a capacity grievance, and the two get handled very differently.
- Hiding the quality trade-off. If doing both means doing one badly, say that explicitly. That is the information your manager actually needs to make the call.
- Making the decision for them. Quietly dropping the lower-profile deliverable without telling anyone is the worst version of this. It removes the choice from the person who owns it.
When to Send Your Deadline Conflict Email
Timing is what determines whether your email reads as a risk report or an excuse. Send it the moment you can articulate the conflict clearly, which is usually the same day you notice it.
- Two or more weeks out: Full notice with options, cost estimates, and a recommended priority order.
- One to two weeks out: Shortened notice focused on the decision you need, not the full background.
- Under a week: Escalation framing. State which deliverable will slip without a decision today.
- Same day as the deadline: Emergency framing. State what is about to fail, offer the least-bad option, and ask for a call.
Send between Tuesday and Thursday morning. Monday inboxes absorb risk reports into a backlog, and Friday afternoon emails get read the following week with the urgency drained out of them.
If the conflict involves a customer commitment or a regulatory deadline, send it the same day you identify it regardless of the day of week. Those carry consequences that compound quickly.
Email Templates for Every Situation
Match the template to how much time you have and how much authority you want to keep. The first is a straightforward notice with a recommendation. The second is a formal escalation when time is short. The third works when you need a written record of the decision.
Option 1: Early Notice With a Recommendation
Subject line options:
- Deadline Conflict: [Project A] and [Project B] Both Due [Timeframe]
- Priority Decision Needed: Two Deliverables Colliding on [Date]
- Flagging a Scheduling Conflict – Need Your Call on Priority
Hi [Recipient Name],
Flagging a scheduling conflict early so we have time to adjust.
What's colliding:
Deliverable A: [Name], due [Date], for [Stakeholder or Client]
Deliverable B: [Name], due [Date], for [Stakeholder or Client]
Overlap: [Number] working days, from [Date] to [Date]
Effort required: [Estimate] hours for A, [estimate] hours for B
Dependency: [Anything blocking, e.g., waiting on input from X]
Both are currently committed, and doing both at full quality in that
window isn't realistic. I don't want to quietly let one slip without
your input.
My recommendation: prioritize [Deliverable A] and move [Deliverable B]
to [proposed new date]. Reasoning: [one or two sentences on impact,
stakeholder sensitivity, or downstream dependencies].
Alternatives if you'd rather not move the date:
1. Reduce scope on [Deliverable B] to [specific subset]
2. Bring in [Colleague Name] to take part of [Deliverable A]
3. Extend [Deliverable A] instead, if that's more flexible
Which option do you want me to take?
Thanks,
[Your Name]
[Your Title]
[Team or Department]Option 2: Urgent Escalation When Time Is Short
Subject line options:
- Urgent: Deadline Conflict on [Deliverable] – Decision Needed Today
- At Risk: Two Deadlines This Week – Need Priority Call
- Escalation: Cannot Deliver Both [A] and [B] by [Date]
Hi [Recipient Name],
I need a priority decision today on two deadlines that are now
colliding.
Deliverable A: [Name], due [Date]
Deliverable B: [Name], due [Date]
Days remaining: [Number]
Status: A is [percent] complete, B is [percent] complete
Without a call from you, here's what happens: [Deliverable B] slips
past its date, and [specific consequence: client escalation, missed
reporting cycle, blocked downstream work].
I can deliver one of these at full quality. I cannot deliver both.
My recommendation is [A or B], with [the other] moving to
[proposed date].
If you'd rather I attempt both, tell me which one accepts reduced
quality and I'll work to that standard.
Can we decide this today? A five-minute call is fine if that's faster.
Thanks,
[Your Name]
[Your Title]
[Team or Department]Option 3: Written Record After a Verbal Decision
Subject line options:
- Confirming Our Decision on [Deliverable A] and [Deliverable B]
- Summary: Priority Call on Overlapping Deadlines
- Recap and Next Steps – Deadline Conflict Resolution
Hi [Recipient Name],
Thanks for the call. Writing this up so we're aligned on the decision
and the new dates.
Agreed:
Priority: [Deliverable A] – remains on schedule for [Date]
Deferred: [Deliverable B] – moves to [New Date]
Scope change: [None / reduced to specific subset]
Support added: [Colleague Name] will take [specific piece]
Stakeholders to
notify: [Names or roles]
What I'll do next:
- Notify [Stakeholder] about the revised date by [Date]
- Send a revised task plan by [Date]
- Flag immediately if [Deliverable A] starts to slip as well
If anything above doesn't match your understanding, let me know and
I'll correct it.
Thanks,
[Your Name]
[Your Title]
[Team or Department]What To Do If You Don't Get a Response
Silence on a deadline conflict is dangerous because the clock keeps running. Treat no response as an unresolved risk, not as permission to choose for yourself.
- Follow up the same day if the deadline is within a week. Reply on the original thread with the decision restated in one line.
- Escalate one level up. If your manager is unavailable, copy their manager or the project's executive sponsor with the same information.
- Propose a default. State that without a decision by a specific time, you will proceed with your recommended priority. That converts silence into an implicit approval and gives you cover.
- Notify the affected stakeholder directly. If a client or internal partner is waiting, tell them a priority decision is pending. Do not let them discover the slip on the due date.
- Document the timeline. Keep the original email and every follow-up. If the conflict later becomes a performance question, the record settles it.
The default-proposal approach works especially well because it removes the ability to ignore the problem. Most managers respond quickly once inaction has a stated consequence.
Frequently Asked Questions
Q: How do I tell my manager about overlapping deadlines?
A: Send a short email as soon as you notice the conflict. Name both deliverables, their due dates, the overlap window, and your recommended priority, then ask for a decision.
Q: When should I inform my manager about a deadline conflict?
A: The same day you identify it. Two or more weeks out, you have options to present. Under a week, the email becomes an escalation and the available solutions shrink fast.
Q: What should I include in an email about conflicting deadlines?
A: Include both deliverable names, their due dates, the number of overlapping days, the effort each requires, the consequence of missing each one, and a recommended priority with a proposed new date for the deferred item.
Q: Should I apologize for having overlapping deadlines?
A: No. A brief acknowledgment is fine, but heavy apologizing implies you caused the conflict. Frame it as a scheduling risk that needs a priority decision.
Q: What if my manager does not respond to my deadline conflict email?
A: Follow up the same day if the deadline is close, escalate one level up if needed, and state that you will proceed with your recommended priority if no decision arrives by a specific time.