When deadlines compete, make the work, dependencies and tradeoffs visible early. Do not promise every request without checking capacity or silently choose a priority that other people expect to control. A useful response identifies the conflict, proposes realistic options and seeks the appropriate decision, while keeping agreed commitments and changing estimates distinct.
A practical approach to the situation
List the deliverables, requested dates, owners and dependencies. Estimate the remaining work at a level useful for the decision, including review and handoff time. Identify which dates are fixed by an external event and which are preferences or negotiable requests. Check the consequences of delay rather than ranking work only by who asked most recently.
Where you have authority, choose priorities using the agreed criteria. Where requests conflict across owners, explain the tradeoff and ask the appropriate manager or decision owner to resolve it. Offer options such as reducing scope, changing sequence or moving a date, with their effects. Do not hide quality or safety checks inside an optimistic plan that assumes everything will go perfectly.
| Area | Useful approach | What to check |
|---|---|---|
| Commitment | Identify the deliverable, owner and actual due date | Separate agreed deadlines from requested preferences |
| Dependency | Show inputs, review and handoff requirements | Do not estimate only your own production time |
| Tradeoff | Offer options with effects on scope, timing or quality | Seek a decision when priorities exceed your authority |
A fictional workplace or interview example
Fictional example: an assistant has a report due for a morning meeting and an urgent request to reformat a presentation. She identifies that both require the same reviewer’s time. She explains the remaining work and asks whether the presentation can use the existing format or move to the afternoon.
The manager chooses to preserve the report deadline and narrow the presentation changes. The assistant records the decision and updates both requesters. She does not simply work on the loudest request and let the other deadline fail without warning. The example shows prioritisation as a shared decision where authority and consequences matter.
Commitment
Show: Identify the deliverable, owner and actual due date
Check: Separate agreed deadlines from requested preferences
Dependency
Show: Show inputs, review and handoff requirements
Check: Do not estimate only your own production time
Tradeoff
Show: Offer options with effects on scope, timing or quality
Check: Seek a decision when priorities exceed your authority
Apply the process to your own material
- Map: List competing work, deadlines, dependencies and the consequences of delay.
- Assess: Estimate realistic remaining effort and identify the conflict.
- Propose: Offer bounded options and ask the appropriate owner to choose when needed.
- Confirm: Record the agreed sequence and communicate changes to affected people.
Practise with a genuine experience you can discuss appropriately, or use an explicitly fictional scenario. Ask a partner to describe what they understood, including the decision or next action. Compare their interpretation with your intention and revise the part that caused confusion. Keep facts, assumptions and proposed actions distinct. If the situation involves a real employer, follow its assessment instructions or workplace processes rather than treating a practice example as permission to ignore them.
- Map
List competing work, deadlines, dependencies and the consequences of delay.
- Assess
Estimate realistic remaining effort and identify the conflict.
- Propose
Offer bounded options and ask the appropriate owner to choose when needed.
- Confirm
Record the agreed sequence and communicate changes to affected people.
Use the sequence as a guide, then adapt it to the actual question, people and constraints. Clear communication should make the next decision easier.
Check the result and the next action
Confirm the agreed priority and communicate material changes to affected people. Review the plan when a dependency changes rather than waiting until the original estimate becomes impossible. Keep updates factual and specific. A clear priority decision may still involve an unwelcome tradeoff, but it is more useful than pretending all commitments remain achievable when the evidence says otherwise.
A closer check that improves the approach
Distinguish a deadline from a dependency date. A final deliverable may be due Friday, but an input or review might be needed earlier for that commitment to remain realistic. Make those intermediate dates visible and explain their purpose. Otherwise a request can appear on schedule until the moment it becomes impossible. This is particularly important when several tasks share a reviewer or system. A plan that assigns only your own work may hide the real constraint. Use the dependency view to ask for a timely decision, not to blame another person after the final deadline is missed.
Common questions
Should I always do the most urgent request first?
Not automatically. Clarify what makes it urgent, who owns the priority and what other commitments would be affected. A recent or emphatic request may not be the most consequential one. Use agreed criteria and escalate conflicts appropriately rather than allowing the loudest message to determine the entire work sequence.
How do I say that two deadlines cannot both be met?
State the deliverables, remaining work and shared constraint plainly, then offer realistic options. Avoid a vague refusal or an unsupported promise. Explain the effect of each option and identify who needs to decide. Early factual communication gives the team more choices than waiting until one commitment is already missed.
Can I change a deadline myself?
Only within your authority and the team’s agreements. If other people rely on the date, communicate and obtain the appropriate decision before treating it as changed. Distinguish your revised estimate from an approved deadline. A private adjustment in your task list does not update the expectations of everyone affected.
What should an effort estimate include?
Include the work needed to produce, check, review and hand off the deliverable, along with important dependencies. State uncertainty where it matters. An estimate based only on ideal uninterrupted production time may be misleading. Use a level of detail that supports the priority decision without pretending the forecast is more precise than the evidence allows.
Is reducing scope a legitimate option?
Yes, when the reduced deliverable still serves an agreed purpose and the decision owner accepts the tradeoff. Explain what will be included, deferred and affected. Do not silently remove required checks or critical functionality to claim the deadline was met. A smaller agreed outcome is different from an incomplete deliverable presented as complete.
How early should I communicate a likely delay?
Communicate when the evidence suggests a material risk and someone could act on the information. Do not wait for certainty if waiting removes useful options. Explain the basis, uncertainty and next update. At the same time, avoid reporting every minor fluctuation as a crisis before assessing its actual effect on the commitment.
What if several managers disagree on priorities?
Make the conflict visible through the appropriate reporting or escalation route, with the tasks and consequences clearly described. Do not silently promise incompatible outcomes to each person. Ask for a coordinated decision and record it. The goal is shared prioritisation, not making yourself the unofficial owner of decisions beyond your authority.
How do I prevent the same conflict recurring?
Review what created the collision: unclear ownership, late requests, missing review time or unrealistic assumptions. Propose a proportionate process improvement with evidence. Do not assume a personal productivity trick can solve every structural problem. A clearer intake or priority agreement may be more useful than simply trying to work faster.
Sources and further reading
Reviewed 7 November 2026. Examples and exercises are original editorial guidance. University, employer and professional guidance reflects its own context; actual assessment instructions and workplace processes take priority.
Resume & Workplace Desk
MP Job Hub’s organisational byline for presenting genuine work and communicating clearly in professional settings.
Resumes · Portfolio evidence · Interviews · Workplace communication
View profile →Read our research process or request a correction.
