Turn your project plan into a living risk register. Automatically surface scope creep, timeline slippage, budget overruns, and resource gaps before they become crises.
You are a project risk analyst. Extract all risks, threats, and assumptions from the project plan below. For each risk, determine:
1. Risk description (one sentence, specific)
2. Category: scope creep, timeline slippage, budget overrun, resource constraint, or dependency failure
3. Probability (1-5, where 5 is almost certain)
4. Impact (1-5, where 5 is project-ending)
5. Risk score (probability × impact)
6. Assigned owner (who monitors this?)
7. Mitigation trigger (what signal tells us this risk is materializing?)
Project plan:
{{PROJECT_PLAN_TEXT}}
Output as a table sorted by risk score (highest first). Flag any risks with score ≥16 as critical. Include a one-line recommendation for each critical risk.1. Paste your project plan (Notion doc, Asana timeline, Gantt export, or narrative) into {{PROJECT_PLAN_TEXT}}. 2. Run the prompt. 3. Copy the output into a shared risk register (Google Sheet, Airtable, or your project tool). 4. Assign owners to each critical risk within 24 hours. 5. Set a weekly sync to review risks with score ≥16 and check mitigation triggers. 6. Re-run this prompt every sprint or after scope changes to catch new risks.
Project: Launch mobile app in Q2. Timeline: 12 weeks. Team: 1 iOS dev (contractor), 1 Android dev (full-time), 1 designer (part-time). Budget: $180k. Dependencies: API from partner team (not yet started). Key milestones: Alpha by week 6, beta by week 10, launch by week 12. Known constraints: Designer leaves in week 8. No QA resource allocated.
| Risk | Category | Prob | Impact | Score | Owner | Trigger | |------|----------|------|--------|-------|-------|----------| | Partner API delayed; blocks Android integration | Dependency | 4 | 5 | 20 | Tech Lead | API not in staging by week 5 | | Designer departure in week 8 leaves UI unfinished | Resource | 5 | 4 | 20 | PM | No design handoff doc by week 7 | | No QA resource; launch quality risk | Resource | 5 | 4 | 20 | PM | Testing starts week 10 with no tester | | Contractor iOS dev unavailable mid-project | Resource | 2 | 5 | 10 | Tech Lead | Dev misses 2+ standups | | Scope creep from stakeholder requests | Scope | 4 | 3 | 12 | PM | Feature requests after week 6 freeze | Critical risks (score ≥16): Recommend: (1) Confirm API timeline with partner this week. (2) Hire contract QA by week 4. (3) Document all design decisions by week 7.