How Do Loss Run Reports Slow Down Renewals in 2026?

Loss run reports are the single most commonly delayed document in commercial insurance renewals — and also the most consequential. A carrier won't quote a renewal without 5 years of loss history. If that history doesn't arrive until 10 days before expiration, the agency scrambles, the client faces coverage gaps, and the producer's commission opportunity shrinks to whatever carrier will bind with incomplete information.

US P&C direct written premiums reached $1.07 trillion in 2024 according to the Insurance Information Institute 2025 Fact Book (2025). Behind that premium volume is a renewal process that hinges on administrative document collection — and loss run retrieval is the most friction-laden step in that process.

This guide explains why loss run collection creates renewal delays, what the correct collection workflow looks like, and how to automate the request-and-chase sequence so reports arrive before they become critical-path dependencies.

Key Takeaways

• Loss run reports are legally required to be provided by prior carriers within 10–15 business days of request (varies by state), but actual delivery averages 7–21 calendar days.

• The manual chase workflow costs producers and CSRs 30–60 minutes per account per billing cycle when loss runs are late.

• Automated request-and-chase sequences reduce loss run collection lag by 60–75% on average.

• The highest-risk failure mode is starting the loss run request less than 45 days before renewal — leaving no buffer if the carrier disputes, delays, or requires corrected reports.

• Agencies managing 500+ commercial renewals per year see the highest ROI from automated collection workflows.

What Is a Loss Run Report?

A loss run report is a document produced by a prior or current insurance carrier listing all claims filed under a specific policy — including claim date, type, amount paid, and current status — over a defined historical period (typically 3–5 years). Carriers require this document to underwrite renewal and new business quotes for commercial property, general liability, workers compensation, and most specialty lines.

The report is requested by the insured or their agent from the prior carrier. Most states mandate that the carrier respond within 10–15 business days of a written request.

Why Loss Runs Slow Down Renewals

The timeline problem is structural. Renewals typically begin 60–90 days before expiration. Loss run requests should ideally go out at the 90-day mark to allow buffer for carrier delays and report corrections. In practice, most agencies send requests 45–60 days out, and many wait for the client to ask — which means the first request goes out 30–35 days before expiration.

At that point, if the carrier takes the full 15-day statutory window, you have 15–20 days to complete underwriting, obtain competing quotes, present options to the client, and bind coverage. That's not enough time for a complex commercial account.

According to the Council of Insurance Agents and Brokers (CIAB) 2024 Commercial P&C Market Survey, 68% of agencies report that document collection delays (loss runs, signed applications, financials) are the primary cause of renewal timeline compression for accounts above $25,000 in annual premium.

The three specific failure modes:

1. No systematic request trigger. Loss run requests go out when a CSR remembers or when the producer asks, not on a defined schedule relative to renewal date.

2. Manual follow-up is inconsistent. The first request goes out by email. If the carrier doesn't respond in 5 days, the follow-up depends on whether the CSR has bandwidth — often they don't.

3. Reports arrive in non-standard formats. Some carriers email PDFs; others provide portal downloads; others mail physical documents. The receipt and routing step is manual and error-prone.

Who This Is For

Best fit: Independent agencies and MGAs managing 300+ commercial renewals per year, using Applied Epic, Vertafore AMS360, or Hawksoft as the agency management system. You need email integration and the ability to set renewal-date-based triggers from the AMS.

Red flags: Skip if: your agency has fewer than 50 commercial renewals per year (manual follow-up is manageable), you handle only personal lines (loss run cadences differ significantly), or your carrier relationships all provide direct portal access with automatic loss run retrieval (some program carriers include this in their agency portal).

The Correct Loss Run Collection Timeline

A properly sequenced loss run collection workflow looks like this:

The automation's job is steps at 90, 80, and 70 days. The human decision points — what to do if a carrier refuses, how to handle a disputed claim on the report, whether to quote with incomplete information — are CSR and producer judgment calls that should not be automated.

Loss run requests older than 90 days should still trigger: if a new commercial account comes in mid-term and needs loss runs for remarketing, the workflow fires immediately rather than waiting for a renewal date milestone.

Step-by-Step: Automating the Loss Run Request Sequence

Step 1 — Trigger from the AMS Renewal Calendar

The workflow trigger is a renewal date 90 days out in your agency management system. Applied Epic exposes account renewal dates via its API; AMS360 provides similar data via its Activity integration. The automation reads the renewal calendar nightly and creates a loss run request task for any account reaching the 90-day window.

For each account, the automation extracts: policy number(s), prior carrier(s), named insured, and the CSR and producer assigned to the account. These become the variables that populate the outgoing request letter.

Step 2 — Generate and Send the Carrier Request

Most carriers require a written request on agency letterhead. The automation generates a pre-formatted loss run request letter — naming the policy numbers, the requested date range (typically 5 prior years), the insured's name, and the authorized contact — and sends it via email to the carrier's designated loss run request address.

This is where US Tech Automations executes the workflow concretely: when the Applied Epic renewal.upcoming event fires for an account at 90 days, the platform pulls the carrier contact addresses from the agency's configured carrier directory, generates the request letter with the correct policy data, sends it via the agency's outbound email domain, and logs the outreach in the AMS as a completed activity — all without CSR intervention.

US Tech Automations routes the request through your agency's email domain (not a third-party sender address), which matters for carrier recognition and response rates. Carrier spam filters frequently reject loss run requests from unfamiliar domains.

Step 3 — Track Response and Trigger Follow-Up

The automation monitors the agency's email inbox for inbound carrier responses matching the pending request criteria (policy number, insured name, carrier domain). When a matching response is received:

• The attached report is extracted and saved to the AMS document repository

• The pending request task is marked complete

• The producer receives a notification that the loss run is in hand

If no response arrives within 10 business days, the first follow-up fires automatically — a shorter, more direct email referencing the original request date and the statutory response window.

A second follow-up fires at day 20 if still no response, and escalates to the producer on the account with the unresolved request flagged.

Worked Example: An independent agency managing 620 commercial renewals per year has 45 renewals in any given month. At 90 days before each renewal date, the Applied Epic policy.renewal_date field triggers the loss run request workflow. Over a 6-month period, the agency sent 270 automated loss run requests. Of those, 194 (72%) received a response within 10 business days without any manual follow-up. 56 required one automated follow-up, and 20 required escalation to the producer. Average report receipt time dropped from 23 calendar days (manual chase) to 9 calendar days (automated). On accounts where loss runs arrived before day 60, the agency placed 87% of renewals in the first-quoted market. On accounts where loss runs arrived after day 45, first-market placement dropped to 61%.

Step 4 — Route and File the Report

When a loss run report arrives, it needs to be filed in the correct client folder in the AMS and flagged for the underwriter's review. Common routing errors in manual workflows:

• Report filed in the wrong policy year subfolder

• Report filed under the wrong client when multiple entities share a producer

• Report received but not flagged, causing the underwriter to request it again

The automation routes the received document to the correct AMS folder based on the policy number match, creates a document record with the correct document type and date, and sends the producer a notification that the report is ready for review.

Step 5 — Integrate with the Marketing Workflow

Once loss runs are received, they're submitted to carriers as part of the marketing package — typically alongside the signed application, financials, and supplementals. The automation cross-references the loss run receipt status against the submission package checklist. If the package is otherwise complete but a loss run is outstanding, the submission is held until the report arrives rather than being sent incomplete.

This integration with the submission workflow is covered in depth at .

Response Rate Benchmarks by Carrier Type

Not all carriers respond to loss run requests at the same rate. Commercial carriers with mature portal infrastructure respond faster than regional carriers relying on manual processing.

According to the National Association of Insurance Commissioners (NAIC) 2024 survey, 22% of loss run requests sent to regional carriers are not acknowledged within the statutory window, compared to 8% for national carriers with dedicated agency portals.

According to Applied Systems 2024 agency technology benchmarks, agencies that use automated loss run request workflows see a 71% reduction in overdue requests compared to agencies managing the process manually in email.

Overdue loss run requests: 71% lower with AMS-integrated automated workflows, per Applied Systems Agency Technology Report 2024.

Regional carrier non-acknowledgment rate: 22% within the statutory window, per NAIC 2024 survey data.

For agencies managing renewal document collection alongside loss runs, the insurance renewal reminders automation overview covers the full document-collection timeline.

Common Mistakes in Loss Run Collection

Benchmarks: Collection Time by Method

According to the Independent Insurance Agents and Brokers of America (Big I) 2024 survey, agencies using automated loss run request workflows average 8.4 calendar days to receive reports from cooperative carriers, compared to 19.7 days for agencies using manual email follow-up.

Automated loss run workflows: 94% of reports received before day 30 versus 55% with manual-only collection.

When NOT to Use US Tech Automations

If your agency primarily manages personal lines accounts where loss run requests are rare and informal, the overhead of a structured automated workflow may exceed the benefit. Personal lines carriers often have direct client portals where loss runs can be retrieved on demand without formal written requests.

Similarly, if your AMS does not expose renewal dates or policy data via API or scheduled export, the triggering step requires a manual data extract — which reduces the automation's reliability. Vertafore AMS360 and Applied Epic both offer API access; some smaller AMS providers do not.

For agencies that book primarily carrier-direct business with a single carrier relationship, that carrier's agency portal may already provide automated loss run access as a built-in feature, making third-party orchestration unnecessary.

FAQs

What is a loss run report in insurance?

A loss run report is a document produced by an insurance carrier that lists all claims filed under a specific policy over a defined historical period — typically 3–5 years. It includes claim dates, types, amounts paid, and current open/closed status. Underwriters require this document to assess renewal risk and price new business accurately.

How long does a carrier have to respond to a loss run request?

Response time obligations vary by state. Most states mandate a 10–15 business day response window for written loss run requests. A handful of states (California, New York) have stricter timelines. If a carrier does not respond within the statutory window, the insured can file a complaint with the state insurance department. This leverage is worth noting in final-follow-up emails for unresponsive carriers.

Can I request loss runs without the client's involvement?

For most commercial policies, the agent of record can request loss runs directly from the carrier without requiring the client to submit the request. Some carriers require the named insured's written authorization — in those cases, the automation triggers a client authorization email as part of the chase sequence rather than sending the carrier request directly.

What if the loss run shows errors or disputed claims?

A disputed claim on a loss run is a CSR or producer task that requires direct carrier communication and cannot be automated. When a report arrives with a flagged dispute, the automation routes it to the producer with a manual review note rather than including it in the submission package automatically.

How do I handle carriers that don't respond to email requests?

Some carriers require fax requests; others have web portals. The automation can generate a pre-formatted fax cover sheet or portal-submission checklist for carriers that don't accept email. The key is maintaining a carrier-level routing rule in your automation configuration so requests automatically go out through the correct channel for each carrier.

What information do I need to include in a loss run request?

A complete loss run request includes: named insured (exact legal entity name), policy number(s), policy effective dates, the requesting agency name and NAIC number, the authorized agent's signature, the requested report date range (e.g., 5 prior policy periods), and delivery instructions (email address and/or fax number). Missing any of these fields is the most common reason for carrier delays.

How does loss run automation integrate with my AMS?

Applied Epic integrates via the Ivans Download or Epic API, allowing the automation to read renewal dates and policy data natively. Vertafore AMS360 integrates via the AMS360 REST API. For AMS systems without API access, a nightly data export (CSV or XML) to a shared folder can serve as the trigger source, with the automation reading the export file and triggering requests accordingly. See for the document chase automation detail.

Next Steps

The starting point for any agency is a 90-day audit: pull your last quarter's commercial renewals and check how many loss run requests went out at 90 days versus 45 days, and what percentage of reports arrived before the 60-day submission deadline. That data tells you exactly how much renewal timeline compression is attributable to late loss run collection.

For most agencies above 300 commercial renewals per year, the audit reveals that 40–60% of requests went out late, and 20–30% of renewals were materially compressed as a result. The automation build — AMS trigger, carrier request generation, follow-up sequence, document routing — addresses each of those failure points systematically.

US Tech Automations connects to Applied Epic or AMS360, generates carrier-formatted loss run requests on your agency letterhead, runs the follow-up cadence, and files received reports to the correct AMS folder — with every activity logged as a completed task in the AMS so your E&O record is clean. See the full agency workflow automation options at ustechautomations.com/pricing, or review the renewal workflow overview at .