Deep dive — scenario walkthrough

The sample scenario — what the SC auto-claims AI was doing and why it failed silently

Mid-size South Carolina-domiciled P&C carrier. ~150K-500K personal auto policies-in-force + ~20K-80K homeowners across the state. AI-driven claims-severity classifier + adjuster-routing engine at the front of every incoming auto bodily-injury claim. Standard-of-market AI deployment. Standard operational instrumentation. Standard silent failure.

The AI system

Model: auto BI claims-severity classifier + adjuster-routing engine (mock version sc-claims-severity-v2.3.1).

Function: each incoming auto BI claim is scored 0-100 on projected severity + fraud-signal, using structured claim fields + loss-narrative text + prior-loss profile + territory + credit-based-insurance-score inputs. Score routes the claim to one of three lanes:

  • Fast-Close (score 0-33) — low-severity, low-fraud-signal, direct-to-close pathway
  • Standard Adjust (score 34-66) — human adjuster ownership + standard investigation
  • SIU-flag (score 67-100) — hold pending Special Investigations Unit review

Audit period: 90 days. Claim volume in scope: ~12,000 auto BI claims statewide.

Training window: claims through 2026-02-15. Deployed Day 1 of the audit period. Not retrained during the 90-day production run.

The county groups

The audit used five county groupings reflecting the SC market shape:

County groupCounties
C1 UpstateAnderson, Cherokee, Greenville, Oconee, Pickens, Spartanburg
C2 MidlandsAiken, Lexington, Newberry, Richland, Saluda, Fairfield, Kershaw
C3 CoastalBeaufort, Charleston, Colleton, Georgetown, Horry, Jasper
C4 Pee DeeChesterfield, Darlington, Dillon, Florence, Marion, Marlboro, Williamsburg
C5 PiedmontAbbeville, Chester, Edgefield, Greenwood, Lancaster, Laurens, McCormick, Union, York

What shifted during the 90 days

Three input distributions moved silently and simultaneously in the C3 coastal group:

  1. Post-storm claim mix shift. Hurricane-season activity in coastal counties raised the share of claims involving vehicle-damage-plus-BI patterns the model had seen less of in training.
  2. Provider-narrative shift. A larger share of coastal-county BI claims involved a small number of high-volume medical-provider networks whose narrative-text patterns triggered fraud-signal features in the classifier.
  3. Territory + credit-adjacent input shift. Post-shift C3 claimants skewed toward higher-risk-class territories and slightly lower credit-based-insurance-score bands.
The AI was not retrained. Its baked-in coastal-provider offset compounded with the shifted input mix. C3 SIU-flag lane rate rose from ~5% baseline to ~19% recent — a 14 percentage-point group-differential in the wrong direction, silent to every aggregate metric the carrier was watching. First high-severity drift event landed Day 44.

What the carrier's dashboards showed (green)

Standard claims instrumentation cannot see group-differential in aggregate. That is not a criticism of the claims-ops team; it is a structural property of aggregation.

What the independent-verifier sensor saw

See how the drift-detection chart is read →

The one sentence a Chief Claims Officer would care about

The auto BI claims-severity classifier's SIU-flag lane rate for C3 (Beaufort, Charleston, Colleton, Georgetown, Horry, Jasper) rose from ~5% to ~19% over the audit period — a 14 percentage-point group-differential in the wrong direction that occurred silently while the carrier's claims dashboard showed aggregate cycle-time and closure metrics within normal bands throughout, putting each affected claim at risk under the SC UCSPA "prompt investigation" standard.

$499 Snapshot on your carrier's actual AI system.

Same scenario structure. Your data, your AI, your SC DOI footprint. Same 3 business day turnaround.

Buy $499