Skip to main content

elan1 Research · Paper

The confidence line: where AI hands a claim to a person

A confidence score is only useful if it means what it says, and if someone has decided what a wrong answer costs. This paper explains how calibration and a signed cost matrix set the line at which an insurance claim moves on its own or reaches a handler.

Author
elan1 research team
Published
Reading time
4 min read
Access
Read free · no form

Findings

Three findings.

  1. 01

    Confidence scores must be calibrated on your own data before any claim moves without a person.

  2. 02

    The risk owner signs a cost matrix; the line between act and review follows from it.

  3. 03

    Four routes (act, review, escalate, hold) use more of what the model knows than a yes-or-no threshold.

The report

Method, evidence and what it means.

Why a raw score is not enough

Most models produce a number between 0 and 1. Many teams treat it as a probability and pick a threshold, often 0.9, because it sounds safe. Two things can go wrong. The score may not be calibrated, so 0.9 does not mean right nine times in ten. And the threshold may have nothing to do with what a mistake actually costs.

Calibration first

A model is calibrated when, across all cases scored at 0.9, about 90% are right. elan1 Decide reports calibrated confidence for each typed answer, whether it is a Boolean, a choice or a score. Calibration is checked on your own historical claims, in shadow beside your current process, before any automation is switched on. No calibration, no automation.

A signed cost matrix

Calibration says how often the model is wrong. The cost matrix says what each kind of wrong costs. For a first-notice-of-loss triage decision, the matrix might set out:

  • Routing a simple claim to a handler unnecessarily: a few minutes of handler time.
  • Fast-tracking a claim that needed a handler: rework, a delayed settlement and a possible complaint.
  • Missing an injury flag: potentially serious harm and a regulatory conversation.

The values are a business judgement, and the person who owns the risk signs them. That signature is the point: the line is set by someone who can answer for it, not by a data scientist's default.

Where the line falls

With calibrated confidence and a signed matrix, the line is arithmetic. A claim moves on its own only when the expected cost of acting is lower than the cost of a person reviewing it. Everything else is routed.

Four routes, not two

A yes-or-no threshold wastes information. elan1 Decide has four routes. Act, when confidence clears the line. Review, when a handler should confirm. Escalate, when a harder case needs deeper reasoning or a specialist. Hold, when inputs are missing or the system is unsure in a way the matrix did not anticipate. Fraud signals always go to a specialist; they never deny a claim on their own.

Watching the line move

Lines drift as claim mix, weather and repair costs change. The record of every decision, including the handler's answer where one was asked, lets the risk owner see whether the line still sits in the right place. Re-signing the matrix each quarter is a sensible default.

Regulators expect this discipline. IRDAI's policyholder protection regulations ask for timely and reasoned claim decisions, and the EU AI Act lists risk assessment and pricing in life and health insurance as high-risk. A line someone signed, with a record behind it, is easier to defend than a threshold nobody owns.

Further reading

Download

Read free. No form.

Keep a copy for your risk owner or auditor. Your browser saves this page as a PDF; nothing to fill in.

Cite this report

elan1 Research (2026). The confidence line: where AI hands a claim to a person. elan1.ai/research/the-confidence-line

Questions

The report, answered.

First check that the model's confidence is calibrated on your own historical cases, in shadow beside your current process. Then the person who owns the risk signs a cost matrix that says what each kind of wrong answer costs. A case moves on its own only when the expected cost of acting is lower than the cost of a person reviewing it.

A model is calibrated when its confidence means what it says: across all cases scored at 0.9, about 90% are right. A raw score is often not calibrated, so 0.9 may not mean right nine times in ten. elan1 Decide reports calibrated confidence for each typed answer, and calibration is checked on your own claims before any automation is switched on.

Whenever confidence falls below the line the risk owner signed, or the case needs more than a yes or no. elan1 Decide has four routes: act when confidence clears the line, review when a handler should confirm, escalate for a harder case or a specialist, and hold when inputs are missing. Fraud signals always go to a specialist.

Start with one process.

Pick the process that costs you most in review time. We configure it, you keep the approval, and the receipt is there from the first run.

  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
Illustrative data.

Add the next when it holds.

Approvals · Kolam ComponentsIllustrative
  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
RCPT-0042 · signed · chained
A product view with three decisions: allowed and approved by Asha R., held for the CFO, and refused under rule 4.2. Illustrative data.