Subrogation recovery,
powered by AI.
Reviewed by you.
Certvian turns messy claim files into demand-ready cases, assists your adjusters through the recovery workflow, and drafts the demand package, so your team pursues recoveries that would otherwise be written off.
Working in ten minutes. No integration project: if your team can forward an email, it can run Certvian.
Sarah Okafor
Acme Logistics · Claims
Fwd: Rear-end collision on I-71
VerifyingReading the forwarded thread…
The invariants
Three rules the system cannot break.
No claim without a citation.
Every AI statement links to the exact passage it came from: page, paragraph, timestamp. A grounding judge verifies each quote verbatim; anything it can’t verify is held back and labelled, never presented as fact.
Evidence · [1]
…Progressive’s adjuster accepts liability for the rear-end collision[1], verified verbatim against the Apr 2 email.
Nothing leaves without approval.
An outbound email structurally cannot exist without a recorded human approval, enforced in the database rather than just the interface. The AI drafts and proposes. People decide.
Approval gate
Every model call accounted for.
Each AI run logs its prompt version, cost, latency, and output. When a regulator, auditor, or arbitrator asks how a number was produced, the answer exists.
Run log
drafting.v12 · $0.041 · 3.2s · logged
The status quo
Subrogation dollars are lost quietly.
Nobody decides to forfeit a recovery. It happens by default: a referral not made, a deadline not watched, a file not worth the hour. The leak is silent, which is why it survives every process fix. Certvian is built to make it loud.
At risk this week · demo org
$0
Three files, one deadline, visible only because the review was automatic. Every leak below surfaces here, before it becomes a write-off.
Needs attention · this week
ACM-2026-00112 · Auto intersection · GEICO
$7,20012 days to statuteHigh priority · unworkedACM-2026-00022 · Burst pipe · Liberty Mutual
$12,000Blocked 11 daysWaiting on police report · request draftedACM-2026-00130 · Auto side-swipe · Nationwide
$9,200Ready, unassignedReconstructed two days ago
Priority recomputed as deadlines approach
Manager home · live
01The referral never happens
An overloaded adjuster closes the file as a paid loss. The subrogation potential was real; it just needed an hour nobody had. When every forwarded claim is reviewed automatically, referral stops depending on attention.
02The statute clock runs silently
A missed statute of limitations isn’t a delay; it’s a forfeiture, written off without anyone deciding to. Certvian computes the deadline the day a case is created and escalates as it approaches.
03Small files don’t justify the hour
Below a threshold, manual review costs more than it recovers, so those dollars are abandoned by policy. When reconstruction takes minutes instead of hours, the $5,000 rear-end is worth working again.
04The closed book stays closed
Files closed without pursuit hold recoveries no one will ever look for, and a look-back is a project nobody staffs. Unless the review is automatic, those dollars stay buried.
How it works
From a forwarded email
to a recovered dollar.
Certvian is an operations layer on top of the systems you already run. There is nothing to integrate on day one; the pipeline starts where your team already works: the inbox.
Sarah Okafor
Acme Logistics · Claims
Fwd: Rear-end collision on I-71
VerifyingCase intelligence
The case file, reassembled.
A claim arrives as a mess of quoted threads, a scanned crash report, a recorded-statement summary, a repair invoice. Certvian reads it the way your best analyst would: it builds the chronology, maps who is adverse to whom, and writes the liability argument under the governing state’s comparative-negligence rule. An admission buried in paragraph two of an adjuster’s email becomes a starred event on the timeline, with the sentence it came from one click away.
Chronology · ACM-2026-00014
- Mar 11
Rear-end collision on I-71 SB[2]
Insured stopped at signal; struck from behind.
- Mar 11
Ohio Traffic Crash Report filed[2]
Officer assigns fault to Unit 2.
- ≈ Mar 18
Recorded statement · D. Kim[3]
Driver describes looking away before impact.
Conflict flagged: Statement says traffic “suddenly stopped”; the crash-report narrative records the insured already stopped at the signal.
- Mar 24
Liability admission[1]
Progressive’s adjuster accepts liability in writing.
- Mar 28
Acme pays insured $8,750[5]
First-party payout; subrogation flag set.
- Nov 2027
Statute of limitations
Ohio two-year property-damage window: computed, watched, escalated.
Subrogation viability
A verdict you can defend, not a score you have to trust.
Every case gets a rating, a recovery estimate anchored to the damages you actually paid, and a calibrated confidence figure, with every supporting and risk factor cited to its source. Even what’s missing is explained: “no witness statement on file” is a finding backed by a record of what was searched, not a shrug. Priority recomputes from the rating and the days left on the statute clock, so your queue reads in the order the money would be lost.
Viability assessment · v2
Anchored to the $8,750 paid, the recovery ceiling.
- +Written liability admission[1]
- +Police report assigns fault[2]
- +Payment substantiates quantum[5]
- –Repair invoice not itemized[4]
- –No witness statement on fileabsence noted · search scope recorded
AI drafting · The human gate
Work product, ready for a second set of eyes.
Certvian drafts the demand with the file’s facts highlighted and cited inline. Anything the evidence can’t support, like the adverse policy limits or an unproven quantum, appears as an amber placeholder that blocks submission, so the letter cannot overclaim. Then the gate: your guardrails decide who approves what, every approval pins the exact version reviewed, and an edit after the request voids it. This sends a real email; the system treats that with the gravity it deserves.
Demand letter → Progressive
Draft · v2Re: Subrogation demand · claim ACM-2026-00014
Acme Insurance, as subrogee of Elena Vasquez, demands reimbursement of $8,750 paid for property damage arising from the March 11 rear-end collision[5] for which your insured has accepted liability[1]. Policy limits of [ADVERSE POLICY LIMITS] are presumed adequate to satisfy this demand…
1 unresolved placeholder blocks submission until resolved or waived.
Awaiting manager approval · v2 pinned
Edited after the request? Approval is refused until re-requested.
Ask
Ask the file. Get an honest answer.
Every case carries a grounded analyst, deliberately not a chatbot. It reads the case the way you would: opening documents, searching the file, quoting spans. Every sentence in its answer is labelled for what it is: grounded in cited evidence, an inference drawn from it, general knowledge to verify, or a gap the file simply doesn’t answer. It will draft the follow-up for you. It will never send anything.
Ask · scoped to ACM-2026-00014 · reads this case only
Why is viability only 82%?
groundedLiability is effectively settled: Progressive’s adjuster accepted fault in writing[1], and the crash report assigns fault to the other driver[2].
reasoningThe remaining uncertainty is quantum, not fault. The estimate holds, but the proof of damages has a hole.
gapThe repair invoice shows a summary total only; line items are not in the file. That absence is stated, not papered over.
The operational layer
Everything around the intelligence, handled.
Reconstruction and drafting are the headline. The rest of the platform exists so a recovery operation can actually run on it, every day.
Email-native intake
Thread matching, deduplication, quarantine for mail that doesn’t belong. One Outlook or Gmail rule and the pipeline feeds itself.
OCR built for claims
Scanned crash reports, photos of invoices, handwriting flagged for review, with layout-aware extraction into citable spans.
Entity & relationship graph
Insureds, carriers, counsel, repair shops, and witnesses resolved across documents, with the adverse-to spine made explicit.
Statute-of-limitations tracking
Computed per jurisdiction from the loss date, watched daily, escalated at thirty days. A missed statute forfeits the recovery.
Continuous re-analysis
Replies and new documents re-run the pipeline. A ribbon shows exactly what moved since your last visit: viability 73% → 82%.
Guardrails & roles
Owner, admin, manager, analyst, viewer. Dollar thresholds and who-can-send-what, set once at onboarding, enforced everywhere.
Arbitration-ready preparation
Inter-company disputes mostly resolve in industry arbitration, not court. Certvian assembles the contentions and cited evidence package as an approved work product.
Notifications that matter
“Progressive replied: liability admission detected.” Deduplicated and batched, in-app and by email, so signal survives.
Security & governance
Built for the scrutiny insurance demands.
Subrogation files carry claims data, payment records, sometimes medical information. Certvian’s trust posture is structural, with constraints in the schema rather than promises in a policy document, so it holds up in an audit, an arbitration, or a deposition.
Tenant isolation, enforced by the database
Every row carries your organization’s identity, and Postgres row-level security is the backstop: the application connects as a role that cannot read across tenants. Even a query that forgets to filter cannot cross the line.
Approval, structurally guaranteed
Four independent layers stand between a draft and a sent email: a database constraint, a trigger, an API check, and a send-worker re-check. No approval record, no send. Not policy. Physics.
An append-only audit log
Every consequential action by a human, the system, or the AI is recorded with the actor, the before-and-after, and the context. The history cannot be edited after the fact.
Versioned, never overwritten
Liability and viability assessments and every draft supersede their predecessors; nothing is destroyed. When a number changes, you can see what it was, when, and why.
Retention you control
Record-retention windows are set at onboarding and applied automatically: seven years on closed recovered cases by default, aligned with common insurance requirements.
Your identity provider, not another password
Single sign-on via OIDC, role-based access from owner to read-only viewer, and single-use hashed invitation tokens for bringing the team aboard.
Certvian Recovery Services
No subrogation team? Send us the claims. We’ll be the team.
The same platform, operated by our own recovery unit. Send us your paid-claim files, or the closed book nobody had time to work, and we pursue the recoveries end to end: viability triage, document requests, demands, negotiation, arbitration preparation, remittance.
You get exactly what our software customers get: a login, cited case files, an append-only audit trail, and approval over every demand that goes out under your name. Nothing about the work is a black box; you can open any case and read the evidence behind every dollar figure.
Because our analysts run on Certvian, we can profitably work the mid-size and small files most recovery vendors decline: the $5,000 rear-end, not just the six-figure loss. Engagements are typically contingency-based, so we’re paid when you recover.
Regional & mid-market carriers
Recovery potential without a dedicated subrogation desk. We become the desk.
Self-insured fleets & businesses
You absorb losses a carrier would normally chase. Your paid claims have recoveries in them too.
TPAs adding recovery
Offer subrogation as a service to your book without building the team. White-glove, on our platform.
Closed-file reviews
A look-back across files closed without pursuit. Missed recoveries are found, documented, and worked.
Start with a no-obligation review of a sample of your paid or closed files.
Common questions
Asked in every walkthrough.
Does Certvian replace our claims system?+
No. Certvian is an operations layer that sits on top of whatever you run today: Guidewire, a TPA portal, spreadsheets. Work arrives by forwarded email, so there is nothing to integrate on day one, and analytics export to CSV so your reporting keeps working.
How long does setup actually take?+
About ten minutes. Onboarding is a five-step wizard: name the organization, pick lines of business and jurisdictions, get your dedicated forwarding address, set approval guardrails, invite the team. You’re live the moment your first forwarded claim comes back as a reconstructed case.
Which lines of business does it handle?+
Auto and property damage are the primary lines today, with workers’ compensation recovery supported. Liability rules are jurisdiction-aware: comparative-negligence variants and statute-of-limitations windows are applied per state.
How do we know the AI isn’t making things up?+
Every AI statement must cite the exact source span it came from, and an independent grounding judge verifies each quote verbatim against the document. Claims it can’t verify are held back and labelled “needs verification” rather than presented as fact. When information is missing, the system says so; absence is reported with a record of what was searched.
Can the AI send anything on its own?+
No, and not as a matter of policy but as a matter of schema. An outbound email cannot exist in the database without a recorded human approval, enforced by four independent layers. The AI drafts, proposes, and prepares. People approve and send.
What about inter-company arbitration?+
Most auto subrogation disputes between carriers resolve through industry arbitration rather than court. Certvian assembles the contentions, the cited evidence package, and the chronology as a work product that goes through the same approval gate as a demand. Filing with the arbitration forum stays with your team today; the file arrives ready to submit.
How do we buy it?+
Through a walkthrough; there’s no self-serve signup. Bring one of your own claims and we’ll show you the analysis live, then cover security, SSO, and pricing for your volume. If a software rollout isn’t right for you, Recovery Services can work your files instead.
Request a walkthrough
See one of your own claims reconstructed.
Bring a claim file to the walkthrough and we’ll run the analysis live: chronology, liability, viability, the drafted demand. Then we talk security, SSO, and pricing for your book.
We reply within one business day. If we don’t, write founders@certvian.com.