Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Organize witness evidence around discrete claim-handling propositions, not simply witness names or document folders. Preserve each original statement, identify the speaker’s knowledge basis, link precise document passages, and record contradictions, timing uncertainties, and verification tasks. The resulting witness evidence matrix should show what each witness can establish about investigation, valuation, communications, payment, or denial—and what remains unsupported. Counsel can then prepare document-linked interviews and deposition questions without treating an adjuster’s later explanation as proof of what was known when the decision occurred.
When to use this workflow
Use this workflow when a claim-file production, interview, recorded statement, or deposition creates competing accounts of an insurer’s handling decision. It serves policyholder counsel, insurer counsel, and in-house teams testing allegations and defenses against the available evidence.
Define governing substantive law, forum, policy type, first-party or third-party posture, and the decisions at issue. A property-loss investigation and a third-party settlement opportunity require different witness questions. Federal rules discussed below concern federal proceedings; identify the applicable state rules or arbitral requirements before adapting those steps.
Keep coverage breach, alleged unreasonable handling, causation, damages, and defenses distinct in the matrix. Do not use a coverage-supporting document as a substitute for evidence concerning investigation quality or the cause of an asserted loss. This workflow organizes evidence; it does not supply the applicable bad-faith elements.
What you need
Collect a bounded source set relevant to the disputed decisions:
- Policy materials: complete policy, endorsements, relevant applications, and correspondence identifying disputed coverage terms.
- Handling records: native claim-file exports, audit history, attachments, adjuster assignments, supervisory approvals, payment transactions, and relevant third-party administrator records.
- Witness material: original recordings, transcripts, signed statements, interview notes, and deposition testimony, with speaker and recording context.
- Decision inputs: notices, proofs of loss, estimates, expert instructions and reports, vendor submissions, and relevant settlement communications.
- Working controls: stable document IDs or Bates numbers, a chronology, current allegations and defenses, and counsel’s privilege and confidentiality instructions.
Record collection boundaries, custodians, and production cutoffs. A collection described as the “claim file” may omit vendor attachments, earlier report versions, or another repository. Treat an absent document initially as a collection question, not proof that the underlying event never occurred.
Use the template
The Insurance Bad-Faith Matters — Witness evidence matrix links a factual proposition to statements, documents, uncertainty, and action. Copy this table into your working document or spreadsheet. Use one row per proposition; repeat a witness where that person addresses different decisions.
| Row / issue | Witness / basis | Proposition / timing | Statement pinpoint | Document pinpoint | Conflict / gap | Foundation / access | Action / owner |
|---|---|---|---|---|---|---|---|
Assign stable row IDs so an outline can reference a row after sorting. Under Witness / basis, distinguish personal observation, decision involvement, information received from others, and organizational knowledge requiring separate preparation.
Under Proposition / timing, identify the event date and, where material, entry, receipt, and review dates. Statement pinpoint identifies the recording timestamp, transcript page and line, or interview-note paragraph. Label notes as notes, not verbatim testimony.
Use Document pinpoint for Bates numbers plus page, paragraph, attachment, or native-record identifier. Foundation / access records authentication questions and handling restrictions; keep sensitive legal analysis in a separately controlled version. Action / owner includes the verification task, responsible person, and status. Avoid blank cells that leave readers guessing whether an issue was checked.
Step by step
1. Define the decisions and propositions to test
Start with disputed acts: an inspection not performed, a revised valuation, repeated information requests, a payment interval, or a denial approved on a particular record. Break broad allegations into propositions that statements and documents could support or contradict.
For a third-party matter, test who received a settlement communication, its contents, and what reached the decision-maker. For a first-party matter, test whether an adjuster considered a particular report before denying part of a loss. Keep witness facts separate from counsel’s application of the governing legal standard.
Record: row ID, issue category, neutral proposition, and decision date or disputed range. Cross-reference related coverage, handling, causation, or damages rows rather than combining them.
2. Preserve and index each statement
Retain the original recording or document and link any transcript or extracted passage to it. Identify participants, date, statement format, and whether the witness reviewed documents before answering. Check transcription against the recording where wording matters; do not overwrite the original with a corrected transcript.
Separate the witness’s words from counsel’s interpretation. A statement that an adjuster “normally” requests a second estimate does not establish that one was requested on this claim. Preserve qualifications such as uncertain recollection, reliance on routine practice, or information learned afterward.
Record: witness role, knowledge basis, source pinpoint, statement date, and a concise paraphrase retaining material qualifications. Identify any transcript correction and its supporting timestamp.
3. Reconstruct what was available at the decision time
Compare statements with diary entries, email headers, attachments, report versions, approval records, and audit history. Distinguish creation, upload, receipt, review, and decision dates. A later explanatory note should not silently become contemporaneous proof; a report’s presence in the produced file does not establish when an adjuster read it.
The California Department of Insurance’s 2026 disaster-adjusting guide, page 19 describes California’s requirement to diligently pursue a thorough, fair, objective investigation. Use that guidance only within its jurisdiction-specific context, not as a nationwide liability test or authority establishing a private remedy.
Record: supported event, entry, receipt, and review dates. Label inferences and identify the record or witness needed to test them.
4. Pair supporting and adverse evidence
For each material proposition, find the strongest contrary account. A supervisor may remember approving a denial while the approval log identifies another person. An insured may recall supplying photographs while the produced email contains no attachment.
Classify the discrepancy: direct contradiction, different period, ambiguous wording, incomplete collection, or unresolved evidence gap. Preserve both accounts. Do not resolve credibility merely by preferring the more detailed statement or the document with the earlier date.
For alleged delay, identify the triggering communication, receipt evidence, requested action, and completion event. Keep the elapsed interval separate from any legal characterization until counsel validates the applicable source and exceptions.
Record: both pinpoints, discrepancy type, significance, and missing fact needed to resolve it.
5. Review foundation, privilege, and access separately
A useful document link is not an admissibility determination. In federal proceedings, Evidence Rules 901(a) and 803(6) address authentication and the business-records exception separately. Identify who can explain the record’s creation and maintenance, and investigate embedded third-party statements rather than assuming file location resolves admissibility.
Route mixed legal-business communications to counsel. Civil Rule 26(b)(5)(A) requires express claims and descriptions permitting assessment when otherwise discoverable information is withheld as privileged or protected; it does not establish the protection itself. Under Evidence Rule 501, state privilege law governs a civil claim or defense for which state law supplies the rule of decision; mixed claims require further analysis.
Record: foundation witness or question, protection-review status, and access restriction. Do not assume an internal matrix is protected merely because counsel created it.
6. Turn gaps into targeted witness questions
Draft questions tied to missing facts: “What does this status field mean?” or “Which report version did you review before approving the denial?” Supply conflicting passages and enough surrounding context to permit a meaningful answer.
Separate individual recollection from organizational testimony. Federal Civil Rule 30(b)(6) requires reasonably particular examination topics, organizational designation, and good-faith conferral; designees address information known or reasonably available to the organization. An individual adjuster’s involvement does not itself make that person the organizational designee.
Record: proposed question or targeted collection request, intended witness or repository, owner, and the decision the answer would inform. Keep organizational topics distinct from individual interview questions.
7. Verify and issue a controlled working version
Have a reviewer trace material propositions to original statements and documents. Check that attachments exist, timestamps identify the correct speaker, and apparent contradictions survive reading surrounding passages. Mark whether each row is verified, provisionally supported, contradicted, or unresolved; those labels describe evidence status, not liability.
Keep the internal matrix separate from proposed exhibits. Federal Evidence Rule 1006 addresses summaries of voluminous admissible materials and availability of underlying originals or duplicates. A matrix containing argument, uncertainty, and follow-up tasks does not automatically qualify.
Record: verifier, verification date, status, and unresolved assignments. Identify the source-set cutoff and retain earlier versions so new production does not erase the history of an unresolved issue.
Worked example
Fictional scenario: Cedar Quay Foods presents a first-party property claim to Harbor Lantern Insurance after water damages a refrigerated storage room. The April 18, 2026 denial relies on an alleged preexisting equipment condition. Counsel is testing what adjuster Mira Vale considered before denial, not deciding coverage or liability. All parties, dates, documents, and evidence descriptions are fictional.
The bounded collection contains recorded interviews, a claim diary, a vendor report dated April 16, a supervisor’s statement, and an insured representative’s email. It lacks complete audit history and the email’s alleged photograph attachments. The vendor report’s contents have not yet been analyzed in this example.
| Row / issue | Witness / basis | Proposition / timing | Statement pinpoint | Document pinpoint | Conflict / gap | Foundation / access | Action / owner |
|---|---|---|---|---|---|---|---|
| W01 / Investigation | Vale / decision participant | Report considered before April 18 denial | INT-01, 12:10–13:02: recalls reading report beforehand | CLM-0042, p. 2: upload April 20; REP-01, p. 1: dated April 16 | Earlier delivery possible; upload does not disprove recollection | Verify upload-field meaning; restricted analysis | Associate: obtain delivery record and identify version reviewed; open |
| W02 / Approval | Jonah Reed / supervisor | Approval communicated before issuance | ST-02, ¶4: recalls April 17 approval | CLM-0045, p. 1: approval entry April 19 | Late entry or different event unresolved | Identify entry author and audit source | Counsel: ask how approval was communicated; obtain audit history; open |
| W03 / Submitted evidence | Lena Moss / insured representative | Photographs sent April 12 | INT-03, 08:20–09:15: recalls attachments | EMAIL-07, p. 1: references photographs; copy lacks attachments | Sending, receipt, and contents unverified | Preserve native message; verify recipient evidence | Paralegal: obtain native email and attachments from custodians; open |
W01 directs counsel toward transmission evidence and report-version identification rather than treating upload as receipt. W02 requires testing whether an approval occurred before its diary entry. W03 presents a collection gap, not proof that photographs were ignored or never sent.
These distinctions change the next interview and collection tasks. They do not establish whether the investigation was unreasonable. Even after transmission is verified, counsel must examine what the report or photographs actually showed and how that information related to the stated denial reason.
Common mistakes
- One row per witness: Different decisions become indistinguishable. Use one row per proposition and cross-reference related entries.
- Treating the claim file as complete: Missing vendor materials can distort the theory. Identify repository boundaries and request the specific missing source.
- Collapsing receipt and knowledge: Upload does not necessarily establish personal review. Identify delivery route, recipient, and evidence of consideration.
- Extracting only favorable passages: Qualifications disappear. Include adverse passages and explain whether they contradict or address another event.
- Recording conclusions as facts: “Bad-faith delay established” conceals unresolved law and evidence. Record the interval, sources, and separately assigned legal analysis.
Final quality check
- Each row addresses a distinct proposition relevant to the policy and claim posture.
- Paraphrases match original passages, including qualifications and knowledge limits.
- References resolve to the correct version, page, recording segment, and attachment.
- Event, entry, receipt, and review dates remain distinguishable.
- Supporting and adverse evidence appear together; collection gaps are labeled accurately.
- Foundation, protection, and access questions are resolved or assigned.
- Every open issue has an owner, specific task, and status.
- The source-set cutoff is stated; internal analysis remains separate from proposed exhibits.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, chronology, evidence analysis, and deposition preparation. Use chronology work to examine decision timing and connect verified references to deposition preparation. The matrix is counsel’s work product, not a promised dedicated product module; lawyers retain responsibility for significance, protection, and follow-up. To discuss this workflow for claim-handling records, book a demo.
Frequently asked questions
Should statements be quoted or paraphrased?
Use faithful paraphrases for navigation. Preserve exact wording when a qualification, admission, or disputed phrase matters. Retain the original and pinpoint, and label interview notes distinctly from recordings or testimony.
How should conflicting adjuster accounts be organized?
Link both accounts to the same proposition with dates and knowledge bases. Test whether they concern the same decision, report version, and period. Assign a targeted question instead of silently choosing an account.
Can the matrix identify a witness for every document?
Record a proposed foundation witness, then verify the basis. Distinguish recognizing a document from explaining its creation, transmission, recordkeeping context, or contents. Preserve unresolved foundation questions rather than treating the designation as established.
When is the matrix ready for deposition preparation?
When material propositions have checked pinpoints, adverse evidence is visible, and gaps produce specific questions or collection tasks. Full collection is not required, but the source cutoff and unresolved assignments must be explicit.
Sources
- Federal Rules of Civil Procedure: Rules 26(b)(5)(A) and 30(b)(6).
- Federal Rules of Evidence: Rules 501, 803(6), 901(a), and 1006.
- California Department of Insurance, 2026 disaster-adjusting guide: page 19.
Scope: General professional workflow guidance with a research cutoff of October 13, 2026. Applicable law, historical versions, policy language, and case-specific orders require matter-level verification.
This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.
