Write a Status Update for Your Boss When Your Project Is Behind Schedule

You get a short, decision-ready update that leads with the new date and its impact, explains the cause in one line, and offers two costed recovery options plus a recommendation.

Prompt

Prompt
You are a senior project manager who writes short, decision-ready updates for busy executives.

Your job: write a status update to my manager about a project that is behind schedule. First ask me these questions in one message, then wait for my answers:
1. What is the project, the original deadline, and the realistic new date?
2. What caused the delay, and what does the slip affect (customers, revenue, other teams)?
3. What could speed recovery (extra people, budget, scope cuts, overtime)?
4. How does my manager prefer updates (email, Slack, bullets) and by when do I need a decision?

Rules:
- The first sentence states the new date and the main impact. No preamble and no apology paragraph.
- State the cause in one sentence, owning it plainly without blaming individuals.
- Give exactly two recovery options, each with its cost in time, money or scope, and the risk if it fails.
- Recommend one option and give the reason in one sentence.
- Keep the update under 200 words. Use only facts I give you and label any figure you estimated as an estimate.

Output format:
Subject line
1. New date and impact (1-2 sentences)
2. Cause (1 sentence)
3. Options table: Option | New date | Cost | Risk
4. Recommendation (1-2 sentences)
5. Decision needed (by when and what exactly)

After the update, add one line listing any assumptions you made or information still missing.

Example output

At a glanceTwo recovery options for the portal migrationOption B recommended; decision needed by Friday, March 7
ItemA. Add contract engineerB. Ship without SSO
New dateMarch 28March 21
CostAbout $18,000 (estimate)No added spend; SSO moves to May
Risk3-4 day onboarding; may still land near April 4Around 40 enterprise accounts keep separate logins for 6 weeks

Example for: a product lead whose customer portal migration will miss its March 14 launch; manager prefers email.

Subject: Portal migration: new launch date April 4, decision needed by Friday

1. New date and impact

The customer portal migration will launch April 4 instead of March 14. The 3-week slip delays the planned shutdown of the old portal, adding about $9,000 in extra hosting costs (estimate), and pushes the support team's training by two weeks.

2. Cause

During load testing we found the billing vendor's API rate limits block bulk account transfers, and I did not plan for that check early enough.

3. Options
OptionNew dateCostRisk
A. Add one contract integration engineer for 3 weeksMarch 28About $18,000 (estimate)Onboarding takes 3-4 days; if the vendor fix is slower, we still land near April 4
B. Ship without single sign-on and add it in phase 2March 21No added spend; SSO moves to MayAround 40 enterprise accounts keep separate logins for 6 weeks and may raise tickets
4. Recommendation

I recommend Option B. It gets most customers onto the new portal fastest at no extra cost, and the SSO gap affects a small, reachable group we can notify in advance.

5. Decision needed

Please confirm an option by Friday, March 7 so I can brief the support team and, if you choose B, send the enterprise notice on Monday.


Assumptions and gaps: the $18,000 contractor rate and the $9,000 hosting figure are estimates; I have not yet confirmed with Sales whether any enterprise contract requires SSO by a set date.

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

Tips and common edits

Why this works

  • Leading with the new date and impact gives the reader the bad news and its stakes in one glance, which builds trust.
  • Limiting the cause to one sentence stops the update from turning into excuses or blame.
  • Two options with cost and risk in a table turn the email into a quick decision instead of a long thread.

Use this as soon as you know a deadline will slip, before your boss hears it elsewhere. Have the old and new dates, the cause, and recovery ideas ready. Works in ChatGPT, Claude or Gemini.

Common edits

  • Ask for a three-line Slack version alongside the email.
  • Change to three options if your boss likes to see a 'do nothing' baseline.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Career & Job Search