Will escalateR-CONTRADICTION-BIAS · degrades this item
Your policy commits to scheduled fairness testing the estate does not show
AI policy (3.3) commits to testing fairness or disparate impact on a set schedule. MDL-001 Claims triage does not meet it, because no test is on record at all. A reviewer who reads the policy first expects a test result from the last ninety days to be in the file, and its absence tells them the schedule exists on paper. Once they have found one control that exists only on paper, they check the others the same way.
To fix: Run the test the policy already requires and record the date, or amend the policy to the cadence you actually keep. A commitment you do not meet costs more than one you never made.
Will escalateR-NO-MONITORING · degrades this item
No performance monitoring on record for MDL-001
MDL-001 Claims triage is not monitored in production against a threshold that would trigger a review, or you have not said that it is. The evaluation tool asks about drift because a model that was fair and accurate at validation can stop being either without anyone changing a line of code. For a system whose output reaches a consumer, a reviewer treats an unmonitored model as one whose current behaviour is unknown, and escalates rather than accepts it.
To fix: State the metric you watch, the threshold that triggers a review, and who receives the alert. A weekly report with one number and one named owner satisfies the question; a dashboard nobody is responsible for does not.