A recorded statement can lock a claimant into details before the full medical and liability record is assembled. Months later, a demand letter that changes the sequence, certainty, or scope of those details gives the carrier an avoidable credibility issue—even when the underlying claim remains strong.
The drafting problem is not simply “stay consistent.” Plaintiff firms need a repeatable way to distinguish genuine contradictions from harmless differences in wording, incomplete early recollection, and facts clarified by later evidence. The demand should remain faithful to the client’s testimony without treating the first account as more complete than the record supports.
Why recorded statements create a distinct demand-drafting risk
Recorded statements are usually taken early, when the claimant may still be treating, may not have reviewed the police report, and may not yet understand which facts will become disputed. Questions can move quickly across vehicle position, speed, visibility, prior symptoms, immediate complaints, and later treatment. The answers become a fixed reference point for the carrier’s evaluation.
That matters because the demand is normally prepared from a broader source set: intake notes, the collision report, photographs, witness accounts, medical records, billing, employment documents, and attorney analysis. A polished narrative can therefore sound more definite than the client sounded in the earlier statement. If the demand says the plaintiff “saw the defendant enter against the light,” but the recorded statement says the plaintiff did not see the signal before impact, the issue is not style. It is a factual conflict that should be resolved before the package leaves the firm.
California Evidence Code section 1220 provides that a party’s own statement may be offered against that party, subject to the rest of the evidentiary framework. A carrier’s pre-suit use of a recorded statement is not the same as a trial court’s admissibility ruling, but the practical lesson is straightforward: assume the adjuster can compare the demand against the claimant’s earlier words. Do not create a cleaner narrative by silently replacing uncertainty with certainty.
The same discipline applies beyond California. The governing evidentiary and procedural rules differ by jurisdiction, but factual consistency remains central to claim evaluation, deposition preparation, mediation, and trial strategy.
Build the liability narrative from sources, not memory
A reliable workflow starts by treating the recorded statement as a source document, not as background material. The person drafting the demand should be able to identify which propositions come directly from the client, which come from independent evidence, and which are attorney inferences.
Create a statement-to-evidence crosswalk
Before drafting liability, extract the portions of the statement that bear on fault and credibility. The crosswalk does not need to reproduce every question and answer. It should capture the statements an adjuster is likely to test against the demand:
- where each vehicle or person was immediately before the incident;
- what the client saw, heard, or felt before impact;
- whether the client estimated speed, distance, timing, or signal phase;
- what the client said about immediate symptoms and activity limits;
- any prior injury, symptom, treatment, or similar event discussed;
- uncertain answers, corrections, interruptions, or qualified language; and
- facts later confirmed or contradicted by photographs, reports, witnesses, or records.
For each item, identify the supporting source and classify the relationship as aligned, clarified, unresolved, or conflicting. This is more useful than a generic “consistent/inconsistent” label. A client who initially could not estimate speed may later describe the force of impact after seeing vehicle damage; that is not automatically a contradiction. A client who first denied prior neck symptoms and whose earlier records show cervical treatment presents a different problem.
Preserve uncertainty where the evidence remains uncertain
Demand letters often become vulnerable when the prose outruns the record. Words such as “approximately,” “appeared,” “did not observe,” and “could not estimate” are not drafting defects when they accurately reflect the evidence. They can make the narrative more credible by separating established facts from interpretation.
The safer approach is to anchor the account to what can be supported. Instead of converting a client’s rough timing estimate into a precise number, the demand can describe the sequence and cite the physical evidence that matters. Instead of attributing a statement to the client that appears only in counsel’s intake summary, confirm it against the recording or transcript. This complements a broader intake-to-demand source review, but recorded testimony deserves its own checkpoint because the carrier may already possess the exact audio.
A practical pre-demand consistency review
The review should occur before the liability narrative is finalized, not after the demand is assembled. A five-step process keeps the issue manageable.
- Confirm the authoritative source. Obtain the actual audio, transcript, or both. A claim-handler summary is useful for issue spotting, but it is not a substitute for the client’s words and the context of the questions.
- Separate material points from verbal variation. Focus on facts that could affect liability, causation, damages, notice, comparative fault, or credibility. Two descriptions can differ in phrasing without differing in substance.
- Resolve true conflicts with counsel. Do not let a drafter or software quietly choose the version that reads better. Counsel should determine whether the demand must disclose, explain, qualify, omit, or investigate the conflict.
- Use independent evidence deliberately. Photographs, event data, video, witness accounts, and official reports may clarify an early statement. Say what the evidence establishes without rewriting what the client personally perceived.
- Run a final source check. Compare the completed liability and causation sections against the statement crosswalk. Confirm that quotations are exact, paraphrases are fair, and no uncertain answer has become an unqualified assertion.
This review is particularly important when treatment develops after the statement. A claimant may accurately report mild soreness on the day of the incident and later develop symptoms that lead to additional evaluation. The demand should present the documented progression without implying that the later condition was fully described in the initial call. Medical chronology and causation analysis should do that work.
What automation should flag—and what it should not decide
AI can help compare a transcript against a draft and surface mismatched dates, body parts, prior-treatment references, speed estimates, quoted language, and degrees of certainty. It can also produce a list of propositions that appear in the draft but lack an obvious source. These are valuable review tasks because they reduce the chance that a long file hides a small but material discrepancy.
Automation should not decide whether two statements are legally inconsistent, whether a conflict is material, or how counsel should address it. Context matters. A transcript may contain a transcription error. A question may be compound. The client may have corrected an answer two minutes later. New evidence may explain an early uncertainty without changing the client’s testimony. Those judgments belong to the attorney responsible for the demand.
Firms should also preserve a review trail. Keep the source used, the flagged passages, the attorney’s disposition of each material issue, and the final approved language. If the demand changes after review, rerun the comparison rather than assuming the earlier clearance still applies.
How Legal Power AI fits
Legal Power AI supports source-grounded demand-letter workflows by organizing case materials and helping firms draft from the assembled record rather than from disconnected notes. When sensitive records or transcripts are processed, work-product and confidentiality obligations still apply; Legal Power AI uses OpenAI and Anthropic under business associate agreements for HIPAA-eligible processing, and the attorney remains responsible for reviewing every factual statement and approving the final demand.
Consistency is a review discipline, not a writing trick
A demand letter should not mimic the client’s recorded statement word for word. It should synthesize the complete file while remaining honest about what the client said, what later evidence established, and what counsel is arguing. The best safeguard is a visible chain from source to proposition: recorded testimony, corroborating or conflicting evidence, attorney decision, and final language.
When firms make that chain part of pre-demand review, they reduce avoidable credibility disputes and give attorneys a clearer record for negotiation, discovery, and mediation. The objective is not artificial uniformity. It is a liability narrative that can withstand comparison with the sources the carrier already has.
See a source-grounded demand workflow in action.