Live Webinar 5/27: Dive into ParseBench and learn what it takes to evaluate document OCR for AI Agents

Demand Letter Analysis

Demand letter analysis is a structured evaluation process applied to formal legal demand letters in personal injury, insurance, and civil dispute contexts. For claims professionals, attorneys, and adjusters, the ability to assess the validity, strength, and fair value of a demand is a core competency — one that directly affects settlement outcomes and litigation exposure. Understanding what the analysis involves and how to carry it out accurately is essential before taking any response action.

One practical challenge in this process is document parsing. Demand letters rarely arrive as clean, structured text. They typically come with dense PDF packages containing medical records, billing statements, itemized damages, and legal arguments — documents with inconsistent formatting, multi-column layouts, embedded tables, handwritten annotations, and sometimes exhibits that require right-to-left text recognition. OCR tools that rely on simple text extraction frequently misread or omit critical data from these materials, introducing errors before the analysis even begins. Accurate document parsing is therefore a prerequisite for reliable demand letter analysis, not an afterthought.

What Demand Letter Analysis Actually Involves

A demand letter analysis is the structured review and evaluation of a formal legal demand letter to assess the validity, strength, and fair value of the claims it contains. It is distinct from simply receiving a demand letter — the letter is the document, while the analysis is the deliberate, methodical process applied to it.

Why the Analysis Matters

Receiving a demand letter triggers a legal and financial obligation to respond. The analysis ensures that response is informed, defensible, and proportionate to the actual merits of the claim. Without a structured review, respondents risk either overpaying on inflated claims or exposing themselves to litigation by improperly denying valid ones.

Who Performs Demand Letter Analysis

Demand letter analysis is performed by professionals with legal, claims, or risk management expertise. The table below identifies the primary roles involved, the context in which each performs the analysis, and the specific objectives and considerations that shape their approach.

Role / ProfessionalContext in Which They AnalyzePrimary ObjectiveKey Considerations Unique to This Role
Insurance AdjusterUpon receipt of a demand from a claimant's attorney during the claims processDetermine fair settlement value within applicable policy limitsPolicy coverage scope, bad faith exposure, reserve adequacy
Defense / Coverage AttorneyWhen litigation is anticipated or the insurer requires legal guidance on a complex claimAssess legal liability, litigation risk, and defensibility of the claimDiscovery costs, case law precedent, jurisdictional exposure
Plaintiff's AttorneyWhen reviewing a demand on behalf of a client to verify it accurately reflects documented damagesConfirm the demand is well-supported and strategically positionedCompleteness of damages documentation, negotiation leverage
Independent Claims ProfessionalThird-party review engagements, audits, or high-value claim evaluationsProvide an objective, unbiased valuation of the claimNeutrality, consistency with industry standards, documentation quality

When the Analysis Is Triggered

Analysis begins at a specific point in the legal or claims lifecycle — typically after a formal demand letter is received and before any response is issued. In insurance contexts, this is usually after an incident has been reported, investigated, and a claimant's attorney has submitted a settlement demand. In civil dispute contexts, it may occur pre-litigation as a final attempt to resolve the matter without court involvement.

Components of a Demand Letter That Require Evaluation

The analytical process focuses on several distinct components of the demand letter, each requiring independent evaluation. Reviewers assess not only what is claimed, but whether the claims are supported, reasonable, and internally consistent.

Establishing Liability

The first question in any demand letter analysis is whether fault is clearly established. A strong liability argument identifies the responsible party, explains the legal basis for that determination, and connects the incident directly to the claimant's damages.

  • Clearly established liability — The demand identifies a specific act or omission, cites applicable law or duty of care, and provides evidence linking the respondent to the incident.
  • Disputed liability — The demand relies on vague assertions, lacks corroborating evidence, or involves comparative fault scenarios where the claimant may share responsibility.
  • Missing liability foundation — No causal chain is established between the respondent's conduct and the claimed damages, which significantly weakens the demand.

Scrutinizing the Damages Breakdown

Damages are the financial core of any demand letter and require the most detailed scrutiny. Each category carries its own documentation requirements, evaluation logic, and common failure modes. The table below provides a structured reference for evaluating each damage type.

Damage CategoryDescriptionCommon Supporting DocumentationKey Evaluation CriteriaCommon Red Flags
Medical Expenses (Past)Costs incurred for treatment directly related to the incidentHospital bills, itemized invoices, explanation of benefits (EOB)Causal link to incident, treatment necessity, billing accuracyDuplicate billing, unrelated treatments, inflated procedure codes
Medical Expenses (Future)Projected costs for ongoing or anticipated treatmentLife care plan, physician prognosis, specialist reportsMedical necessity, realistic cost projections, supporting diagnosisSpeculative projections without physician support, no documented ongoing condition
Lost Wages / Loss of Earning CapacityIncome lost due to inability to work during recovery or permanentlyPay stubs, employer verification letter, tax returnsVerified employment, documented time missed, causal link to injuryUndocumented income, inconsistent work history, no employer confirmation
Pain and Suffering / Emotional DistressNon-economic damages for physical pain and psychological impactPhysician notes, mental health records, personal journal entries, witness statementsConsistency with documented injuries, duration and severity of impactDisproportionate demand relative to documented injury severity, no supporting records
Property DamageRepair or replacement costs for damaged physical propertyRepair estimates, replacement invoices, photographs, appraisal reportsAccuracy of estimates, pre-incident condition of property, fair market valueInflated repair estimates, pre-existing damage included, no independent appraisal
Miscellaneous / Out-of-Pocket ExpensesIncidental costs such as transportation, home care, or assistive devicesReceipts, invoices, care provider statementsDirect connection to incident, reasonableness of amountsUndocumented expenses, costs unrelated to the claimed injury

Assessing Supporting Documentation Quality

The strength of a demand letter depends on the quality of the evidence package behind it. Reviewers must assess both completeness and quality:

  • Are all claimed damages supported by corresponding records?
  • Are medical records internally consistent with the injury narrative?
  • Are billing statements itemized and free of duplicate or unrelated charges?
  • Is there a clear evidentiary chain connecting the incident to each claimed loss?

Gaps in documentation — missing records, unsigned authorizations, or unexplained treatment gaps — are legitimate grounds for requesting additional information before responding.

Component Evaluation Checklist

The table below consolidates the full review into a repeatable checklist, mapping each component to its strength and weakness indicators and the action each finding should trigger.

ComponentWhat to Look ForIndicators of StrengthIndicators of Weakness or ConcernAction Triggered
Liability ArgumentClear identification of fault, legal basis, causal chainSpecific incident details, corroborating evidence, established duty of careVague assertions, no evidence, shared fault scenarioStrong: proceed to damages review; Weak: flag for denial or request clarification
Damages RequestedItemized breakdown of all claimed losses by categoryEach category documented, amounts consistent with recordsLump-sum demand, undocumented categories, amounts inconsistent with recordsStrong: evaluate reasonableness; Weak: request itemization or flag for reduction
Supporting DocumentationComplete records package accompanying the demandAll categories supported, records internally consistentMissing records, treatment gaps, unsigned authorizationsComplete: proceed with analysis; Incomplete: issue documentation request
Settlement Amount ReasonablenessDemand amount relative to documented and verifiable lossesDemand aligns with documented damages and comparable settlementsDemand significantly exceeds documented losses, no valuation basis providedReasonable: consider acceptance or minor counteroffer; Unreasonable: prepare counteroffer with documented rationale
Claim CompletenessAll elements of a valid claim present (liability, causation, damages)Coherent narrative, all elements addressedMissing causation argument, unexplained damage categoriesComplete: proceed to response; Incomplete: request supplemental information

Evaluating Whether the Settlement Demand Is Reasonable

Even when liability is clear and damages are documented, the demanded settlement amount must be evaluated against fair market value for comparable claims. Reviewers should consider:

  • The total of all documented, verifiable losses
  • Applicable policy limits and coverage terms
  • Comparable settlement values for similar claims in the same jurisdiction
  • The strength of the liability argument and the likelihood of a plaintiff prevailing at trial

A demand that significantly exceeds documented losses without a credible legal or factual basis is a strong indicator that negotiation — rather than acceptance — is the appropriate response.

Selecting and Documenting the Right Response

The analysis findings directly determine the response strategy. There are three primary response paths: accept the demand, deny it, or issue a counteroffer. Each carries distinct legal, financial, and procedural implications.

Matching the Response to the Analysis Findings

The table below maps each response type to the conditions that warrant it, the key factors to weigh, the documentation required, and the common pitfalls to avoid.

Response TypeWhen This Response Is AppropriateKey Factors to ConsiderRecommended Documentation / RationaleCommon Pitfalls to Avoid
AcceptLiability is clear, damages are well-documented, and the demanded amount is reasonable relative to verified lossesStrength of liability evidence, completeness of documentation, policy limits, litigation cost comparisonWritten acceptance confirming settlement terms, internal memo documenting the valuation basisAccepting without verifying all damage categories; failing to obtain a signed release
Deny / RejectLiability is disputed or absent, damages are entirely unsupported, or the claim falls outside coverageAbsence of causal link, lack of documentation, coverage exclusions, statute of limitations issuesWritten denial letter citing specific grounds; internal file note documenting each basis for denialIssuing a denial without documented grounds; failing to cite specific deficiencies, which creates bad faith exposure
Counteroffer / NegotiateLiability is established but damages are exaggerated, documentation is incomplete, or the demand exceeds fair market valueDocumented loss total, comparable settlement data, litigation risk, strength of specific damage categoriesCounteroffer letter with itemized reasoning; internal valuation worksheet supporting the proposed figureMaking a counteroffer without a defensible valuation basis; failing to document the analytical rationale

Building a Defensible Counteroffer Amount

When the analysis supports a counteroffer rather than acceptance or denial, the proposed figure must be grounded in documented evidence. The following factors inform a defensible counteroffer:

  • Verified damages total — Sum only the losses that are documented and causally linked to the incident.
  • Liability percentage — If comparative fault applies, adjust the offer proportionally.
  • Jurisdiction-specific benchmarks — Reference comparable settlements or jury verdicts for similar claims in the same venue.
  • Litigation cost analysis — Weigh the cost of defending the claim at trial against the cost of settling within a reasonable range.
  • Policy limits — Ensure the counteroffer is within applicable coverage boundaries.

Response deadlines vary by jurisdiction, claim type, and the terms stated in the demand letter itself. Missing a deadline can have serious legal and financial consequences. The table below provides a reference for common scenarios.

Context / ScenarioTypical Response TimeframeConsequences of Missing the DeadlineRecommended Internal Timeline
Personal Injury — Insurance Claim30 days (varies by state; some jurisdictions mandate specific windows)Claimant may proceed to litigation; insurer may face bad faith exposureBegin analysis within 5 days of receipt; complete review by day 20; issue response by day 28
Civil Dispute — Pre-LitigationPer deadline stated in the demand letter (commonly 10–30 days)Claimant may file suit without further noticeAcknowledge receipt immediately; complete analysis before the midpoint of the stated deadline
Property Damage Claim30–45 days depending on policy terms and state lawPotential breach of contract claim; regulatory complaint riskRequest any missing documentation within 10 days; finalize response within policy-mandated window
Workers' CompensationGoverned by state-specific workers' compensation statutesAdministrative penalties; loss of right to contest the claimConsult applicable state statute immediately upon receipt; do not rely on general timelines

Note: All timeframes are general references only. Applicable deadlines vary by jurisdiction and claim type. Readers should verify requirements with qualified legal counsel.

Why Documenting the Response Rationale Matters

Regardless of which response path is chosen, the rationale must be documented in the claim file or legal record. Proper documentation serves multiple purposes:

  • Creates an auditable record of the analytical process
  • Supports the response decision if the matter proceeds to litigation
  • Demonstrates good faith handling in insurance contexts
  • Provides a reference baseline if the claim is reopened or escalated

At minimum, the file should include a summary of the analysis findings, the specific factors that drove the response decision, the valuation methodology used for counteroffers, and the date and method of the response.

Final Thoughts

Demand letter analysis is a multi-layered process that requires systematic evaluation of liability, damages, documentation quality, and settlement reasonableness before any response is issued. The process covered in this article — from identifying who performs the review and what components to examine, to selecting and documenting the appropriate response — provides a repeatable structure that applies across personal injury, insurance, and civil dispute contexts. Accurate document parsing is a foundational prerequisite for this process, as errors introduced at the extraction stage carry through every subsequent evaluation step.

LlamaParse delivers VLM-powered agentic OCR that goes beyond simple text extraction, boasting industry-leading accuracy on complex documents without custom training. By leveraging advanced reasoning from large language and vision models, its agentic OCR engine intelligently understands layouts, interprets embedded charts, images, and tables, and enables self-correction loops for higher straight-through processing rates over legacy solutions. LlamaParse employs a team of specialized document understanding agents working together for unrivaled accuracy in real-world document intelligence, outputting structured Markdown, JSON, or HTML. It's free to try today and gives you 10,000 free credits upon signup.

Start building your first document agent today

PortableText [components.type] is missing "undefined"