Insurance AI and underwriting governance
AI-04Draft
Explain decisions and monitor changes
How Leela would run itContinuous · during covered underwriting or pricing use
Proposed stepsThe requirement
Monitor drift, complaints and material changes. Keep decision explanations and notices accurate, route challenges to qualified reviewers and suspend unsupported uses when necessary.
- Before this work
- Model-performance, decision and complaint records Reviewed thresholds, explanation criteria and escalation permissions
- Applies
- Tell Leela about your company to see whether this applies.
- Status
- Setup needed
Tell Leela how you handle it today, or hand it over: see what’s next.
How Leela would run it · proposed steps
- LeelaMonitor approved drift indicators, complaints and material model or data changes.Proposed step
- LeelaFlag inconsistencies between recorded decision reasons and notices, and route challenges with supporting evidence.Proposed step
- Underwriting governance leadQualified reviewers approve explanations and determine corrective action or suspension of a use case.Your team decides
What Leela keepsThe evidence this obligation leaves, as the work happens
Listed from the policy libraryContents
- 01Monitoring record, decision explanations and change logControlled record with date, owner, source and review history
Evidence
Monitoring record, decision explanations and change log
Insurance AI and underwriting governance §3.4
1
of 1 record
The steps are the library’s proposed workflow for this obligation: a description of the work, not a run. The records are its evidence in the library.