How to prepare a privilege review log for Insurance Bad-Faith Matters

Prepare a privilege review log by connecting withheld claim-file material to the applicable protection, verifying each participant’s role, and distinguishing legal advice from ordinary adjusting activity. Review emails, diary entries, attachments, and proposed redactions individually, then draft descriptions that permit assessment without exposing protected substance. The deliverables are a source-linked internal review table and a separately approved disclosure log. In insurance bad-faith litigation, counsel’s participation starts the inquiry; the communication’s function, confidentiality, preparation context, and governing law determine the decision.

When to use this workflow

Use this workflow when insurer, policyholder, or coverage counsel must explain privilege-based withholding from a claim file or related collection. Typical triggers include requests for coverage evaluations, adjuster diaries, denial drafts, investigation instructions, and third-party administrator records.

Define the review population by request, custodian, repository, and production tranche. Claim files can combine investigation facts, reserve discussions, settlement authority, legal analysis, and litigation preparation. Avoid assigning one disposition to the entire file.

This guide uses US district-court procedure. Identify the forum, substantive law, policy type, first-party or third-party posture, and applicable orders before adapting it to state litigation or arbitration. Evidence Rule 501 applies state privilege law to a civil claim or defense for which state law supplies the rule of decision; mixed claims require further analysis. Separately identify the law governing work-product protection. Federal Rules of Evidence, Rule 501. (uscourts.gov)

What you need

Assemble these inputs before substantive logging:

• Discovery instructions: requests, responses, objections, protective orders, privilege protocols, production specifications, and counsel-confirmed log dates.
• Claim-file sources: native diary exports, emails, attachments, coverage evaluations, denial drafts, expert instructions, vendor submissions, and available audit histories.
• Participant information: adjuster assignments, supervisory roles, counsel engagements, administrator responsibilities, and identities behind shared mailboxes.
• Context documents: policy and endorsements, claim notice, coverage correspondence, demands, and contemporaneous records supporting any asserted anticipation of litigation.
• Review controls: stable document IDs, family relationships, duplicate information, Bates references where assigned, and prior-production records.

Prepare legal instructions identifying the protections and jurisdiction-specific tests counsel will apply. Include escalation criteria for mixed legal-business communications, outside recipients, and any asserted reliance on counsel’s advice. Treat labels such as “privileged” and folder names such as “litigation” as review clues, not completed analyses.

Use the template

The companion template is Insurance Bad-Faith Matters — Privilege review log. Copy this table into your working document or spreadsheet. It is an internal review work product; create the disclosure version separately to avoid serving protected reasoning or strategic notes.

Use “Record / source” for the document ID, request linkage, page or diary-entry citation, attachment relationship, and Bates range if assigned. Distinguish creation, sending, and entry dates when they differ. Identify senders, recipients, copied recipients, and their verified functions.

“Protection / basis” holds the asserted protection and supporting facts. “Scope / description” records full withholding or precise redactions plus proposed disclosure wording. Keep sensitive reasoning in the internal basis field. Give each gap an owner and decision checkpoint; record approval, rejection, or escalation with the reviewer and version. Adapt the served fields to the governing protocol rather than assuming this internal table satisfies every forum.

Step by step

1. Set the logging rules before reviewing documents

Read the requests, responses, orders, and stipulations together. In federal district court, Rule 26(b)(5)(A) requires an express protection claim and a description permitting assessment without revealing protected information. Rule 26(f)(3)(D) includes timing and method of compliance in discovery planning. These requirements do not establish the underlying privilege. Federal Rules of Civil Procedure, Rules 26(b)(5)(A) and 26(f)(3)(D). (uscourts.gov)

Determine whether the protocol addresses redactions, email chains, duplicates, post-complaint communications, or categorical entries. Do not assume exemptions. Record the controlling instruction and request linkage in the working document; enter unresolved protocol questions in “Gaps / action.”

2. Stabilize the claim-file population

Inventory collected repositories, including administrator systems and coverage counsel correspondence within scope. Preserve source IDs and connect rendered diaries to native entries where possible. A single export may combine entries by different adjusters, later edits, and embedded communications.

Review parent messages and attachments as connected but distinct records. Identify missing attachments without reconstructing their contents from surrounding correspondence. Check whether the same report appears elsewhere with different instructions or forwarding history. Record family relationships, exact source locations, and collection uncertainty in affected rows. The output should let another reviewer reproduce the population and locate every decision.

3. Identify participants and their functions

Resolve unfamiliar recipients against assignment histories and engagement information. Distinguish coverage counsel, defense counsel in an underlying liability action, in-house lawyers, adjusters, supervisors, engineers, brokers, and administrators. Record which client and capacity are involved rather than treating every lawyer as serving the same function.

For shared mailboxes, distribution lists, and forwarded messages, investigate actual recipients where records permit. Verify identities and retain the supporting source. Enter confirmed roles in “Participants / roles”; assign unresolved identities before final approval. Refer the legal effect of outside participation to counsel under the applicable law rather than making a domain-based confidentiality decision.

4. Test legal purpose and litigation context separately

Read each communication in its claim-handling sequence. Identify requests for legal advice, ordinary investigation activity, business decisions, and mixed purposes. Apply counsel’s jurisdiction-specific instructions; record the textual evidence and contextual facts in separate fields.

For federal work-product claims, Rule 26(b)(3) addresses qualifying materials prepared in anticipation of litigation or for trial and provides conditions for discovery despite that protection. Identify the preparation purpose and any applicable exceptions, not simply whether litigation eventually occurred. Federal Rules of Civil Procedure, Rule 26(b)(3). (uscourts.gov)

Record the relevant triggering event, date, contemporary knowledge, and connection to preparation. Do not substitute a denial date or counsel-engagement date for document analysis. Escalate dual-purpose records, third-party participation, and advice-reliance issues. The output is a supported assertion or a specific unresolved question—not a presumed file-wide protection.

5. Decide withholding and redaction scope

Compare the asserted protection with the actual passages. An adjuster diary may reproduce counsel’s advice within a factual entry; a legal-advice email may attach an independently prepared repair estimate. Assess components separately rather than copying the parent’s disposition across the family.

Where counsel approves partial production, identify exact pages, entries, or passages and inspect the rendered redactions. Check that hidden text, comments, or another produced copy do not expose the redacted content. Preserve the original securely. Record full withholding, partial redaction, production, or pending review in the table, with material reasons for rejecting broader or narrower treatment. Keep confidentiality designations separate from privilege decisions.

6. Draft assessable descriptions

Describe the communication’s function, general subject, participants, and asserted protection without revealing advice. A description might identify a request for coverage counsel’s interpretation of a specified policy exclusion as applied to the reported loss; it should not disclose the recommended coverage position.

Avoid circular entries such as “privileged email concerning privileged matters.” Also avoid replacing every subject with “coverage,” which obscures meaningful differences among inspection instructions, exclusion analysis, and denial drafting. Verify each description against its source. Record proposed disclosure text in “Scope / description,” keeping sensitive reasoning outside the disclosure version. Where the source lacks a reliable date or identity, explain the uncertainty rather than inventing metadata.

7. Reconcile the log with the production

Compare approved decisions with the withheld inventory, redacted production, family relationships, and responses. Rule 34(b)(2) requires specific objections and disclosure of whether responsive materials are withheld on their basis; ensure the response and production record agree with approved decisions. Federal Rules of Civil Procedure, Rule 34(b)(2). (uscourts.gov)

Have a lawyer approve disputed assertions and disclosure wording. Record reviewer, decision, and version; assign every remaining issue before the affected release. Evaluate any Rule 502(d) order: it can prevent litigation-connected disclosure from constituting waiver in other federal or state proceedings. Under Rule 502(e), a private agreement alone binds only its parties. Federal Rules of Evidence, Rules 502(d)–(e). (uscourts.gov)

Worked example

Fictional scenario: Alder Cove Foods LLC sues Beacon Harbor Indemnity over handling of a warehouse water-loss claim. The federal action presents state-law claims. Counsel has identified the applicable privilege and work-product standards and confirmed the logging protocol. A request seeks claim-handling communications through denial, including coverage counsel correspondence.

The following fictional records are dated in 2026. The table illustrates internal review decisions, not a served log. Approvals are stipulated facts of this example, not conclusions that the limited descriptions independently establish protection.

These entries change the production decision. Email approval does not resolve the absent attachment. The diary requires passage-specific redaction instead of blanket withholding. The report remains unresolved because forwarding history does not supply the missing preparation evidence. If instructions cannot be located, counsel must decide on the available record or pursue an authorized resolution; the gap cannot become indefinite, unexplained withholding.

Common mistakes

• Using denial as the privilege boundary. Analyze each record’s purpose and supporting facts; use chronology as context, not an automatic classification rule.
• Protecting coverage counsel’s entire file. Assess advice, adjusting functions, underlying factual records, and attachments separately.
• Copying advice into disclosure descriptions. State function and general subject while reserving substantive reasoning for the controlled internal table.
• Missing advice inside diary exports. Review individual entries and rendered pages, not just filenames or document-level labels.
• Ignoring outside recipients. Verify brokers, vendors, administrators, and forwarding recipients; send the effect on protection to counsel.
• Serving the internal worksheet. Prepare a disclosure version that excludes strategic notes and protected analysis, then reconcile it to approved dispositions.

Final quality check

• Every logged withholding or redaction maps to a verified source and precise location.
• Dates, participants, roles, and family relationships match the underlying records.
• Assertions follow counsel’s identified legal standards and include supporting facts.
• Descriptions permit assessment without revealing protected substance.
• Attachments, diary passages, and forwarded chains receive separate treatment where needed.
• The log reconciles with redacted files, withheld records, responses, and the governing protocol.
• Open issues are resolved or assigned to a named owner with a checkpoint before affected release.
• The disclosure version contains no internal legal analysis, and its final version is preserved.

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, and redaction. Use these capabilities to support claim-file review while retaining counsel’s responsibility for governing law, assertions, descriptions, and release decisions. A chronology can help organize the claim-handling context used in this workflow. To discuss supporting this review process, book a demo.

Frequently asked questions

Does copying coverage counsel establish privilege?

Do not use the recipient list as the decision rule. Verify counsel’s client and role, the communication’s purpose, confidentiality facts, and other recipients. Apply the governing law and escalate mixed adjusting and legal communications.

Can we use one entry for an entire claim diary?

Check the protocol before choosing the logging unit. Internally, retain entry-level references and decisions so factual entries, advice passages, and unrelated material do not receive an unexplained common disposition. A categorical approach still needs a reproducible basis.

Should the log include documents produced without redactions?

Maintain their review decisions internally for reconciliation. Determine the served log’s contents from the applicable rules, orders, and agreements; do not automatically include every reviewed document or confuse production tracking with privilege logging.

What if the file does not establish why a report was prepared?

Record the gap and seek engagement instructions or contemporaneous correspondence. Assign the issue to counsel before release and track the decision checkpoint. Do not invent a litigation purpose or treat transmission to counsel as resolving preparation context.

Sources

• Federal Rules of Civil Procedure, Rules 26(b)(3), 26(b)(5)(A), 26(f)(3)(D), and 34(b)(2): work-product framework, privilege-claim procedure, discovery planning, and withholding disclosures.
• Federal Rules of Evidence, Rules 501 and 502(d)–(e): applicable privilege law and disclosure-related nonwaiver provisions.

Scope: General professional workflow guidance as of October 13, 2026, not advice for a particular matter; apply the governing law and 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.