compliance-statement-library

gtmagents's avatarfrom gtmagents

Repository pattern for pre-approved financial disclosures and claim language.

⭐31stars🔀7forks📁View on GitHub🕐Updated Dec 23, 2025
[Positioning and Messaging]

When & Why to Use This Skill

The Compliance Statement Library skill provides a centralized repository pattern for managing pre-approved financial disclosures and claim language. It is designed to bridge the gap between legal compliance and go-to-market execution by ensuring that all marketing materials, sales decks, and product pages utilize verified, up-to-date regulatory language. By automating the retrieval and management of disclosures, it minimizes legal risks and accelerates content production cycles.

Use Cases

  • Marketing Content Assembly: Automatically pull required legal disclosures and pre-approved claims into marketing campaigns, landing pages, and social media assets to ensure 100% compliance.
  • Regulatory Change Management: Rapidly update financial messaging across all sales and marketing channels when interest rates, product terms, or government regulations change, using version-controlled statement catalogs.
  • Legal Review & Audit Readiness: Maintain a single source of truth for all approved language, complete with reviewer metadata, expiration dates, and evidence references to streamline internal audits and regulator responses.
  • Global Localization: Manage translated versions of compliance statements and accessibility requirements (like alt-text) to ensure consistent messaging across different regions and platforms.
namecompliance-statement-library
descriptionRepository pattern for pre-approved financial disclosures and claim language.

Compliance Statement Library Skill

When to Use

  • Assembling marketing campaigns, sales decks, or product pages requiring disclosures.
  • Responding to regulator/legal review comments.
  • Updating messaging after rate changes, product updates, or new regulations.

Framework

  1. Statement Catalog – define taxonomy (product, channel, audience, regulation, status).
  2. Approval Metadata – reviewer, date, expiration, evidence references, risk level.
  3. Usage Guidelines – instructions on required pairing, placement, and typography.
  4. Localization & Accessibility – translations, readability requirements, alt-text guidelines.
  5. Change Control – versioning, diffs, and notification hooks for GTM teams.

Templates

  • Disclosure record form with required fields (text, context, owner, evidence, reviewer).
  • Usage checklist to confirm placement and pairing rules.
  • Version change log referencing prior statements.

Tips

  • Link statements to product SKUs/offers so updates cascade automatically.
  • Store short and long-form variants for different channels (email vs landing page).
  • Pair with review-financial-campaign and build-product-go-to-market for automation.