How do I explain that a requested turnaround is unrealistic?
Quick answer
State that you can’t complete the full request by the proposed deadline, briefly name the work or dependency that affects timing, and give a realistic alternative. If useful, offer a smaller version that can be ready sooner. Be specific about what each option includes, ask which they prefer, and avoid promising a date until you have allowed time for the work and any review.
The question, the details, the next step.
How do I tell someone their requested turnaround isn’t realistic without sounding unhelpful or making excuses?
Be direct about the constraint, then make it easy to decide what happens next. A useful response has four parts:
- Acknowledge the requested deadline.
- Say clearly whether the full work can be ready by then.
- Explain the main work or dependency affecting the timing, in one sentence.
- Offer a realistic date, a smaller deliverable, or both.
Keep the explanation factual rather than apologetic or defensive. For example, “I can’t complete the full review by Thursday because it includes checking the draft and incorporating feedback. I can send the key issues by Thursday, or the complete review by Monday.” Use dates and deliverables that fit your actual workload.
What if I’m not sure how long the full job will take yet?
Don’t guess just to give an immediate answer. First identify what remains, what information or decisions you’re waiting for, and whether another person needs to review the work. Then give a time to confirm the schedule, or provide a provisional estimate that you clearly label as such.
For example, assuming you still need to review the scope and check one dependency, you might write: “I can’t confirm a delivery date until I’ve checked the remaining requirements. I’ll review those today and send you a realistic schedule by [time].” That is more useful than agreeing to a deadline you haven’t assessed. If the requester needs an answer now, give the clearest bounded option you can support, such as offering an initial section by a specific date rather than claiming the whole task will be done.
How do I explain the work involved without making the message too long?
Name only the steps that materially affect the deadline. A short, concrete explanation helps the other person see why the proposed timing and the full request don’t fit together. You don’t need to list every small task or defend your schedule.
For example, assuming the request is to prepare a polished presentation from notes, the relevant work might be organizing the material, drafting the slides, and checking the final version. You could say: “The full presentation needs the material organized, slides drafted, and a review pass, so I can’t send a finished version tomorrow.” If the scope is already clear, avoid reopening it in your explanation. The point is to make the constraint understandable, not to persuade the requester that you are busy.
Can you give me a template that offers a smaller option without making it sound like I’m lowering the quality?
Yes. Make the difference about scope, not quality: say what the quicker version includes and what it leaves for a later delivery. For example, assuming the work is a review of a long document, a first-pass list of the most important issues could be a smaller deliverable than a complete review with detailed comments. Don’t describe a partial version as complete if it isn’t.
Copy and adapt this:
“Thanks for sharing the requested timing. I can’t complete [full deliverable] by [requested deadline] because it requires [brief, relevant work or dependency]. I can deliver [realistic full deliverable] by [realistic date]. If you need something sooner, I can send [smaller, clearly defined deliverable] by [earlier date], with [what remains or will follow] due by [later date]. Which option would be more useful?
If neither option meets your need, let me know the must-have outcome and I can suggest a different scope.”
Before sending, replace every bracket with a specific, supportable detail. If you don’t yet know the date, say when you’ll confirm it rather than inserting a guess.
A practical checklist
State plainly whether the complete request fits the requested deadline.
Name the main task, review, or dependency affecting timing.
Offer a realistic date for the full deliverable, if you can support it.
Define any faster, smaller option and what it excludes or defers.
Ask which option the requester prefers, or when you will confirm timing.
A few more useful answers
Should I apologize for not meeting the requested deadline?
A brief, courteous acknowledgment is fine, but don’t let an apology replace a clear answer. State what you can deliver and when.
What if the requester says everything is urgent?
Ask which outcome is most important by the earlier date, then offer a defined smaller deliverable if one is feasible. Don’t promise the full scope by a date you can’t support.
How specific should my explanation of the work be?
Include the one or two steps or dependencies that most affect timing. Leave out a long task-by-task defense unless the requester needs that detail to choose between options.