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
- Reads the source document against the policy set you already hold
- Maps each obligation in it to the ones that apply to your organisation
- Cites the controls that satisfy them, with the evidence attached
- Names what is not covered, rather than writing around it
- Routes the pack to the accountable owner for sign-off
What you get
A response pack
A response pack: the obligations the source creates, the controls that answer each one, the evidence attached to each control, and a plain list of what is not yet covered. It carries the name of the person who signed it and the date they did.
What it needs from you
The policy set you already hold, the regimes you are subject to, and one named owner who can sign a response. Tredy reads what you have rather than asking you to restate it.
Where it stops
It does not decide. The response names what is covered, what is not, and what it could not determine — then a named person signs it. Anything Tredy is not confident about is escalated rather than filled in.
What starts it
A supervisory circular
A regulator publishes a circular or amends an existing one in a regime you are subject to.
A questionnaire
A regulator, client or reinsurer sends a due-diligence or supervisory questionnaire.
A reporting deadline
A periodic return falls due against a date you have already set.
Start with one service.
A 30-minute scoping session with your risk owner and your IT contact.