Written for Claims, SIU, underwriting, operations and technology leaders in insurers and agencies, and the sponsors who have to fund a first case.
What's in this playbook
Insurers are not short of AI ideas. They are short of first cases that can travel: a named process, a signed baseline, a system on the inventory the institution already knows how to run, a person who can stand behind a payment, a denial or a message to a policyholder, and a way to stop. This playbook is the single insurance document behind the insurance industry pages. It is complementary to the Enterprise AI Governance Framework already in the Resource Library, with FNOL, document processing, adjudication and fraud in depth, on purpose. It is not a near-duplicate of that framework, not a survey, and not a close of any named regime.
It maps six families of work. Each family has an honest first case and a case that is too wide. A first-notice assist that extracts fields, flags missing items, and prepares a file for a named intake handler — with a person on anything that opens a claim, contacts a claimant, or sounds like a coverage decision — is an honest first case in FNOL. An unsupervised decision that opens coverage, denies a claim at the door, or tells a claimant a payment is on the way is not. The same distinction is drawn for document processing, adjudication (not recommended as unsupervised settlement; a later straight-through path, if it is ever honest, has written bounds: coverage confirmed, fraud below a written ceiling, a person on SIU and on every deny), fraud and SIU, underwriting (not a first case; an honest later case is decision support for a named underwriter), and servicing drafts: AI as an intake and evidence layer first; an unsupervised settlement or deny is not a first case this playbook will recommend.
How the tests and the method are meant to be used
Fourteen design tests are applied to every case. The answers will differ. The standard does not. A missing counsel answer, an undefined "review," or a pilot already run and off the inventory, is a reason to pause, not permission to proceed. Counsel and the compliance function decide what an unfair-claims practice, a licensing rule, a privacy rule, or a notice duty requires, and when. This playbook will not make those determinations, and it will not recite dates. Hosting is decided before a case is funded. Where data cannot leave the environment, AsymiLink AI runs on your own hardware, with an optional air gap. Built to SOC 2 standards is the exact wording we use; it is not a certification of your system.
The illustrative organization is the same hypothetical mid-size property and casualty insurer as in the governance framework and the 2026 diagnostic: overall 15, Emerging, with Governance at 1, two claims pilots not in production with an operator, and a next-level target of 24, Developing — a next level, not a timeline, and not a promise. Its honest first work is to write a proportionate governance path, put those two pilots on the inventory, and only then to consider a bounded FNOL or document assist — not a third claims pilot, and not a model that settles or denies unsupervised. The financial method is The Complete Guide to AI Automation ROI. This playbook will not invent an insurance-sector result. The 3.8x average first-year ROI across client engagements is an average, not a forecast or a commitment for any individual project. ROI is measured across client engagements against a baseline agreed before work starts. It is an average, not a forecast for any insurance project.
Six families of work
each with an honest first case, a case that is too wide, and a defined gate. Each item below is the shape of the map; the full wording, honest first cases and “too wide” warnings are in the PDF.
F1
FNOL and claims intake
F2
Claims document processing
F3
Adjudication, settlement and STP bounds
F4
Fraud detection and SIU
F5
Underwriting
F6
Servicing and policyholder communications
The PDF gives, for each family, an honest first case, a case that is too wide, and a defined gate. The summaries above are the shape of the map, not a substitute for that wording.
Fourteen design tests (excerpt)
Fourteen design tests are applied to every case. The answers will differ. The standard does not. The full wording is in the PDF and the companion workbook.
T1–early
inventory and owner; proportionate consequence; a person on any payment, denial, bind or policyholder message, with review defined, and a person on SIU and on every deny; counsel asked in time; explanations, lineage and a frozen evaluation set.
Mid-tests
hosting decided up front; a write that pays or denies as a different design from a read; an audit trail that can reconstruct a day; a named operator and a switch-off; training and reuse written down.
Later tests
fairness examined for this use, not scored against a threshold we invented; honest notice; a bounded first case that raises the path; a signed baseline on the ROI method, and monitoring after launch that the organization that owns the system writes down.
A completed test sheet is not a certificate, not a compliance score, and not a finding that a system is safe or aligned with a named regime.
Get the guide and workbook
Enter your name, work email and company. The files appear on this page immediately. A backup download link is also emailed when email delivery is available.