Find the money owed back, and the demands owed out.
Recovery hides in police reports, contractor invoices, and engineers’ findings, and inbound demands arrive as e-subro packages on files nobody is watching. Isomer™ Signals reads each one on arrival, flags both directions, and checks the claim again as the facts come in.
Built onIsomer Graph · Isomer Signals
Three-vehicle collisionCommercial auto
Reading on arrival- Day 2High
Police report · PDF, 6 pages
Vehicle 3 cited for following too closely.
- Day 9High
Email from another insurer · e-subro PDF attached
Demand for reimbursement of $19,800.
Recovery owed back, demand owed out
Third-party fault on day 2 · inbound demand on day 9
Act
- Recovery referred to the subrogation team
- Inbound demand routed to the liability team
In production at a large commercial carrier
Recovery was hiding in plain sight.
6%
of new claims carried a subrogation opportunity, a rate its subrogation leaders confirmed.
4 in 10
signals in the first two weeks were recovery or inbound subrogation.
2x
the claims with a signal once recovery was counted, from 14% to 28%.
Two directions, two teams.
Subrogation opportunity
Money owed to you
Third-party fault in the file: a contractor’s error, a product defect, a utility failure, another driver. Isomer flags the recovery for the subrogation team, with the page that shows it.
Inbound subrogation demand
Money asked of you
A demand from another insurer, a recovery vendor, or an attorney, often an attachment on a routine email. Isomer routes it to the liability team before the response window closes.
Recovery, with guardrails.
| Example signal | What it catches | Typical severity |
|---|---|---|
| Subrogation opportunity | Third-party fault indicators above a dollar floor you set | High |
| Inbound subrogation demand | A third party asking you or your insured to reimburse a loss it paid | High |
| Contractual risk transfer | A waiver of subrogation or indemnity limit, so no one chases a recovery the contract rules out | Medium |
| Statute of limitations countdown | The time bar on a recovery or claim, before it runs | Critical |
Examples from the 90+ detectors in the signal library.
Checked again as the facts arrive.
Most recoveries aren’t visible at first notice. They show up when the police report, the fault finding, or the engineer’s report lands, so Isomer reads the claim again each time one does.
Stage 1
At first notice
Obvious third-party fault, flagged the day the claim is created.
Stage 2
When the evidence lands
Police reports, medical records, and expert findings re-checked for fault as they arrive.
Stage 3
At the liability decision
Once the adjuster confirms fault, the subrogation file is opened, so the handoff isn’t late.
Responses run on Isomer Actions where configured: subrogation opened in the claim system, weekly recovery reports, and a closed-file review for missed recoveries.
Lines of business Commercial auto · General liability · Commercial property · Workers’ compensation
From the production record
Precise enough to trust.
Found in the attachment
A $19,800 e-subro demand from a national auto insurer, against a construction materials company, flagged from the PDF attached to the email.
Stopped by the contract
A recovery against a broker was flagged, then held back: a contractual waiver of subrogation ruled it out.
Held below the floor
A $360 shortage on a parcel shipment was recognized as a recovery, and held because it fell under the carrier’s threshold.
Find the recoveries on your book.
In our workshop, your team builds synthetic claims modeled on your book and sees Isomer find the recoveries. A pilot then finds those still inside the time bar on your own claims.