At claim creation and each update, retrieve the current paid-to-date, outstanding reserves, and case reserve history from your claims management system.
Apply your carrier's initial reserve guidelines (typically based on coverage type, injury severity tier, or loss description keywords) to set an initial case reserve; encode these rules as a reserve-recommendation service that accepts claim attributes and returns a suggested reserve amount.
After each reserve change, log the change with timestamp, prior reserve, new reserve, adjuster ID, and change reason to a reserve-history audit table.
Implement stair-stepping detection by querying the reserve history: flag any claim where reserves have been increased in three or more consecutive transactions without a corresponding new loss event or supplement, or where the reserve increase exceeds a carrier-defined percentage threshold (consult your carrier's reserve adequacy guidelines for the threshold).
Route flagged claims to a reserve review queue for supervisor approval; generate a reserve-adequacy report summarizing flagged claims by adjuster and line of business for management review.
Integrate with your actuarial reserving system to feed open-claim reserve data for IBNR calculations at each financial close cycle.
Known gotchas
Stair-stepping is a regulatory and audit red flag; state market conduct examiners specifically look for patterns of inadequate initial reserves followed by incremental increases — ensure detection logic aligns with your state's reserve adequacy regulations.
Reserve changes made solely for financial-statement smoothing (holding reserves artificially low or high across a quarter-end) can constitute unfair trade practices; build governance controls around quarter-end reserve change volumes.
Reserve recommendation models trained on historical claims can perpetuate bias if the training data reflects prior under-reserving patterns; periodically audit model outputs against actual closure amounts.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp