Litigation support · Guide

Privilege log requirements: what courts expect

A privilege log identifies each withheld document and states why it is protected. Under Federal Rule of Civil Procedure 26(b)(5)(A), the description must let the other side assess the claim without revealing the privileged content itself.

Muhammad DanishIndependent consultant · Updated 15 November 2026
On this page
  1. What the rule requires
  2. The standard fields
  3. What a good description looks like
  4. Common reasons logs fail
  5. Categorical logs
  6. Redaction logs
  7. Building the log without losing the thread
  8. Privilege is a legal judgment
  9. A pre-service checklist

A privilege log is a list of the documents a party is withholding and the reason for withholding them. It sounds administrative. In practice it is one of the most contested documents in discovery, because a vague log invites a motion to compel and a careless log can waive protection.

The governing principle in federal practice is Federal Rule of Civil Procedure 26(b)(5)(A): a party withholding information must expressly claim the privilege and describe the nature of the withheld documents in a way that lets the other side assess the claim — without revealing the privileged content itself.

What the rule requires

Rule 26(b)(5)(A) sets three obligations:

  1. Expressly claim the privilege or protection.
  2. Describe the nature of the documents, communications or things not produced, in a manner that enables other parties to assess the claim.
  3. Not reveal information that is itself privileged or protected.

State rules often mirror the federal rule, and local rules frequently add requirements: a specific format, additional fields, a deadline for the log, or a categorical approach for large volumes. The first step in any matter is to read the rule that applies in that court.

The standard fields

A defensible log usually contains:

FieldWhy it matters
Document ID / BatesLinks the entry to the withheld document
DatePlaces the communication in context
AuthorIdentifies who created it
RecipientsShows the scope of distribution
Document typeLetter, email, memo, draft, notes
Subject / descriptionSupports the privilege claim without revealing content
Privilege assertedAttorney-client, work product, joint defence, other
BasisWhy the element is met — legal advice sought, litigation anticipated
Withheld or redactedDistinguishes full withholding from partial production

Some courts require the author's role (attorney, client, third party), the number of pages, or the specific request to which the document responds. Build the log to the most demanding rule that might apply, not the least.

What a good description looks like

The description has to do two things at once: give enough detail to assess the claim, and avoid disclosing the protected content.

A weak entry says: "Email — privileged communication."

A stronger entry says: "Email from outside counsel to in-house counsel, 14 March 2025, requesting legal advice on the enforceability of the non-compete in the asset purchase agreement; reflects legal analysis prepared in anticipation of litigation."

The second identifies the roles, the advice and the basis for the claim without quoting the email.

Common reasons logs fail

Boilerplate. The same description repeated for hundreds of documents suggests nobody reviewed them individually. Courts have ordered production after boilerplate logs.

Missing authors or recipients. Without them, the other side cannot test whether the communication was between privileged parties.

Inconsistent privilege labels. The same document type labelled attorney-client in one entry and work product in another undermines credibility.

Over-designation. Marking every document that mentions a lawyer as privileged is a common error. Copying a lawyer on an operational email does not make the email legal advice.

Under-designation. Failing to log a document that was withheld is worse than a weak description; the other side may not know it exists until a witness mentions it.

Late production. Many local rules set a deadline for the log. A log produced after the deadline can be treated as a waiver in some courts.

Categorical logs

For large volumes, some courts permit categorical privilege logs: instead of one entry per document, the producing party describes categories of documents and the basis for withholding the category.

Categorical logs are efficient but risky. They require:

  • A clear definition of each category
  • A representative sample of documents reviewed
  • A showing that the category is uniformly privileged
  • A method for the other side to test the claim

They are usually agreed with opposing counsel or ordered by the court. Do not assume a categorical approach is available; ask before relying on it.

Redaction logs

If documents are produced with redactions rather than withheld entirely, a redaction log records what was removed and why. Some courts require it, and some treat a redaction as a partial withholding that must be logged like any other.

A redaction log entry should identify the document, the redacted portion, the privilege asserted and the basis. The same specificity standard applies.

Building the log without losing the thread

A workable workflow for a small team:

  1. Collect the candidate documents and give each a stable ID.
  2. Review in batches with the privilege criteria in front of the reviewer.
  3. Record the decision at the time of review — not later from memory.
  4. Apply consistent descriptions using a controlled vocabulary for document types and privilege bases.
  5. Run a QC pass for missing fields, duplicates, inconsistent labels and documents withheld without an entry.
  6. Cross-check the log against the production — every withheld document should appear, and every produced document should not.
  7. Final review by a lawyer before service.

Step 6 is the one that catches the expensive mistakes. A document marked "withheld" in the review platform but missing from the log is a gap the other side will find.

No tool can decide whether a document is privileged. Software can enforce fields, check consistency, flag missing entries and generate the log in the required format. The privilege call belongs to a lawyer, and the log should record who made it.

That division matters: a log showing a lawyer reviewed each entry is more defensible.

A pre-service checklist

  • Applicable rule and local requirements identified
  • Every withheld document has an entry
  • Every entry has a document ID, date, author, recipient, type and description
  • Privilege basis stated for each entry
  • Descriptions specific enough to assess the claim
  • No privileged content revealed in the descriptions
  • Log consistent with the production and redaction logs
  • Lawyer review completed
  • Log served by the deadline and in the required format

A log that passes it is defensible, which is the standard the rule asks for.

Frequently asked questions

What must a privilege log include?

At minimum: a document identifier, the date, the author and recipients, the document type, the privilege asserted, and a description specific enough to support the claim. Local rules often add fields or set a format.

What does FRCP 26(b)(5)(A) require?

A party withholding information must expressly claim the privilege and describe the nature of the withheld documents in a way that enables other parties to assess the claim, without revealing information that is itself privileged.

Why do courts reject privilege logs?

Common reasons are boilerplate descriptions, missing authors or recipients, inconsistent privilege labels, and logs produced so late that the other side cannot challenge them. Specificity and consistency are the defence.

Is a privilege log the same as a redaction log?

No. A privilege log covers documents withheld entirely. A redaction log records what was removed from documents that were otherwise produced, and some courts require both.

Can software decide privilege?

No. Privilege is a legal judgment. Software can standardize fields, check consistency and generate the log; a lawyer must make and review every privilege call.

LawFirmTools provides software tools only. Nothing here is legal advice, and LawFirmTools is not a lawyer or a law firm. This article is general information for legal professionals; it is not a substitute for professional judgment or for your state bar's rules.