# Project Risk Mitigation Matrix Builder

> Converts unstructured risk lists into a structured mitigation table with likelihood, impact, and action plans.

## Install

Copy the content below into your project:

# Project Risk Mitigation Matrix Builder

Converts unstructured risk lists into a structured mitigation table with likelihood, impact, and action plans.

## 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:

| Risk ID | Risk Description (Event -> Consequence) | Likelihood | Impact | Risk Score (H/M/L) | Mitigation Action (Prevent) | Contingency Plan (React) | Owner (Role) |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |

*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

| Risk ID | Risk Description (Event -> Consequence) | Likelihood | Impact | Risk Score | Mitigation Action (Prevent) | Contingency Plan (React) | Owner (Role) |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| R01 | IT equipment boxes are lost during transit -> Work stoppage on Day 1 | Medium | High | High | Require signed chain-of-custody logs for all IT crates; GPS track moving truck. | Activate cloud-based VM backup workstations; rent temporary laptops from local vendor. | Office Manager |
| R02 | Internet installation fails by Friday deadline -> No connectivity for staff | TBD | High | Pending | Schedule pre-installation test 48 hours prior; escalate ticket with ISP manager. | Deploy 4G/5G mobile hotspots as temporary bridge; allow remote work for Day 1. | IT Lead |
| R03 | Key employee (Sarah) departs without handover -> Loss of access credentials | Low | High | Medium | Initiate immediate password audit and force-reset procedure; document all admin accounts. | Engage external IT security firm for emergency access recovery; freeze affected accounts. | HR Director |

## 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](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 项目风险缓解矩阵构建器

将非结构化的风险列表转换为包含可能性、影响和行动计划的结构化缓解表格。

## 开始使用

1. **复制提示词**：复制下方提供的完整提示词文本。
2. **粘贴到 AI 聊天窗口**：打开任何接受文本输入的标准 AI 聊天界面。
3. **插入您的数据**：用您的原始风险列表（例如会议记录或头脑风暴要点）替换提示词底部的 `{{user_input}}`。
4. **检查结果**：验证 AI 是否返回了一个包含风险 ID、描述、可能性、影响、缓解措施、应急计划和负责人的 Markdown 表格。

## 介绍

此工具专为项目经理和业务分析师设计，旨在将模糊的担忧转化为可操作的风险登记册。它强制要求具体的“如果/那么”定义和具体的缓解步骤，而不是提供通用的建议。对于缺失的数据，它会标记字段而不是编造细节。

## 先决条件与权限

- **输入**：您需要一份潜在项目风险列表。这些可以是要点、转录笔记或自由文本段落。
- **隐私**：除非您的 AI 提供商保证数据隐私，否则请勿粘贴敏感的个人身份信息 (PII) 或机密财务秘密。提示词使用 `[姓名]` 等占位符表示未知实体。
- **限制**：这是一个文本处理工具。它不会自动连接到外部项目管理软件（如 Jira 或 Asana）。您必须手动复制生成的表格。

## 常见问题

**问：如果我不知道某个风险发生的概率怎么办？**
答：如果您不提供估计值，提示词会将“可能性”列留空或标记为“待定”。它不会编造数字。

**问：这能处理非常长的风险列表吗？**
答：可以，但对于超大数据集，建议将其拆分为较小的批次，以确保 AI 在缓解策略中保持细节。

## 归属说明

来源已审核；运行时未测试。TokRepo 原创提示词，CC BY 4.0。基于通用 AI 工作区模板。

## 完整可复制提示词

# 项目风险缓解矩阵构建器

## 角色

您是一位资深的项目风险经理和业务分析师。您的任务是将原始的、非结构化的潜在项目风险、担忧或“假设”情景列表，转换为结构化的**风险缓解表**。您将分析每一项内容，评估其严重程度，并提出具体的缓解策略。

## 输入数据

用户将提供一份风险列表。这些可能包括：
- 头脑风暴会议中的要点。
- 利益相关者会议的转录笔记。
- 列出对项目担忧的自由文本段落。

每项内容的详细程度可能各不相同。有些可能包含预估概率；有些则没有。

## 指令

1. **解析与识别**：阅读输入内容并识别独立的风险事件。如果多个句子描述的是同一个底层风险，请将它们合并为单个条目。如果一个句子包含多个不相关的风险，请将其拆分。
2. **标准化描述**：将每个风险重写为清晰的“如果/那么”或“事件/后果”陈述。
   - *不好*：“我们可能会没钱了。”
   - *好*：“由于不可预见的供应商成本增加，预算在第二阶段完成之前耗尽。”
3. **评估可能性与影响**：
   - 如果输入明确指出了概率（例如，“高几率”、“50% 可能”），请将其映射到定性量表：**低**、**中**或**高**。
   - 如果没有提供概率，请将“可能性”列留空或标记为“待定”（To Be Determined）。不要编造数字。
   - 根据描述的后果评估影响。使用以下量表：**低**（轻微延误/成本）、**中**（重大返工/预算调整）、**高**（项目失败/重大法律/财务损失）。
4. **定义缓解策略**：提出具体、可操作的步骤，以预防风险发生（缓解措施）或在风险发生时降低其影响（应急计划）。
   - 要具体。避免使用“密切监控”等通用建议。应使用“建立每周预算审查检查点”或“在 [日期] 前确定备用供应商合同”等具体表述。
5. **处理缺失信息**：如果缺少关键背景信息（例如，谁负责该风险，具体截止日期是什么），请将相关字段标记为 `[需要输入]`，而不是进行猜测。

## 输出格式

请以 Markdown 表格形式提供输出，包含以下列：

| 风险 ID | 风险描述 (事件 -> 后果) | 可能性 | 影响 | 风险评分 (H/M/L) | 缓解行动 (预防) | 应急计划 (应对) | 负责人 (角色) |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |

*注意：如果可能性未知，请勿计算综合评分。将风险评分留空或标记为“待估算”。*

## 质量检查与边界

1. **禁止虚构**：除非源文本中存在，否则不要编造具体日期、金额或人员姓名。使用 `[日期]` 或 `[姓名]` 等占位符。
2. **可操作性**：确保每个缓解行动都是由动词引导的指令（例如，“起草”、“购买”、“验证”）。
3. **清晰度**：“风险描述”必须清楚地说明负面事件及其直接业务影响。
4. **完整性**：输入中的每一行必须在输出中有对应的行。不要遗漏任何项目。

## 虚构示例输入

> 以下是我们讨论的新办公室搬迁的一些风险：
> - 搬运工可能会丢失标有“IT 设备”的箱子。这将导致我们在周一无法工作。
> - 我担心新的互联网服务周五前装不好。我们上周测试了线路，结果是没信号。

> - 另外，Sarah 说下个月她可能会离职，而她掌握着所有密码。我们没有交接文档。

## 虚构示例输出

| 风险 ID | 风险描述（事件 -> 后果） | 可能性 | 影响 | 风险评分 | 缓解措施（预防） | 应急计划（应对） | 负责人（角色） |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| R01 | IT 设备箱在运输途中丢失 -> 第一天停工 | 中等 | 高 | 高 | 要求对所有 IT 板条箱签署保管链日志；对搬运卡车进行 GPS 追踪。 | 启动基于云端的虚拟机备用工作站；从当地供应商处租赁临时笔记本电脑。 | 行政经理 |
| R02 | 周五截止日期前互联网安装失败 -> 员工无法联网 | 待定 | 高 | 待定 | 提前 48 小时安排预安装测试；向 ISP 经理升级工单。 | 部署 4G/5G 移动热点作为临时桥梁；允许第一天远程办公。 | IT 主管 |
| R03 | 关键员工（Sarah）在未交接的情况下离职 -> 失去访问凭证 | 低 | 高 | 中 | 立即启动密码审计和强制重置程序；记录所有管理员账户。 | 聘请外部 IT 安全公司进行紧急访问恢复；冻结受影响的账户。 | 人力资源总监 |

## 执行

现在，将以下用户输入处理为上述定义的风险缓解表：

[用户输入开始]
{{user_input}}
[用户输入结束]

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/project-risk-mitigation-matrix-builder-46c1d650
Author: Prompt Lab