Push Back on an Unrealistic Deadline with a Clear Trade-Off Menu

Get a firm, apology-free email that declines an unworkable deadline and offers three costed options: cut scope, add people, or move the date.

You getSubject line, email body and trade-off table

Prompt

Prompt
Act as a senior project lead who writes firm, calm emails to stakeholders.

Your job: help me push back on a deadline I don't think my team can meet. Offer clear trade-offs instead of a flat no.

Before drafting, ask me these 3 questions in one message, then wait for my answers:
1. What is the work, what deadline was set, and who set it (their role)?
2. What date can you realistically hit, and what causes the gap (people, dependencies, testing, other priorities)?
3. Which parts matter most to the stakeholder, and what could be cut, delayed or staffed differently?

Rules:
- Offer exactly three options: cut scope, add resource, or move the date. Each states what they get, by when, and what it costs.
- No apologizing or hedging: never use "sorry," "unfortunately," "I'm afraid," "just," or "I hope this is okay."
- State the risk of keeping the original deadline in one sentence with a concrete consequence.
- Keep the email body under 200 words and the subject line under 9 words.
- End with a direct ask and a date for their decision.

Output format:
1. Subject line
2. Email body
3. Trade-off table: Option | What you get | Delivery date | Cost
4. One line on what to say if they reject all three options

Flag any numbers or dates you assumed that I didn't give you.

Example output

At a glanceThree options for the March 14 deadlineCut scope, add people, or move the date
ItemDelivery dateCost
Cut scopeMarch 14 (SSO April 4)Password login for 3 weeks
Add resourceMarch 212 Billing engineers; redesign slips to May
Move the dateApril 43-week delay to full launch

Example for: an engineering lead asked by the VP of Sales to ship a customer portal with SSO and usage reports by March 14; realistic date is April 4.

1. Subject line
Portal launch: three options for March 14

2. Email body

Hi Dana,

We can't ship the full customer portal (SSO plus usage reports) by March 14 at the quality your enterprise accounts expect. Our honest estimate for everything is April 4, because SSO depends on the identity team's API, which lands March 7.

If we hold March 14 for the full scope, we'd skip security testing on SSO, and a login failure at a client like Northfield would reach their IT team in week one.

Here are three ways forward:

  1. Cut scope: Launch portal with usage reports on March 14. SSO follows April 4. Clients log in with email and password for three weeks.
  2. Add resource: Lend us two engineers from the Billing team for three weeks. Full portal on March 21. Billing's invoice redesign slips to May.
  3. Move the date: Full portal on April 4 with no other changes.

I recommend option 1, since reports are what your pilot clients asked for first.

Can you choose by Wednesday, March 5, so we can lock the sprint plan?

Thanks,
Marcus

3. Trade-off table

OptionWhat you getDelivery dateCost
Cut scopePortal + usage reportsMarch 14 (SSO April 4)Clients use password login for 3 weeks
Add resourceFull portalMarch 212 Billing engineers for 3 weeks; invoice redesign slips to May
Move the dateFull portalApril 43-week delay to the full launch

4. If they reject all three
"Then let's get 20 minutes with you, me and the identity team lead this week. The SSO dependency is the constraint, and only they can move it."

Assumptions flagged: I assumed the Billing engineers are free to lend and that the invoice redesign would slip to May. Confirm both with the Billing lead before sending.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • A fixed three-option menu turns a no into a decision the stakeholder controls, with the cost of each option stated up front.
  • Banning words like "sorry" and "unfortunately" keeps the tone confident, so the pushback reads as a plan rather than an excuse.
  • Asking about the cause of the gap and what's flexible first means the options are grounded in real constraints, not made-up ones.

Use when a manager or client sets a date your team can't hit. Have the real deadline, your honest estimate, and what's flexible. Works in ChatGPT, Claude or Gemini.

Common edits

  • Ask for a shorter Slack or Teams version with the three options as a numbered list.
  • Change the tone for an external client by adding a line about protecting their launch quality.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Email