A prior injury does not automatically weaken a personal-injury demand. An incomplete prior-injury record does. When the file leaves unanswered whether the same body part was symptomatic before the incident, the carrier gets to frame the gap: preexisting condition, unrelated treatment, degeneration, or an intervening cause.
The better workflow begins before drafting. Plaintiff firms should identify potentially similar prior injuries, separate baseline symptoms from post-incident change, and build a source-supported causation record that an attorney can evaluate. The point is not to hide unfavorable history or let software decide medical causation. It is to prevent a predictable issue from surfacing for the first time in the adjuster’s response.
Why prior similar injuries become a drafting problem
Most causation problems are not created by one bad fact. They are created by inconsistent descriptions of the same fact across intake notes, medical records, testimony, and the demand. A client may describe an old shoulder injury as “resolved,” while a record shows intermittent complaints six months before the new collision. A provider may document “no prior symptoms,” even though the client previously received conservative care. The demand writer may then repeat the cleanest version without seeing the conflict.
That inconsistency gives a carrier several ways to challenge the presentation. The adjuster may argue that the current condition predates the incident, that treatment addressed ordinary degeneration, or that the demand overstates the duration of a symptom-free period. Even if the attorney has a sound aggravation theory, the demand loses credibility when its factual language is broader than the supporting records.
California’s civil jury instructions provide a useful conceptual distinction. CACI No. 3927 addresses aggravation of a preexisting condition or disability and focuses damages on the harm caused by the aggravation. CACI No. 3928 addresses an unusually susceptible plaintiff—the familiar “eggshell plaintiff” concept. A pre-litigation demand is not a jury instruction, but the distinction still matters: a firm should know whether it is asserting a new injury, an aggravation, an increased susceptibility theory, or some combination supported by the evidence.
The operational mistake is waiting until the demand paragraph is being written to make that classification. By then, the file may have moved through intake, records collection, treatment monitoring, and attorney review without anyone owning the prior-history question.
Build the causation record before choosing the narrative
A useful prior-injury review should answer four separate questions: what happened before, what the plaintiff’s baseline was immediately before the subject incident, what changed afterward, and what evidence supports that change. Those questions require more than a keyword search for the same body part.
1. Define “similar” broadly enough to catch the real issue
Exact diagnosis matching is too narrow. A prior cervical strain, intermittent arm numbness, chiropractic care, and an earlier MRI finding may all be relevant to a later neck-and-radiculopathy claim even when the labels differ. The review should include:
- the same anatomical region and adjacent regions;
- overlapping symptoms, including radiating pain, weakness, headaches, or range-of-motion complaints;
- prior accidents, workers’ compensation claims, sports injuries, and non-traumatic treatment;
- pre-incident imaging findings and specialist recommendations; and
- medications, injections, therapy, or activity restrictions that continued near the incident date.
This does not mean every historical complaint belongs in the demand. It means the attorney should see the potentially relevant history before deciding what belongs.
2. Establish the pre-incident baseline
“Prior injury” and “active symptoms at the time of loss” are not interchangeable. A meaningful baseline asks whether symptoms had resolved, stabilized, recurred intermittently, or remained under active treatment. Useful sources may include the last pre-incident visit, refill history, imaging chronology, work restrictions, activity notes, and the client’s account—each weighed according to reliability.
Absolute language creates avoidable risk. “The plaintiff had no prior neck problem” is materially different from “the available records show no neck treatment during the eighteen months before the collision.” The second statement defines the evidence and time period. It does not claim more than the file proves.
3. Identify the post-incident change
The causation analysis should focus on delta, not merely chronology. What became new, more frequent, more severe, or functionally limiting after the incident? Did the treatment modality change? Did imaging show a finding that a qualified medical professional connected to the incident? Did the plaintiff move from occasional self-management to structured therapy, injections, or specialist care?
Temporal proximity helps organize the story, but sequence alone does not establish medical causation. Drafting software can surface dates, compare symptom descriptions, and flag contradictions. It should not invent a physician opinion or convert silence in a record into an affirmative causal conclusion.
4. Separate source facts from attorney theory
Build two layers. The first is the source layer: record date, provider type, complaint, diagnosis, treatment, imaging, and functional limitation. The second is the advocacy layer: why the pattern supports a new-injury or aggravation theory. Keeping those layers distinct makes attorney review faster and reduces the risk that an inference is presented as a charted fact.
This separation also makes updates easier. If a late-arriving prior record changes the baseline, the team can revise the theory without rebuilding the entire treatment chronology. For a broader framework on that separation, see why demand automation should keep medical facts distinct from advocacy language.
A practical pre-demand workflow for prior similar injuries
The following sequence turns a vague “check priors” instruction into a repeatable review gate.
- Ask targeted intake questions. Identify prior complaints by body region, not only prior claims. Ask about symptom status, treatment, imaging, restrictions, and the last date of care before the subject incident.
- Create a prior-history issue list. Record each potentially similar condition, the relevant time window, known sources, missing sources, and the attorney responsible for deciding materiality.
- Collect proportionately. Request records that can establish baseline and change without turning the file into an indiscriminate lifetime-history search. Scope should follow the claims, defenses, authorizations, and applicable procedural obligations.
- Build a side-by-side comparison. Compare pre- and post-incident symptoms, treatment intensity, imaging, work status, activities, and provider assessments. Mark unsupported fields as unknown rather than filling them by inference.
- Flag conflicts. Surface discrepancies among intake notes, client statements, prior records, current records, and draft language. A conflict is an attorney-review item, not something an automated system should quietly reconcile.
- Choose the causation frame. Decide whether the evidence supports a new condition, aggravation, increased susceptibility, or a narrower presentation. Identify which propositions are record facts and which require medical or legal judgment.
- Draft with bounded language. Use dates, source attribution, and defined time periods. Avoid “never,” “fully resolved,” and “entirely caused by” unless the evidentiary record supports them.
- Run a final consistency check. Confirm that the liability section, medical chronology, causation analysis, damages discussion, and exhibits describe the prior history consistently.
This workflow should happen early enough to change collection strategy. If the review reveals unresolved prior complaints, the firm may need additional records, clarification from the client, or an attorney decision before the demand is ready. That is a better outcome than learning about the issue from the carrier after submission.
What AI can support—and what remains attorney work
AI can assist with document sorting, date normalization, symptom comparison, treatment-gap detection, and conflict flags across a large record set. Those are valuable functions because prior-history analysis often fails through omission: one old imaging report, an intake phrase, or a continuing medication is overlooked.
But relevance, admissibility, medical causation, privilege, proportionality, and advocacy remain legal decisions. An attorney should verify the cited source, review the surrounding context, and decide whether the proposed narrative fairly represents the evidence. AI-assisted drafts are work product that still require the firm’s accuracy review before use. When medical records or other protected health information are processed, the firm should also evaluate vendor safeguards and contractual terms rather than treating a general-purpose model as an approved legal workflow.
How Legal Power AI fits
Legal Power AI is designed to support plaintiff PI demand workflows by organizing source material, helping teams identify inconsistencies, and producing a reviewable starting draft—not by replacing attorney judgment. Its demand-letter workflow can help keep the prior-history source layer visible while counsel controls the causation theory, verifies accuracy, and approves the final document.
Conclusion
Prior similar injuries should be treated as an early file-management issue, not a late drafting surprise. A disciplined process defines the relevant history, establishes the plaintiff’s baseline, identifies the post-incident change, and separates record facts from advocacy. That produces a demand that is more precise about what the evidence shows and clearer about what the attorney is asking the carrier to conclude.
The goal is not to eliminate difficult facts. It is to surface them early enough for counsel to investigate, frame, and review them before the demand leaves the firm.
See a more reviewable demand workflow
Explore how Legal Power AI helps plaintiff PI teams move from organized source material to an attorney-reviewed demand draft.