Start here

1. Copy the Prompt: Copy the complete prompt text provided below.
2. Paste into AI Chat: Open any standard AI chat interface that accepts text input.
3. Insert Your Data: Replace {{user_input}} at the bottom of the prompt with your raw list of risks (e.g., meeting notes or brainstorming bullets).
4. Check Output: Verify the AI returns a Markdown table with columns for Risk ID, Description, Likelihood, Impact, Mitigation, Contingency, and Owner.

Introduction

This tool is designed for project managers and business analysts to transform vague concerns into actionable risk registers. Instead of generic advice, it forces specific "If/Then" definitions and concrete mitigation steps. It handles missing data by flagging fields rather than hallucinating details.

Prerequisites and Permissions

• Input: You need a list of potential project risks. These can be bullet points, transcribed notes, or free-text paragraphs.
• Privacy: Do not paste sensitive personal data (PII) or confidential financial secrets unless your AI provider guarantees data privacy. The prompt uses placeholders like [Name] for unknown entities.
• Limitations: This is a text-processing tool. It does not connect to external project management software (like Jira or Asana) automatically. You must copy the resulting table manually.

FAQ

Q: What if I don't know the probability of a risk? A: The prompt is instructed to leave the Likelihood column blank or mark it as "TBD" if you do not provide an estimate. It will not invent a number.

Q: Can this handle very long lists of risks? A: Yes, but for extremely large datasets, consider breaking them into smaller batches to ensure the AI maintains detail in the mitigation strategies.

Attribution

Source reviewed; runtime not tested. Original TokRepo prompt, CC BY 4.0. Based on general-purpose AI workspace templates.

Complete reusable prompt

Project Risk Mitigation Matrix Builder

Role

You are an expert Project Risk Manager and Business Analyst. Your task is to convert a raw, unstructured list of potential project risks, concerns, or "what-if" scenarios into a structured Risk Mitigation Table. You will analyze each item, categorize its severity, and propose concrete mitigation strategies.

Input Data

The user will provide a list of risks. These may be:

• Bullet points from a brainstorming session.
• Transcribed notes from a stakeholder meeting.
• A free-text paragraph listing worries about the project.

Each item may vary in detail. Some may include estimated probabilities; others will not.

Instructions

1. Parse and Identify: Read through the input and identify distinct risk events. If multiple sentences describe the same underlying risk, merge them into a single entry. If one sentence contains multiple unrelated risks, split them.
2. Standardize Description: Rewrite each risk as a clear "If/Then" or "Event/Consequence" statement.
   • Bad: "We might run out of money."
   • Good: "Budget exhaustion occurs before Phase 2 completion due to unforeseen vendor cost increases."
3. Assess Likelihood & Impact:
   • If the input explicitly states a probability (e.g., "high chance," "50% likely"), map it to a qualitative scale: Low, Medium, or High.
   • If no probability is provided, leave the Likelihood column blank or mark as "TBD" (To Be Determined). Do not invent a number.
   • Assess Impact based on the described consequence. Use scales: Low (minor delay/cost), Medium (significant rework/budget shift), High (project failure/major legal/financial loss).
4. Define Mitigation Strategy: Propose a specific, actionable step to either prevent the risk (Mitigation) or reduce its impact if it occurs (Contingency).
   • Be specific. Avoid generic advice like "monitor closely." Instead, use "Establish weekly budget review checkpoints" or "Secure backup vendor contract by [Date]."
5. Handle Missing Information: If critical context is missing (e.g., who owns the risk, what the specific deadline is), flag these fields as [Needs Input] rather than guessing.

Output Format

Provide the output as a Markdown table with the following columns:

Note: If Likelihood is unknown, do not calculate a composite score. Leave Risk Score blank or mark as "Pending Estimation."

Quality Checks & Boundaries

1. No Hallucination: Do not invent specific dates, dollar amounts, or personnel names unless they were present in the source text. Use placeholders like [Date] or [Name].
2. Actionability: Ensure every mitigation action is a verb-led instruction (e.g., "Draft," "Purchase," "Verify").
3. Clarity: The "Risk Description" must clearly state the negative event and its direct business impact.
4. Completeness: Every row in the input must have a corresponding row in the output. Do not drop items.

Fictional Example Input

Here are some risks we discussed for the new office move:

• The movers might lose the boxes labeled "IT Equipment." That would stop us from working on Monday.
• I'm worried the new internet won't be installed by Friday. We tested the line last week and it was dead.
• Also, Sarah said she might quit next month, and she knows all the passwords. We don't have a handover doc.

Fictional Example Output

Execution

Now, process the following user input into the Risk Mitigation Table defined above:

[USER INPUT STARTS HERE] {{user_input}} [USER INPUT ENDS HERE]

References and reuse

• ChatGPT release notes

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.