Privilege Logs: A Practical Guide for Litigation Teams

A privilege log is where withheld documents become visible. Every item your team keeps back on privilege or work-product grounds has to be described well enough for the other side to test the claim, without giving away what the privilege protects. Logs assembled in a rush at the end of review are a reliable source of motion practice, and in some courts an inadequate or late log can put the privilege itself at risk.

This guide covers what the federal rule requires, the fields each entry needs, how to write descriptions that work, how to choose between traditional, metadata and categorical logs, how to handle threads and attachments, and a review workflow that catches problems before the log is served.

What does Rule 26(b)(5)(A) require in a privilege log?

It requires a party withholding otherwise discoverable information as privileged or work product to expressly make the claim and to describe the nature of the withheld items in a way that, without revealing protected information, lets the other parties assess the claim. The rule does not prescribe a format. Formats come from local rules, judges’ standing orders, ESI protocols and the parties’ agreements.

Amendments that took effect on December 1, 2025 added privilege logging to the planning stage: Rule 26(f)(3)(D) now asks parties to address the timing and method for complying with Rule 26(b)(5)(A), and Rule 16(b)(3)(B)(iv) allows the scheduling order to cover it. Rule 45(e)(2)(A) imposes a parallel requirement on nonparties withholding documents under a subpoena. Most states have similar rules, with their own formats and deadlines, and in federal civil cases where state law supplies the rule of decision, Federal Rule of Evidence 501 points to state privilege law.

What goes in each privilege log entry?

Enough fields to identify the item, the people involved, the subject and the protection claimed. A typical document-by-document log looks like this:

Sample entries

Attach a names legend listing every person who appears on the log, with affiliation and role, and mark the attorneys. Many disputes over individual entries disappear once the other side can see who each participant is.

How do you write privilege log descriptions that are specific without waiving?

Describe the kind of communication, its purpose, its general subject and the roles of the participants. Never describe the advice itself.

Traditional, metadata or categorical log: which format fits?

Document-by-document logs remain the default expectation in many courts. Metadata and categorical logs can work well for large volumes of similar items when the parties agree or the court allows them.

The 1993 advisory committee note to Rule 26(b)(5) recognized that item-by-item detail can be unduly burdensome when voluminous documents are withheld, particularly if they can be described by categories. Agreements to exclude whole groups from logging, typically communications with litigation counsel after a set date, are among the most valuable terms to settle at the ESI meet-and-confer.

How should you log email threads, attachments and redactions?

Decide the rules up front and apply them consistently, because inconsistency is easier to attack than any single entry.

• Email threads. Some agreements allow one entry for the most inclusive email, describing the earlier messages it contains; others expect each message logged. Settle it in the protocol.
• Attachments. Assess each attachment on its own. A non-privileged attachment to a privileged email is generally produced or separately justified, and parent and child entries should show their family relationship.
• Redactions. Documents produced with privilege redactions usually belong on the log as well, unless the parties agree that labeled redactions are enough. Our guide to redacting exhibits covers labeling.
• Text messages. When chats are produced in day or thread units, log at the same unit and identify every participant. See producing text messages in discovery for unitization.
• Third parties. A friend, relative or new partner on a client communication may defeat the privilege, subject to exceptions. Flag these for the attorney rather than deciding them in first-pass review.

A privilege review workflow for small teams

Many log problems are workflow problems. This sequence keeps logging inside the review instead of after it.

1. Set the rules. Agree on exclusions, thread handling, format and timing, and ask for a Federal Rule of Evidence 502(d) order.
2. Build the names list. List every attorney, staff member and agent, and search for those names and email domains to pull potentially privileged items forward.
3. Code and describe in first pass. Use four codes: privileged, partially privileged, not privileged and needs attorney review. Draft the basis and description while the item is open.
4. Attorney second-level review. Every withhold and redaction call gets attorney review, consistent with supervision duties under ABA Model Rules 5.1 and 5.3.
5. Quality-check against the production. No logged item appears in the production, every family member is accounted for, duplicates are treated the same way and redacted Bates numbers match.
6. Serve and maintain. Serve the log with a cover letter noting format and agreed exclusions, and update it with every supplemental production.
7. Stay clawback-ready. Know the Rule 26(b)(5)(B) notice procedure and the Rule 502(b) standard, and remember ABA Model Rule 4.4(b) when your team receives something that looks inadvertently sent.

Keeping internal firm discussion separate from client-facing messages, as CourtBriefly does by design, also reduces the chance that work-product notes end up in a production set in the first place.

What privilege log mistakes cause the most trouble?

Boilerplate, over-designation and missing context drive many of the disputes.

• The same generic description repeated across hundreds of entries
• Logging business communications merely because a lawyer was copied
• No indication of which participants are attorneys
• Third parties on a communication with no explanation of why privilege survives
• A duplicate withheld in one place and produced in another
• A log served long after the production without an agreement
• A log that never gets updated for supplemental productions

Reviewing the other side’s log

The same standards work in reverse when a log arrives. Before the meet-and-confer, check:

• Entries that list no attorney as author or recipient
• Third parties whose presence is not explained
• Descriptions identical across many unrelated items
• Attachments withheld only because their parent email was
• Date gaps, or items you know exist that appear nowhere on the log or in the production

Group the problems by category in your deficiency letter rather than disputing entries one at a time; it keeps the conversation focused and makes any later motion easier for the court to follow.

Whether a privilege applies, and whether it survived a third party’s involvement, are legal judgments under the governing law. Staff should flag rather than decide, and teams working in an unfamiliar court should confirm logging conventions with counsel licensed in that jurisdiction.