The agent that audits the agents
In July 2025, Allianz Australia put the group's first agentic AI to work on storm-season claims: seven agents that verify, screen, and calculate in minutes. The seventh exists only to audit the other six. And none of them may pay a cent. By design, payout decisions are never automated.
Worked case · public-source reconstruction Autonomy: prepareWhy this case matters
A weaker version of the story would be "insurer automates claims." The stronger reading is the order of decisions: a global insurer that could have automated payouts chose a deliberately tiny scope, placed an auditor inside the agent system, and put its never-do in the press release. Allianz says the bounded case settles claims up to 80 percent faster. The design is what made that speed safe to buy.
The case
A storm knocks out the power, a freezer full of food spoils, and a small claim lands in a queue behind thousands of others. It is exactly the kind of claim that used to take days: low value, high volume, and arriving in bulk at the worst moment. Project Nemo hands it to a pipeline. A planner agent orchestrates the work; a cyber agent checks data security; a coverage agent verifies the policy; a weather agent confirms, against external meteorological data, that the storm actually happened; a fraud agent screens for suspicious patterns; a payout agent calculates the settlement.
Then comes the part that makes this a design story. A seventh agent, the audit agent, reviews every step the other six took, writes a summary of all their decisions, and passes it to a human claims professional, who makes the payment decision. "The ultimate responsibility always rests with a claims professional," says Maria Janssen, Chief Transformation Officer at Allianz Services. The AI phase completes in under five minutes; Allianz says settlement times fell from days to hours, and that the whole system was built in under one hundred days.
The scope is the other half of the design. One claim type, one peril, one ceiling: food spoilage, severe-weather outages, under five hundred Australian dollars. Expansion to travel delays, simple motor claims, and property assessments comes only after the bounded case proves out. The model is not the story. The boundary is.
Why it matters
Most agent governance lives in policy documents that the workflow can quietly skip under deadline. Nemo's governance lives in the system itself: one agent's entire job is reviewing the others, and the one action that touches money is withheld from every agent. The never-do is not a line in a handbook; it is an absence in the architecture.
Read through the Agent Operating Model, the design is unusually legible. Cognition comes from the models inside each agent. Control comes from the audit agent and the human payout gate. Reach stops, deliberately, one step short of the money. Its power comes from the combination, and so does its safety.
The filled canvas
The entries below are intentionally compact. A canvas should not read like a requirements document; it should make the load-bearing choices visible enough for a team to argue about them.
Worked example
What business outcome should this agent's work ultimately contribute to?
Settle simple storm-season claims in hours instead of days for customers in distress, while keeping every payout decision in human hands.
Which workflow is it part of, and what contribution is the agent responsible for making within it?
Workflow: food-spoilage claims under AUD 500 arising from severe-weather power outages (Allianz Australia). Role: verify, screen and cost each claim (a seven-agent pipeline) so a human assessor can settle it the same day.
01Who uses it directly, and who else is affected by what it does?
Direct users: claims professionals who receive the assembled file and decide. Affected: storm-hit customers awaiting payment, claims operations, fraud teams, regulators, and reinsurers.
02What measures will show that the workflow improved, and what performance standards must the agent meet?
Measures: settlement time (days to hours) and claims closed within a day. Standards: AI phase under five minutes, every claim weather-corroborated and fully auditable.
03What information may it use, and which sources should take priority when they disagree?
Policy records and coverage terms, the customer's claim and documentation, transaction patterns for fraud screening, and external meteorological data confirming the storm actually happened.
07What should it remember across interactions, what must it forget, and how should it learn and improve over time?
Learning happens by widening scope, not by silent drift: prove the bounded case, then extend to travel delay, motor, and property claims. Retention is not publicly specified.
08Who owns the workflow outcome, who is accountable for how the agent operates, and how will it be reviewed?
An audit agent reviews every step the other six take and writes the summary; a claims professional makes every payment decision. Ultimate responsibility rests with that person, not the pipeline.
09What to notice
"By design, payout decisions are never automated" is a sentence from the company's own announcement, not a compliance gloss added later. The boundary preceded the build.
The seventh agent exists only to audit the other six and package their work for the person who decides. A control that is part of the system cannot be skipped under deadline.
Under AUD 500, one claim type, one peril. Small enough to prove safely, frequent enough to matter: storm season delivers these claims in bulk, to customers in distress.
Travel delays, simple motor claims, and property assessments come only after the bounded case proves out. The expansion path is the learning loop, stated in advance.
Coach audit
Not as an outside fact-checker, but as a claims-transformation lead asking the question that matters before the scope widens: does the design that made the bounded case safe survive its own expansion? Here is what came back.
“Who is the person who can inspect the pipeline's work, tighten its standards, or switch it off, and is that a different person from the assessor deciding each claim?”The coach, on Ownership & Oversight (Cell 09)
Sources
Only public-source claims are treated as facts. The speed and build-time figures are Allianz's own; the underlying platform is undisclosed. Internal thresholds and routing rules should be read as design implications unless Allianz confirms them.
More worked cases