Agents assessing reserve adequacy against industry benchmarks should describe reserve deficiencies by comparing loss development, identifying whether access limitations affected the actuarial analysis, and tracing the external consequences that reserve strengthening can have for capital, ratings, reinsurance capacity, and compliance timing.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill compare-loss-reserves-against-industry-benchmarks --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Compare Loss Reserves Against Industry Benchmarks?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-compare-loss-reserves-against-industry-benchmarks)More formats (shields.io, HTML) on the badges page.
---
name: compare-loss-reserves-industry-benchmarks-adequacy
task_id: insurance/compare-loss-reserves-against-industry-benchmarks
description: Agents assessing reserve adequacy against industry benchmarks should describe reserve deficiencies by comparing loss development, identifying whether access limitations affected the actuarial analysis, and tracing the external consequences that reserve strengthening can have for capital, ratings, reinsurance capacity, and compliance timing.
activates_for: [planner, solver, checker]
---
# Skill: Reserve Adequacy Assessment Memo — Compare Loss Reserves Against Industry Benchmarks
## 1. Subject-matter triage
- Identify the reporting date, accident years, lines of business, and benchmark set before evaluating adequacy.
- Determine whether the record contains an actuarial report, Schedule P, reserve history, benchmark tables, and related filings; if any are missing, say so and limit conclusions accordingly.
- If only one line or period is truly in scope, state that affirmatively; otherwise analyze each relevant line and period separately rather than collapsing them into a blended view.
## 2. Failure modes the skill is correcting
- Adverse development is noted in the aggregate without testing whether deterioration is stable, improving, or accelerating across periods, which can hide a worsening reserve posture.
- An actuarial access limitation is mentioned but not translated into the practical point that incomplete claim visibility can make the estimate conservative rather than fully informed.
- Reserve strengthening is treated as a bookkeeping entry without tying it to likely effects on surplus, capital metrics, ratings, reinsurance capacity, and compliance timing.
- A line that appears adequate in total is not tested for masked deficiency from a concentrated large claim or other latent exposure.
- Benchmark comparisons are recited without stating whether the subject reserve is above, near, or below the industry reference and what that means operationally.
## 3. Legal frameworks / domain conventions that apply
- Reserve development trend analysis: compare prior accident-year development over time to determine whether deficiencies are isolated, persistent, or worsening.
- Actuarial access limitations: if the actuary lacked access to key claims files, treat the estimate as potentially understated and explain why the limitation matters.
- Masked large-claim exposure: evaluate whether favorable development elsewhere obscures a concentrated adverse reserve position in a specific claim or cohort.
- Survival ratio: compare carried reserves to recent average paid losses as a cross-check on development-based adequacy.
- Reserve-to-surplus ratio: assess reserve leverage relative to surplus and describe how strengthening changes capital posture.
- RBC ratio: consider the effect of surplus reduction on proximity to regulatory intervention thresholds.
- Rating-agency impact: explain whether a material reserve action could trigger rating scrutiny and affect business capacity.
- Reinsurance aggregate erosion: if aggregate protection is partly used, assess whether further losses or strengthening reduce remaining capacity and increase net retention.
- Regulatory timing: identify any filing, remediation, or examination deadlines and state the consequence of missing them.
- Line-by-line adequacy: when the data support it, analyze reserve adequacy by line rather than only at the total-company level.
## 4. Analytical scaffolds
1. Build the record map: list the accident years, lines, and benchmark sources to be compared; note any missing or incomplete source.
2. Trend analysis: compare development across successive periods; describe whether the current period is tracking above or below prior patterns and whether the trajectory is stable, improving, or accelerating.
3. Access-limitation analysis: identify any disclosed limitations on claim, large-loss, or data access; explain how that affects confidence in the actuarial estimate.
4. Concentration analysis: test whether a specific claim, accident year, or line carries disproportionate development risk that could be masked by offsetting favorable items.
5. Benchmark comparison: measure carried reserves against the stated industry benchmark and characterize the gap as favorable or unfavorable, noting the relevant scale from the source materials.
6. Survival-ratio cross-check: compare reserves to average recent paid losses and state whether the cross-check corroborates or undermines the development analysis.
7. Capital-impact analysis: assess reserve-to-surplus and RBC implications before and after any strengthening, and explain the downstream effect on regulatory and ratings posture.
8. Reinsurance analysis: if aggregate coverage exists, identify remaining capacity and explain whether further adverse development could erode it.
9. Deadline analysis: extract any compliance, filing, or remediation dates and state the operational consequence of each.
10. Management-justification analysis: evaluate any reasons given for holding reserves below indications and explain whether they are persuasive in light of the record.
11. Recommendation synthesis: if strengthening is warranted, state it by line or period, tie it to the benchmark gap, and connect it to follow-on monitoring steps.
## 5. Vertical / structural / temporal relationships
- Treat reserve adequacy as time-sensitive: current indications must be read against prior development, not as a static point estimate.
- Distinguish company-wide adequacy from line-level adequacy; a benign aggregate can conceal a materially weak line.
- Compare the actuarial estimate to external benchmark evidence and then test whether the benchmark is corroborated or contradicted by development history.
- If the file set spans multiple periods, present the progression in chronological order so the reader can see whether the reserve posture is worsening or stabilizing.
- Link any proposed strengthening to the timing of regulatory filings, board review, and any examination response dates.
## 6. Output structure conventions
- Write a board-committee reserve adequacy memo in conventional memo form with a clear executive summary, analysis body, and conclusion.
- Include a trend section that walks through development by period and notes the directional pattern.
- Include a benchmark comparison section that addresses line-level and total-company adequacy, not just one or the other.
- Include a financial impact section addressing surplus, capital adequacy, ratings, and reinsurance implications.
- Include a deadline or follow-up section when the source materials contain filing, response, or remediation dates.
- State any recommendation for strengthening in operational terms, and identify the business or finance role that should act next with the relevant timing anchor.
- Use quantified comparisons only from the source documents and avoid unsupported arithmetic or unstated benchmark assumptions.
- When a conclusion depends on an authority or filing requirement, identify the governing source by name and section or part as stated in the record.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!