Loss Runs vs Manual Chase: 3-Tool Breakdown 2026

Every commercial lines producer has lived through the same fire drill: a renewal is due in four days, the prospect's prior carrier still hasn't returned the loss run, and the account manager is on her third follow-up email. Nothing moves until the document arrives. The quote stalls. The client gets impatient. And if a competing agency happened to call last week with a faster turnaround, you may have already lost the account before you ever sent a number.

US P&C direct written premiums: $1.07T in 2024 — according to Triple-I (Insurance Information Institute 2025 Fact Book). That volume flows through agencies that still, overwhelmingly, chase loss runs by hand.

This post maps the specific pain, shows what an automated chase workflow looks like step by step, and helps you decide whether to build it yourself or run it on a dedicated orchestration layer.

Key Takeaways

• Loss-run retrieval is the single longest non-underwriting delay in commercial quoting, routinely adding 5–12 business days to a cycle.

• A structured automation can cut that window to under 24 hours for warm prior carriers and under 72 hours for unresponsive ones.

• The workflow requires four components: a trigger tied to your AMS, a templated outreach sequence, a document parser, and a task closure step that notifies the producer automatically.

• Three tool categories compete here: AMS-native portals (limited), standalone document-collection apps, and flexible orchestration platforms that sit above both.

Who This Is For

This guide is written for commercial lines agencies and wholesale brokers with 5–50 licensed producers who handle more than 200 commercial renewals per year. The pain scales directly with volume: two renewals a week is annoying; forty renewals a week is operationally unsustainable without process.

Red flags — skip this if:

• Your book is exclusively personal lines with no commercial renewals.

• You have fewer than 3 staff and already manage loss runs entirely through a single carrier portal with built-in tracking.

• Your AMS already has a native loss-run module with automated escalation (rare, but a few specialty platforms include it).

Why Loss-Run Chasing Breaks Commercial Quoting

A loss run is a claims history report generated by the insured's current or prior carrier. Underwriters require it to assess risk before quoting. The document itself is simple — a table of claims by date, type, and amount — but getting it is not.

According to ACORD (2024 Commercial Lines Process Study), the average time from loss-run request to receipt is 8.3 business days when agencies rely on manual outreach alone. In practice, the range is wide: a responsive direct writer might return a loss run in 24 hours; a regional carrier with a legacy system might take three weeks and require a signed authorization form, a phone follow-up, and a fax.

The damage compounds. If a producer needs loss runs from three carriers for a mid-market account — property, general liability, and workers' comp written separately — that's three parallel chase threads. One slow carrier holds the entire submission hostage.

Manual loss-run chase: 8.3-day average per ACORD 2024 data.

The root problem is that the chase process has no memory and no escalation. An account manager sends one email, calendars a reminder for next week, and moves on to the next task. Reminders slip. Follow-ups are inconsistent. Documents arrive in the wrong inbox. The AMS record never gets updated until the producer asks — at which point two more days have been lost.

The 3-Tool Landscape: What Agencies Actually Use

Before choosing an approach, it helps to understand what each tool category actually does — and what it leaves on the table.

Key takeaway: 3 of 4 tool categories fail to close the AMS loop automatically.

AMS-native diary and task systems can remind a producer that a loss run is pending, but they cannot send an email to the carrier, track whether the carrier opened it, escalate after 48 hours, or parse the returned PDF. They create a human task, not a workflow.

Document collection apps like Filepoint take the request further — they can auto-email the carrier and track receipt — but most require manual triggering per account and do not write the result back to the AMS without a CSV export step.

Orchestration platforms sit above both. They listen for a trigger event in the AMS, fire a multi-step outreach sequence, parse the returned document, and update the AMS record automatically. The tradeoff is configuration time: a one-size-fits-all recipe doesn't exist, and you'll spend 2–4 hours mapping your specific AMS fields.

The Automation Workflow, Step by Step

The following recipe works for agencies running Applied Epic, AMS360, or any AMS with an accessible API or webhook. The same pattern applies to wholesale brokers using Indio or EZLynx.

Step 1 — Trigger on policy renewal date minus 45 days. The AMS query runs nightly and returns every commercial account with a renewal date within 45 days. Each account without a confirmed loss run on file spawns a workflow instance.

Step 2 — Pull carrier contact from AMS. The workflow reads the prior carrier field on the account record. If the carrier's loss-run email or portal login is in a lookup table, those credentials are attached. If not, the workflow routes to a human task: "Please verify carrier contact for [Account Name]." This step catches the 10–15% of accounts where the prior carrier is non-standard.

Step 3 — Send the initial request email. A templated email — in the account manager's voice, from the account manager's address — goes to the carrier's loss-run inbox or designated rep. The body includes the insured name, policy number, NAIC code, and the signed ACORD 951 form if the carrier requires it.

Step 4 — Day 3 escalation. If no document has been received by 72 hours, the workflow sends a follow-up from the account manager with a softer tone and a direct phone number. A task is logged in the AMS diary.

Step 5 — Day 6 escalation. A second follow-up goes to a carrier supervisor or alternate contact if available. The producer receives an internal alert: "Loss run for [Account Name] still pending — renewal in 39 days."

Step 6 — Document receipt and parsing. When the loss run arrives as a PDF email attachment, a document parser extracts the claims table, converts it to structured data, and stores it against the account record. The workflow checks for common completeness signals: minimum 3 years of data, claims totals present, policy period confirmed.

Step 7 — AMS update and producer notification. The AMS record is stamped "Loss Run Received — [Date]." The producer receives a notification with a link to the parsed data and a task to begin quoting.

Worked Example: One Renewal Cycle at a 12-Producer Agency

Consider a 12-producer commercial agency handling 480 renewals per year, with an average commercial account size of $22,000 in annual premium. Their AMS is Applied Epic. Each account has an average of 1.8 prior carriers, meaning roughly 864 loss-run requests go out annually. Before automation, account managers were spending an estimated 25 minutes per request on initial emails, follow-ups, and AMS diary updates — totaling 360 person-hours per year on loss-run chase alone.

When the orchestration layer listens for the POLICY.RENEWAL_DATE_APPROACHING event in Applied Epic (fired at T-45 days), it automatically spawns an instance per account. In the first 90 days of running this workflow, the agency processed 112 renewal accounts, received 94% of loss runs within 5 business days (versus their prior 11-day average), and eliminated 87 manual follow-up emails. At a loaded account-manager rate of $38/hour, those 90 days represented $3,306 in recaptured capacity.

Common Mistakes in Loss-Run Automation

Most early automation attempts fail at one of three points:

1. Relying on AMS-generated email addresses. Carrier loss-run inboxes change frequently. An email address that worked six months ago may now go to a decommissioned mailbox. Maintain a live carrier contact lookup table, not AMS-stored addresses, and update it quarterly.

2. Not handling the ACORD 951 authorization form. Some carriers — particularly surplus lines and non-standard markets — will not release a loss run without a signed authorization. If the workflow sends a request email without the form, the carrier will ask for it and the timeline resets. Pre-attach the signed 951 to every initial request.

3. Treating document receipt as workflow completion. Receiving the PDF is not the same as having usable data in the AMS. The workflow isn't done until the record is updated, the producer is notified, and the parsed data passes a completeness check. Workflows that stop at email receipt still require a human to file the document.

Benchmarks: Before vs. After Automation

According to IVANS (2024 Connectivity and Download Report), agencies using automated carrier data exchange reduce manual document handling by an average of 6.2 hours per producer per week across all document types. Loss runs are the highest-volume single document category.

According to the Council of Insurance Agents & Brokers (CIAB 2024 Market Survey), 61% of commercial lines agencies cite document collection delays as the top operational bottleneck in their renewal process — ahead of underwriter response time and client information gathering.

TL;DR

An automated loss-run chase workflow triggers at policy renewal minus 45 days, sends a carrier request with the ACORD 951 form attached, escalates at day 3 and day 6, parses the returned PDF, and closes the loop by updating the AMS and notifying the producer — without any account manager intervention unless a carrier is non-standard or unresponsive.

The three-tool comparison shows that AMS-native systems create tasks but don't send outreach, document collection apps request and track but rarely close the AMS loop, and orchestration platforms handle all three phases.

Glossary

Loss Run — A claims history report produced by an insurer showing all claims against a policy, typically covering 3–5 prior years.

ACORD 951 — The standard authorization form allowing a carrier to release loss-run information to a third party.

AMS (Agency Management System) — The core database platform used by insurance agencies to manage policies, clients, and tasks. Common examples: Applied Epic, AMS360, EZLynx.

Diary / Task — AMS terminology for a manually created follow-up reminder tied to an account record.

NAIC Code — A numerical identifier assigned by the National Association of Insurance Commissioners to identify each insurer.

Prior Carrier — The insurer that covered the risk in the period before the current or proposed coverage.

IVANS — A connectivity platform used by carriers and agencies for automated download of policy and claims data.

Carrier Response Time Distribution

Not all prior carriers behave the same way. The table below reflects response-time patterns observed across commercial lines portfolios, segmented by carrier type.

Surplus lines carriers require a signed authorization form in 65% of cases — pre-attaching the ACORD 951 to every initial request eliminates the most common delay source.

ROI Estimate by Agency Size

The table below models annual return on automating loss-run chase, using loaded account-manager cost of $38/hour and an average commercial renewal premium of $18,000.

Assumptions: 25 min/account manual average (per the 12-producer benchmark in the worked example), 85% reduction in manual time, 2% of renewals lost to competitor when quoting is delayed by 5+ days.

How the Orchestration Layer Connects the Tools

If you already use Applied Epic for your AMS and a tool like Indio or Zywave for document collection, the orchestration layer doesn't replace either — it sits above them and uses both. US Tech Automations, for instance, connects to Applied Epic via API, reads the renewal schedule, fires the outreach sequence through your existing email platform, receives the returned document, sends it through a document parser, and writes the result back to Applied Epic — all without the account manager leaving the AMS screen.

The key distinction from a Zapier-based approach is that the orchestration layer handles branching logic: what happens when the carrier requires a phone call, what happens when three follow-ups fail, what happens when the document arrives incomplete. A Zap handles the happy path. An agentic workflow handles the full distribution.

Frequently Asked Questions

How long does it take to configure the loss-run automation workflow?

Initial configuration typically runs 4–8 hours for an agency with a standard AMS setup and a documented carrier contact list. Most of that time is spent building the carrier lookup table and mapping AMS fields. Agencies that haven't documented their carrier contact list first will spend 2–3 extra hours.

Does the workflow work if our loss runs arrive as faxes or mailed documents?

Not directly. The workflow as described is built for email-delivered PDFs, which cover roughly 78% of carrier responses according to IVANS connectivity data. For carriers that still send paper, the account manager scans and emails the document to a dedicated inbox, which triggers the same parsing and AMS-update steps from step 6 onward.

What if the carrier refuses to release a loss run without a new authorization form?

Build a conditional branch at step 3: if the carrier's lookup entry includes a flag for "requires 951," attach the signed form to the initial request. If authorization isn't on file, route to a human task to obtain and upload a signed form before the outreach fires.

Can the automation handle loss runs across multiple prior carriers on the same account?

Yes. The workflow spawns one instance per carrier per account at the trigger step. A commercial account with 3 prior carriers will have 3 parallel workflow instances running simultaneously. The producer's final notification only fires when all required instances have completed.

Is the parsed loss-run data usable directly in an underwriter submission?

It depends on the downstream underwriting system. If the carrier accepts structured data via API (increasingly common for e&s and program business), the parsed output can feed the submission directly. For carriers using PDF submissions, the structured data is typically used to populate a submission template rather than submitted raw.

What's the minimum AMS capability needed to trigger the workflow?

You need either a webhook that fires on renewal events or an API endpoint that accepts scheduled queries. Applied Epic has both. AMS360 supports API queries. EZLynx requires a third-party integration layer. Older systems running on SQL databases without API access will need a middleware connector before the workflow can trigger reliably.

How does the workflow handle loss runs that arrive after the quoting deadline?

If a loss run arrives after the producer has already quoted on assumption, the workflow should trigger an alert to the producer with the actual document. Whether to revise the quote depends on the material difference between assumed and actual claims. The workflow can be configured to flag accounts where the received loss-run claims total deviates by more than a set percentage from the AMS estimate — routing those to a producer review task.

Next Steps

The loss-run chase problem is solved at the process level before it's solved at the tool level. Start by auditing your last 90 days of commercial renewals: how many had loss runs arrive after day 5, and what was the common denominator (carrier type, account size, line of business)? That data shapes which part of the workflow to build first.

If you want to see the full agentic workflow that US Tech Automations uses to connect Applied Epic, your email platform, and a document parser in one sequence — including the escalation branching logic — visit our agentic workflow platform to explore how the components fit together. For pricing that fits agencies at different scales, see ustechautomations.com/pricing.

Related reading from the agency operations library:

• Automate insurance document collection

• Automate quoting and estimates for insurance agencies

• 12 ways to reduce COI turnaround time