For insurers and brokers
AI prepares the case.
A person makes the call.
Underwriting, claims and placement are decisions a regulator can ask about, and AI now does much of the groundwork for them. An agent working a claim or a renewal stops to ask before it acts: a named person decides, each counterparty sees only their own position, and the record shows who decided, on what, and when.
No card required · Unlimited readers · Secure by default
The situation
What this looks like today
A decision a regulator will ask about
Accepting a risk, paying a claim or declining one is examined afterwards. When a model did the groundwork, the first question is which person decided and what they were looking at — and a chat transcript does not answer it.
One mistake in a recipient list is a disclosure
The same report goes to several counterparties with different entitlements, most of them in nobody's directory. The control between the wrong one and the wrong version is a person checking an address bar.
“What did they see, and when?”
When a placement or a claim is questioned, the answer needs to be evidence rather than recollection. A sent-items folder proves what left, not what was opened, and a system log shows what ran, not who allowed it.
What changes
Deliverd for insurers and brokers
Everything below ships today. Where something needs a paid plan, it says so.
Your AI asks before it acts
An agent that needs a decision puts it to a named person and waits: what it wants to do, why, how risky it is, and what to read first. They approve, approve with changes, reject with a reason, or ask the agent a question — on the page, from an email link, in Slack or Teams, or from a push notification on a phone — and a colleague can cover their approvals while they are away. It can also ask for a review, or for information it is missing, the same way.
A check before the agent acts
Before a consequential action — a payment, a deployment, a message to a customer — the agent declares what it is about to do and waits for the answer. A named person decides, or your organisation's rules settle the routine cases and send the rest to a person; with no rules, every one goes to a person. Afterwards the agent records what ran, and the record is checked against what was allowed.
On every plan; policy rules included in Business and Enterprise
Governance recorded as the work happens
Compliance Mode adds a register of the AI systems you use and, on governed work, the owners and the risk and data classification. That profile decides the controls: evidence or a person's approval meets each one, and an exception, with an owner and an expiry, shows as waived rather than met. The whole record exports as one evidence pack. It records how the work was governed — it does not certify compliance with any law or standard.
Included in Business and Enterprise
One pack for the auditor
Every step of a piece of work — who was asked, what they said, what was decided and when — exported as a single timeline in JSON, CSV or PDF. It carries a digest so an altered copy can be told apart, and the export itself is on the record.
A second thought, where it matters
Your organisation writes rules for requests that touch someone's job, money, health or privacy, or that cannot be undone. When one matches, whoever decides sees the concern first and has to say why it is right to go ahead; a rule can also ask more people to agree, or refuse. Ethics rules only add oversight — none of them can approve anything — and they are on every plan.
External readers, verified by one-time code
A reader outside any directory gets a link that emails them a code before it opens. Links can be restricted to named email domains, so a forwarded one does not become an open one.
A record of who opened it
Views, versions, access changes and share links are written to an audit trail you can export — which is the difference between believing a client saw something and being able to show it.
A workspace per client
Segment who can reach what, so an analyst on one engagement cannot browse another. Access is decided per report and evaluated on every request, assets included.
Every version kept, one URL
Reissuing updates the address and keeps what was there before. You can see what changed between two drafts and roll back if the new one is wrong.
The work keeps its objective
A task holds what the work is for apart from the conversation doing it, with a short state — where it stands, the next action, what is in the way — that any agent reads when it resumes. Side tasks take a bug or a piece of research out of the main thread and come back with a result. Switch tool or model and the next one picks up where things stand instead of starting over, and only a person changes the objective.
Included in Team, Business and Enterprise
Rules your firm sets once
Publishing policies run on every publish and share: no external sharing for a classification, a ceiling on how long a link may live, a workspace that must be named. A tester shows what a publish would do before anyone tries it.
When deletion has to stop, it stops
A matter opens and routine destruction becomes the wrong thing to do. Place a hold and the retention schedule suspends, the organisation cannot be closed, and a report’s data cannot be deleted — refused in the database, not by a setting somebody has to remember. Released with a reason, and both ends are on the record.
Included in Enterprise
Questions
Insurers and brokers and Deliverd.
Can a person decide before an agent acts on a claim or a risk?
Yes. The agent declares what it is about to do — pay this claim, quote this risk — and waits for the answer. With no rules, a named person decides every one. Policy rules, included in Business and Enterprise, settle the routine cases and send the rest to one person, or to two as the amount rises; only an owner or an administrator writes them. A gate is advisory: the agent asks and then performs the action itself, and its execution record shows whether what ran matches what was allowed.
What do we show a regulator who asks who decided?
An evidence pack: every step of the work — who was asked, what they said, what was decided and when — as one timeline in JSON, CSV or PDF, with a digest so an altered copy can be told apart. With Compliance Mode, included in Business and Enterprise, it also names the AI system that did the work, its owners, its risk and data classification and the controls it was held to. It is the record of how the work was governed; it does not certify compliance with any regulation.
How does a counterparty open something without an account?
A share link can require email verification: the reader enters their address, receives a one-time code, and the link opens only after it is verified. The link can be restricted to that firm's email domains.
Can two counterparties get different versions of the same report?
Publish them as separate reports and grant each to its own audience. That is the honest answer — one report is one document, and access decides who may open it, not what it says.
Is there a record of who opened which one?
Yes, per report: views, the version that was current, access grants and the share links themselves, all exportable.
Can a link be withdrawn after the fact?
Access can be revoked and the report archived, at which point the URL stops serving. What a reader downloaded before then is out of anyone's reach — which is why downloads are a setting you control.
Can a request about someone's credit or insurance get a second look?
Yes. The starter ethics rule “Credit, housing and insurance” flags requests about loans, mortgages, insurance claims and underwriting, and asks whoever decides to check that nothing like age or postcode is standing in for a protected characteristic. It arrives switched off; once on, a flagged approval needs a reason before it goes ahead, and the concern goes into the evidence pack.
Who decided, and when? Have the answer ready.
Let the agent do the groundwork, put the decision in front of the person who owns it, and keep the record before anyone asks for it.