risk-assessment · 把运营风险写成可跟进的风险台账

作者提供的示例，实际效果取决于你的输入和使用工具。

输入

编辑虚构材料：周五开放报名；短信供应商本月有两次延迟；报名失败会影响300名参与者；林负责技术，周负责运营。现有方案只有短信确认，没有其他回执。组织暂定短信延迟可能性高、影响中。

输出

编辑示例 · 未运行

风险	可能性/影响	等级	缓解措施	负责人	状态
短信延迟使用户重复报名	高/中	高	页面提供报名编号；按手机号和活动去重；上线前演练延迟场景	林	开放
人工无法判断是否报名成功	中/中（待核验）	中	准备只读查询表和客服答复口径，限制访问人员	周	开放

高风险项在周四演练后复查。只有通过重复报名与回执测试，才能记录已实施控制；风险是否接受仍由活动负责人决定。

---
name: risk-assessment
description: Identify, assess, and mitigate operational risks. Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, process, or decision.
---

# Risk Assessment

Systematically identify, assess, and plan mitigations for operational risks.

## Risk Assessment Matrix

| | Low Impact | Medium Impact | High Impact |
|---|-----------|---------------|-------------|
| **High Likelihood** | Medium | High | Critical |
| **Medium Likelihood** | Low | Medium | High |
| **Low Likelihood** | Low | Low | Medium |

## Risk Categories

- **Operational**: Process failures, staffing gaps, system outages
- **Financial**: Budget overruns, vendor cost increases, revenue impact
- **Compliance**: Regulatory violations, audit findings, policy breaches
- **Strategic**: Market changes, competitive threats, technology shifts
- **Reputational**: Customer impact, public perception, partner relationships
- **Security**: Data breaches, access control failures, third-party vulnerabilities

## Risk Register Format

For each risk, document:
- **Description**: What could happen
- **Likelihood**: High / Medium / Low
- **Impact**: High / Medium / Low
- **Risk Level**: Critical / High / Medium / Low
- **Mitigation**: What we're doing to reduce likelihood or impact
- **Owner**: Who is responsible for managing this risk
- **Status**: Open / Mitigated / Accepted / Closed

## Output

Produce a prioritized risk register with specific, actionable mitigations. Focus on risks that are controllable and material.

先看看示例

输入

输出

方法说明