# Loss run automation | Working Pace

Canonical: https://workingpace.com/solutions/loss-run-automation
Updated: 2026-10-22

- [Home](https://workingpace.com/)
- [Workflow solutions](https://workingpace.com/solutions)
- Loss run automation

Loss run automation

# From authorization. To records received.

Custom loss run request automation for commercial insurance operations. Connect client approvals, carrier communication, incoming records and exceptions in a workflow built for your team.

[Discuss this workflow](https://workingpace.com/book)

Image: A carrier follow-up tied to the original loss run request.

The workflow

## Complete means every required record.

- ### Authorization

Identify the client, carriers and policy years.
- ### Retrieval and follow-up

Collect available records and pursue missing ones.
- ### Complete or review

Return the full set or an explicit exception.

## Track the request all the way to completion.

A loss run request may depend on a signed authorization, several carriers and multiple policy years. A sent message is not a completed request.

We model the required records and keep each communication connected to the original request. The system can distinguish received items, missing items and exceptions needing a person.

## Let the agent coordinate the repeat work.

The real project in our case study coordinates client signature requests, carrier follow-up, incoming email and attachment handling, and CRM updates. AI handles email and document context; rules govern authorization and state changes.

Your implementation needs its own carrier access, approved communication rules and completion conditions. We test representative requests before expanding the rollout.

[Read the carrier-request case study](https://workingpace.com/work/carrier-request-agent)

## Return the exception with its context.

A missing year, unavailable record or ambiguous response should arrive with the original request, communications and actions already taken. That makes review useful rather than another investigation.

Measure completion within a fixed request window, with consistent inclusion rules. Track outstanding and unavailable records separately so changing labels cannot inflate the result.

A little clarity

## Questions worth asking.

Is this a subscription product?

Working Pace designs and implements custom work for each business. This page describes a capability we can build, not an off-the-shelf software subscription.

What do you need to assess a project?

A walkthrough of the current process, the tools involved and a few redacted examples are a useful start. We can help define the outcome before a full specification exists.

Keep exploring

## A useful next step.

[Commercial insurance](https://workingpace.com/industries/commercial-insurance)[Carrier-request agent case study](https://workingpace.com/work/carrier-request-agent)[How to automate loss run requests](https://workingpace.com/guides/loss-run-automation-guide)[AI agent development](https://workingpace.com/services/ai-agent-development)

Start where you are

## Discuss this workflow.

Start with the task, the tools and what you want to improve. We will help define a practical way forward.

[Book a conversation](https://workingpace.com/book)

---

Contact: jake@workingpace.com
Book a conversation: https://workingpace.com/book