Build a recovery plan for a project that is behind schedule
Turns a late project's facts into ranked recovery options (crash, fast-track, de-scope) with cost, risk, and a recommendation.
The prompt
Help me build a recovery plan for a project that is behind schedule.
Project and goal: [WHAT WE ARE DELIVERING and for whom]
Committed date vs. current forecast: [e.g. "June 30 committed, now forecasting Aug 15"]
Why we slipped: [CAUSES - be honest: late dependencies, underestimates, scope added, people lost]
Remaining work: [MILESTONES or major tasks still open, with estimates]
Levers I could pull: [extra budget, more people, overtime, vendor help, scope that could move to a later release]
Hard constraints: [fixed date? fixed budget? regulatory scope that cannot be cut?]
Analyze recovery using these options, and say which ones actually apply:
- Crashing - adding people or money to critical-path tasks (watch for onboarding drag and Brooks's law).
- Fast-tracking - running sequential tasks in parallel (note the rework risk).
- De-scoping - moving features to a later release (name what users lose).
- Re-sequencing - delivering the highest-value slice first.
- Moving the date - and what that costs.
Rules: do not invent estimates or costs - where I have not given a number, mark [ESTIMATE NEEDED]. Be realistic about how much time each option really buys back.
Return:
1. A one-paragraph diagnosis of the slip.
2. An options table: option | days recovered (range) | added cost | new risks | who must approve.
3. My recommended combination and the new forecast date with a confidence level.
4. What I must stop, start, and change this week.
5. A short message to my sponsor presenting the options and my recommendation.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- WHAT WE ARE DELIVERING and for whom
- e.g. "June 30 committed, now forecasting Aug 15"
- MILESTONES or major tasks still open, with estimates
- ESTIMATE NEEDED
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.
- Plan an event from start to finishTimelines, budgets, logistics, run-of-show, and checklists for work or personal events.
- Turn my project plan into an Excel task tracker with owners and dependenciesBreaks a project or plan into a task tracker with owners, dates, dependencies, and status columns you can paste into Excel.
- Turn my team's updates into a weekly RAG status reportPulls scattered team updates into a weekly status report with honest red-amber-green ratings, risks, and asks.