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

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

Example for: mobile app project adding multi-language localization three weeks before launch

1. Scope Impact Summary
  • Deliverables Added: String extraction across 42 app screens, third-party translation integration, right-to-left layout testing, and multi-currency UI adjustments.
  • Primary Risks: Regression in checkout flow, localization text breaking fixed button containers, and App Store review delays.
2. Trade-Off Options
  • Option A: Extend Timeline

    • Approach: Build and test full multi-language capabilities before initial release.
    • Timeline Impact: Pushes hard launch out by 4 weeks.
    • Cost Impact: Neutral to existing contractor burn, but adds 80 billable developer hours.
    • What Gets Sacrificed: The scheduled Q3 marketing campaign launch date.
  • Option B: Add Budget via Dedicated Contractor

    • Approach: Bring in an external localization specialist to work in a parallel branch.
    • Timeline Impact: Pushes launch by 1 week for merge and final QA.
    • Cost Impact: Direct agency cost increase of approximately $14,000.
    • What Gets Sacrificed: Margin target on the primary contract.
  • Option C: Phase for Post-Launch (Recommended)

    • Approach: Launch initial release in primary language on schedule; release localized update in v1.1 four weeks later.
    • Timeline Impact: Zero delay to initial release date.
    • Cost Impact: Zero change to the initial project budget.
    • What Gets Sacrificed: Immediate multi-language availability on day one.
3. Recommendation

Choose Option C. Launching core functionality on schedule protects committed media spend and provides real-world telemetry, while allowing localized strings to be audited safely in a staged release.

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

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.

Keep exploring

More in Project Management
Project Management

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.

Project Management

Draft a formal project charter

Create a clear, authoritative project charter defining scope boundaries, measurable success metrics, and sponsor decision rights.

Project Management

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.

Project Management

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.