All solutions
Support function · Risk and compliance

Each release's tests and approval in one place, for the people who audit them.

Auditors ask how each agent was tested and approved, and the answer is scattered.

For risk and compliance teams, the compliance officer who signs off, and the IT team that governs them.

How the example fits together: tools and an agent built on Unflood, with a person approving before anything is written.

Made from a conversation in Claude, released to the AI platforms your team already uses, running in your own environment.

Claude
Turn this conversation into an agent that answers an auditor's question about a release from its test results and approval.
Unflood created the agent from this conversation, ran its tests and asked a second person to approve the release.
  • Unflood: Audit-answer agent created from this conversation 3m ago
  • Unflood: Test results recorded against the version tested 2m ago
  • Unflood: Released once a second person had approved it 1m ago
  • Unflood: Shared with the risk team Just now

See it happen in a chat

A person on the team asks for an agent. Unflood does the building in the background and comes back for the decisions that are yours.

  • Unflood tests them.
  • A person approves each release.
  • They are shared with the right people.
  • They are kept up to date, so you step in only when a decision is yours.

Examples for Risk and compliance, to learn from

Example 1

Answer an auditor's question about a release from its test results and approval

On Unflood: Release records and test results, as already kept.

Example 2

Flag any release that lacks a second person's approval

How release evidence fits together

Test results
Each case judgedEvery case judged against the version tested.
Person
A second person approvesNot the one who packaged it.
Record
The release recordVersion, policy and approval in one place.
People
Internal audit and riskThey read the record, not a scattered trail.

Six moments that make the difference

Each one is shown on sample data, with this team's own example where there is one.

Build it from a conversation

Describe the agent in a Claude chat. Unflood records it, its tools and its tests.

In Risk and compliance: Answer an auditor's question about a release from its test results and approval

  • Builds itA compliance analyst, from the audit requests they already answer.
Recorded from the conversation
Test resultsSecond personRelease recordAudit
Drawn on sample data.

Test it

Suites and a judge run it; each failed case becomes an item to fix.

  • Test resultsEach case judged against the version tested.
Test lab
  • A case failsJudged against the version tested.
  • It becomes an item to fixNothing is lost between runs.
  • Retest, then release
Drawn on sample data.

Release it with approval

Package a version. Nothing reaches people without a person's approval; the builder cannot approve their own.

In Risk and compliance: The compliance officer.

  • Release recordWhich version was published where, and the policy it was held to.
  • Release with approvalA second person approves each release.
  • Approves itThe compliance officer.
Release waiting for approval
  • Packaged byA compliance analyst, from the audit requests they already answer.
  • Needs approval fromThe compliance officer.
The builder cannot approve their own release.
Drawn on sample data.

Share it

Choose who can use it, person by person or team by team, where the team already works.

In Risk and compliance: Internal audit and the risk team.

  • Uses itInternal audit and the risk team.
Who can use it
  • The Risk and compliance teamInternal audit and the risk team.
  • A named personChoose person by person or team by team.
Drawn on sample data.

Keep it up to date

Change it, retest it, release the next version. Every version can be rolled back.

Versions
  • Current versionLive.
  • Next versionChanged, retested, waiting for approval.
  • Roll backEvery version can be rolled back.
Drawn on sample data.

The organisation stays in control

Members, roles and a record of every change belong to the organisation.

  • A workspace for the organisation, on its proven domains
  • Members and roles: who uses an agent and who changes it
  • Release approval by a second person
Record of every change
  • The builderCreated the agent.
  • UnfloodRan the tests.
  • The approverApproved the release.
Drawn on sample data.

How the team gets there faster

Your people describe the work and approve it. Unflood does the building, testing and publishing.

Today

Auditors ask how each agent was tested and approved, and the answer is scattered.

With Unflood

Each release's tests and approval in one place, for the people who audit them.

Your people do
  • Builds itA compliance analyst, from the audit requests they already answer.
  • Approves itThe compliance officer.
  • Uses itInternal audit and the risk team.
Unflood does
  • Connects your tools and data
  • Writes and runs the tests
  • Packages each version
  • Publishes it where your team works
  • Retests every change before the next release
  • Keeps the record of who changed what

Talk to us about your team

Tell us the work your team wants an agent for. We set up a workspace with you and build the first one with the people who know the work.

Get in touch