Workflow

The Capacity Pushback Builder

Say no to an unrealistic deadline or scope cut upward — without sounding defensive.

Published 2026-09-26  ·  Last updated 2026-09-26

TL;DR / The Direct Answer: Pushing back on your own reporting manager is different from giving downward feedback. Lead with what you can deliver, name the trade-off explicitly, and offer two options — not a flat refusal. The builder below drafts that email in the upward register Indian management culture expects.

The Tough Conversation Simulator covers feedback to your team; this workflow covers the opposite direction — when leadership adds scope or cuts headcount but keeps the deadline. Pair with Explaining Technical Delays when the ask is delivery-related.

Build your pushback prompt

Capacity Pushback Builder

Plain prompt (copy as-is)

Prompt — Copy into ChatGPT / Claude / Gemini
I need to push back on a new request from my reporting manager without damaging the relationship.

Write a 150-word email that:
- Acknowledges the priority
- States what my team can realistically deliver by the requested date
- Names one explicit trade-off if we take the new ask
- Offers two options and asks which they prefer

My situation:
[PASTE YOUR COMMITMENTS AND THE NEW ASK HERE]

A worked example

Placeholders only. Replace every bracket from your own notes, then remove the brackets before you send.

Sample input

  • The ask: an unrealistic deadline with unchanged scope
  • Addressee: direct reporting manager
  • Already committed: [Project] due [date]
  • New ask: [deliverable] by [date]
  • What still fits by that date: [the part you can deliver]

What good output looks like

  • One sentence that acknowledges [the priority].
  • By [date] we can deliver [the part that fits].
  • If we also take [the new ask], [Project] moves past [date].
  • Option A: start the new ask now and move [Project] to [later date].
  • Option B: keep [Project] on [date] and start the new ask on [later date].
  • Question: which option do you want?

Check before you send

  • The priority is acknowledged before the constraint.
  • The capacity line uses a date or quantity from your notes.
  • The trade-off names what slips.
  • There are two options.
  • The email ends by asking which option they prefer.
  • No project name you did not type in.

Do next: Draft pushback for one real scope or deadline conflict this week.

Read next: AI for Managers: Start Here

Avoid: Sending a flat “we cannot do this” without offering a trade-off.

K

Kalpit is a Bengaluru-based Consultant with 5 years of experience, currently working at one of India's largest organizations in an AI-first environment. He built LearnAI.how to help Indian professionals cut through the hype and actually use AI at work.



Become the most productive person in your office

Get one practical AI-at-work workflow when a new workflow ships — roughly monthly. No hype, no AI news. Unsubscribe anytime.