Goal
Tell the audience the bad news first, show a credible plan, and leave the meeting with the decisions the plan needs.
Inputs
- Project and audience: [e.g. app rebuild, presenting to the client's leadership team]
- Original date and new proposed date: [dates]
- What slipped and why: [causes, with dates and evidence]
- What is done, in progress and not started: [list or percentages per workstream]
- Recovery options considered: [e.g. add two developers, cut scope, phase the release]
- Decisions or support needed: [e.g. approve phased release, extra budget, faster sign-offs]
Steps
- Put the delay, the new date and the main reason on the first content slide.
- Separate causes inside the team's control from causes outside it, without blame.
- Compare the recovery options and recommend one.
- Give the new date a confidence level and say what would move it.
Output format
- Slide 1: headline status, original date, new date, one-line reason.
- Slide 2: | Cause | Impact in days | In our control? | What we changed |
- Slide 3: timeline, original against revised, with milestones.
- Slide 4: progress by workstream.
- Slide 5: recovery options in a table with cost, time saved and risk; the recommended one marked.
- Slide 6: top risks to the new date and early warning signs.
- Slide 7: decisions requested, each with a deadline.
- Speaker notes for slides 1 and 7, word for word.
Check before answering
- The delay is stated plainly on slide 1, not softened or moved later.
- Every date and number comes from the inputs.
- No individual is named as the cause.
- The new date is not promised with more confidence than the plan supports.






