Claims on the policy you wrote.
First notice opens a claim against the bound policy, and exposures split it by coverage and claimant. Reserves, payments and recoveries attach there, so the portfolio numbers add up without an extract.
From first notice to closure. The claim moves through the states you defined, and it cannot close until every exposure under it is settled.
Notice, from any channel.
Email, portal, phone, API, or the submission that bound the policy. An emailed loss notice is read on arrival and drafts the claim for a handler to confirm.
The policy that responds.
The claim binds to the version in force at the date of loss. Occurrence and claims-made triggers resolve to different terms, and the claim knows which.
Exposures, one per liability.
A claim splits into an exposure for each coverage and claimant. That is the grain reserves, payments and ceded loss attach to.
Closure that has to balance.
A claim cannot reach closed until every exposure is terminal and outstanding reserve is zero. Reopening a closed claim is a transition, not a workaround.
“Our adjusters stopped asking underwriting for the policy language. It was already on the claim.”
Money moves on a ledger. Reserves, payments and recoveries post as entries that are never edited. Paid, outstanding and incurred are read back from them.
Reserves.
Set a case reserve, then move it with a reason code attached. Outstanding is the running sum of those movements, not a field somebody overwrote.
Payments.
Indemnity and adjustment expense post separately, so each reconciles on its own. A void posts an offsetting entry instead of deleting the original.
Recoveries.
Salvage, subrogation and deductible recovery come back against the exposure they belong to, and reduce net incurred where the loss was booked.
The whole file, in one place. A claim is a record like any other here, so everything the platform already does to a record applies to it.
Diary and tasks
Every follow-up is a task on the claim, assigned, dated and chased.
Notes and comments
Written on the claim itself, with mentions that reach the right handler.
Full activity history
Every change on the file, with who made it and when.
Documents on the file
Loss notices, estimates, reports and correspondence, attached where they belong.
A lifecycle you configure
States, events and the roles allowed to fire them, configured rather than coded.
Authority that holds
Reserve, pay, settle, close, deny and reopen, each gated by the handler's limit.
The paths that cost you. Litigation, subrogation and reopening are states on the claim, not spreadsheets kept beside it.
Litigation
A suit moves the claim into litigation and flags the file for legal hold. Defense counsel sits on the claim as a party, and their bills post as expense rather than indemnity.
Subrogation
Pursuing an at-fault third party is a state on the exposure, with the referral tracked on the file and the money posted back against the exposure it came from.
Reopened claims
A late demand reopens a closed claim as a first-class transition. Nothing is retyped, the prior history stays intact, and the reserve picks up from zero on the record.
Built on one connected model.
Underwriting, rating, documents and claims read the same records. Nothing is exported between them.
Walk a real loss through.
Bring a claim your current system handles badly. Several coverages, two claimants, a late demand after closure.
Usually 30 minutes, with an adjuster on the call.