How to prepare a document collection checklist for Insurance Bad-Faith Matters

Prepare the checklist by translating each disputed claim-handling decision into document categories, custodians, repositories, and collection instructions. Start with the complete policy and claim history, then trace investigation, valuation, communications, approvals, and payments across insurer, insured, and vendor systems. Record what was collected, what remains uncertain, and who must resolve each gap. The deliverable is a source-linked collection checklist that distinguishes uncollected material, unavailable records, and material awaiting privilege review while preserving the context counsel needs for discovery decisions.

When to use this workflow

Use this workflow when counsel receives an incomplete claim file, prepares document requests, organizes a client-side collection, or investigates gaps in an insurer’s production. It serves policyholder and insurer counsel, although access differs: an insurer may retrieve internal audit histories directly, while policyholder counsel may need discovery.

Identify the forum, governing substantive law, policy type, first-party or third-party posture, and applicable orders. A first-party property dispute may turn on inspection and estimate revisions; a third-party failure-to-settle dispute may require demands, defense evaluations, settlement-authority requests, and insured notifications.

In federal district court, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case’s needs. Relevance does not establish admissibility. Use this standard to prioritize collection without equating collection with production eligibility. Federal Rule of Civil Procedure 26(b)(1). Check state or arbitral requirements separately. (uscourts.gov)

What you need

Assemble these inputs before assigning searches:

• Matter boundaries: allegations, defenses, claim numbers, relevant dates, and disputed handling decisions.
• Coverage documents: policies, declarations, endorsements, applications, binders, and correspondence identifying potentially applicable periods or versions.
• Claim materials: notices, proofs of loss, photographs, estimates, expert instructions and reports, statements, recordings, reservation letters, denials, settlement communications, and payment records.
• People and systems: adjusters, supervisors, coverage personnel, third-party administrators, brokers, investigators, experts, and their repositories.
• Collection constraints: prior productions, request numbers, inventories, access restrictions, preservation instructions, confidentiality arrangements, and privilege-review instructions.

Obtain a sample claim-system export early. Determine whether it includes attachments, historical entries, assignment changes, and audit information. Identify sources at risk of routine deletion and refer preservation questions to counsel before searches or exports alter records.

Use the template

Use the Insurance Bad-Faith Matters — Document collection checklist below. You can copy this table into your working document or spreadsheet. Maintain discovery-response commitments separately; this checklist records collection tasks and results.

Create one row per independently verifiable task. Separate an adjuster’s mailbox from the claim platform, even when both contain related correspondence.

Use Issue / scope for the disputed decision, period, and request reference. Collection instruction specifies attachments, versions, native records, date filters, and the approved search scope. Evidence / status identifies document IDs, Bates ranges, pages, or a linked inventory—not merely “complete.” Use an inventory reference when collection-method details will not fit in the cell.

Distinguish “pending collection,” “collected—review pending,” and “verified against defined scope.” Under Gap / review flag, separate inaccessible sources, missing attachments, privilege questions, and discrepancies. Assign every unresolved row an owner and concrete action.

Step by step

1. Translate the allegations into collection questions

List the challenged decisions: delayed investigation, selective reliance on an expert, unexplained valuation changes, denial despite contrary information, or failure to address a settlement opportunity. Ask what the decision-maker knew, when information arrived, what further investigation occurred, and who approved the outcome.

Separate coverage, alleged unreasonable handling, causation, damages, and defenses. Identify evidence supporting the insurer’s explanation as well as evidence challenging it.

For California property claims, the Department of Insurance’s disaster-adjusting guide describes section 2695.7(d)’s investigation requirements and restrictions on persistent requests for information not reasonably required or material to resolving the dispute. Use this jurisdiction-specific guidance to frame collection questions, not to establish liability or a private remedy. California Department of Insurance guide, page 19. (insurance.ca.gov)

Record: an issue-linked task and the evidence needed to test competing explanations.

2. Map custodians and repositories beyond the claim file

Ask the collection contact how the claim moved through the organization. Identify reassigned adjusters, supervisor approvals, vendor portals, shared folders, email, messaging, recorded calls, and payment systems. Determine whether a third-party administrator retains records outside the insurer’s platform.

For policyholder collections, include submissions through brokers or contractors and evidence of delivery. For third-party matters, locate demands, defense evaluations, and authority communications, subject to privilege review.

Do not treat an inaccessible vendor repository as empty. Identify whether the client can obtain its records or counsel must pursue another discovery route. Collection access and any asserted right to obtain records require separate assessment.

Record: the custodian or responsible function, repository, access limitation, and collection owner.

3. Define policy, time, and version boundaries

Collect the complete potentially applicable policy, including endorsements modifying definitions, exclusions, conditions, or settlement provisions. Match policy numbers and periods to the claim rather than relying on declarations or a policy copied from another file.

Choose date ranges around the disputed decisions. A denial-focused collection may need earlier investigation and later communications revisiting the denial. Tie manuals and training materials to the handling period; a current manual does not establish historical instructions.

Include applications or underwriting materials when an asserted issue makes them relevant. Avoid undifferentiated searches for every underwriting record, unrelated claim, or company manual.

Record: policy identifiers, date boundaries, version requirements, and the reason for each category. Assign uncertain boundaries to counsel for approval.

4. Specify how each source should be collected

For claim platforms, seek available native exports, attachments, audit histories, assignments, vendor submissions, and payment transactions. Ask the system contact to explain export omissions and timestamp conventions. Preserve original statements and recordings, not only summaries or transcripts.

For email, retain attachments and sufficient thread context. For revised estimates, collect identifiable versions and transmission records. Distinguish event dates, entry dates, and receipt dates; an entry timestamp alone may not show when an adjuster received information.

Record who supplied the collection and how it was generated. In federal proceedings, authentication under Rule 901(a) and the business-records foundation under Rule 803(6) are separate evidentiary questions; collecting a claim-file document does not resolve either. Federal Rules of Evidence 901(a) and 803(6). (uscourts.gov)

Record: collection method, included components, inventory reference, and technical limitations.

5. Reconcile the collection against internal references

Follow references within collected records. Match diary entries mentioning reports to the reports themselves, outgoing letters to attachments, and payment entries to transaction records. Investigate “supervisor approved” entries without corresponding approval records.

Sample key dates and custodians before accepting a large export. Check whether early entries, closed tasks, archived attachments, or available edit histories were excluded. A sequence gap warrants investigation; it does not prove destruction.

Separate “not found in this collection” from “confirmed unavailable after a documented search.” If a source owner reports no responsive records, document the repository, search scope, and explanation. Avoid closing a task based solely on an unexplained assurance that the claim file is complete.

Record: pinpoint references, reconciliation results, missing components, and supplemental collection instructions.

6. Route privilege and confidentiality questions separately

Preserve source relationships while directing potentially protected material to counsel. Identify participants and roles, apparent legal or business purpose, and facts relevant to anticipated litigation. Do not assume counsel’s involvement protects every communication.

In federal cases, Rule 26(b)(5)(A) requires express privilege claims and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses the timing and method of compliance in discovery planning. These provisions do not establish privilege. Federal Rules of Civil Procedure 26(b)(5)(A) and 26(f)(3)(D). (uscourts.gov)

Identify the governing privilege law: Evidence Rule 501 applies state privilege law to civil claims or defenses for which state law supplies the rule of decision. Mixed claims require further analysis. Federal Rule of Evidence 501. (uscourts.gov)

Flag sensitive medical, financial, or personal information separately. Keep substantive legal advice out of broadly shared collection records.

Record: review flag, assigned lawyer, and review status—not an unverified protection conclusion.

7. Close each task with evidence or an assigned exception

Compare the requested scope with the actual collection. Record exclusions: unavailable recordings, unsearched mailboxes, missing historical manuals, or vendor records awaiting retrieval. Follow-up dates are workflow decisions unless counsel identifies an applicable deadline.

If the checklist supports federal party document responses, reconcile results with the response tracker. Rule 34(b)(2) requires specific objections, disclosure of whether responsive materials are withheld, and completion of promised production by the specified inspection time or another reasonable time identified in the response. Federal Rule of Civil Procedure 34(b)(2). (uscourts.gov)

Record: verified scope, collection references, unresolved exceptions, and the next decision’s owner. An assigned exception permits administrative closure but does not establish evidentiary completeness.

Worked example

Fictional scenario: Counsel represents Alder Workshop LLC in a first-party commercial property dispute against Mariner Peak Insurance. Alder alleges that Mariner Peak reduced its storm-loss estimate and partially denied coverage without evaluating an engineering supplement containing additional photographs. All parties, documents, amounts, and facts are fictional.

The collection contains a policy PDF, claim diary, final estimate of $64,000, and partial-denial letter. The diary references an earlier $91,000 estimate and an engineering supplement, neither supplied. Counsel has not verified when the insurer received the supplement. No inference about its contents or effect is justified yet.

These entries change collection priorities. The missing endorsement prevents a complete assessment of the supplied policy. The estimate discrepancy calls for revision history, not an immediate accusation of undervaluation. The supplement requires both content and receipt evidence: later-received information presents a different investigation question from information available before denial. None of the three rows should be marked verified merely because the current production has been reviewed.

Common mistakes

• Treating a claim PDF as the complete file. Reconcile it with source-system components, attachments, and referenced records.
• Collecting only adverse evidence. Include inspection attempts, insured responses, contrary reports, and reasons for further investigation.
• Using current manuals to explain historical conduct. Obtain applicable versions and flag uncertain effective dates.
• Calling every delay unlawful. Collect triggering communications and receipt evidence; have counsel validate the governing standard and exceptions.
• Marking protected material “missing.” Distinguish collected material awaiting review from unavailable records and production withholding decisions.

Final quality check

• Each row connects to an issue, defense, or discovery request.
• Policy identifiers and endorsement schedules reconcile with collected documents.
• Key repositories and administrator sources are collected or expressly assigned.
• Referenced attachments, versions, and approvals have been checked.
• Document IDs and page references resolve to the correct records.
• Privilege and confidentiality flags remain separate from completeness status.
• Open issues have owners and actions; closed rows state verified scope or exceptions.
• Legal sources match the forum, relevant period, and supported proposition.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, chronology, and evidence analysis capabilities can support review of collected claim materials. Use the chronology viewer to examine the handling sequence alongside counsel-maintained collection records. Counsel must verify completeness, determine protection, and approve discovery decisions. To assess its fit for your claim-file review, book a demo.

Frequently asked questions

Should every checklist include reserves and reinsurance records?

No. Identify the issue those records would address, then assess applicable law, proportionality, and protection questions before adding a targeted task. Do not use their inclusion or omission as a substitute for that analysis.

What if the insurer supplies only a flattened PDF?

Inventory its limitations. Identify missing attachments, versions, metadata, or histories relevant to disputed decisions, then formulate a focused supplemental request. Explain the evidentiary gap rather than demanding another format without a reason.

How should counsel record an unavailable call recording?

Identify the call, the record referencing it, the repository checked, and the collection contact’s explanation. Assign further inquiry where warranted. Label a diary summary as a summary; do not present it as the original recording.

When is the checklist complete?

When every defined task has a verified result or an assigned exception. Reopen affected rows when new records identify additional sources or attachments. Keep unresolved exceptions visible to the lawyer responsible for discovery responses.

Sources

• Federal Rules of Civil Procedure, December 1, 2025 edition, Rules 26 and 34.
• Federal Rules of Evidence, Rules 501, 803(6), and 901(a).
• California Department of Insurance: 2026 disaster-adjusting guide, page 19.

This general professional workflow reflects the supplied research cutoff of October 13, 2026; application depends on governing law, policy language, facts, and applicable orders.

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.