Extract and structure project risks from your plan into a prioritized risk register. Identifies threats to scope, timeline, budget, and resources.
You are a project risk analyst. Review the following project plan and create a comprehensive risk register.
Project Plan:
{{PROJECT_PLAN}}
Project Context:
- Timeline: {{PROJECT_TIMELINE}}
- Budget: {{PROJECT_BUDGET}}
- Team size: {{TEAM_SIZE}}
- Key dependencies: {{KEY_DEPENDENCIES}}
Instructions:
1. Identify at least 8-12 distinct risks across these categories: scope creep, timeline delays, budget overruns, resource constraints, technical/external factors, and stakeholder alignment.
2. For each risk, assess:
- Likelihood (1=rare, 5=almost certain)
- Impact (1=negligible, 5=project failure)
- Risk Score (likelihood × impact)
3. Assign a risk owner (role, not name).
4. Provide a specific, actionable mitigation strategy for each risk.
5. Flag any risks with a score of 15+ as critical.
6. Format as a table with columns: Risk ID | Risk Description | Category | Likelihood | Impact | Score | Owner | Mitigation Strategy | Status (New/Active/Mitigated).
Prioritize by risk score (highest first). Be specific to this project—avoid generic risks.1. Gather your project plan document and key project parameters (timeline, budget, team, dependencies). 2. Fill in all five placeholders with accurate, specific information. 3. Run the prompt in your AI tool. 4. Review the output risk register for accuracy and relevance to your context. 5. Assign owners and schedule mitigation planning sessions for critical risks (score 15+). 6. Update the register monthly or when project scope changes.
Project Plan: Build internal analytics dashboard for sales team. Scope: 5 dashboards, 3 data sources, real-time updates. Phases: discovery (2 weeks), design (3 weeks), build (8 weeks), testing (2 weeks), launch (1 week). Timeline: 16 weeks, must launch by end of Q2 Budget: $120K Team Size: 1 PM, 2 backend engineers, 1 frontend engineer, 1 QA (one engineer is new to the codebase) Key Dependencies: Data warehouse team (owns ETL), Finance (approves spend), Sales leadership (final sign-off on requirements)
Risk Register (excerpt): | Risk ID | Risk Description | Category | Likelihood | Impact | Score | Owner | Mitigation Strategy | Status | |---------|------------------|----------|------------|--------|-------|-------|---------------------|--------| | R001 | Sales requirements unclear; scope creep likely | Scope | 4 | 5 | 20 | PM | Weekly requirement review meetings with Sales; document sign-off by week 2 | New | | R002 | New engineer ramp-up delays backend work | Resource | 4 | 4 | 16 | Tech Lead | Pair new engineer with senior engineer; allocate 20% buffer in sprint planning | New | | R003 | Data warehouse team delays ETL delivery | External | 3 | 4 | 12 | PM | Establish weekly sync with DW team; define data contracts by week 3 | New | | R004 | Real-time update performance issues discovered late | Technical | 3 | 4 | 12 | Backend Lead | Prototype real-time architecture in week 3; load test by week 8 | New | | R005 | Q2 deadline conflicts with other company priorities | External | 2 | 5 | 10 | PM | Secure executive sponsorship and resource commitment in kickoff | New |