Risk Assessment
Create a Risk Assessment tailored to your inputs.
Prompt template
You are an expert project risk analyst. Generate a comprehensive risk assessment for the following project.
Project Name: {{project_name}}
Project Type: {{project_type}}
Description: {{project_description}}
Team Size: {{team_size}}
Timeline: {{timeline}}
Known Concerns: {{known_concerns}}
Generate a structured risk assessment in markdown format with:
1. An **Executive Summary** (2-3 sentences summarizing overall risk profile and key recommendations)
2. A **Risk Register** table with columns: # | Risk | Likelihood (Low/Medium/High) | Impact (Low/Medium/High) | Priority (Low/Medium/High/Critical) | Mitigation Strategy
Include 5-8 risks relevant to this specific project type, description, and context. Consider:
- Technical risks
- Resource and personnel risks
- Timeline and schedule risks
- External dependency risks
- Budget and financial risks
- Stakeholder and communication risks
3. **Detailed Risk Analysis** for the top 3 risks (Likelihood, Impact, Early Warning Signs, Mitigation steps)
4. **Recommended Actions** with timeframes (Immediate, Short-term, Ongoing)
Format the output as clean markdown. Be specific to the project details provided, not generic. Reference the actual project name, type, and concerns in the analysis.Fill the 6 fields below to customize.
Customize before copy
Fill these — your prompt updates live.
Stays in your browser. Nothing sent anywhere — we don't run a server for this.
Using Gemini, Llama, Mistral or local LLMs? Copy the prompt and paste — no deep-link supported.
Example output
What the prompt produced when KLI ran it for a real case. Yours will vary by model and inputs.
# Risk Assessment Report
**Project:** Demo Project
**Date:** ${new Date().toISOString().split("T")[0]}
**Project Type:** Software Development
---
## Executive Summary
This risk assessment identifies 5 key risks for the project. The overall risk profile is **Medium**. Primary concerns include technical complexity, resource availability, and timeline constraints. Recommended immediate actions include establishing clear communication channels, defining scope boundaries, and setting up monitoring for critical dependencies.
---
## Risk Register
| # | Risk | Likelihood | Impact | Priority | Mitigation Strategy |
|---|------|-----------|--------|----------|---------------------|
| 1 | Scope creep due to unclear requirements | High | High | **Critical** | Define and freeze requirements in a signed-off PRD; use change request process for any additions |
| 2 | Key team member unavailability | Medium | High | **High** | Cross-train team members; document critical knowledge; maintain bus-factor > 1 |
| 3 | Third-party API dependency failure | Medium | Medium | **Medium** | Implement fallback mechanisms; monitor SLAs; have contingency vendors identified |
| 4 | Budget overrun due to underestimation | Low | High | **Medium** | Add 20% contingency buffer; weekly budget reviews; track burn rate against milestones |
| 5 | Security vulnerabilities in dependencies | Low | Medium | **Low** | Automated dependency scanning in CI/CD; regular security audits; keep dependencies updated |
---
You might also like
Budget Justification
Create a Budget Justification tailored to your inputs.
OperationsBusiness Continuity Plan
Create a Business Continuity Plan tailored to your inputs.
OperationsChange Management
Create a Change Management tailored to your inputs.
OperationsAppointment Letter
Generate a Appointment Letter tailored to your inputs.
HRBonus Justification
Generate a Bonus Justification tailored to your inputs.
HRAgency Agreement
🇮🇳Draft a Agency Agreement tailored to your inputs.
Legal & ContractsMade with KLI — extracted from real tools, shared free. krakelabsindia.com