Contents
See amaise on one of your own demand packages.
Book a demoThe short answer
A bodily injury demand package is the file a claimant's attorney sends to an insurer to demand payment for an injury. It bundles the demand letter with the evidence behind it: medical records, bills, lost-wage proof, the police report, photos, and often expert or IME reports. The package argues liability, ties the injury to the incident, totals the damages, and usually names a dollar figure and a deadline to respond.
For the adjuster on the other side, it is the document that decides the claim. Read it well and you settle for the right number. Miss something in it and you overpay, underpay, or hand the other side an opening. This guide walks through what a demand package contains, how to review one, the issues that move value the most, and where AI now fits.
A bodily injury demand package is a settlement demand plus its proof. A claimant, almost always through a personal injury attorney, assembles the documents that support the injury claim and sends them to the at-fault party's insurer. The package says, in effect: here is what happened, here is who is at fault, here is the harm, here is what it is worth, and here is how long you have to pay.
Demand packages show up across casualty lines: auto liability after a crash, general liability after a slip and fall or a premises injury, and workers' compensation and medical malpractice in their own forms. The common thread is a person claiming physical injury and money to compensate for it, backed by medical evidence.
The insurer's job is to test that claim. An adjuster reads the package to confirm the story holds up, to value the injury fairly, and to respond within the deadline. On a small soft-tissue claim that can take an hour. On a serious injury with years of treatment it can take a full day of reading, and the file can run past a thousand pages.
These two terms get used loosely, so it helps to separate them.
The argument
The demand letter is the attorney's written argument. It lays out the facts, argues liability, describes the injuries and treatment, summarizes the damages, and states a settlement figure, often with a deadline and sometimes a demand for policy limits.
The argument plus the proof
The demand package is that letter plus the evidence: the medical records, itemized bills, imaging, wage documentation, police report, photographs, and any expert reports.
The letter makes the claims. The package is supposed to prove them.
A careful adjuster reads the letter for the argument, then checks every claim in it against the documents behind it.
Most packages include some mix of the following. The order and completeness vary by attorney and by line of business.
The attorney's argument for liability, the injury narrative, a damages summary, and a settlement figure with a deadline. On serious claims it may demand the full policy limits.
Treatment notes from every provider the claimant saw: the emergency room, primary care, orthopedics, physical therapy, chiropractic, pain management, imaging centers, and surgeons. These are the core of the file and usually the largest part.
Itemized charges, often hundreds of line items across multiple providers. Bills drive the economic damages and are the first place leakage appears.
MRI, X-ray, and CT images with the radiologist's read. These support or undercut the claimed severity of an injury.
Pay stubs, employer letters, and tax records that support a wage-loss claim. Self-employed claimants may include profit-and-loss statements.
The official account of the crash or incident, including any citations and the responding officer's notes on fault.
Images of injuries, the scene, and vehicle or property damage. Low property damage in an auto case, for example, invites questions about injury severity.
Opinions on causation, prognosis, permanent impairment, and future care. An independent medical examination (IME) report often carries the most weight on disputed causation.
Third-party accounts of the incident, plus any medical liens or subrogation interests that affect how a settlement gets paid out.
A routine package runs 200 to 600 pages. Complex injury files run longer, and they often arrive as scanned PDFs that an adjuster has to read by hand. Handwritten notes, faxed records, and foreign-language reports all show up, which is part of why review is slow.
Reading the demand letter well is faster once you know its parts. Most follow a similar shape:
The review is not one task. It is a stack of them, and each one has to hold up later if the claim goes to litigation. Here is the sequence most adjusters follow.
Does the file support the attorney's version of fault? Read the police report, witness statements, and scene photos. Note any comparative fault that reduces the claim.
Did this incident cause this injury, or is the file describing something older? Look for the first treatment date relative to the incident, and for any gap that suggests an unrelated cause.
Prior treatment for the same body part changes the value. Search the records for earlier injuries, degenerative findings, and past imaging of the same region.
Put every visit, diagnosis, procedure, and gap in treatment in date order. This is the backbone of the evaluation.
Find duplicate charges, unrelated treatment, and inflated codes. Compare charges against usual and customary rates. This is where leakage hides.
Total the economic and non-economic damages, then separate what this defendant owes from what belongs to a pre-existing condition or another party.
Set a reserve and a settlement range, document the reasoning, and respond in writing before the deadline.
Done by hand on a 400-page file, this takes hours, sometimes a full day. Multiply by a caseload and the math gets ugly fast. Every step also has to be documented, because a reserve or a settlement that cannot be explained later is a problem in its own right.
Four questions decide most of what a bodily injury claim is worth. An adjuster who gets these right values the claim well, and can defend the number.
Who is at fault, and by how much. In comparative-fault states, a claimant found partly responsible recovers less. Liability sets the ceiling on the claim before damages even enter the picture.
Whether the incident actually caused the claimed injury. A herniated disc that first appears in the records two months after a low-speed crash raises a real causation question. Causation is often the single most contested issue in a serious file.
Whether the claimant had prior problems with the same body part. Degenerative changes, old injuries, and earlier imaging all reduce the share of harm that this incident caused. Missing a pre-existing condition is one of the most expensive review errors.
How to divide the harm between this incident and everything else. Apportionment turns a causation finding into a number, and it is where a careful chronology pays off directly.
A medical chronology is a date-ordered timeline of every visit, diagnosis, procedure, and gap in treatment. It is the tool that turns a stack of records into a story an adjuster can evaluate.
Each entry links back to the page it came from, so a reviewer can open the record behind any date in one click.
A good chronology shows the first treatment date, the course of care, the providers involved, the diagnoses over time, and any gaps. Gaps matter. A claimant who stops treatment for four months and then returns just before filing raises questions about how serious the injury really was. So does treatment that keeps going long after the records show recovery.
Building a chronology by hand is slow and error-prone, because the dates are scattered across hundreds of pages from different providers in different formats. It is also the step most worth getting right, since causation, apportionment, and damages all rest on it. This is one of the tasks AI handles well, as long as every date it lists links back to the page it came from. For a worked example, see how to build a medical chronology from a 400-page claim file.
Claim leakage is money paid out that a fuller review would have saved. In demand package review, leakage usually comes from a handful of sources:
Each of these leaks money quietly, one claim at a time, and it adds up across a book of business. Catching leakage is a large part of what accurate review is for, and it is a direct reason to read the whole file rather than the summary the other side wrote.
Demand packages come with clocks. The most important is the time-limited demand.
A time-limited demand asks the insurer to accept a settlement, often at policy limits, within a set window such as 30 days. The tactic puts pressure on the insurer: accept quickly, or risk a later verdict above the limits that the insurer may have to pay because it did not settle when it could. In many states, mishandling a time-limited demand can expose the insurer to a bad-faith claim, which removes the protection of the policy limits.
That is why cycle time is not only an efficiency question. A demand that sits unreviewed while the clock runs is a real exposure. The adjuster needs a complete, accurate read of a large file inside a short window, which is exactly the pressure that makes fast, source-linked review valuable.
Note that the specific rules for time-limited demands and bad faith vary by state, so any process built around them should be reviewed with counsel. For a day-by-day approach, see Time-limited demands: a 30-day playbook for adjusters.
Two trends have raised the stakes on injury claims.
The first is social inflation: jury awards for bodily injury have grown faster than economic inflation, driven in part by litigation funding and shifting juror attitudes.
The second is the rise of nuclear verdicts, awards in the tens of millions that were once rare and are now a recurring risk on serious claims.
Both trends reward carriers that evaluate claims quickly and accurately. A file valued well and settled early avoids the litigation path where a nuclear verdict can happen. A file valued on a rushed skim is the one that turns into a problem. Faster, more accurate demand package review is a direct hedge against both trends. More on the numbers in nuclear verdicts and social inflation in 2026, and a practical screen in the nuclear verdict risk checklist.
The same errors show up again and again:
Most of these trace back to the same root cause: too many pages, too little time. That is the problem AI is now good at, provided it can show its work.
AI reads the full file in minutes and surfaces what matters: the timeline, the gaps, the contradictions, the billing that does not add up. The catch is trust. A general chatbot can summarize a PDF, and it can also invent a detail that was never in the record. In a claim file, an invented impairment rating or a missed prior surgery is a liability, not a rough edge.
General chatbot
Any prior treatment to the lower back?
No prior lumbar treatment found. Permanent impairment rated at 12%.
No sources. Nothing to check, so nothing to trust.
Source-linked, like amaise
Any prior treatment to the lower back?
Yes. Chiropractic care for low back pain before the incident p. 88p. 91. No impairment rating appears in the file.
Every statement opens the page it came from.
amaise was built for this specific problem. It rebuilds the claim file into a knowledge graph it calls CaseDNA, then answers every question with click-to-evidence: each finding links back to the exact source page it came from. No generated facts, no filled-in gaps. The line amaise uses with adjusters is direct:
Don't trust the AI. Click and check it yourself.
How amaise puts it to adjusters
In practice that means the medical chronology comes back with every date linked to its record, the billing review flags charges you can open and confirm, and the causation and pre-existing findings point to the exact pages that support them.
less time on document review
greater precision
reduction, while keeping decisions fair
In amaise deployments, teams report up to 84% less time on document review, 4x greater precision in their evaluations, and a 10% reduction in payouts while keeping decisions fair. The work that took a day takes minutes, and every number traces to a page an adjuster can open.
amaise works across auto liability, general liability, workers' compensation, and medical malpractice, and it is built for the insurance side: adjusters, claims managers, IMEs, defense attorneys, and the VPs and chief claims officers who answer for the outcome. You can see how it handles a real file on the Bodily Injury AI page.
See it on one of your own demand packages
amaise reads every page and returns a source-linked chronology, billing review, and summary in minutes.
If you are evaluating AI for this work, these criteria separate a tool you can rely on from one you cannot:
0 of 6 checked
For a side-by-side look at the main options, see our guide to the best AI tools for casualty and bodily injury claims, and for why verification matters so much, read explainable AI for insurance claims.
Looking for more terms? See the bodily injury claims glossary.
The demand letter is the attorney's written argument and settlement figure. The demand package is the letter plus all the supporting evidence: medical records, bills, reports, wage proof, and photos.
Most run 200 to 600 pages. Serious-injury and long-treatment files can run past a thousand pages, and many arrive as scanned PDFs.
By hand, several hours to a full day for a large file. AI built for claims, like amaise, brings that down to minutes while linking each finding to its source page.
A time-limited demand asks the insurer to accept a settlement, often at policy limits, within a set window such as 30 days. Missing the window can expose the insurer to a bad-faith claim for any verdict above the limits. The rules vary by state.
Leakage is money lost to missed details: an overlooked pre-existing condition, an unrelated medical charge, an inflated code, or a reserve set without a full read of the file.
A medical chronology is a date-ordered timeline of every visit, diagnosis, procedure, and gap in treatment, built from the records so an adjuster can see the injury and treatment story at a glance.
A general chatbot can invent details. amaise links every answer to the exact source page through its CaseDNA knowledge graph, so an adjuster can verify each finding rather than trust it blind.
On the insurance side, the claims adjuster leads the review, often with a nurse reviewer, a defense attorney, and a claims manager on larger files. amaise is built for this insurance-side team.
Cookies & privacy
We’d like to use cookies and similar technologies to analyze site use and support our marketing, including identifying companies and people that visit us. We only do this if you accept. You can change your choice anytime under “Cookie settings” in the footer.
See our Privacy Policy and Cookie Notice.
Choose which cookies and similar technologies we may use. You can change your choice at any time. Details are in our Cookie Notice.