Skip to main content

SortSpoke for Loss Run Reports

Turn any carrier's loss runs into clean, verified claims data

Every field extracted from a loss run traces back to the source document and the person who reviewed it — bring your own loss runs and see live results, not a canned demo.

SortSpoke is insurance document AI: we turn submissions, loss runs, and the rest of your document intake into verified data — inside the systems your team already works in.

  • Extract carrier, claim, and loss details from any loss run format
  • Eliminate manual data entry from scanned PDFs, spreadsheets, and multi-carrier documents
  • Prioritize high-potential submissions with enriched, structured data
  • Every value verified by your reviewers and traceable to its exact spot in the source PDF
Your Options

Four ways to solve loss run data extraction

If you're evaluating how to get clean claims data out of loss runs, you're weighing the same four options as every underwriting team. Here's the honest comparison.

1. Keep it manual

Underwriters or assistants rekey claims data line by line. Accurate on any format — but it doesn't scale. A multi-carrier loss run takes hours, and industry estimates put up to 40% of underwriters' time on administrative work.

2. Send it to a vendor's review pool

A human-powered service keys the data for you. It works — but the vendor's staff sit in your critical path: throughput depends on their headcount and shift coverage, turnaround is measured in hours or days, and cost scales with people rather than documents.

3. Point a generic tool at it

Generic document AI — or a DIY LLM pipeline — handles clean, consistent forms well, then breaks on the messy reality of multi-carrier loss run formats. And when it's wrong, nothing governs, verifies, or traces the output.

4. Automation-first AI

Straight-through platforms route only what the model itself flags as low-confidence to review. A confidently-wrong extraction never surfaces — you find it at renewal, or in an audit.

SortSpoke's approach: governed extraction

AI does the extraction. Your people — and only your people — verify it. You set the confidence thresholds that decide what gets reviewed, and every field traces back to its exact place in the source document. Accuracy is governed, not promised.

How SortSpoke is different

Built for underwriting teams that need the speed of AI and the accountability of their own reviewers.

You set the confidence thresholds

Every extracted field either clears the confidence bar you set or goes to your reviewers. What gets human review is governed by your rules — not by the model's opinion of itself.

Every value traces to its source

Click any extracted value to see exactly where it came from in the source PDF — with an audit trail of who reviewed it, what changed, and when. Your underwriters don't have to trust the AI; they can check it.

Inside the systems you already run

SortSpoke is one of the few extraction platforms built to run inside your underwriting workbench, intake inbox, or policy admin system. What lands in your system of record is verified data your team can check — not a recommendation you have to trust.

A product, not a service

There's no vendor review pool behind the curtain. Cost scales with documents, not people, and your throughput never depends on anyone else's headcount or shift coverage. The only humans in the loop are yours.

How It Works

Extract Data Quickly

From messy, multi-carrier loss runs to clean claims data — here’s the pipeline.

Six-step automated document processing flow: ingest, pre-process, classify, extract, validate with human review, and integrate - from document to data in minutes

Embedded in the tools your team already uses

SortSpoke isn't another portal. Loss run extraction and underwriter review run inside your existing underwriting workbench, intake inbox, or policy admin system — so adoption doesn't depend on changing how your team works.

AI extracts and standardizes the claims data; your underwriters review and approve without leaving the tools they know. The clean loss data lands in your system of record, ready for risk assessment.

Stylized illustration of SortSpoke's extraction workbench embedded in an underwriting system, showing a carrier loss run report with highlighted extractions and the Loss Runs field panel

Eliminate the Loss Run Bottleneck

5X

Process loss run submissions 5X faster — Great American.

>95%

Extraction accuracy on real-world loss runs, measured on production data — and every field either clears the confidence threshold you set or your reviewers make the call.

30m

Live in 30 minutes. Go from sign-up to extracting your first loss runs in under half an hour.

Customer Reviews

What SortSpoke Customers Say

Untitled design (17)
P&C Manager
SORTSPOKE CUSTOMER
"Feedback has been positive. The system is intuitive, so there was limited training. People are really excited about the process and what they can do with SortSpoke. We’re seeing good adoption.”
Untitled design (21)
Manager, Global Digital Underwriting
RGA International
"We’ve achieved great accuracy levels with SortSpoke. The training time was really quick and easy. We evaluated quite a few different systems and SortSpoke really stood out among the others"
Untitled design (16)
VP Underwriting Business Solutions
RGA
“SortSpoke has made one of the messiest and most manual problems in underwriting easy to solve. Turning documents into high-quality data is a core capability that enables RGA to deliver the future of digital life underwriting with faster review times, better risk assessment and greatly reduced the manual effort."
Untitled design (14)
Assistant VP of Analytics
SORTSPOKE CUSTOMER
"You guys are my favorite people.SortSpoke is my favorite vendor by far, and I don't say that lightly. I work with a lot of vendors."
Untitled design (19)
Assistant VP of Analytics
Sortspoke customer
“I really like SortSpoke because of the ability to extract information from unstructured documents in a user-friendly, interactive way. No other product on the market does that. Others want you to create models, and pull information out, but they don't have the same kind of interface that allows you to correct through workflow."
SortSpoke Security (500 x 800 px)-1

SortSpoke Platform | Security

Built for Enterprise

At SortSpoke, we understand that document processing in insurance and financial services demands the highest levels of security and compliance. Your sensitive data never leaves your control.

Our Security Foundation:

End-to-end encryption with TLS 1.2+ in transit and AES 256 at rest

SOC 2 Type II compliant infrastructure built on AWS

Role-based access controls

Comprehensive audit logging and monitoring

By clicking Book Now you're confirming that you agree with our Terms and Conditions.

See your loss runs processed 5X faster

Enter your email and go straight to the calendar — pick a demo time that works for you. Then bring your messiest loss runs and watch the extraction live.

What is a loss run?

Quick reference: what a loss run is, what one contains, and how to read it.

Definition

A loss run is a report issued by an insurance carrier that lists a policyholder's claims history over a set period — typically three to five years.

Each entry records the claim date, type, status, amount paid, and reserves. Underwriters use loss runs to assess risk and price renewals. Every carrier formats them differently, which is what makes them slow to process at scale.

Sample insurance loss run report example with key fields annotated: claim number, date of loss, status, paid, reserved, total incurred, and valuation date (synthetic document)
An example loss run report with the key fields annotated. Synthetic sample — fictional carrier, insured, and claim data.

What is in a loss run report?

A loss run report typically contains the policy number and effective dates, a line per claim with date of loss and claim status (open, closed, or reopened), amounts paid, outstanding reserves, and a total incurred figure. Carriers vary in whether they include claimant detail, cause-of-loss coding, and subrogation recovery.

How far back does a loss run report go?

Most submissions ask for three to five years of loss history. A 5 year loss run report is standard for commercial lines; a 3 year loss run report is common for smaller accounts.

How do you read a loss run report?

Read a loss run by first checking the policy period and whether the report is valued to a recent date. Then review each claim line for status, paid amount, and reserves. Total incurred is paid plus reserves. Open claims with large reserves carry the most forward-looking risk.

How long does manual loss run review take?

Simple (1–3 pages): 15–30 minMulti-year: 1–3 hrsMulti-carrier: 4+ hrs

Industry estimates put up to 40% of underwriters' time on administrative work — much of it manual document handling like loss run processing. At 1,000 submissions a month, that's roughly 500–1,000 hours of underwriter time on loss run processing alone — time an automated extraction workflow gives back to risk assessment.

Loss Run Resources

Everything you need to know about modernizing your loss run workflows

What is a Loss Run Report
Insurance
What is a Loss Run Report
by SortSpoke
Learn what loss run reports are, why they matter in underwriting, and how to process them efficiently. Complete guide on loss run report analysis and automation.
5 Best Loss Run Processing Tools (2026)
Insurance
5 Best Loss Run Processing Tools (2026)
by SortSpoke
Compare the top 5 loss run processing solutions: BPO, platform integrations, AI automation, and broker-side retrieval and extraction tools. Find your fit.
Insurance-Specific AI with Human-in-the-Loop Outperforms Generic AI
Insurance
Insurance-Specific AI with Human-in-the-Loop Outperforms Generic AI
by SortSpoke
Generic AI hallucinates 15% of the time. Learn why insurance-specific AI with human-in-the-loop validation eliminates this risk + earns underwriter trust.