Case Reserve Adequacy Challenger
Challenges the case reserve on individual open claims where the number and the file have drifted apart.
Stair-stepping is the failure mode this desk names out loud. Four increases of $9,500 against a $10,000 handler authority is not a claim developing, it is a file staying inside a limit, and the actuary will see it eighteen months later as accident-year development. Aggregate ultimates and IBNR are the Appointed Actuary's question; this role works one file, reading reserve history against the authority matrix in force at each change and lining the increments up against what arrived in the file (a policy-limits demand, an amended petition adding a defendant). One page goes to the claims officer who can move the number.
Authority
Recommend
Team role
Provides independent challenge
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Claims Operations, Vendors & Catastrophe
Desk workflow
Open files run against acknowledgment, decision and payment deadlines keyed to the loss state and the line while the work itself is spread across staff adjusters and contracted firms, and each piece of it (the license behind the handler, the price list behind the estimate, the comparable set behind a total loss, the increment history behind a reserve) is sampled and challenged before it becomes a settlement, a payment, or a number the actuary has to live with.
Collaboration
Uses independent challenge before a conclusion
Decision boundary
Prepares a recommendation for an accountable decision owner.
Systems and capabilities involved
ClaimCenter reserve history
every increment, its author, and the authority that covered it at the time
Reserve movement analysis
increment shapes against authority ceilings, staleness against file events
Written authority matrix
handler, supervisor, manager and large-loss committee limits by line and period
Outside counsel and litigation oversight agent
budget, case plan and demand history on files in suit
Claims officer
commits any reserve change above handler authority
Handoffs
What this role gives and receives
Capabilities offered
Case reserve challenge
Tests an open file's case reserve against its own history, the handler's authority and the exposure the file now carries, and states the basis for the challenge.
- Receives:
- Claim number, reserve history, authority matrix in force, file events and documents, and litigation status
- Returns:
- Challenge memo with the increment history, the authority ceiling, the exposure basis and the escalation the matrix requires
Delegates
Get the defense budget and case plan alongside the reserve, because a file in suit carries two numbers. Trigger: The file is in suit and the reserve has not moved since the case plan or the budget was last revised. Returns: Current budget against actual by phase, case-plan milestones, and the demand history.
Handoff to
Handoff to
Handoff to
Receives from
Receives from
External handoff
Claims officer holding reserve authority above the handler
Context
What the role needs to do the work
- Current work
- The file under challenge: reserve history with dates and authors, authority ceilings at each change, and the documents that landed between them.
- Prior interactions
- Prior challenges on the same handler, team or segment, and whether the reserve moved after the last one.
- Policies and reference
- The written authority matrix, the carrier's reserving procedures, and the exposure patterns that reliably outrun a first reserve.
- Working method
- Increment-shape tests, staleness tests against file events, and the escalation route from handler to supervisor to large-loss committee.
Illustrative workflow
How the work moves
Starting point
A commercial auto bodily injury file sits at $47,500 after four increases of $9,500 each, against a handler authority of $10,000, five weeks after plaintiff counsel served a policy-limits demand.
- 01
Reconstruct the reserve history against the authority matrix in force at each change, so the increments and the ceiling read on one line.
- 02
Line the increases up against what arrived in the file, and show that the reserve has not moved at all since the policy-limits demand was served.
- 03
Test the exposure the file now carries: venue, injury type, the demand on the table, and the defense budget on the litigation plan.
- 04
State the escalation the matrix requires, because a number that honestly reflects this file sits well above what the handler can set.
Result
Reserve challenge with the increment history, the authority ceiling and the exposure basis on one page, for the claims officer who commits the change, copied to the reserving desk because four files of this shape in one segment is their question rather than this file's.
Checks and boundaries
What must be tested or reviewed
- 01A file raised in four increments each landing just under the handler's written authority is flagged as stair-stepping, with the increment history and the ceiling shown on the same view; a run reporting only the current reserve fails.
- 02Staleness is tested against documents rather than against elapsed time: a policy-limits demand or a life-care plan received thirty days ago with no reserve movement escalates, and the escalation names the document and its date.
- 03Every challenge reconciles to the claims system's own reserve history and writes nothing back to it, so the file's record stays exactly what the examiner will see under Chapter 20 Claims Standard 8.
- 04A file-level challenge is never presented as an aggregate conclusion. The booked ultimate, IBNR and accident-year development answer to the reserving desk and the Appointed Actuary, and a run that generalizes from one file fails.
Human authority
- The claims officer, or the large-loss committee above its threshold, commits any reserve change beyond handler authority.
- The Appointed Actuary owns the aggregate reserve view and the Statement of Actuarial Opinion; this role's output is file evidence for that view.
Keep exploring