How to build a discovery request and response tracker for Insurance Bad-Faith Matters

Build the tracker around individual discovery requests, then connect each request to the claim-handling issue it tests, the response obligation, and the evidence delivered. Record service, verified response dates, extensions, objections, withheld categories, production commitments, Bates ranges, deficiencies, and supplementation in one controlled record. The deliverable is a request-level discovery response tracker that distinguishes a written response from completed production and turns missing claim-file material into specific, assigned follow-up—not an unsupported allegation of bad faith.

When to use this workflow

Use this workflow when counsel serves or receives discovery concerning an insurer’s investigation, valuation, coverage position, settlement conduct, or payment decisions. Requesting counsel tracks evidentiary gaps; responding counsel tracks searches, responses, withholding, and production commitments.

Start before service or reconcile existing responses against rolling productions. The focus is party document requests, with cross-references to other discovery where useful—not a complete discovery calendar or liability assessment.

Identify the forum, governing substantive law, policy type, and first-party or third-party posture. The federal provisions cited here concern United States district-court proceedings; state litigation and arbitration require separate procedural review. Keep discovery deadlines distinct from alleged claim-handling response intervals.

What you need

Collect operative pleadings, discovery orders, stipulations, served requests, service records, written responses, extension correspondence, production letters, indexes, and privilege materials.

For insurance-specific completeness review, gather or identify:

• Complete policies and endorsements, coverage correspondence, notices, proofs of loss, and payment records.
• Claim diaries, assignment histories, native system exports, audit histories, attachments, and relevant communications.
• Adjuster estimates, expert instructions and reports, supervisory approvals, valuation revisions, and settlement communications.
• Manuals and procedures, including versions applicable during the disputed handling period.
• Custodians and repositories at the insurer, third-party administrator, independent adjusters, and vendors.

Assign responsibility for date verification, substantive review, privilege decisions, and production reconciliation. Use stable document IDs before Bates numbering and preserve the later mapping. A folder labeled “complete claim file” does not establish search completeness.

Use the template

Copy the Insurance Bad-Faith Matters — Discovery response tracker into your working document or spreadsheet. The table is a team work product, not a dedicated software module.

Use one row per request. An identifier such as PL-RFP1-012 distinguishes party, request type, set, and number. Keep materially different subparts distinguishable in linked notes.

The date cell should preserve service evidence, original and revised response dates, verification owner, and extension references. The response cell cites the response page and separates objections from commitments. Withholding entries identify categories, grounds, and log references rather than merely saying “privileged.”

Record promised and actual production dates separately, with Bates ranges and batch IDs. Use controlled statuses: response pending, production pending, deficiency open, supplementation pending, or closed after verification. Put lengthy search histories and correspondence in linked records. For spreadsheet implementations, identify the row and column when assigning a correction so reviewers can locate it reliably.

Step by step

1. Establish the scope and identifier for each request

Enter the request number, parties, discovery set, request type, and concise scope. Link the served version and preserve definitions and instructions affecting its reach.

Separate the individual claim file from broader requests for manuals, practices, or other claims. Federal Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case’s needs. Apply that analysis to proposed comparators and institutional records; their insurance subject matter alone does not establish discoverability. See Rule 26(b)(1). (uscourts.gov)

Record: the request ID, served-text reference, scope, and any scope decision assigned to counsel.

2. Connect the request to a claim-handling question

Identify what the request tests: information available before denial, reasons for a valuation change, supervisory approval, settlement evaluation, or evidence supporting an asserted defense.

Keep coverage breach, alleged unreasonable handling, causation, damages, and defenses distinct. A missing engineering report may bear on investigation without proving coverage or loss amount. Include adverse documents and distinguish contemporaneous knowledge from later explanations.

For manuals, identify the relevant period. For third-party matters, connect requests to the underlying claim, settlement communications, and decision authority rather than importing first-party proof-of-loss assumptions.

Record: the issue, event or document IDs, and unanswered factual question.

3. Verify dates and preserve each commitment

Record service date, method, and evidence. Counsel should verify the response date against applicable rules, orders, and stipulations—not a universal interval. Preserve original dates when extensions occur.

Separate response obligations from production commitments. For federal party document requests, 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. See Rule 34(b)(2). (uscourts.gov)

Record: verified dates, verification owner, governing reference, and the response or correspondence supporting each production commitment.

4. Parse the response and withholding position

Read the response beside the request. Distinguish agreement to produce, narrowed scope, objections, assertions that responsive material does not exist, and withholding. Flag ambiguity rather than assuming what “subject to objections” means operationally.

Connect privilege withholding to descriptions and review records. Rule 26(b)(5)(A) requires express claims and descriptions permitting assessment without disclosing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning; neither establishes privilege. See Rules 26(b)(5)(A) and 26(f)(3)(D). (uscourts.gov)

Counsel participation alone should not end review of mixed legal-business communications. Evidence Rule 501 directs application of state privilege law to civil claims or defenses governed by state substantive law; mixed claims require further analysis. See Rule 501. (uscourts.gov)

Record: response citations, withheld categories, log references, and assigned legal questions.

5. Reconcile production against the request

Map batches and Bates ranges to each request, then inspect coverage. Review claim-system attachments, audit histories, date ranges, adjuster assignments, vendor submissions, and payment transactions within the agreed or disputed scope.

Compare diary references with emails and attachments. Distinguish “not produced,” “not located in reviewed materials,” “withheld,” and “reported not to exist.” Each calls for different follow-up.

Link a shared production range to multiple requests where appropriate, but identify responsive portions. For responding counsel, connect production to documented search scope and any unresolved repository questions. Keep batch-level detail outside the main row.

Record: reviewed ranges, reviewer, review date, apparent coverage, and specific missing or unexplained material.

6. Convert gaps into targeted follow-up

State the request citation, response citation, observed fact, and requested action. “Diary entry references a revised estimate; identify its production location or clarify its disposition” is more useful than “claim file incomplete.”

Counsel should decide whether clarification, supplementation, a new request, or testimony fits the gap. Do not silently expand the original request. Track the applicable discovery cutoff and any dispute procedures in linked calendar records, with verification responsibility assigned.

Keep proposed organizational testimony separate from document deficiencies. Federal Rule 30(b)(6) requires reasonably particular topics, organizational designees, and good-faith conferral about examination matters. See Rule 30(b)(6). (uscourts.gov)

Record: targeted action, responsible lawyer, correspondence reference, and next review date.

7. Close only after substantive verification

Recheck each gap when supplemental responses or productions arrive. Identify whether it was resolved, narrowed, disputed, or closed by an express counsel decision. Retain prior commitments and explanations.

Distinguish verified completion from closure because the team will not pursue a disputed issue. Transfer residual evidentiary questions to the relevant work product. Federal Evidence Rules 901(a) and 803(6) separately address authentication and business-records foundations; production alone does not establish admissibility. See Rules 901(a) and 803(6). (uscourts.gov)

Record: closure rationale, final references, supplementation status, and owner of any transferred issue.

Worked example

Fictional scenario: Alder Workshop LLC sues Meridian Harbor Insurance Company over a first-party commercial-property claim in federal district court. Alder alleges that Meridian rejected repair costs without considering a revised engineering assessment. Meridian disputes that account. All parties, records, dates, and identifiers are fictional.

Counsel reviews production on September 25, 2026. Service record SR01 documents August 3 service. The example’s verified original response date is September 2; EXT02 extends it to September 11. RESP01 promises completion of specified production by September 24. These are hypothetical case commitments, not generally applicable deadlines.

The first row justifies an attachment inquiry, not a finding that Meridian ignored the assessment. The second separates privilege review from unexplained omission. The third prevents closure merely because a manual arrived: counsel needs to determine which version applied. None supplies the missing assessment, privilege facts, or earlier manual by inference.

Common mistakes

• Treating a response as completed production. Track written responses, production promises, and verified delivery separately.
• Equating a diary export with the entire claim file. Reconcile attachments, audit histories, communications, and vendor sources within scope.
• Recording objections but not withholding. Capture commitments, narrowed scope, withheld categories, and unresolved ambiguity.
• Calling missing material proof of bad faith. Record the observed gap and competing explanations; assign the legal assessment.
• Overwriting extensions or production promises. Preserve dates, source records, and subsequent performance.
• Closing on the wrong manual version. Check effective period and connection to the handling decision.

Final quality check

• Every row matches the correct served request, definitions, and discovery set.
• Service and response dates have source records and counsel verification.
• Extensions and production promises retain their original references.
• Objections, withholding, and privilege issues remain distinguishable.
• Bates ranges and document IDs match the actual production.
• Gaps identify specific records, periods, attachments, or repositories.
• Open issues have owners and next actions; disputed closures have express reasons.
• Closed rows preserve supplementation status without implying liability or admissibility findings.

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 claim-file examination. Use chronology review to inform request-specific follow-up while counsel maintains the tracker and decides obligations, withholding, and closure. To discuss this workflow, book a demo.

Frequently asked questions

Should requesting and responding counsel use the same tracker?

Use the same core fields. Requesting counsel records deficiencies and clarification questions; responding counsel records search verification and production commitments. Keep privileged internal analysis separate from materials intended for exchange.

How should rolling productions be recorded?

Maintain batch dates and Bates ranges in linked records. Update request-level coverage without erasing earlier promises. A new batch does not establish completion; reconcile it against the remaining gap.

What if the insurer says an attachment does not exist?

Record the statement and source precisely. Compare it with diary references, then assign counsel to assess clarification concerning location, terminology, or search scope. Do not substitute “destroyed” or “withheld” without evidence.

Can one row cover documents and deposition topics?

Keep separately served discovery items separate. Cross-reference related testimony topics so attachment deficiencies remain visible. Also distinguish an adjuster’s individual recollection from organizational testimony preparation.

Sources

• Federal Rules of Civil Procedure, December 1, 2025, Rules 26, 30, and 34.
• Federal Rules of Evidence, Rules 501, 803(6), and 901.

Scope: General professional workflow guidance using the supplied research cutoff of October 13, 2026; apply governing law, forum requirements, and matter-specific 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.