13 June 2025

Why Reserve Drift Panels Need Claim Numbers in the Margin | Hazelhub Analytics

Annotated drift charts fail in ops meetings when directors cannot trace a spike back to specific files. Here is how we structure margin notes for weekly review.

A reserve drift panel shows movement between two valuation dates. Operations directors use it to decide which regions need adjuster reinforcement. The chart itself is simple—a line or bar series by vintage or region. The failure mode is almost always the same: someone points at a spike and asks "which claims?" and the presenter flips to a spreadsheet.

We build drift panels with a fixed margin column listing the top five claim numbers contributing to each visible spike. Numbers are redacted for external packs (last four digits only) but full numbers appear on internal copies. The rule is one margin block per spike, never a separate appendix.

Field requirements

Your extract must include claim number, reserve at date A, reserve at date B, and line of business. Without both valuation dates per claim, we cannot compute drift at file level—only aggregate movement, which is weaker evidence in a rebalancing discussion.

When to skip drift panels

If your organization revalues reserves on rolling individual file review without fixed monthly snapshots, drift panels mislead. In that case we recommend cycle-time histograms instead, which do not depend on synchronized valuation dates.

Print consideration

Drift panels with full margin notes need A3 width minimum. A4 compresses the annotation column below readable size for directors over fifty—a demographic we do not ignore when choosing format.