How to map investigation steps and response intervals for Insurance Bad-Faith Matters

Map investigation activity by linking each request, investigative decision, receipt, follow-up, and response to a specific source and a defined interval. Separate what the insurer knew at the time from later explanations, and distinguish elapsed time from an applicable deadline. The resulting investigation activity tracker should identify completed actions, unresolved gaps, competing explanations, and assigned follow-up. Counsel can then test allegations of unreasonable handling against supporting and contrary evidence without treating an incomplete claim file as proof of inactivity or a long interval as proof of bad faith.

When to use this workflow

Use this workflow when policyholder counsel, insurer counsel, or an in-house litigation team must assess alleged delay, repeated information requests, incomplete investigation, or an unexplained denial. Concrete triggers include receiving a claim-file production, preparing an adjuster interview, or determining whether an expert recommendation informed a coverage decision.

The scope is investigation conduct and response timing, not a complete coverage or damages analysis. Identify governing substantive law, forum, policy type, first-party or third-party posture, and relevant historical rules before assigning legal significance to an interval. Federal rules discussed below concern federal proceedings; verify state and arbitral requirements separately.

California supplies a limited example. Its Department of Insurance’s disaster-adjusting guide describes diligent, thorough, fair, objective investigation and restrictions on persistent requests for unnecessary or immaterial information. The guide concerns California property claims; it is not a nationwide standard, a substitute for applicable regulatory text, or authority establishing a private remedy. California Department of Insurance guide, p. 19.

What you need

Collect records showing both activity and information available when decisions were made:

• Complete policies and endorsements, claim notices, proofs of loss, coverage correspondence, and relevant settlement communications.
• Native claim-system exports, audit histories, diary entries, assignment changes, attachments, and third-party administrator records.
• Adjuster emails, portal submissions, call recordings, delivery records, and acknowledgments establishing receipt.
• Expert instructions, inspection records, preliminary and final reports, estimates, supervisory approvals, and payment transactions.
• Relevant handling manuals and a counsel-verified list of potentially applicable policy provisions, rules, orders, or express commitments.

Document repositories searched, custodians included, production cutoff, known omissions, and redactions. Preserve originals and stable document identifiers. Check whether flattened exports retain attachment relationships and entry histories before relying on them to explain apparent gaps.

Use the template

The Insurance Bad-Faith Matters — Investigation activity tracker uses one row per material investigation action or response interval. Copy this table into your working document or spreadsheet. Split a communication into linked rows when it requests independently completed actions.

Keep IDs stable when sorting. Distinguish event dates, system-entry dates, and receipt dates; use “unknown” rather than blanks for material missing dates. Add time zones when timestamps affect sequence.

“Trigger / interval” identifies linked endpoints, elapsed days, counting convention, and open or completed status. “Governing basis” records an exact policy clause, verified legal provision, express commitment, or “analytical interval only.” Do not insert an assumed industry deadline.

Use “Evidence / uncertainty” for contrary evidence, disputed dates, missing attachments, and verification status. The last field assigns a concrete task to a responsible person. Maintain a linked issue note for governing-law assumptions and collection boundaries rather than overcrowding individual cells.

Step by step

1. Define the handling question and claim segment

Frame a testable question: Did the insurer pursue the recommended inspection before denying the structural component? Do not begin with a conclusion such as “unreasonable 60-day delay.”

Identify the disputed claim segment, alleged harm, and proposed start and end events. Investigation and payment activity may proceed concurrently: a contents payment does not necessarily complete the building-damage investigation. Separate the coverage position, alleged handling failure, causation theory, and defense so evidence supporting one does not silently establish another.

Record: the issue ID, precise question, claim segment, and linked governing-law note. Assign unresolved legal questions before calculating compliance.

2. Reconstruct actions from source records

Read diary entries alongside emails, reports, attachments, and audit history. Separate inspection requested, vendor accepted, inspection performed, and report received. An entry saying “inspection complete” may not establish every event.

Distinguish contemporaneous records from retrospective descriptions. A supervisor’s later explanation does not itself establish what the adjuster knew earlier. When dates conflict, retain both sources, identify the provisionally selected date, and explain the selection. Preserve the exact passage supporting each action rather than citing an entire claim file.

Record: actor, action, date types, document ID, and page, message, or audit-entry pinpoint. Label inferred dates explicitly and keep them distinguishable from verified events.

3. Identify triggers and responsive completion

For each alleged delay, identify the triggering communication, receipt evidence, requested action, and recipient. Sending an email, delivering it to a shared mailbox, and routing it to the assigned adjuster are different events. Which event controls legally requires separate analysis.

Define completion against the requested action. An acknowledgment can end an acknowledgment interval while leaving substantive review unresolved. Scheduling an inspection does not establish performance. Partial payment may answer one demand without resolving another.

Record: linked trigger and completion IDs. Where receipt or completion is unverified, state that explicitly. Use “open through collection cutoff” only when the reviewed record supports that limited description; it does not establish continued inactivity beyond the cutoff.

4. Validate the governing basis

Examine actual policy language and potentially applicable historical rules, including scope, conditions, and exceptions. Keep internal targets and insurer promises distinct from legal requirements. A promised update date may be relevant evidence without independently establishing a statutory deadline.

In Wilson, the California Supreme Court explained that the genuine-dispute doctrine does not excuse thorough and fair investigation and found a triable issue concerning denial without further medical investigation. This California first-party underinsured-motorist summary-judgment decision supports examining investigation substance, not simply counting days. Check subsequent treatment before relying on it. Wilson v. 21st Century Insurance Co., 42 Cal.4th 713 (2007).

Record: the verified authority or commitment, its applicable trigger and limits, or “analytical interval only; legal applicability unresolved.” Leave compliance conclusions unresolved until the necessary facts and legal basis are verified.

5. Calculate intervals and explain intervening activity

Use a stated analytical convention, such as calendar-date subtraction excluding the start date. Keep it separate from any legally prescribed counting method. Preserve dates and formulas so another reviewer can reproduce results.

Break a long span into referral-to-acceptance, acceptance-to-inspection, inspection-to-report, and report-receipt-to-decision intervals where relevant. Identify supported access problems, pending information, reassignment, or conflicting instructions. Do not automatically subtract these periods as legally excused time.

For repeated requests, compare the requested items with prior submissions and receipt records. A second request may concern genuinely missing information or duplicate material already supplied.

Record: elapsed days, status, intermediate activity, and the source supporting each explanation. Distinguish “no activity documented in reviewed material” from “no activity occurred.” An unknown endpoint cannot support an exact receipt-based duration.

6. Test competing explanations and assign follow-up

Identify evidence supporting and undermining each handling allegation. Ask whether the missing step mattered to the stated denial reason and whether another documented investigation addressed the same question. Avoid assuming every omitted recommendation establishes inadequate investigation.

Convert uncertainty into focused requests or witness questions: Who received the attachment? Was the preliminary report available before denial? Why was recommended testing not commissioned? In federal district court, discovery concerns nonprivileged matter relevant to claims or defenses and proportional to the case’s needs. Federal Rule of Civil Procedure 26(b)(1).

Record: the competing explanation, missing evidence, targeted follow-up, and owner. Flag potentially privileged material for counsel review; do not treat withheld content as proof that no investigation occurred.

7. Verify the map and separate analysis from evidence

Have a second reviewer trace material rows to source passages and recalculate intervals. Test whether substituting disputed dates changes the sequence or assessment. Keep counsel’s legal evaluations separate from factual descriptions prepared for witnesses or potential exhibits.

A sourced tracker is not automatically admissible. Federal Rule of Evidence 901 addresses authentication; Rule 803(6) separately conditions the business-records exception on recordkeeping foundations and trustworthiness. Locating a statement in a claim file does not resolve every admissibility issue. Federal Rules of Evidence 901 and 803(6).

Record: reviewer verification, unresolved conflicts, and needed witnesses or foundations. Revise affected rows when follow-up supplies new evidence, retaining the basis for changed dates or conclusions.

Worked example

Fictional scenario: Harbor Fern Properties submits a first-party water-damage claim to Alder Basin Insurance. A May 3, 2026 denial rejects a disputed structural component. Counsel is testing whether recommended additional testing was pursued before denial, not assuming elapsed time establishes bad faith.

A portal receipt confirms an estimate upload on April 2, 2026; the insurer acknowledges it on April 18. An April 5 vendor instruction requests inspection, and a signed field sheet records an April 12 visit. A preliminary report dated April 12 recommends moisture testing. The production contains neither delivery metadata nor a final report. The collection cutoff is May 15, 2026. All parties, records, dates, and circumstances are fictional.

The calculations below use calendar-date subtraction excluding the start date. No legal response deadline has been established.

I-02 undermines an assertion of total investigative inactivity. I-01 establishes acknowledgment timing, not evaluation timing. I-03 redirects attention to whether the recommendation reached the decision-maker and what followed. The 21-day comparison cannot establish a 21-day failure to act on a received report. Neither a denial’s date nor the collection cutoff supplies the missing receipt evidence.

Common mistakes

• Using diary-entry dates as event dates. Preserve both and reconcile retrospective entries with contemporaneous records.
• Counting any answer as completion. Match acknowledgments, substantive responses, inspections, and payments to distinct requested actions.
• Importing a familiar deadline. Verify jurisdiction, policy type, historical version, trigger, and exceptions first.
• Equating file silence with inactivity. State collection boundaries and identify missing vendor, administrator, or attachment records.
• Showing only adverse intervals. Include contrary activity and supported explanations, then explain the remaining concern.

Final quality check

• Every material action has a stable ID and source pinpoint.
• Event, entry, and receipt dates remain distinguishable.
• Each calculated interval identifies endpoints and counting method.
• Open intervals identify the collection cutoff without implying later inactivity.
• Legal requirements, commitments, and analytical comparisons are separately labeled.
• Contemporaneous knowledge, contrary evidence, and missing repositories are visible.
• A second reviewer has checked sources and calculations.
• Every material open issue is resolved or explicitly assigned with a next action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, and chronology capabilities can support organizing claim records and examining investigation sequences. Use the verified tracker to guide document-linked questions in deposition preparation. Counsel remains responsible for receipt findings, calculations, governing-law analysis, and conclusions. To assess the workflow against your claim-file review needs, book a demo.

Frequently asked questions

Should every diary entry receive a separate row?

No. Capture material actions and response intervals without obscuring them in administrative detail. Preserve the underlying records. Split rows when different actors, triggers, or completion events would otherwise become ambiguous.

How should time awaiting policyholder information be shown?

Record the specific request, purpose, receipt, follow-up, and responsive submission. Show the pending-information period separately. Whether it changes a deadline or supports a delay explanation requires counsel’s analysis, not automatic subtraction.

What if claim-file and email timestamps conflict?

Retain both, inspect time zones and message history, and determine whether one reflects entry rather than receipt. Explain any provisional selection. Show alternative calculations when the difference materially affects the assessment.

Can the tracker become a court exhibit?

Possibly, but separate it from privileged analysis. In federal proceedings, Rule 1006 addresses summaries proving the content of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. Illustrative aids fall under Rule 107. Verify the intended use and applicable requirements. Federal Rules of Evidence 1006 and 107.

Sources

• Federal Rules of Civil Procedure, Rule 26(b)(1).
• Federal Rules of Evidence, Rules 901, 803(6), 1006, and 107.
• California Department of Insurance, 2026 disaster-adjusting guide, page 19.
• Wilson v. 21st Century Insurance Co., California Supreme Court opinion, 42 Cal.4th 713 (2007).

Scope: General counsel-facing workflow with an October 13, 2026 research cutoff; application depends on the actual policy, governing law, facts, and forum.

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.