Governing AI and human actions across the tools your teams already use
- Claude
- ChatGPT
- Slack
- Microsoft Teams
- Microsoft 365
- Gmail
- GitHub
- GitLab
What it does
- Gap-assesses the draft against the obligations currently in force
- Determines which stakeholders are required to review it, and why
- Routes it to each named reviewer with the relevant section marked
- Collects each decision with the rationale behind it
- Keeps the signed trail bound to the exact version approved
What you get
An approval trail
An approval trail: the gap assessment against the obligations in force, the reviewers required and why each one was required, and every decision with its rationale — bound to the exact version of the text it was made against.
What it needs from you
Your current policy set and who is accountable for each domain. Reviewer routing uses the org structure you already have, not a new approval matrix.
Where it stops
It does not approve policy. It gap-assesses, routes and records. Every approval on the trail belongs to a person who made it.
What starts it
A draft or revision
Someone writes a new policy or amends one that already exists.
A review date
A policy reaches the review date set when it was approved.
A forced amendment
A regulatory change makes the current text non-compliant.
Start with one service.
A 30-minute scoping session with your risk owner and your IT contact.