# Email: Request to Approve Scope Cut — Launch Timeline at Risk

---

**Subject:** Action Needed by Friday: Approve Scope Adjustment to Hold Launch Timeline

**From:** [Your Name], [Your Title]
**To:** [Exec Stakeholder Group]
**CC:** [Program Manager], [Engineering Lead]
**Date:** [Current Date]

---

**TL;DR:** Our launch is slipping two weeks due to upstream dependency delays outside our control. To protect the revised timeline and avoid further risk, I'm recommending we cut Feature B from the initial release. I need your approval by end of day Friday.

---

## Situation

During our integration milestone this week, we identified that two critical external dependencies (from [Team/Vendor X]) are running approximately two weeks behind their committed delivery dates. This delay directly blocks our launch-readiness path.

We have confirmed with the dependency owners that there is no realistic way to accelerate their delivery. The delay is structural, not resourcing-related.

## Impact

Without intervention, our launch date shifts from **[Original Date]** to **[Original Date + 2 weeks]**. Letting the timeline slip further carries additional downstream consequences:

- **Revenue impact:** Delays alignment with [sales cycle / partner commitment / seasonal window].
- **Team cost:** Extended crunch and context-switching across engineering and go-to-market teams.
- **Credibility risk:** We have already communicated the original date to [customers / partners / board].

## Recommendation

**Cut Feature B from the v1 launch scope.** Ship Feature A and Feature C on the revised date of **[Original Date + 2 weeks]**, and move Feature B to a fast-follow release targeted for **[Date, ~3–4 weeks post-launch]**.

Here is why this is the right trade-off:

| Factor | Feature B In | Feature B Out (Recommended) |
|---|---|---|
| Launch date | Slips 4+ weeks (high uncertainty) | Holds at +2 weeks (high confidence) |
| Revenue exposure | Significant; misses [window] | Contained; core value prop ships on time |
| Customer impact | Low incremental — Feature B affects ~15% of initial users | Minimal; addressed in fast-follow |
| Engineering risk | Compressed schedule, integration unknowns | Clean critical path, reduced defect risk |

Feature B is valuable, but it is not load-bearing for launch. Our early-access feedback and presales conversations confirm that Features A and C are the primary drivers of adoption and initial revenue.

## What I Need From You

**Approve the removal of Feature B from v1 scope by end of day Friday, [Date].**

This allows us to:
1. Lock the revised launch plan by Monday.
2. Communicate updated scope to customers and partners next week with a clear, confident message.
3. Reallocate Feature B engineering capacity to launch hardening and quality.

If there are concerns or constraints I'm not seeing, I want to hear them before Friday so we can factor them in.

## What Happens if We Don't Decide by Friday

If we delay this decision past Friday, we lose the ability to hold the +2 week timeline. Every day of indecision adds roughly a day of slip, because the team cannot parallelize work without a locked scope. We risk turning a manageable two-week delay into a month-plus delay with compounding credibility costs.

## Next Steps

- **By Friday:** I need a go / no-go on cutting Feature B.
- **Monday:** Revised launch plan distributed to all stakeholders.
- **Next week:** Customer and partner communications updated.
- **Post-launch:** Feature B fast-follow plan shared with timeline and owners.

I am available to discuss this in person or on a call anytime between now and Friday. If a 15-minute sync would help, I will send a calendar invite — just let me know.

Thank you for the quick turnaround on this. The team is ready to move as soon as we have alignment.

Best,
[Your Name]

---

## Notes on Approach

**Why this email is structured the way it is:**

1. **TL;DR up front.** Executives scan before they read. The first line tells them exactly what happened, what is proposed, and what they need to do.

2. **Situation before recommendation.** Establishes shared understanding of the facts without editorializing. The cause is external and structural — this framing avoids triggering blame dynamics.

3. **Concrete trade-off table.** Removes ambiguity from the decision. Executives can compare the two paths side by side without needing to reconstruct the logic themselves.

4. **Explicit ask with a deadline.** "Approve by Friday" is unambiguous. The email explains why the deadline matters (decision delay = timeline delay), which creates urgency without panic.

5. **Consequence of inaction.** This is the most important paragraph for getting a timely response. It reframes the decision from "should we cut scope?" to "the cost of not deciding is worse than either option."

6. **Tone: direct and calm.** No hedging language ("I think maybe we should consider..."), no catastrophizing ("this is a disaster"). Confident, factual, solution-oriented. This signals that the team has the situation under control and just needs a decision to proceed.

7. **Fast-follow commitment.** Acknowledging that Feature B matters and giving it a concrete future home makes the scope cut feel like a sequencing decision, not an abandonment. This reduces resistance.

8. **Offer to discuss.** Keeps the door open without making the email feel like the start of an endless thread. A short sync offer is more efficient than a long email chain.