Automate Loss Run Requests: Save 12 Hours 2026

Key Takeaways

• A single commercial renewal can require loss runs from three to five carriers, and chasing them by email is the slowest step in the entire renewal underwriting cycle.

• A well-built workflow can cut roughly 70% of manual loss run chasing time by templating requests, tracking responses, and parsing returned PDFs automatically.

• The biggest payoff is not labor savings alone — it is submitting clean, complete renewal packages 10 to 14 days earlier, which protects retention and remarketing leverage.

• Loss run automation complements your AMS (Applied Epic, AMS360, HawkSoft) rather than replacing it; the workflow lives in the gaps your management system leaves open.

• US Tech Automations sits across email, carrier portals, and your AMS to orchestrate the request-track-parse-file loop most agencies still run by hand.

A loss run is a carrier-issued claims history report — typically three to five years of paid and reserved losses on a policy — that underwriters require to price a renewal or a remarketed risk. The problem is rarely the report itself. It is the chase: emailing a carrier service desk, logging into a portal you forgot the password to, waiting a week, re-sending, and finally receiving a PDF that someone has to read, summarize, and drop into the AMS. This guide is a concrete workflow recipe for automating that loop, with the ROI math agencies actually care about.

TL;DR: Templating loss run requests, auto-tracking carrier responses, and parsing returned PDFs removes the most error-prone manual step in renewal underwriting. Most commercial agencies recover 8 to 12 hours per CSR per week and submit renewal packages roughly two weeks earlier.

The independent agency channel handles the majority of commercial property and casualty premium in the United States, independent agencies write a majority of US commercial P&C premium according to the Big "I" 2024 Agency Universe Study. That share is why renewal throughput is an existential metric for an agency: every commercial renewal that slips because a loss run never arrived is premium at risk of being remarketed away.

Who this is for

This recipe is built for commercial lines agencies and MGAs that run 50 or more commercial renewals a month across multiple carriers, with at least one or two account managers whose week is dominated by document chasing. It assumes you already operate a real agency management system and have carrier portal credentials on file.

Red flags — skip this if: you write fewer than 20 commercial renewals a year, you are a pure personal-lines shop where carriers push loss data automatically, or your team is under three people and the chasing genuinely fits in the margins of the day. Automation pays back on volume and repetition; below a certain renewal count, the build cost outruns the savings.

Why the loss run chase quietly wrecks renewal timelines

The US property and casualty market is enormous — US P&C direct written premiums exceed $900 billion annually according to the Insurance Information Institute 2025 Fact Book — and most of that premium renews on an annual cycle. Each renewal triggers the same predictable scramble 60 to 90 days out: identify which carriers hold the expiring coverage, request loss runs from each, and assemble a submission for the incumbent and any remarket targets.

When that request process is manual, three failure modes compound. Requests go out late because no one owns the 90-day trigger. Responses arrive on no schedule and land in a shared inbox where they are easy to lose. And the returned PDFs require a human to read claim counts, loss ratios, and large-loss detail before underwriting can begin. The cycle-time cost is real: claims and document handling in P&C still moves slowly, with average auto claim cycle time measured in multiple weeks according to the NAIC 2024 claims processing benchmark — a useful proxy for how long carrier-side document operations take to respond.

An agency that submits renewal packages two weeks earlier doesn't just save labor — it gives underwriters time to negotiate, which is where retention is won or lost.

The point of automating loss run requests is not to eliminate the underwriter. It is to make sure the underwriter is never the one waiting on a document.

The workflow recipe: request, track, parse, file

Here is the end-to-end loop, broken into the four stages that matter. Each stage is something you can build with a workflow platform sitting on top of your AMS and email.

1. Trigger the request at T-minus-90. When a policy crosses 90 days from expiration in the AMS, the workflow fires automatically. No human has to remember.

2. Generate the carrier-specific request. The workflow pulls policy number, named insured, and effective dates from the AMS and drops them into the right template for each carrier — some accept email, some require a portal submission.

3. Send and log. The request goes out and is logged against the renewal as an activity, so the entire team sees the request exists and when it was sent.

4. Track the response window. If no loss run arrives within the carrier's typical turnaround, the workflow escalates: a polite second request, then a flag to the account manager.

5. Capture the inbound document. When the carrier replies, the workflow recognizes the loss run attachment and routes it to the correct renewal file.

6. Parse the PDF. Claim counts, paid and reserved totals, and loss-ratio inputs are extracted into structured fields the underwriter can read at a glance.

7. Attach to the AMS and notify. The parsed summary and original PDF are filed against the renewal in the AMS, and the account manager is notified the package is ready.

8. Surface the exceptions. Anything the parser can't read cleanly — a scanned image, an unusual format — is flagged for a human instead of silently failing.

The parsing step is where most teams under-invest. Extracting claim data from carrier loss runs is exactly the kind of document work that document-extraction automation handles well; our guide to automating document upload from insureds into Applied Epic covers the same parse-and-route economics inside the AMS, and the pattern transfers cleanly to inbound loss runs.

The trigger stage matters more than it looks. Most renewal slippage traces back to a request that went out late, not a carrier that responded slowly. A meaningful share of insurance operations leaders cite document and data handoffs as a top efficiency drag, according to a Deloitte 2024 insurance operations outlook, and the renewal request is the single most repeatable of those handoffs. Automating the T-minus-90 trigger removes the human memory dependency entirely — the workflow doesn't get busy, go on PTO, or forget which carriers hold the expiring lines.

The escalation logic is equally underrated. A carrier that hasn't responded in its normal window needs a second nudge, not a silent wait. Insurers continue to invest heavily in process technology precisely because manual follow-up doesn't scale; a majority of carriers and intermediaries are prioritizing automation investment, according to a McKinsey 2024 insurance technology survey. Your agency benefits from that same logic on the distribution side: a timed, automatic second request closes far more loss runs before the deadline than a CSR who has to remember to chase.

Building it on top of your stack

The single most common mistake is trying to make the AMS do everything. Applied Epic, AMS360, and HawkSoft are systems of record — they store policies and activities well, but they were never designed to chase carriers across email and a dozen portals. The workflow layer lives above the AMS and reaches into it.

US Tech Automations is built for exactly this orchestration role: it watches the AMS for the renewal trigger, composes and sends carrier requests, monitors the inbox for inbound loss runs, parses them, and writes the result back as an AMS activity. The system of record stays the system of record; the chasing stops being a person's job. For commercial agencies running an M&A integration where two AMS instances coexist, our agency M&A tech integration checklist walks through keeping a single renewal workflow alive across both.

If your team is also drowning in certificates of insurance, the same request-track-file pattern applies; see our guide to 12 ways to reduce COI turnaround time for the parallel build.

The ROI math

The savings come from three buckets: direct labor, faster cycle time, and reduced leakage (renewals lost because a package was late). Labor is the easiest to quantify, so start there.

A commercial CSR spends meaningful time per renewal on loss run logistics alone — requesting, chasing, reading, and filing. Across a book of several hundred renewals a year, that adds up to multiple full weeks of recovered capacity. A well-built workflow cuts roughly 70% of manual chasing time, which on a typical mid-size commercial book translates to 8 to 12 hours recovered per CSR per week.

The labor recovery alone usually justifies the build. The retention upside — submitting clean packages early enough that the underwriter can actually negotiate — is the larger but less visible prize. Agencies focused on the labor line specifically should read our analysis of how to save 30% on CSR labor through agency automation, which models the staffing math in detail.

Comparison: where loss run automation fits among your tools

You may already own pieces of this. The point of the table below is honest scoping: these tools each do something well, and a workflow layer fills the gap between them.

When NOT to use US Tech Automations: if your carriers already push loss runs to you automatically on renewal — some appointed-carrier programs do — then the request-and-chase problem doesn't exist and a workflow layer adds cost without value. If you're a small personal-lines agency, Applied Epic or your AMS workflow tools alone are enough. And if your real bottleneck is comparative rating rather than document chasing, Tarmika solves a different problem better than any orchestration layer will. Automation earns its keep when the chase is genuinely the constraint.

Tarmika wins on multi-carrier commercial quoting; DocuSign wins on signature workflows; Applied Epic wins as the system of record. None of them was built to chase, parse, and file loss runs — which is precisely the gap a workflow platform closes. For agencies weighing AMS choices first, our Applied Epic vs AMS360 comparison is the right starting point.

Common mistakes when automating loss runs

The teams that get the least from this build tend to repeat the same errors. Automating a broken process just makes the breakage faster.

• Skipping the exception path. Some carrier loss runs are scanned images that no parser reads cleanly. If the workflow has no human fallback, those renewals silently fall through.

• Over-templating the carrier request. Each carrier wants the request a slightly different way. One generic template gets ignored or bounced; build per-carrier variants.

• Not writing back to the AMS. If the parsed result lives in the workflow tool and never lands in the system of record, the underwriter still has to go looking. Always close the loop into the AMS.

• Triggering too late. A T-minus-60 trigger leaves no slack for a slow carrier. T-minus-90 is the standard for commercial.

According to a Deloitte 2024 insurance operations analysis, document-heavy renewal processes are among the highest-leakage workflows in P&C distribution — which is to say, fixing the chase is rarely the lowest-value project on the list.

Glossary

• Loss run: A carrier-issued claims history report, usually covering three to five years, required for renewal and remarketing.

• Renewal underwriting: The process of re-pricing an existing risk at expiration, which depends on current loss data.

• Carrier loss run portal: A web portal where appointed agencies request and download loss runs for a specific carrier.

• Loss ratio: Incurred losses divided by earned premium — the headline number underwriters read off a loss run.

• AMS: Agency Management System (Applied Epic, AMS360, HawkSoft) — the agency's system of record.

• Remarketing: Shopping an account to alternative carriers, which requires a fresh, complete loss run package.

Frequently asked questions

How long does it take to get a commercial loss run from a carrier?

Carrier turnaround typically runs from a few days to two weeks, with no reliable schedule. That variability is exactly why automated tracking and escalation matters — a workflow re-requests on a timer instead of waiting for a human to notice the gap.

Can I automate loss run requests without replacing my AMS?

Yes. The workflow layer sits on top of Applied Epic, AMS360, or HawkSoft. It reads the renewal date, sends the request, and writes the result back as an activity. The AMS stays your system of record; only the chasing is automated.

What does it cost to automate loss run requests?

Cost scales with renewal volume and the number of carriers you work with, not with a flat license. Most commercial agencies see the labor recovery alone — 8 to 12 hours per CSR per week — pay back the build within the first renewal cycle. See US Tech Automations pricing for scoping.

Does loss run automation work with carrier portals, not just email?

Yes, though portals are harder than email. A robust workflow handles both — composing and submitting portal requests where carriers require them, and parsing the downloaded result the same way it parses emailed PDFs.

Will automation read a scanned image loss run?

Modern document extraction handles most scanned loss runs, but image quality varies. A well-designed workflow flags anything it can't read cleanly for a human rather than guessing — preserving data integrity for underwriting.

How early should I trigger the loss run request?

The commercial standard is 90 days before expiration. That leaves room for a slow carrier, a second request, and time for the underwriter to negotiate once the package is complete.

Get started

Loss run chasing is the clearest single-workflow win in renewal underwriting: high volume, high repetition, and a direct line from "package submitted earlier" to "renewal retained." If your CSRs are spending a day a week emailing carrier service desks, that is the workflow to automate first.

US Tech Automations builds the request-track-parse-file loop on top of your existing AMS and carrier connections, so the chase stops being a person's job. Start at the home page or scope a build directly through our pricing page. For the broader picture on where insurance automation is heading, read our overview of the state of insurance automation in 2026.