Door one
First party FNOL
The insured reports their own loss. Policy resolution and coverage verification run as the notice is taken, so the adjuster starts with a verified position rather than a promise to check.
The portals / Claims Platform
Intake through closure and recovery: assignment at creation, reserves and payments under authority, statutory clocks computed per jurisdiction, and a file that shows its own history.
Request a DemoDoor one
The insured reports their own loss. Policy resolution and coverage verification run as the notice is taken, so the adjuster starts with a verified position rather than a promise to check.
Door two
A claimant who is not your insured. Parties, attorneys and the liability posture are captured from the start, where they belong on the file.
Door three
Jurisdictional intake for indemnity and medical, with the statutory reporting the line demands computed from the loss and report dates.
Door four
Documents and conversations are read into a draft intake with per-field confidence, then a reviewer confirms before a claim exists. Nothing is created by a model alone.
Status, loss detail, assignment and the exposure figure at a glance.
Resolved policy, coverages, limits, deductibles and the verification result.
Insured, claimants, attorneys, vendors and contacts, de-duplicated across claims.
Reserves by category, payments, recoveries, incurred and net liability.
Payment requests, approvals and subrogation activity.
File notes, encrypted, attributed and timestamped.
Uploaded and generated documents, including the letter package.
Every status change and material edit, with who and why.
Money set aside for an expected liability, by category — indemnity, expense, legal.
Money actually disbursed against the claim.
Paid plus outstanding reserve. The exposure figure.
Money coming back: subrogation, salvage, deductible reimbursement.
Incurred less recoveries. What the loss actually cost.
Allocated loss adjustment expense — the cost of handling this specific claim.
Claim Compliance
Acknowledgment, contact and decision dates derived per jurisdiction from the loss and report dates — not typed in by whoever opened the file.
Compliance Deadlines
Every claim’s clock across the operation on one page, so an aging deadline is a queue item rather than a discovery.
Diary
Entries carry a due date, an assignee and a claim, raised by hand or automatically by platform events.
Referral, investigation and outcome tracked on the claim. Fraud rules and predictive screening raise candidates; the referral blocks closure until it is resolved, which is the point.
Screening results and overrides recorded against the party, so a match is answered on the file rather than in somebody’s inbox.
Event-scoped surge handling: adjusters deployed to an engagement, licensing respected per state, and the fee structure carried into the invoice at the end.
Quality
Auto-assignment runs at creation across every intake door and respects state licensing, so a new loss has an owner before anyone reads it.
A payment inside the adjuster’s authority proceeds; one above it routes to an approver as a queued request on the file, not an email somebody may open.
Total reserve is maintained by the database itself, so the figure on the file is the sum of the rows beneath it no matter which door wrote the last transaction.
Deadlines are computed per jurisdiction from the loss and report dates and shown across the whole book, so an aging clock is a queue item rather than a discovery.
Opening a claim for editing takes a lock; the second person sees it read-only with the holder named on screen.
A claim cannot close while an SIU referral is open. The transition refuses rather than warns.
Volume, cycle time, reserve accuracy and closure rates per adjuster and per team, with file-review scoring alongside and a drill-through to the claims behind every number.
Bring a real claim shape and we will walk it end to end.
Request a Demo