- Before
- Can list the models the company built, but not the AI it bought; chases owners, validators and vendors by email.
- Now
- Sees every system and every broken chain each morning, with the AI nobody filed already proposed and its clause quoted.
One vendor amendment, from overnight to the examiner’s answer
Monday, October 12, 2026, at Calder Ridge Insurance Group, a fictional carrier writing personal auto, homeowners, small commercial and term life in 14 states. A claims platform amendment arrived overnight. Here is what happens next, screen by screen, in the working solution.
- 01Monday morning
Every AI system in the company, on one register
Nadia Brennan · AI governance leadNadia opens the register: 147 AI systems, 61 built in-house and 86 from vendors, 22 High risk, 8 broken chains. A strip draws every system as one tick, grouped by pricing, underwriting, claims, fraud, life, customer service, marketing and operations. Rows with a broken sign-off chain sit at the top — a refit rating plan, a roof score waiting for its external data review, a letter-drafting tool with no owner. Three documents arrived overnight.
“147 AI systems · 8 broken chains”
- 02One click
Amendment 4, read clause by clause
AI finderNadia presses “Read with AI finder”. It reads the 38 pages of Vantor Systems’ Amendment 4 to the ClaimsCore Master Subscription Agreement and writes a margin note against every clause that matters. §7.4 lets Vantor switch on machine-learning features without notice. §7.6 lets it train them on Calder Ridge’s de-identified claims, pooled with other insurers’ data. §12.2 gives audit rights over data security, not over the model. §14.1 does require cooperation with regulators.
“Vendor may enable Intelligent Features … that use machine learning to generate recommendations … without further notice.” — Amendment 4, §7.4
- 03Seconds later
Row 148: a High-risk reserve recommender nobody filed
AI finderThe finder matches §7.4 to ClaimsCore release notes 24.3 — Auto-Reserve Assist, a suggested initial reserve on new bodily-injury and PIP claims, on by default since Sep 3. It checks the register: no ClaimsCore reserve system among 147 rows. It counts use in the claim system: 2,316 claims, 212 adjusters, 71% of suggestions accepted unchanged. It proposes AIS-148, Initial reserve recommender, High risk, and the row lands at the top of the register with the clause quoted under it.
Proposes only — the AI governance lead registers or dismisses.
- 04Model card
A model card, every line cited
Model card writerThe model card is already drafted from three documents: purpose, where it runs, inputs (claim type, injury codes, venue, attorney representation, prior claim history), output, training data, who uses it, why it is High risk and its known limits. Reserves set settlement authority and offers on injury claims, so the output reaches a consumer’s claim payment. Since Sep 3 it has suggested $38.4M in reserves.
“Drafted by the model card writer from 3 documents; every line cites its source.”
- 05Registered
Registered, with a named model owner
Nadia Brennan · AI governance leadNadia registers AIS-148 and names Dev Malhotra, claims analytics lead, as model owner — he owns the claims severity, subrogation and total-loss models already. Registering confirms the finder’s proposal; the owner accepts the system in writing, and the first link of the chain turns solid.
- 06Same morning
The vendor is asked for its evidence
Nadia Brennan · AI governance leadShe sends Vantor an evidence request under §14.1, the regulatory cooperation clause, with a copy to Owen Achebe in third-party risk: the model card, accuracy against incurred losses at 90 days by state, a monthly drift report, adverse impact tests by imputed race and ethnicity, sex and age band on injury claims, and the change log for every release since 24.0. Due Oct 26.
- 07Before the tests arrive
An interim control, approved by the business
Sam Whitfield · VP ClaimsUntil the system is validated, the adjuster saves their own reserve first and the suggestion appears after; differences over 25% go to a supervisor. Sam Whitfield approves it as business owner, and a compliance review opens with Grace Holloway. The chain now reads Dev Malhotra signed, Tomás Reyes, Grace Holloway and Sam Whitfield waiting.
- 08Before use
The tests the validator needs, listed
Tomás Reyes · Senior model validatorThe test evidence checker lists what AIS-148 needs before it can be signed: accuracy at 90 days, monthly drift monitoring, adverse impact by imputed race and ethnicity on BI claims, adverse impact by sex and age band, and independent validation by Calder Ridge. The vendor’s tests are requested for Oct 26; Tomás’s validation is scheduled for Nov 2.
The checker never marks a test passed and never runs a test on production data.
- 09Already updated
The examiner’s questionnaire counts all 148
Examiner pack writerMarket conduct examination MCE-2026-118 asks ten questions about AI systems, due Nov 14. The answers are drafted from the register, so B-1 now reads 148 in use (61 built in-house, 87 from vendors), 7 in development and 6 retired in the last 24 months, and B-2 says 17 systems were found in documents, including AIS-148 on Oct 12. Six answers are approved; the other four wait for Nadia’s approval.
Drafts only — never sends to a regulator.
- 10For the board
An attestation the CRO can sign
Marcus Iyer · Chief Risk OfficerThe annual attestation to the Board Risk Committee is drafted from the same register: 148 systems, 87 from vendors and 17 found in documents; 139 with all four sign-offs; 9 open, each with an owner and a date to close — AIS-148 by Nov 20; 20 open gaps against the rules. Nadia prepares it, Ruth Okonjo reviews it for internal audit, and Marcus Iyer attests.