Case library
Commercial insuranceChief Claims Officer

The Claims Assistant That Did Not Need a Swarm

A leadership team replaces an impressive but untestable multi-agent proposal with a staged architecture that earns complexity from evidence.

The scenario

Teaching composite — not a claim about a named organisation or measured outcome. A claims organisation wants an assistant to prepare a case summary from policy documents, adjuster notes and photographs before a human handler decides the next step. The proposal has a planner, five specialist agents, an autonomous web researcher, a reviewer and a supervisor. It looks sophisticated, but no one can say which agent owns a wrong recommendation, which tools may access claimant material, or how a failed run resumes.

The claims officer reframes the design. The first release needs to retrieve approved internal evidence, extract a fixed summary, identify missing evidence and prepare—not make—the handler's recommendation. A single retrieval-grounded agent with a structured output may meet that need. A planner, specialist workers or browser automation may be added later only if representative evaluation shows a specific limitation that the simpler system cannot meet.

The team records the deterministic controls: case access, permitted sources, validation, the action boundary and a human approval before any customer communication. It defines an evaluation set including ordinary claims, conflicting notes, missing documents and requests outside the assistant's authority. The result is not less ambitious; it is a design the business can test, explain and safely improve.

How AI enters the workflow

  1. Frame the decision

    Human

    The claims officer defines the first work product, accountable handler and unacceptable failure.

  2. Choose the minimum pattern

    Human + AI

    The team tests whether one retrieval-grounded agent can produce the structured summary before adding a planner or worker team.

  3. Set deterministic controls

    Human

    Identity, case access, source eligibility, validation and the action boundary remain code-owned.

  4. Run representative evaluation

    Human + AI

    Handlers test normal, conflicting, incomplete and out-of-scope claims; the system records quality, latency, cost and failures.

  5. Approve the next complexity

    Human

    The owner decides whether evidence justifies a new tool, loop, specialist or durable graph workflow.

Ask about this workflow

ADA, the taskforce deputy, explains exactly how human and AI share the work — ask anything.

The human + agent taskforce

Outcomes

MetricBeforeAfter
Architecture choiceA labelled but untestable swarmA minimum design with an explicit upgrade trigger
Control ownershipImplied by promptsCode-owned permissions, validation and approval
LearningDemo impressionsRepresentative quality, recovery, cost and safety evidence

Key takeaways

  • Start with the smallest pattern that can meet the work product and quality bar.
  • A model may interpret evidence; code must control access, validation and irreversible state changes.
  • Each added loop, tool or specialist needs a measured failure it solves and a bounded recovery path.
  • Human approval is an operational control only when rejection, modification and resume are all explicit.

Related concepts

Go deeper

Ready to bring AI into your organization?

Talk to us about a guided adoption path for your team — from first use case to production.

Ask about this concept

We value your privacy

We use cookies and anonymous analytics to understand how visitors use KUOS and improve the experience. You can change your mind at any time. Cookie policy · Privacy policy