Back to Details

risk-register

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Enterprise Risk Register Skill

企业风险登记Skill

When to Use

适用场景

  • During enterprise pursuits with multiple high-stakes dependencies.
  • Preparing executive updates or steering committee reviews.
  • Handing off deals between pursuit phases or regions.
  • 存在多个高风险依赖项的企业业务拓展项目期间。
  • 准备高管更新或指导委员会评审材料时。
  • 不同业务拓展阶段或区域间进行项目交接时。

Framework

框架

  1. Risk Catalog – categorize by workstream (value, product, legal, security, executive, finance).
  2. Scoring – likelihood x impact, color-coded with thresholds for escalation.
  3. Mitigation Plan – define owner, action, due date, and supporting resources.
  4. Watchlist & Escalation – highlight items nearing deadlines or requiring CRO/exec attention.
  5. Retrospective – update playbooks with resolved risks + guidance.
  1. 风险目录 – 按工作流分类（价值、产品、法务、安全、高管、财务）。
  2. 评分机制 – 可能性×影响程度，通过颜色编码设置升级阈值。
  3. 缓解计划 – 明确负责人、行动方案、截止日期及支持资源。
  4. 观察清单与升级流程 – 突出显示临近截止日期或需要首席风险官（CRO）/高管关注的事项。
  5. 回顾总结 – 根据已解决的风险更新操作手册并补充指导内容。

Templates

模板

  • Risk register table (risk, category, score, owner, mitigation, status).
  • Weekly summary slide for executive steering meetings.
  • Escalation request form with context + proposed action.
  • 风险登记表格（风险、分类、评分、负责人、缓解措施、状态）。
  • 用于高管指导会议的每周总结幻灯片。
  • 包含背景信息及拟议行动的升级请求表单。

Tips

小贴士

  • Keep risk statements precise (impact + trigger) to aid decision-making.
  • Default to weekly updates; high-risk deals may require twice-weekly cadences.
  • Align scoring with 
    pursuit-governance
    to maintain consistent reporting.
  • 风险描述需精准（包含影响及触发条件），以辅助决策。
  • 默认每周更新；高风险项目可能需要每周两次的更新频率。
  • 评分需与
    pursuit-governance
    保持一致，以确保报告的连贯性。