Deckard

Insurance

New claims read on arrival

Coverage checked against the policy first, so adjusters work only the problem files.

Claims consoleDeskFiles

Claims operations

Intake inbox checked 16:52

New losses today

23

18 arrived as documents

Days to coverage decision

4.4 d

volume-weighted, six queues

Claims past service target

7

2 over 30 days

Subrogation candidates

12

$84k estimated recoverable

First notices per dayJul 6 · 31
Last 8 days
On the claims deskCoverage first, then the oldest
  1. Term on the notice ended before the lossUnit 12, commercial strip · water lossVerify term
  2. Third estimate exceeds the reserveReserve change needs a supervisorApprove
  3. Other carrier accepted liabilityAuto PD · collision paid, rear-ended at a lightSubro

Read the loss notice, keep the page it came from

Loss details, policy numbers and parties read from every page, each with a confidence score.

  • Loss notices readEmailed PDFs, portal uploads and faxes, each filed to its claim.
  • Duplicate notices mergedA broker’s copy of a loss the insured already reported is added to the first claim.
  • Problem files firstAdjusters see what is blocked and why.
First notice of loss
Received as a 6-page PDF with 3 attachments
6 fields read

Loss notice, page 1

Policy numberCP 4 471 9920.98
Date of lossJul 9, 20260.96
Loss typeWater damage, supply line0.91
Insured locationUnit 12, commercial strip0.94
Other party carrierTenant’s liability carrier0.78
Coverage at lossTerm on notice ended 07/01/260.62
Coverage question raised before assignment
Broker and insured told the same day
Held

Find the queue where coverage decisions stall

Coverage decisions timed from first notice in each queue, with large losses broken down by step.

  • Reserve approvalsReserve changes above an adjuster’s limit sent to a supervisor with the estimate attached.
  • Follow-up dates enforcedEach open file has a next review date, escalated to the team lead if missed.
  • Recovery identified earlySubrogation and salvage flagged at intake.
Days to a coverage decisionBy queue · 90 days
Property, large loss19
General liability14
Property, non-complex6
Commercial contents5
Auto physical damage3
Glass and small loss1
Where the 19 days goOpen the large-loss files

Large-loss files decided in the last 90 days.

Inspection 3 dAdjuster’s report 12 dCoverage review 4 d

Less chasing on every claims desk

For insurers and claims administrators: faster payouts, more policyholders renewing.

Vendor status chaseTwice daily
List files waiting on an outside report
With the day count each has cost
Ask each vendor once, on the agreed channel
One reference per vendor
3One vendor is past its SLA
Escalated with the file and the elapsed days
4File the report and move the claim
Coverage review starts the same day

Each chase is logged on the claim file with the vendor’s reply.

Linked to your claims system

New claims are set up in Guidewire or Duck Creek with no retyping.

GuidewireClaims system
Duck CreekPolicy and claims
XactimateProperty estimates
CCCAuto estimates
ACORDStandard forms
Applied EpicAgency management
SalesforceBroker CRM
OutlookClaims inbox
Google Sheets
Google SheetsTeam trackers
Airtable
AirtableVendor roster

Trace a claim that stalled

We map its path through your desk and price the fix.

Start a conversation