Analyze timeline and budget trade-offs for scope requests
Turn vague stakeholder feature requests into clear trade-off scenarios. Use this when clients or leaders request additions without considering cost or delay.
You getScope Impact Summary, trade-Off Options and recommendation
Prompt
Act as a senior technical project director. Analyze the scope change request against the current project baseline provided below.
Rules:
- Break down the request into concrete design, development, and testing implications.
- Provide three realistic compromise options: budget increase, schedule extension, or de-scoping existing work.
- State all key assumptions plainly so risk factors are visible.
- Keep business language practical, objective, and neutral.
Output format:
1. Scope Impact Summary (deliverables added and primary risks)
2. Trade-Off Options (3 distinct options structured as: Approach, Timeline Impact, Cost Impact, What Gets Sacrificed)
3. Recommendation (1 paragraph advising the most balanced path forward)
My baseline details and scope request are below:Example output
Paste your current deadline, budget constraints, and the new scope request into Claude, ChatGPT, or Gemini. As a follow-up, ask the model to draft a concise email summarizing the options to send directly to your project sponsor.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Design a client training plan for project launch
Build a structured end-user and administrator training agenda tailored to user roles. Use this two to four weeks before launching a new system or process.
Diplomatic pushback against scope creep
Draft a polite, professional response that acknowledges an out-of-scope request, explains project tradeoffs, and offers clear paths forward.
Draft a formal project charter
Create a clear, authoritative project charter defining scope boundaries, measurable success metrics, and sponsor decision rights.
Turn a statement of work into a WBS
Convert complex, unstructured contract terms into a phased work breakdown structure with clear milestones and acceptance criteria.
Write a post-kickoff scope alignment email
Draft a clear, polite recap email to a client immediately after a kickoff call. Establishes agreed deliverables, out-of-scope boundaries, and upcoming approvals.
Build a realistic buffer strategy for uncertainty
Calculate and place project buffers based on risk drivers rather than arbitrary task padding, protecting your schedule without inflating delivery dates.