Risk Assessment Document Writer

A prioritized risk register with mitigation strategies and an executive summary ready for stakeholder review.

Best For

•A PMO analyst documenting risk for a new system rollout uses it to produce a sorted risk register table that stakeholders can scan without reading a full narrative
•A compliance officer preparing for an audit uses the likelihood-times-impact matrix to justify why certain risks were flagged higher priority than others
•A project sponsor briefing leadership before kickoff uses the executive summary output to communicate the two risks needing immediate attention in three sentences

Prompt Template

Write a risk assessment document for [PROJECT_OR_INITIATIVE_NAME] at [COMPANY_NAME]. The initiative involves: [INITIATIVE_DESCRIPTION]. Identify and document risks across these categories: operational, financial, legal/compliance, reputational, and technical. For each risk: (1) give it a descriptive name, (2) write a 1–2 sentence description of the risk scenario, (3) assign a Likelihood score (Low/Medium/High), (4) assign an Impact score (Low/Medium/High), (5) calculate an overall Risk Level (using a standard likelihood × impact matrix), (6) describe the mitigation strategy, (7) name a Risk Owner. Present the risks in a table format sorted by Risk Level (highest first). After the table, write a 3–4 sentence executive summary that communicates the overall risk posture and the top two risks requiring immediate attention. Use this additional context to identify risks: [ADDITIONAL_CONTEXT].

Pro Tip

Provide the additional context field with details about who is actually running the initiative and any past incidents with similar projects, since the model's risk categories get sharper when it has a track record to reason from instead of a generic description.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

Risk: Third-party API rate limits during peak traffic. Category: Technical. Likelihood: Medium. Impact: High. Risk Level: High. Mitigation: implement request queuing and negotiate a higher rate limit tier before launch. Risk Owner: Platform Engineering Lead. Executive summary: Overall risk posture is moderate, with two risks requiring immediate attention, third-party API limits and incomplete data migration testing, both of which have clear owners and mitigation timelines already in motion.