Workers Comp Loss Runs: What Underwriters Look For

A workers' compensation (workers comp) loss run doesn't get read the way a general liability or auto loss run does — and the difference isn't cosmetic. On most lines, a loss run is a rearview mirror: the claims are settled, the numbers are final, and the underwriter is reading history. On a workers comp loss run, a meaningful share of the claims aren't finished when the report is printed. Reserves are still moving. Claimants are still in treatment. And the number the underwriter ultimately cares about — the employer's experience modification factor — is still being calculated off claims that haven't closed yet.

That's why workers comp loss runs get more scrutiny, take longer to read correctly, and carry more pricing consequence than almost any other line in the submission. This guide covers what a workers comp loss run actually shows, why the line behaves so differently from GL or auto, how underwriters read one in practice, and where the multi-carrier format problem makes all of it harder.

What a Workers Comp Loss Run Shows

A workers comp loss run lists every claim filed under the policy, with a consistent set of claim-level fields repeated for each entry. The exact layout varies by carrier, but the core data is the same:

Body part and nature of injury are worth calling out specifically, because they're what makes a workers comp loss run read differently from the start. A GL loss run tells you what happened to a third party. An auto loss run tells you about a vehicle incident. A workers comp loss run tells you about an injured employee — which is also why WC claims tend to stay open longer than claims on almost any other line, a theme that runs through the rest of this guide.

Why Workers Comp Is Where Loss Runs Matter Most

Every line of business has a loss run. Workers comp is the one where getting the read right carries the most weight — for three connected reasons.

The Experience Mod Connection

Workers comp is the one line where an insured's own claims history feeds directly into a standardized pricing formula: the experience modification factor, or "experience mod." NCCI's experience rating framework compares an employer's actual loss experience over a set period against the average losses expected for similarly classified businesses, producing a mod that adjusts the manual rate up or down. A mod below 1.0 lowers premium; a mod above 1.0 raises it.

Because the mod calculation draws on multiple policy years of claims — many of which may still be open — the loss run isn't just informational on workers comp. It's a direct input into a number that will move the employer's price regardless of which carrier ultimately writes the account.

Open-Reserve Uncertainty

On a GL claim, once a settlement is reached, the claim is typically paid and closed — the number is final. Workers comp claims don't resolve that cleanly. A claimant can remain in active medical treatment for months or years after the injury date, which means the reserve on that claim keeps moving as treatment continues, as return-to-work status changes, or as a claim reopens after a period of apparent closure.

That's why a workers comp loss run's open claims deserve more attention than its closed ones. A large open reserve isn't a settled fact — it's the carrier's current best estimate of a cost that's still developing.

Long-Tail Claims

Some categories of workers comp injury are inherently long-tail: back injuries with recurring treatment, occupational disease claims where onset is gradual, and claims that appear closed and then reopen when a claimant's condition changes. These claims can stay on a loss run — open or recently reopened — for years after the original injury date, which is part of why underwriters typically want more history on workers comp than they do on faster-resolving lines.

The 5-Year Convention (and When Underwriters Ask for More)

Most underwriters request 5 years of workers comp loss run history as a baseline — enough to see whether frequency and severity patterns are improving, stable, or getting worse, and enough runway to catch long-tail claims as they develop. That's a broader window than the experience mod calculation itself uses: NCCI's experience rating plan draws on a three-policy-year experience period, excluding the most recent policy year to give claims time to mature before they're counted. The 5-year loss run request is about trend visibility for the underwriter — it isn't meant to mirror the mod formula's own window.

For employers with severe or long-tail exposure — recurring back injuries, occupational disease claims, or a history of claims that reopen — some underwriters extend the request to 7-10 years, specifically to see how those claims developed rather than judging them at a single point in time. If you need the full mechanics of a loss run request (timelines, what to include, how to handle multiple prior carriers), the definitional guide to loss run reports covers that ground in detail — this section is scoped to what's specific about the workers comp version of that request.

How Underwriters Read a Workers Comp Loss Run

Reading a workers comp loss run well means separating two different risk signals that can look similar on a summary total but mean very different things.

A frequency problem looks like multiple small claims recurring year over year — strain and sprain injuries, minor lacerations, claims in the $2K-$10K range showing up three or four times annually. Frequency at that level usually points to an operational or safety-program issue rather than bad luck, and it tends to move pricing even when no single claim is large.

A severity problem looks different: one large claim, often with a substantial reserve still open, tied to an injury where the claimant remains in treatment. A single severe claim on an otherwise clean loss run gets evaluated on its own circumstances — was it a one-time event or a sign of a systemic exposure — but the size of the open reserve drives how cautiously the underwriter prices around it.

Beyond frequency and severity, underwriters also check reserve adequacy: do the final paid amounts on closed claims track reasonably close to what was initially reserved, or is there significant drift? A workers comp loss run where reserves consistently under- or over-shoot final paid amounts suggests the carrier's claims handling — not just the employer's risk — deserves a second look.

The Multi-Carrier Format Problem

Every carrier's workers compensation loss run report looks different. Some list body part and nature of injury as separate columns; others combine them into a single description field. Some show reserves as a standalone figure; others only surface a combined incurred total. There's no standardized workers comp loss run request format the way there is for an ACORD form, so each carrier's version has to be read on its own terms.

Multi-state employers compound this. It's common for workers comp coverage to be split across multiple carriers by state — one carrier for the home state, others for satellite locations — which means a single submission can arrive with several carriers' formats to reconcile into one coherent picture of frequency, severity, and reserve trend. Comparing loss run processing tools is one way teams evaluate options for handling that reconciliation at scale, whether the current approach is manual, templated, or outsourced.

How SortSpoke Extracts Workers Comp Loss Run Data

Reading one workers comp loss run carefully is manageable. Reading dozens per week, each in a different carrier's format, with claim-level fields like body part, reserve, and open/closed status scattered across different column layouts, is where manual review starts to compound risk rather than reduce it. Per-step accuracy isn't the same as a reliable end-to-end result — the more extraction and classification steps a WC submission requires, the more a small per-step error rate compounds into a materially wrong picture of the claim.

SortSpoke's loss run data extraction is built for that reality: claim-level fields — injury date, body part, paid, reserved, incurred, open/closed status — pulled automatically across carrier formats, with greater than 95% real-world extraction accuracy on loss run documents, measured against actual production data across varied carrier formats, layouts, and document qualities. The point isn't a number in isolation; it's what backs it. Every extracted field either clears the confidence threshold the underwriting team sets, or it routes to the team's own reviewers before it's used — 5X faster with 100% human oversight, not a claim that removes the underwriter from the loop.

That's a different model from handing workers comp loss run processing off to a BPO with no visibility into how a claim was read. The concern with outsourced processing isn't the vendor category — it's the lack of transparency into how a specific field was extracted or classified. A governed, reviewed extraction step keeps that visibility with the underwriting team, regardless of who's doing the initial read.

FAQ

Want to see how SortSpoke extracts claim-level workers comp loss run data across carrier formats, under your own team's review? See a demo →