Subrogation referral: the facts a file needs before recovery is possible
In short
A subrogation referral is the handover of a paid claim to a recovery function, and a file is referable only when 4 facts are already in it: a responsible party identified well enough to pursue, an indemnity payment actually made, evidence that still exists, and a limitation period still running. Miss any one and the referral cannot succeed however clear the liability looks.
Key takeaways
- Referability is 4 conditions, not a judgement: named party, payment made, surviving evidence, live clock.
- A reserve is not a payment, so a file with a reserve and no disbursement has nothing to recover yet.
- Evidence decays faster than liability — the vehicle is sold and the scene cleared long before anyone screens.
- A contractual waiver of subrogation can defeat a file that satisfies all 4 conditions, so read the contract first.
- Limitation periods differ by jurisdiction and cause of action, and must be sourced rather than recalled.
A subrogation referral is the point at which a paid claim is handed to a recovery function to pursue a third party. Treat it as a test rather than a hunch: a file is referable when 4 facts are already present in it, and it is not referable when any 1 of them is absent, however obvious the liability looks.
Subrogation is the insurer's right, having paid, to step into the insured's position against whoever caused the loss. Where that right comes from — policy wording, statute or general law — varies by jurisdiction and by line. That is a legal question, and nothing here is legal advice; the operational question is whether the file can support the right at all.
The 4 facts a referable file already carries
Screening only works if each condition points at something recorded. The obstacle is rarely judgement; it is storage. 2 of the 4 live in free-text adjuster notes, where nothing downstream can read them.
| Condition | What the file must show | If it is missing |
|---|---|---|
| An identified responsible party | A named person, business or vehicle other than the insured, identified well enough to be served | There is nobody to pursue; the file is a loss, not a recovery |
| An indemnity payment made | A disbursement, its amount and the coverage it was paid under | Nothing has transferred to the insurer, so the referral is premature |
| Evidence that still exists | The damaged item, the scene record, statements taken while memory was fresh | Liability cannot be proved later, whatever the merits were |
| A limitation period still running | The loss or discovery date, the jurisdiction and the cause of action | The claim may be time-barred and the referral is worthless |
Conditions 1 and 3 decay; conditions 2 and 4 do not. That asymmetry is the argument for screening early. Recording a responsible party should also prompt a reserve review, since an expected recovery changes net exposure — an event in reserves that get set once and never move.
The clock is the condition everyone checks last
Limitation periods are set by statute and differ by jurisdiction and cause of action. Some run from the date of loss, some from the date it could reasonably have been discovered, and claims against public authorities frequently carry a much shorter notice requirement that bites first.
What changes by line of business and by jurisdiction
- Contractual waivers. Construction contracts and commercial leases routinely waive subrogation between the parties, defeating a file that meets all 4 conditions. Read the contract before referral, not after.
- Doctrines that rank the insured first. Several jurisdictions limit an insurer's recovery until the insured has been made whole, which changes what a recovery is worth rather than whether it exists.
- The line decides the counterparty. Auto damage, first-party property and benefits recoveries produce different responsible parties, different evidence and sometimes arbitration instead of litigation.
- Statutory schemes. Workers compensation and health benefit recoveries often run through their own mechanisms and notice steps, which a general rule mis-handles.
- The insured's deductible. It commonly rides along in the recovery, making the insured an interested party in a negotiation they are not part of.
3 files that look referable and are not
- A third party is named but not identifiable. A white van or a driver who left the scene is not a defendant. Identity sufficient for service is the condition, not the existence of someone at fault.
- The money is reserved, not paid. A reserve is an estimate of future cost; until a disbursement exists the insurer has stepped into nothing, so referral timing keys off the payment record.
- Liability is clear and the evidence is gone. The vehicle was sold, the unit replaced, the scene cleared. Merits survive; provability does not, which puts evidence preservation at first notice rather than at referral.
Referral does double duty here, and the 2 meanings should not share a rule set. A recovery referral asks whether a third party can be pursued; an SIU referral asks whether a claim warrants investigation, a different artefact specified in assembling a referral packet an investigator will use.
Liability decides whether a recovery is deserved. Identity, payment, evidence and the clock decide whether it is possible — and only the second question can be screened.
Two constraints follow. A screen that refers everything produces the fatigue in fraud indicators firing on a third of the book; and severity may order the recovery queue but must not decide referability, the boundary in what a severity score is allowed to decide. Making the 4 conditions readable fields is internal tools and ops work. This page sits in claims handling, fraud flags and recovery, part of insurance and claims software.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is a subrogation referral in claims handling?
It is the handover of a paid claim to a recovery function so the insurer can pursue the party that caused the loss. It is not a view that someone else was at fault: the file has to carry an identifiable responsible party, an indemnity payment already made, surviving evidence, and a limitation period that has not expired.
When should a claim be referred to subrogation?
As soon as a responsible party is identified and a payment has been made, not at file closure. The 2 conditions that decay — the identity of the third party and the survival of the evidence — worsen every week, while the payment record and the limitation date do not. Late referrals usually lose on provability rather than on merits.
Can a claim be referred before any payment is made?
Not as a recovery referral. Until an indemnity payment has been disbursed, the insurer has not stepped into the insured's position and there is nothing to recover. What should happen earlier is preservation: identify the third party, secure the evidence and record the dates, so the file is referable the day the payment clears.
Why do limitation periods have to be stored rather than remembered?
Because they differ by jurisdiction and by cause of action, they change, and some claims — notably against public authorities — carry far shorter notice requirements than the general period. A rule carrying a wrong period silently closes referable files. Keep it in a table with a citation and a date of last confirmation, checked with counsel in the relevant jurisdiction.
- subrogation
- recovery
- claims handling
- referral criteria
The work behind this page
Builds from our portfolio that this page draws on.
AP Copilot
An AI accounts-payable copilot that reads invoices, matches them to POs, and routes clean approvals
FintechPriorPilot
An AI prior-authorization and denial-management platform that auto-assembles and submits auths, predicts denials before submission, and drafts the appeals to recover revenue.
Healthcare AIAskVault
An AI internal knowledge-search platform that answers employee questions from your own docs — grounded in citations, with knowledge gaps surfaced and deflection tracked.
Productivity AIRead next
- Claims leakage: what the term actually counts, and what it quietly cannotLeakage is a subtraction where 1 of the 2 numbers came from a reviewer imagining a file that never happened. The standard is part of the answer.definition
- Reserves get set in the first week and never move until the file closesA reserve that has not moved in nine months is not a stable claim. It is an unasked question, and the repair is a set of file-event triggers rather than a better first estimate.diagnostic
- Fraud indicators fire on a third of the book and nobody reads them any moreInvestigators ignoring alerts is the symptom. The finding underneath is almost always that nobody can say what any single indicator's firing rate buys in accepted referrals.diagnostic
- The claim diary: a scheduling primitive, not a to-do listA diary entry is a dated obligation with an owner, an escalation target and a condition that says when it is met. Without that condition it is a reminder, and reminders leave files untouched.definition
- The oldest and newest files move; the ones in the middle of a caseload stopNew files move because a clock is running and old files move because someone escalated them. The band in between has no forcing function at all, and that is where inventory quietly accumulates.diagnostic
- Cause of loss: the coded field, and why the caller's story is not itThe loss narrative and the coded cause of loss are two fields with two jobs. Conflating them gives reporting nobody trusts and routing nobody can explain.definition
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation