A loss run can arrive as a 60-page carrier report, a scanned PDF with uneven tables, or several files covering different policy terms. The challenge in how to process loss runs is not simply reading claim history. It is turning inconsistent documents into trusted, decision-ready information without asking producers, account managers, or underwriters to rekey the same details repeatedly.
For commercial insurance teams, loss-run processing affects submission speed, appetite decisions, pricing confidence, and the quality of the conversation with the insured. When claim data remains trapped in documents, the submission may look complete while critical patterns remain hard to see. A disciplined workflow brings the right data forward, preserves the source record, and directs exceptions to the people best equipped to resolve them.
Loss runs are not processed in a vacuum. An underwriter may need a fast view of total incurred losses, open claims, large-loss activity, and loss trends by policy year. A producer may need to determine whether the records are current and complete before approaching markets. Operations teams need standardized data that can move into an agency management system, rating workflow, underwriting workbench, or carrier portal.
Define the required output before setting extraction rules. At minimum, establish which policy periods, lines of business, claim fields, and summary measures are required for the intended workflow. This prevents a common failure mode: extracting every visible field from every page while failing to surface the few facts that actually affect a submission decision.
The right level of detail depends on the risk and the receiving market. A small, straightforward account may require current valuation, total paid, total incurred, and the largest claims. A complex workers' compensation, commercial auto, or liability account may warrant claim-level detail, reserve movement, cause of loss, body part or injury codes, litigation indicators, and location or unit references where available.
A reliable process follows a clear path: capture, classify, extract, organize, validate, enrich, review, and deliver. The sequence matters because accuracy depends on both the source document and the business context around it.
Bring loss runs into the workflow alongside the ACORD application, supplemental forms, statement of values, expiring policy information, and relevant emails. A loss run without an account name, line of business, or requested effective date is harder to validate and easier to misroute.
At intake, associate each document with the correct insured, submission, policy, and producer whenever that information is available. Retain the original file and page references. Underwriters need to be able to verify an extracted value against the source, particularly when a material claim changes the direction of a risk review.
Not every report labeled "loss runs" has the same structure. Carrier-generated reports, third-party administrator reports, broker summaries, and spreadsheet schedules often use different headings and valuation conventions. Some reports combine several lines of business or include only closed claims. Others show a claim total on one page and detail across subsequent pages.
Classification identifies the document type, carrier or administrator format, report date, policy periods represented, and whether the document contains claim detail, aggregate summaries, or both. It also helps separate true loss runs from claims narratives, loss-control reports, notices of cancellation, and other attachments that may appear in the same email.
The goal is not a flat transcription of the PDF. It is a usable, normalized record that allows claims from different sources to be reviewed consistently. Common fields include policy number, line of business, policy effective and expiration dates, claim number, claimant, date of loss, report date, status, cause of loss, paid amount, expense amount, reserve, and total incurred.
Preserve distinctions that matter to underwriting. Paid losses and incurred losses are not interchangeable. An open claim with a modest paid amount can carry a significant reserve. Likewise, a $0 paid claim could be closed without payment, still open, or reported in a way that requires further explanation. The workflow should retain the values and statuses supplied by the source rather than infer a conclusion from one number.
Normalize dates, currency formats, and labels carefully. A carrier may use abbreviations for claim status or present negative adjustments in parentheses. Standardizing those values makes downstream analysis possible, but the original terms should remain accessible for auditability and exception review.
Claim-level rows provide the evidence. Policy-level summaries provide the underwriting view. A sound process ties each claim back to its policy period and rolls detail into totals that can be compared with the report summary.
This is where many manual workflows break down. A user may copy claim details into a spreadsheet but fail to connect them to the correct term, line, or coverage. Or they may rely on a summary page that excludes a separate schedule of open claims. Organizing the information into related records helps teams assess frequency, severity, and development without losing the underlying documentation.
Extraction should never be treated as automatic approval. Validate whether the loss runs cover the requested experience period, whether all relevant lines are represented, and whether the valuation date is current enough for the submission. For many markets, a report that is several months old may require an explanation or updated documentation.
Reconcile extracted claim totals against the document's stated aggregates when possible. A mismatch may signal an extraction issue, but it can also reflect differences in how a report treats expenses, subrogation, closed claims, or prior-term adjustments. Those differences should become visible exceptions, not quiet assumptions.
Useful validation checks include duplicate claim numbers, missing dates of loss, blank statuses, claims assigned to an impossible policy period, and totals that materially differ from the source summary. The objective is not to force every report into a perfect template. It is to make uncertainty explicit before information reaches an underwriting decision.
Once the source data is structured, add context that helps a reviewer understand the risk. Compare claim dates to policy periods. Identify claims above a defined severity threshold. Highlight open claims, claims with growing reserves, repeated causes of loss, or clusters at a location. Compare loss activity with payroll, sales, vehicle counts, units, or values when the submission includes those exposures.
Enrichment should support judgment, not replace it. A recurring slip-and-fall pattern may be material for one retail risk and less relevant for another depending on controls, operations, and corrective actions. Similarly, a large claim may be an isolated event with a well-documented remediation plan. Structured loss data gives teams a faster way to ask the right follow-up questions.
Not every issue should stop the submission. Separate hard stops from review items. Missing a required policy term or receiving loss runs outside the requested experience period may warrant a return to the producer. A minor variation in carrier claim-status terminology may simply need normalization. An open, high-severity claim might route directly to an underwriter with the relevant source pages attached.
This exception-based approach keeps frontline teams moving. It also creates accountability: producers can obtain missing documents, operations can correct matching issues, and underwriters can focus on material risk questions rather than document cleanup.
Loss runs are inherently variable, so the strongest process balances automation with review. Straight-through processing makes sense when documents are legible, the carrier format is familiar, coverage periods are complete, and values reconcile within defined tolerances. Human review is appropriate when documents are handwritten, tables are fragmented, the account has complex historical coverage, or a high-value claim creates ambiguity.
Teams should also establish clear rules for versioning. A newer report may revise reserves or claim status without changing the claim number. If both versions are retained without a date-aware process, users can unknowingly review outdated incurred values. Store report dates, identify superseded files, and make the most current validated information clear in the workflow.
Security and access controls matter as well. Loss runs can contain sensitive claimant and medical-adjacent information. Limit access by role, preserve a record of changes and reviews, and avoid moving source files through uncontrolled inboxes or local folders.
The final step is delivery, not another export for someone to manually paste into a different system. Structured loss data should move into the systems and screens where agency teams prepare submissions and underwriters evaluate them. That may mean a submission workspace, rating environment, underwriting workbench, policy administration system, or data warehouse.
A connected workflow can present a concise loss summary while retaining claim-level detail and source-page evidence for review. It can also trigger follow-up tasks when a key field is missing or route a submission based on loss characteristics. Appulate supports this model by turning loss runs and other submission documents into connected insurance data that can extend existing workflows rather than force teams to replace them.
The practical measure of success is simple: underwriters should spend less time locating, reading, and reconciling loss information, and more time evaluating what it means for the account. When loss runs become structured, traceable, and available at the point of decision, faster submissions do not have to come at the expense of underwriting discipline.