home / skills / gtmagents / gtm-agents / risk-register

This skill helps track pursuit risks, owners, mitigation steps, and escalation triggers to streamline executive updates and handoffs.

npx playbooks add skill gtmagents/gtm-agents --skill risk-register

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: risk-register
description: Use to track pursuit risks, owners, mitigation steps, and escalation
  triggers.
---

# Enterprise Risk Register 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.

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

---

Overview

This skill helps teams track pursuit risks, assign owners, document mitigation steps, and define escalation triggers for enterprise deals. It provides a structured risk catalog, scoring model, mitigation planning, and watchlist features to keep executive stakeholders informed. The goal is to reduce surprises during high-stakes pursuits and create repeatable learning for future deals.

How this skill works

The skill lets you capture each risk with a clear statement, category, likelihood × impact score, owner, mitigation actions, due dates, and current status. It highlights items that cross predefined escalation thresholds and generates weekly summaries or escalation requests for CROs and executives. Retrospective outputs update playbooks with resolved risks and recommended process changes.

When to use it

  • Managing enterprise pursuits involving multiple teams or external dependencies
  • Preparing executive or steering-committee updates during a sale
  • Handing off deals between pursuit phases, geographies, or account teams
  • Monitoring high-risk opportunities where fast escalation may be required
  • In weekly pursuit governance cadences to keep reporting consistent

Best practices

  • Write concise risk statements that include the potential impact and specific trigger
  • Categorize risks by workstream (value, product, legal, security, exec, finance) for clearer ownership
  • Use likelihood × impact scoring with color thresholds to standardize escalation
  • Assign a single owner for each mitigation and set firm due dates for actions
  • Keep update cadence weekly by default; increase to twice-weekly for high-risk pursuits

Example use cases

  • A cross-functional pursuit tracker that surfaces product-delivery risks needing executive sign-off
  • Weekly slide deck generation for an executive steering meeting summarizing top escalation items
  • An escalation request form pre-filled with context, proposed action, and supporting evidence
  • Retrospective playbook updates after a closed deal that documented new mitigations
  • Handover checklist when transferring a deal between regional pursuit teams

FAQ

How is scoring applied?

Scoring multiplies likelihood by impact and maps to color-coded thresholds; thresholds can be aligned with your pursuit-governance.

When should risks be escalated?

Escalate when scores exceed predefined thresholds or when deadlines/mitigations are at risk of missing their due date.