Workflow — Demand Package
Demand reviews in days, not 90 days.
Attorney demand letters, medical records, lost-wage docs, police reports — valued against jurisdictional verdict data, with reserve recommendation and settlement-authority memo into Guidewire.
30–90 days
Typical demand-package backlog at senior adjusters
50–2,000
Pages per personal injury demand package
60–85%
Volume off the senior reviewer line after cutover
What This Replaces
The Senior Adjuster With a 90-Day Demand Backlog
The work the senior adjuster or claims attorney does on every demand package — and the cost of leaving it there.
The labor
Demand-package reviews today move through senior adjusters and in-house claims attorneys at the carrier — the most expensive labor on the claims org chart. Some carriers route routine demand packages to offshore preparation teams (extracting damages, building chronologies) before the senior reviewer touches the file, but the judgment work — reserve recommendation and settlement authority — stays onshore by regulation and policy.
The cycle time
Backlogs of 30–90 days are routine. Every day past the demand response deadline raises bad-faith exposure, gives the plaintiff's attorney leverage, and pushes settlement value up. The cost is real — and rarely captured cleanly on the reserve side.
The Workflow
Input · Analysis · Output
What goes in, what we do to it, and what shows up in your claims system.
Input
Demand package & supporting docs
- Attorney demand letter
- Medical records (provider, hospital, IME)
- Lost-wage documentation (W-2, paystubs, employer letter)
- Police report and witness statements
- Photos of damage, scene, injuries
- Prior-claim history from ISO ClaimSearch
- Policy details and coverage triggers
Analysis
Extract, value, defend
- Special damages (medicals paid, wages, property)
- General damages drivers (treatment, surgery, permanency)
- Liability factors and contributory-negligence flags
- Causation gaps and pre-existing condition flags
- Jurisdictional verdict and settlement comparison
- Reserve range and settlement authority recommendation
- Confidence threshold routing to senior reviewer
Output
Reserve memo into the SoR
- Reserve update into Guidewire ClaimCenter
- Duck Creek Claims (OnDemand APIs)
- Origami Risk (REST API)
- Settlement-authority memo to manager
- Response-letter draft for adjuster review
- Subrogation queue routing if applicable
- Source-page citations on every extracted item
Side by Side
Demand Package Review Today vs. With Last Rev
The numbers that matter: cycle time, defensibility, and the cost of demand-response slippage.
| Dimension | Senior Adjuster / Attorney | Last Rev Demand Review |
|---|---|---|
| Cycle time per file | 30–90 days routine | 2–5 days for routine, same-week for most |
| Per-file labor cost | Senior adjuster / attorney loaded rate | 30–50% of incumbent loaded cost on routine files |
| Bad-faith exposure on demand-response timing | Material, increases with backlog | Cycle time short enough to respond on time |
| Source citations on every damage and defense | Variable, reviewer-dependent | Page-level citation per field, every time |
| Verdict-comparison rigor | Reviewer-dependent, sometimes skipped | Jurisdiction-matched verdicts cited every file |
| Senior reviewer time | Field extraction, then judgment | Judgment only — extraction already done |
| Defensibility against bad-faith claim | Reviewer testifies to methodology | Every reserve adjustment traces to source + verdict comparison |
How It Works
From Demand Receipt to Reserve Update
Five steps. Every one logged. Every one reversible if your confidence threshold isn't met.
Demand Package Lands
Attorney demand letter, medical records, lost-wage documentation, police report, photos. Sometimes 50 pages, sometimes 2,000. Indexed and ingested, OCR if needed, classified by document type and provider.
Extraction & Classification
Special damages (medical bills paid, lost wages, property damage). General damages drivers (treatment duration, surgery, permanency, lost-life-quality). Liability factors (police narrative, witness statements). Defenses (causation gaps, pre-existing conditions, contributory negligence).
Validation Against Verdict Data
Jurisdictional verdict and settlement comparison from your verdict database (or jury verdict reporters where you have a license). Defense-side adjustments applied. Reserve range and settlement authority recommended. Anything below your confidence threshold per field is routed to a human exception queue — your call which queue, ours or yours.
Push to System of Record
Reserve update into Guidewire ClaimCenter, Duck Creek Claims, or Origami Risk via the documented integration. Settlement-authority memo to manager. Response-letter draft for adjuster review. Subrogation queue routing if applicable.
Audit Log Persisted
Every special damage, general damage driver, liability factor, and defense flag traces back to the source page in the demand package. Verdict comparisons cited. Model version, prompt, and confidence score recorded. Defensible against bad-faith claim and DOI exam.
Compliance & Defensibility
Built to Meet the Quality Bar Liability Claims Operations Run On
State DOI & fair-claims-practices acts
Demand-response timing tracked per state requirement. Reserve methodology documented per claim, defensible chain of custody for examiner requests and bad-faith defense.
Jurisdictional verdict integration
Verdict comparison from your licensed verdict database (or jury-verdict reporters) — never invented. Comparable cases cited with verdict, jurisdiction, year, and case-distinguishing notes.
Bad-faith defense posture
Every reserve adjustment, defense flag, and verdict comparison traces to source data. Holds up to depositions and bad-faith litigation without reconstructing reviewer notes.
HIPAA & privilege handling
PHI redacted before logging; encryption in transit and at rest. Privileged communications between claim file and counsel handled per attorney-client and work-product rules.
Common Questions
What Carriers Ask About Demand Package Review
How is this different from existing claims-AI vendors and verdict databases?
Verdict databases (Jury Verdict Research, ALM, JuryVerdict.com) are reference data — that's the foundation we build on. The competitor on this page is the senior adjuster or claims attorney line on your operating budget — the people doing 30–90 day demand-package reviews today. We replace that labor cost on routine demand packages, integrate directly into your existing claims system, and deliver a structured reserve recommendation and settlement-authority memo into the system of record.
We have senior adjusters or in-house claims attorneys reviewing demand packages. How does this work alongside that?
Most carriers run AI on the front of the funnel — extraction, valuation, defense identification — and route the high-stakes files (large-loss, contested liability, multi-claimant, MIST-vs-not-MIST disputed) to the senior adjuster or attorney. Volume to the senior reviewer drops 60–85% on routine demand packages once cutover completes. Your team gets to spend their time on the cases that actually need their judgment, not on field extraction from a 1,500-page file.
What's your accuracy bar versus a senior adjuster?
Our pilot success threshold is structured-field extraction and reserve-recommendation accuracy at parity with or above your incumbent reviewer, measured on the same shadow-data sample (same files, same target reserve ranges and settlement authorities). We don't make the final settlement determination — we tag the file with extracted damages, defenses, verdict comparisons, and a recommended reserve range with source citations, so your adjuster or manager makes the call on a richer file than they get from offshore review today.
What about defensibility against bad-faith claims and DOI exam?
Every special damage, general damage driver, liability factor, and reserve adjustment traces back to a specific source page in the demand package and a specific verdict comparison. Discovery-ready, deposition-ready, and structured to answer the documentary questions a bad-faith plaintiff's attorney will ask: when did you know what, what was your basis, how did you reach the reserve number, what verdict data did you compare against.
Can you actually integrate with Guidewire ClaimCenter / Duck Creek / Origami?
Yes — through the standard integration surfaces each platform supports. Guidewire via the ClaimCenter REST API or the EDGE integration framework; Duck Creek via OnDemand APIs; Origami Risk via their REST API. Your IT team reviews and approves a service account, and we connect through the documented integration. We do not require platform-side custom development.
How long until a pilot is live?
Demand-package pilots typically run 6–8 weeks: 1–2 weeks of integration and rule mapping (which jurisdictions, which carrier-specific reserve methodologies, which verdict-database licenses, which severity bands route to AI vs. attorney), 4 weeks of shadow-mode running on real demand packages with no system-of-record writes, 1–2 weeks of supervised cutover on a constrained book (one LOB, one severity range, one region). Production rollout is staged after the pilot meets your accuracy and SLA bar.
What's the per-file pricing structure?
We benchmark against your current per-file reviewer cost — typically loaded senior-adjuster or claims-attorney cost amortized across the demand-package portfolio. Our target is 30–50% of that per-file cost at higher accuracy and faster cycle time. Pricing structures around volume tiers and outcome SLAs, not hourly billable rates.
Is this a good fit for commercial liability or only auto BI?
Both. Auto BI is the densest workflow today. Commercial general liability, marine, construction defect, and product liability all share the same demand-package structure — letter, records, damages, defenses. The per-file complexity is higher on commercial, and so is the per-file labor cost — typically the ROI math gets stronger as the file gets harder.
Two Ways to Start
Take the AI assessment for a structured read on demand-review feasibility in your operation. Or talk to us if you already know how big your demand-package backlog is.
Self-serve · 8 minutes
Take the AI Assessment
A short structured assessment that maps your demand-package volume, jurisdictional mix, and claims system of record to AI feasibility and ROI.
Talk to a specialist
Get a Per-File ROI Model
Send us your monthly demand-package volume, jurisdictional mix, and current senior-reviewer model. We'll come back with a per-file comparison and a 6–8 week pilot plan in 5 business days.
Other Workflows
More Insurance Workflows We Replace
The same approach, applied to the other claims-document labor lines on your operating budget.
FNOL Intake
First-notice-of-loss extracted, validated, and pushed into Guidewire ClaimCenter, Duck Creek, Origami, or Snapsheet in minutes.
Medical Record Summarization
Chronological treatment timelines from 100–2,000 page medical packets.
Property Estimate Review
Xactimate, Symbility, Verisk 360Value line-item review and supplemental flagging.
Acord Form Processing
Acord 1, 25, 27, 125, 130 — every field extracted and validated against carrier business rules.