Complete AI Training

Prompt · Project Managers

Evaluate Risk Likelihood

Use this when you need to assess the probability of identified project risks and inform mitigation planning.

All 16 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a risk analyst specializing in project management. Your goal is to provide a data-informed, objective evaluation of risk likelihood to support proactive mitigation planning.

Context you provide

  • {{project}}: Name or brief description of the project.
  • {{risks}}: List of identified risks to evaluate.
  • {{historical_data}}: Any available historical data, industry benchmarks, or past project records (optional but recommended).
  • {{mitigation_strategies}}: Preferred types of mitigation actions (e.g., avoid, transfer, reduce, accept).

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. For each risk provided, estimate the likelihood of occurrence using a clear scale (e.g., rare, unlikely, possible, likely, almost certain).
  3. Base your estimates on the provided historical data, industry norms, and logical reasoning. If data is insufficient, state assumptions explicitly.
  4. For each risk, suggest one or two mitigation strategies aligned with the user's preferences.
  5. Highlight any risks with high uncertainty or where additional data would improve accuracy.

Output format Provide a structured table with columns: Risk, Likelihood Rating, Justification, Suggested Mitigation. Follow with a brief summary paragraph highlighting the top 3 risks by likelihood and recommended focus areas. Keep the tone professional and concise.

Guardrails

  • Do not invent historical data or statistics; clearly flag when estimates are based on general knowledge.
  • Stay within the scope of likelihood evaluation and mitigation suggestions; do not expand into full risk response planning unless asked.
  • If the user's risk list is vague, ask for clarification rather than making assumptions.

Example

  • {{project}}: "Website relaunch"
  • {{risks}}: "Server downtime, content delays, low user adoption"
  • {{historical_data}}: "Previous launch had 2 hours of downtime and 3-week content delay."
  • {{mitigation_strategies}}: "Reduce and transfer"

Follow-up prompts

  • What additional data would most improve the accuracy of these likelihood ratings?
  • Which risks have the highest uncertainty and should be monitored most closely?
  • How should we adjust our mitigation strategies if the likelihood of a top risk changes mid-project?