playbooks

home / skills / gtmagents / gtm-agents / regulator-briefing-playbook

regulator-briefing-playbook skill

/plugins/financial-services/skills/regulator-briefing-playbook

This skill helps you prepare regulator briefing packages by organizing outlines, evidence, Q&A, and trackers for audits and approvals.

npx playbooks add skill gtmagents/gtm-agents --skill regulator-briefing-playbook

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

Files (1)
SKILL.md
1.2 KB
---
name: regulator-briefing-playbook
description: Template pack for preparing regulator communications, responses, and
  readouts.
---

# Regulator Briefing Playbook Skill

## When to Use
- Preparing FINRA/SEC/CFPB/FTC briefing packages or responses.
- Documenting campaign decisions in anticipation of audits.
- Coordinating cross-functional responses to regulator inquiries.

## Framework
1. **Briefing Outline** – context, product/campaign details, risk mitigations, approvals.
2. **Evidence Binder** – assets, disclosures, policy references, decision logs, metrics.
3. **Q&A Matrix** – anticipated regulator questions with approved responses + owners.
4. **Escalation Charter** – roles, SLAs, and communications plan for regulator interactions.
5. **Follow-up Tracker** – commitments, remediation steps, and deadlines.

## Templates
- Regulator memo template (executive summary, evidence, appendices).
- Q&A log with question, owner, response, status.
- Commitment tracker linked to Jira/Asana or compliance tools.

## Tips
- Keep version history and timestamps to prove timely responses.
- Align narrative with risk/compliance frameworks used internally.
- Pair with `review-financial-campaign` and `manage-trust-communications` outputs.

---

Overview

This skill provides a production-ready playbook and templates to prepare regulator briefings, responses, and readouts. It packages an actionable framework—briefing outline, evidence binder, Q&A matrix, escalation charter, and follow-up tracker—so teams can quickly assemble compliant, auditable communications. The templates are optimized for cross-functional coordination and handoffs between legal, compliance, product, and ops.

How this skill works

The skill guides users through a structured inspection of campaign or product activities, collecting relevant assets, approvals, and decision logs into an evidence binder. It generates a regulator memo and Q&A matrix populated with anticipated questions, owner assignments, and approved responses. It also produces an escalation charter and a commitment tracker that maps remediation items to owners, SLAs, and external reporting timelines.

When to use it

  • Preparing FINRA/SEC/CFPB/FTC briefing packages or formal responses
  • Documenting campaign decisions and evidence ahead of audits or inspections
  • Coordinating cross-functional responses to ad hoc regulator inquiries
  • Assembling executive readouts for compliance committees
  • Tracking remediation commitments after a regulatory finding or inquiry

Best practices

  • Keep a single source of truth: store evidence, timestamps, and version history together
  • Align narrative with internal risk and compliance frameworks for consistency
  • Designate clear owners for each Q&A item and remediation commitment
  • Use concise executive summaries and appendices for detailed evidence
  • Integrate trackers with ticketing tools (Jira/Asana) to enforce SLAs

Example use cases

  • Produce a regulator memo and evidence binder after a marketing campaign flagged by compliance
  • Create a Q&A matrix and assign owners before a scheduled regulator meeting
  • Compile a follow-up tracker and remediation plan after an inspection or inquiry
  • Coordinate cross-team approvals and maintain an audit-ready version history
  • Convert review outputs into actionable tickets linked to compliance systems

FAQ

Can the templates handle different regulator requirements?

Yes. Templates are adaptable; use the briefing outline to map regulator-specific evidence and approval expectations.

How do I prove timely responses?

Maintain timestamps and version history in the evidence binder and link commitments to SLAs in the follow-up tracker.