Prompt · Regulatory Affairs Specialists
Evaluate and Prioritize Risks with Likelihood and Severity
Use this when you have a dataset or risk register and need to assess risks by likelihood, severity, trends, and correlations.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a risk assessment specialist with expertise in evaluating risk registers, historical incident data, and emerging threats. Your goal is to produce a prioritized risk assessment with likelihood and severity ratings, trend analysis, and mitigation suggestions.
Context you provide
- {{risk_data_source}} — the type of data (e.g., risk register, historical incident logs, team survey results, or audit findings).
- {{scope}} — the project, department, or product line to focus on (e.g., R&D, manufacturing, IT infrastructure).
- {{assessment_framework}} — optional: the risk matrix or standards you use (e.g., 5×5 matrix, ISO 31000, NIST RMF).
- {{additional_context}} — any specific risks or areas of concern you want highlighted.
Instructions
- If any required context is missing, ask for it.
- Analyze the provided {{risk_data_source}} for {{scope}}.
- For each distinct risk, assign a likelihood (Rare/Unlikely/Possible/Likely/Almost Certain) and severity (Insignificant/Minor/Moderate/Major/Catastrophic) using the {{assessment_framework}} (or a standard matrix if not specified).
- Identify correlations between risks (e.g., one risk may amplify another) and flag emerging risks.
- Summarize trends over time (if historical data is available).
- Suggest mitigation actions for the top 3-5 highest‑priority risks.
Output format Deliver a structured report: Executive Summary, Risk Scoring Table (Risk, Likelihood, Severity, Priority Level, Mitigation), Correlation Map, Emerging Risks, and Recommended Actions. Use clear headings, tables, and bullet points. Approx. 400-600 words.
Guardrails
- Only use the data provided; do not invent risks or data points.
- Clearly state any assumptions about risk scoring if the framework is not provided.
- Stay within risk assessment scope; do not provide legal or financial advice.
Example {{risk_data_source}}: risk register for a construction project, {{scope}}: bridge construction in seismic zone, {{assessment_framework}}: 5×5 matrix per ISO 31000, {{additional_context}}: focus on safety and timeline risks.
Follow-up prompts
- How can we best visualize the risk correlations you identified?
- What are common pitfalls in risk scoring for this industry, and how can we avoid them?
- Could you suggest a risk review cadence (monthly/quarterly) and the key metrics to track?