9 January 2025

Validating a Claim Extract Before Chart Work Starts | Hazelhub Analytics

Two days spent validating an export prevents two weeks of revised panels. These are the checks we run on every new client file.

Chart projects stall when extracts arrive with inconsistent status codes, duplicate claim numbers, or reserve fields that include payments. We block chart production until validation passes and send a fix list the client's IT or ops team can action without our involvement.

Duplicate claim numbers

We flag exact duplicates and "soft duplicates" where claim numbers differ by suffix but share policy number and loss date. Soft duplicates often indicate split files that should be merged before geographic or adjuster maps run.

Status code consistency

Open files with zero reserve and zero incurred sometimes indicate data lag; sometimes indicate a coding error. We report counts by status and ask the client to confirm which codes mean truly open for their system.

Date field sanity

Loss date after report date, or report date in the future, triggers a row-level exception report. Trend panels excluding these rows without documentation would understate recent activity.

Minimum history length

Drift and cohort panels need at least six months of history for property lines, twelve for liability lines with longer tails. Shorter history produces charts we will not sign our name to.

Client action timeline

Validation results ship within two business days of extract receipt. Chart work clock starts when the client confirms fixes or accepts documented exclusions.