June 12, 2026 · Updated September 5, 2026
Loss runs create two different kinds of work. The agency has to obtain the right reports, then read and use the information they contain. Faster document processing does not remove the time a carrier takes to provide a report.
Keep those stages separate when evaluating automation. The goal is a complete, usable claims-history package for the intended market, with missing reports and questions visible.
Confirm the requirement first
Ask the receiving market which policy years and valuation date it requires. Requirements vary by account, line, and carrier. A new venture or a specific program may have a different process from a mature commercial account.
List the policies and carriers involved before requesting reports. Confirm the named insured and any authorization needed to request or receive the information. Avoid using a generic template that asks for the wrong entity or period.
The loss-runs directory provides carrier-specific starting information. Verify the current carrier process before using a request method. Availability and turnaround should not be inferred from a general statement about state rules.
Track the request as an owned task
| Item | Why it matters |
|---|---|
| Insured and policy numbers | Helps the carrier identify the requested records |
| Requested years | Makes missing periods visible |
| Required valuation date | Distinguishes a recent delivery from a current report |
| Request method and authorization | Records how the permitted request was made |
| Request and follow-up dates | Gives the team an actionable next step |
| Owner and status | Prevents a report from sitting between colleagues |
Set follow-up timing using the account deadline and the carrier's process. If a report has not arrived, retain that status instead of marking the claims-history step complete because the request was sent.
Check a report when it arrives
Match the insured, policies, reporting period, and valuation date to what was requested. A PDF downloaded today can still report an older valuation. A packet can also omit a policy year or contain a similarly named entity.
Read the report's column definitions. Paid, reserve, incurred, expense, recovery, and claim status can be presented differently. Do not add figures or compare reports until the meanings and periods are clear.
An open claim's reserve is an estimate at the reported valuation date. A later report can change even if the policy period is the same. Keep the report date attached to a summary so the next person understands the basis.
Evaluate extraction on a varied sample
Choose reports in formats the agency actually receives, including a scan and a file with an open claim. Check the values and whether a reviewer can trace them back to the correct row and page. Test what happens when text is unclear or a column label is ambiguous.
A tool should make missing or uncertain information visible, but do not assume it flags every error. Define the agency's review for totals, periods, open claims, and important loss details. Retain the source report alongside any extracted data.
Prepare the next deliverable
A reviewed claims table can help the team prepare a submission or answer an underwriter's question. Keep any summary factual and tied to the source. An unexplained loss pattern needs a client or carrier answer, not an invented explanation from the software.
Relay's document parsing workflow can be evaluated with supported loss-run documents. Inspect the output, missing information, and correction effort before incorporating it into your process. Confirm any automated requesting or portal retrieval separately.
Measure request waiting time, active preparation time, and review time independently. That shows whether the improvement came from better follow-up, faster document preparation, or both.
Review a loss-run document workflow with the reports your team uses.