Privilege Log: Format, Required Information, and Common Mistakes

A privilege log is a document that lists each item being withheld from discovery on a claim of privilege or protection, along with sufficient information for the requesting party and the court to evaluate the claim. Required by Federal Rule of Civil Procedure 26(b)(5)(A) whenever a party withholds discoverable material based on attorney-client privilege, work product doctrine, or other protections, the privilege log is the procedural mechanism for asserting and defending privilege claims.

This guide covers what must appear on a privilege log, federal and state-specific requirements, the common mistakes that lead to waiver, and how to challenge a deficient log. Read it beside the requests for production guide for the underlying production framework.

What Goes on a Privilege Log

Under FRCP 26(b)(5)(A), a privilege log must:

• Expressly assert the privilege or protection.
• Describe the nature of the documents, communications, or tangible things not produced or disclosed in a manner that, without revealing information itself privileged or protected, will enable other parties to assess the claim.

The standard fields on a privilege log entry are:

• Document number (Bates or log entry number).
• Date the document was created.
• Author or sender.
• Recipients, including direct, copy, and blind copy.
• Subject or general nature of the document (without revealing privileged content).
• Document type (memo, email, letter, draft).
• Privilege claimed (attorney-client, work product, joint defense, common interest).
• Basis for the privilege (which lawyers were involved, the legal advice context).

Privileges Commonly Asserted

Privilege	What It Protects	Authority
Attorney-client	Communications between attorney and client for legal advice	Common law / state codes
Work product	Documents prepared in anticipation of litigation	FRCP 26(b)(3)
Joint defense / common interest	Communications among co-defendants with shared legal interests	Common law
Doctor-patient	Medical communications (varies by state)	State codes
Spousal	Confidential marital communications	Common law / FRE 501
Self-incrimination	Compelled disclosure of incriminating information	5th Amendment
Trade secret	Proprietary business information	FRCP 26(c) protective orders

The 26(b)(5) Sufficiency Standard

Privilege log entries must satisfy the requirement of Federal Rule of Civil Procedure 26(b)(5)(A)(ii) that sufficient information must be provided to assess each privilege claim. The standard is "sufficient information", neither so vague that the requesting party cannot evaluate the claim, nor so detailed that the privilege itself is waived.

Generic descriptions like "communication regarding case strategy" are usually insufficient. Specific descriptions like "Email from outside counsel John Smith to in-house counsel Jane Doe dated 6/14/2025 regarding analysis of contract dispute and litigation strategy" provide enough context without revealing privileged content.

Privilege Logs in EDiscovery

A privilege log is a record of the responsive or relevant documents that are being withheld from production on a claim that they contain attorney-client communications or work-product. In modern practice, privilege logs are typically generated from electronic discovery (e-discovery) platforms after responsiveness review. The platform exports metadata fields directly into the log, dramatically reducing manual entry.

For large document populations, courts increasingly accept categorical privilege logs that group similar documents (e.g., "all communications between in-house counsel and the litigation team during the litigation period") rather than requiring entry-by-entry logging. Categorical logging requires court approval or stipulation in most jurisdictions.

California-Specific Requirements

California Code of Civil Procedure section 2031.240(c) requires a privilege log to include:

• Identification of withheld documents.
• The privilege or protection claimed.
• Sufficient detail to evaluate the claim.
• Descriptions that don't reveal privileged information.

California courts also enforce a stricter timeline: the privilege log must be served with the response to the document request, not later. Late privilege logs can result in waiver of the privilege under California precedent.

Common Mistakes

The most common privilege-log mistakes:

• Generic descriptions. "Communication regarding case" or "memo prepared for litigation" are too vague.
• Missing recipients. Forgetting to list copy and blind-copy recipients can waive privilege if a non-privileged third party was on the email.
• Including non-privileged documents. Logging documents that are not actually privileged invites motions to compel.
• Mass logging without review. Logging every email an attorney touched, without confirming legal advice was the dominant purpose.
• Late production of the log. Failing to serve the log with the response, or delaying the log for weeks after production, can waive privilege under FRCP 26(b)(5) and state analogs.

Challenging a Deficient Log

If a privilege log is too vague, the requesting party can:

1. Meet and confer demanding a more specific log.
2. Move to compel a sufficient log under FRCP 37(a).
3. Move for in camera review by the court.
4. Argue waiver based on inadequate description.

Courts can review withheld documents in camera to determine whether the privilege claim is proper. In camera review is the preferred remedy when the privilege log is borderline rather than clearly deficient.

Clawback Protection Under FRE 502

Because privilege review is where most production mistakes happen, parties should pair the privilege log with clawback protection. Federal Rule of Evidence 502(b) provides that inadvertent production does not waive privilege if the holder took reasonable steps to prevent disclosure and promptly took reasonable steps to retrieve the document. Stronger still is a Rule 502(d) order: a court order stating that production in the litigation does not waive privilege in that case or any other federal or state proceeding, regardless of the care taken. A 502(d) order costs nothing to request and eliminates most waiver fights, which is why many judges enter one as a matter of course. Clawed-back documents are then added to the privilege log like any other withheld material.

When You Need an Attorney

Privilege logs are technically demanding and the consequences of mistakes (waiver of privilege, motions to compel, sanctions) are serious. Legal Tank's attorney-drafted discovery service handles privilege review, log preparation, and supporting motion practice. For pro se or small-firm matters, the discovery template includes a privilege log shell.

Related Civil Procedure Guides

• interrogatories vs. requests for production
• FRCP 37(a) motion to compel
• Rule 36 requests for admission
• Rule 34 document requests
• subpoena quash standards

Frequently Asked Questions

What is in a privilege log?

A privilege log is a document that describes documents or other items withheld from production in a civil lawsuit under a claim that the documents are "privileged" from disclosure due to the attorney-client privilege, work product doctrine, joint defense privilege, or other protection. Standard fields include date, author, recipients, document type, subject (without revealing privileged content), privilege claimed, and basis for the privilege.

What federal rule requires a privilege log?

Privilege log entries must satisfy the requirement of Federal Rule of Civil Procedure 26(b)(5)(A)(ii) that sufficient information must be provided to assess each privilege claim. The rule requires the withholding party to expressly assert the privilege and describe the nature of the documents, communications, or tangible things not produced in a manner that will enable other parties to assess the claim without revealing the privileged information itself.

What is a privilege log in EDiscovery?

A privilege log is a record of the responsive or relevant documents that are being withheld from production on a claim that they contain attorney-client communications or work-product. In e-discovery practice, privilege logs are generated from review platforms that export metadata directly into the log, dramatically reducing manual entry. For large document populations, courts increasingly accept categorical privilege logs that group similar documents.

What needs to be in a privilege log in California?

California Code of Civil Procedure section 2031.240(c) requires identification of withheld documents, the privilege or protection claimed, sufficient detail to evaluate the claim, and descriptions that don't reveal privileged information. California courts also enforce a stricter timeline: the privilege log must be served with the response to the document request. Late privilege logs can result in waiver of the privilege under California precedent.

Do redacted documents need to be logged?

Generally yes. A redaction for privilege is a partial withholding under FRCP 26(b)(5)(A), and most courts and ESI protocols require a redaction log identifying each redacted document and the basis for each redaction. Because the requesting party can see the unredacted remainder for context, redaction log entries can be lighter than full entries, and many protocols allow the basis to be stamped on the face of the redaction itself.

Should attorney-client privilege and work product be logged differently?

Log each basis separately for each document, because the doctrines have different elements and different vulnerabilities. Attorney-client privilege requires a confidential communication for the purpose of legal advice. Work product under FRCP 26(b)(3) requires preparation in anticipation of litigation, and ordinary fact work product can be overcome by a showing of substantial need and undue hardship, while opinion work product revealing counsel's mental impressions receives nearly absolute protection. A document can qualify for one protection and not the other.

When is a privilege log due in federal court?

FRCP 26(b)(5)(A) does not set an explicit deadline. Federal courts generally require the log within a reasonable time after the written response, with many local rules and ESI protocols fixing a specific date, often thirty to sixty days after production. Unreasonable delay or a plainly inadequate log risks a finding of waiver, though most courts treat waiver as a last resort reserved for bad faith or repeated failures. State timing rules vary, so confirm the local rule early.