Personal-injury demands
Florida Personal-Injury Demand Package and Response Checklist
A source-linked workflow for organizing a personal-injury demand package, verified medical and billing support, lawyer-approved drafting, delivery proof, and insurer follow-up.
Prepared and reviewed by the Law Firm Training Manual Editorial Team. Read our editorial and correction standards or report a correction.
Update note: Initial publication. Current 2026 Florida statutes, Florida Bar ethics guidance, CMS Medicare Secondary Payer recovery guidance, and the connected published lessons were checked on October 3, 2026. This is an operations checklist, not a demand-letter form, valuation method, deadline chart, or substitute for matter-specific lawyer direction.
On this page
Define the assignment before assembling a demand
A personal-injury demand package is not one standard form. Its contents depend on the claim, audience, available coverage information, factual and medical record, financial support, recovery interests, lawyer-selected positions, and delivery instructions. Start with the exact matter, client, responsible lawyer, recipient and claim identifiers, scope, source cutoff, requested sections, approved demand terms, reviewers, and release authority.
Keep an ordinary presuit demand separate from a proposal for settlement under § 768.79 and Rule 1.442, a civil-remedy notice, a PIP demand, a medical-malpractice presuit notice, a sovereign-immunity claim, a UM or UIM notice or consent issue, and any court-ordered settlement process. The lawyer selects the lane and its authority before staff applies a template, date, service route, or status label.
The responsible lawyer decides liability, fault, causation, injury characterization, damages, coverage, recovery interests, admissibility, value, amount, deadline, negotiation position, legal citations, and what the firm will send. Staff can preserve sources, build verified indexes and tables, assemble the approved package, control versions, and document transmission without making those decisions.
- Record the purpose, recipient, claim or policy identifiers, source cutoff, required components, exclusions, reviewers, and target delivery channel.
- Keep a lawyer-decision register for every substantive position, amount, term, legal date, and unresolved exception.
- Do not begin from a prior client's demand or a generic template until the lawyer approves its use for this matter.
Freeze and inventory the exact source set
Preserve each as-received incident record, photograph, video, witness statement, medical record, diagnostic report, bill, provider ledger, explanation of benefits, wage or loss record, insurance communication, benefit or recovery document, and client-impact source. Give each item a stable source ID, version, date or period, page count, origin, storage link, and verification status. Keep originals separate from working copies and summaries.
Florida Statutes § 627.4137 describes specified liability-insurance disclosures following a written claimant request, including a 30-day response requirement for the insurer disclosure addressed by the statute and immediate amendment upon discovery of facts calling for one. That is not a universal deadline to answer a personal-injury demand. The lawyer decides whether the statute and its insurer, insured, agent, or self-insured branches apply, the request language, recipient, timing, sufficiency, amendment implications, and any response. Staff records the exact request, delivery evidence, received disclosure, policy copy, stated coverage information, later amendments, and exceptions without treating the disclosure as a coverage opinion.
- Stop for mixed matters, wrong-client material, missing pages, corruption, illegibility, uncertain provenance, privilege, or unexpected protected information.
- Preserve source classes and versions rather than merging records that appear to describe the same event or amount.
- Use unknown or source support not located when the approved record does not answer a field.
Build a verified medical chronology without medical inference
Use the medical-record chronology as a navigation layer, not as evidence or a medical opinion. Each material entry should link to the exact provider, record type, date label, page, and source wording. Keep service, order, result, procedure, signature, and posting dates distinct; preserve negation, uncertainty, copied-forward history, corrections, addenda, conflicts, and gaps.
Staff and AI must not diagnose, interpret imaging, decide causation, necessity, relatedness, prognosis, permanency, impairment, or evidentiary weight. A trained human opens every cited source, and the lawyer or qualified professional controls every medical or legal characterization used in the demand.
- Reconcile the chronology to the frozen production and its source manifest before using it downstream.
- Keep diagnostic images distinct from imaging reports and route image interpretation to qualified professionals.
- Carry every missing record, ambiguous date, conflicting statement, and verification exception into the demand review package.
Reconcile bills, payments, benefits, and recovery interests
A provider bill, provider ledger, explanation of benefits, payment, adjustment, write-off, collection notice, and balance are different records. Build a source-linked ledger that preserves the source's transaction label and keeps charges, allowed amounts, insurer responsibility, insurer payments, patient responsibility, patient payments, adjustments, refunds, and balances separate. Show approved calculations with their operands, sources, formula, cutoff, precision, and independent recomputation.
Florida Statutes §§ 768.0427 and 768.76 address different medical-expense, letter-of-protection, collateral-source, subrogation, and reimbursement issues. They do not turn the staff ledger into a recoverable-damages calculation. The lawyer decides applicability, required disclosures, evidentiary treatment, reimbursement rights, notice, and the amount or characterization used in a demand.
CMS describes Medicare conditional payments and its recovery process following a settlement, judgment, award, or other payment. Use the lawyer-approved Medicare Secondary Payer workflow and distinguish an interim conditional payment amount from a final recovery demand. Staff should not call every possible recovery interest a lien, infer that a balance is final, or treat a portal status as the lawyer's resolution decision.
- Reconcile provider, biller, account, claim, payer, source, through-date, and later versions before calculating totals.
- Keep letters of protection, health coverage, Medicare, Medicaid, ERISA, workers' compensation, provider claims, subrogation, reimbursement, and other benefit or recovery records distinctly labeled.
- Route relatedness, reasonableness, necessity, collectibility, damages, compromise, allocation, and resolution decisions to the lawyer.
Create a source-linked package index and assembly manifest
Build the package index from the lawyer-approved category map and frozen source set. For each proposed item, record its stable ID, neutral title, source class, author or holder, displayed date or period, page count, pinpoint support, version, confidentiality treatment, verification status, and proposed package location. Do not treat the index, chronology, or ledger as a replacement for the underlying evidence.
Then create an assembly manifest listing the exact files, order, exhibit labels, page ranges, redactions, confidentiality handling, and relationship to the approved proposition or demand section. A second reviewer should be able to reproduce the complete proposed package and identify every omission, duplicate, superseded item, broken citation, or unresolved exception.
- Keep allegations, client statements, third-party statements, estimates, calculations, and lawyer-approved positions distinctly classified.
- Open every material citation and verify identity, context, wording, amount, date label, and version against the source.
- Use an exception log instead of silently resolving conflicts or excluding inconvenient material.
Draft only from approved, verified propositions
Build a claim-to-source matrix before drafting. Each proposed material statement or amount should have a proposition ID, section, exact wording or calculation, source and pinpoint citation, classification, verification status, and lawyer approval. Give an approved AI system only the authorized input set and instructions; require visible gap markers and prohibit new facts, citations, theories, medical conclusions, amounts, deadlines, or demand terms.
Florida Ethics Opinion 24-1 is an advisory opinion, not a binding court rule. It emphasizes confidentiality, competence, supervision, accurate work, billing, and lawyer responsibility when generative AI is used. Verify the exact product, account, retention, training, sharing, integrations, access, export, deletion, and incident controls before protected information is exposed. A confident AI output, second AI review, or citation-looking reference is not source verification.
Compare the complete draft against the proposition matrix, chronology, ledger, index, source set, correspondence, and instructions. The lawyer approves every substantive statement and the final amount, terms, response language, date, and release decision.
- Never upload confidential, medical, financial, privileged, settlement, or identifying information to an unapproved service.
- Keep source facts, quotations, paraphrases, calculations, allegations, and lawyer positions visibly distinct during review.
- Do not let AI or staff select case value, negotiation strategy, legal deadlines, or final transmission language.
Verify the exact outgoing package and preserve delivery proof
Review the exact files that will leave the firm—not an earlier draft or source folder. Verify the recipient and delivery route, claim identifiers, clean approved letter, signatures, amount and terms, response language, exhibit order, file names, page counts, bookmarks, redactions, confidentiality, accessibility, metadata, hidden text, comments, prompts, placeholders, and delivery limits. Confirm that every manifest entry matches the release set.
Transmit only after documented lawyer approval. Freeze the exact as-sent letter and attachments together with recipient details, channel, sent time, delivery or upload proof, failures, and sender. Submitted, delivered, acknowledged, responded, accepted, settled, and paid are separate statuses.
- Do not change the as-sent package when later records arrive; preserve a separately approved supplement and its proof.
- Do not treat a portal upload, sent email, tracking event, or verbal report as proof of every later status.
- Reconcile the released files to the approved index, manifest, and lawyer decision record immediately after transmission.
Track every response and follow-up as a separate event
Preserve every email, letter, portal item, enclosure, delivery event, voicemail record, and contemporaneous call note in its original context. Give each event a stable ID and record the source-displayed date, received date, parties, channel, exact amount or term, requests, conditions, attachments, status, verification, owner, and lawyer instruction. Never replace an earlier offer, request, correction, or communication with the latest version.
Keep demand, sent, delivered, acknowledged, sender-stated response, internal target, lawyer-calculated deadline, offer, expiration, agreement, settlement, release, payment, clearance, and closure dates separate. Staff should not characterize language as an offer, counteroffer, acceptance, rejection, denial, waiver, coverage decision, bad-faith event, release, or settlement without lawyer approval, and should route any possible formal litigation offer or proposal immediately.
Florida Statutes § 90.408 addresses admissibility of compromise evidence for a stated purpose; it does not justify labeling every settlement communication privileged or categorically confidential. Preserve the exact communication and applicable confidentiality instructions while the lawyer determines its legal treatment and permitted use.
Florida Statutes § 627.4265 addresses payment after a written settlement agreement between a person and an insurer and states a 20-day tender rule subject to the agreement and release language. Sending a demand does not trigger that rule. The lawyer decides whether the statute applies, when a written settlement was reached, what the agreement requires, whether a release condition is satisfied, what date controls, and what action follows. Staff records the source events and follows the lawyer's written instructions rather than starting a universal settlement-payment timer.
If the claimant is a minor or ward, create a visible § 744.387 court-approval and guardianship branch and stop for lawyer direction; staff must not infer settlement or release authority from a parent or other person's signature. Keep Medicare, Medicaid under § 409.910, ERISA, workers' compensation, provider, and other asserted recovery interests in separate lawyer-controlled tracks through approved resolution, payment, or holdback evidence.
- Prepare follow-ups only from approved language, recipients, attachments, channel, timing, and send authority.
- Preserve qualifications, contingencies, allocations, releases, recovery-interest language, fees, costs, parties, and nonmonetary terms.
- Close only after the verified history, current status, exact approvals, transmission proof, recovery-interest work, payment evidence, next owner, and unresolved exceptions agree.
Continue with the related workflow
Use these guides when the next step moves from general verification into a specific filing or scheduling workflow.
Personal-injury demand package workflow checklist
Use this as a conversation starter with the person responsible for the work. Replace general language with the firm’s actual systems, owners, and procedures.
- The matter, client, responsible lawyer, recipient, claim identifiers, assignment, source cutoff, reviewers, and release authority are verified.
- Liability, causation, medical conclusions, damages, coverage, recovery interests, value, amount, terms, legal dates, negotiation, and settlement remain lawyer-controlled decisions.
- Every original source is preserved with a stable identity, provenance, version, page count, storage link, and verification status.
- The medical chronology links every material entry to an opened source and preserves date meanings, uncertainty, corrections, conflicts, and gaps.
- The billing ledger keeps bills, ledgers, EOBs, payments, adjustments, write-offs, refunds, balances, and source meanings distinct.
- Medicare, benefit, subrogation, reimbursement, letter-of-protection, and other recovery-interest records are separately tracked under lawyer direction.
- The package index and assembly manifest identify the exact files, versions, order, labels, pages, confidentiality treatment, citations, and exceptions.
- Every material draft proposition and calculation is source-linked, human-verified, and lawyer-approved.
- Any AI use occurred only in an approved environment with minimized inputs, visible gaps, source verification, human review, and lawyer control.
- The exact outgoing letter and exhibits were checked for recipients, identifiers, signatures, amount, terms, file integrity, metadata, redactions, confidentiality, and placeholders.
- The exact as-sent package, delivery evidence, failures, acknowledgments, supplements, and change history are frozen without overwriting earlier records.
- Every insurer response, request, offer, condition, follow-up, release, settlement, and payment event remains distinct and source-linked.
- No universal response, offer, settlement-payment, recovery, or other legal deadline was calculated by staff or AI.
- Every unresolved conflict, missing source, legal decision, follow-up, recovery item, and next action has a named owner and verification date.
Official references
These primary sources support the general operational controls discussed above. Check their current versions and follow the governing court, judge, clerk, software, and firm procedures for the actual work.
- Rules Regulating The Florida Bar — Chapter 4
The Florida Bar
- Florida Ethics Opinion 24-1
The Florida Bar
- Florida Statutes § 627.4137 — Disclosure of Certain Information Required
Florida Senate
- Florida Statutes § 627.4265 — Payment of Settlement
Florida Senate
- Florida Statutes § 768.0427 — Medical-Expense Evidence and Letters of Protection
Florida Senate
- Florida Statutes § 768.76 — Collateral Sources of Indemnity
Florida Senate
- Florida Statutes § 768.79 — Offer of Judgment and Demand for Judgment
Florida Senate
- Florida Rules of Civil Procedure — October 1, 2026 Compilation
The Florida Bar
- Florida Statutes § 90.408 — Compromise and Offers to Compromise
Florida Senate
- Florida Statutes § 744.387 — Settlement of Claims
Florida Senate
- Florida Statutes § 409.910 — Responsibility for Payments on Behalf of Medicaid-Eligible Persons
Florida Senate
- Attorney Services: Medicare Secondary Payer Recovery
Centers for Medicare & Medicaid Services
- Medicare's Recovery Process
Centers for Medicare & Medicaid Services
Related lesson previews
Practice one workflow at a time
AI-Assisted Law-Firm Workflows
Use AI to Build a Verified Medical-Record Chronology and Treatment Index
Use approved AI to organize medical records into a source-linked chronology and treatment index while humans verify every citation and lawyers control medical and legal conclusions.
Preview lessonAI-Assisted Law-Firm Workflows
Use AI to Build a Verified Medical-Billing and Payment Ledger
Use approved AI to organize bills, ledgers, EOBs, payments, adjustments, and balances into a source-linked ledger while humans verify every entry and lawyers control medical and legal conclusions.
Preview lessonAI-Assisted Law-Firm Workflows
Use AI to Build a Verified Personal-Injury Demand Package Index
Use approved AI to organize a personal-injury demand package into a source-linked index while humans verify every citation and the lawyer controls liability, causation, damages, coverage, liens, value, and strategy.
Preview lessonAI-Assisted Law-Firm Workflows
Use AI to Prepare a Source-Verified Personal-Injury Demand Letter Draft
Draft a personal-injury demand letter from a lawyer-approved proposition matrix while humans verify every source and the lawyer controls all substantive positions, terms, and transmission.
Preview lessonDemand and Settlement Operations
Track a Personal-Injury Demand, Insurer Responses, Offers, and Follow-Ups
Preserve the exact demand and every response as a source-linked event while humans verify dates, terms, and status and the lawyer controls legal effect, deadlines, negotiation, authority, and settlement.
Preview lesson
