In nearly every litigation or government investigation, a party must produce relevant documents to the other side—but it is not required to surrender material protected by a recognized legal privilege. Privilege review is the disciplined process of examining a collection of potentially responsive documents to identify those that are shielded from disclosure, and a privilege log is the formal record that describes each withheld document in enough detail to let the requesting party and the court evaluate the claim. Together they sit at the heart of the discovery exchange, balancing one party’s right to relevant evidence against another’s right to keep confidential communications and protected work product out of an adversary’s hands.
Because an inadvertent disclosure can waive a privilege—and because an overbroad or unsupported withholding can draw sanctions—privilege review demands both legal judgment and rigorous records discipline. It is one of the most time-consuming and expensive phases of e-discovery, and the quality of an organization’s underlying records management directly affects how efficiently it can be done.
What Privilege Review Protects
Privilege review typically screens for several distinct categories of protection, each with its own legal contours:
- Attorney-client privilege protects confidential communications between a client and its lawyer made for the purpose of seeking or providing legal advice. The privilege belongs to the client and can be waived, intentionally or inadvertently.
- Work-product protection shields materials prepared by or for a party or its representative in anticipation of litigation. Unlike attorney-client privilege, it can sometimes be overcome by a showing of substantial need.
- Other privileges and protections may apply depending on the matter—such as those covering certain physician, spousal, or clergy communications, or, in the government context, deliberative-process and other statutory exemptions.
In federal civil litigation, the duty to produce relevant, non-privileged material flows from the discovery provisions of the Federal Rules of Civil Procedure. Privilege review is how a party honors its production obligations while preserving the protections the law allows it to assert.
Building the Privilege Log
When a party withholds a document on privilege grounds, it must ordinarily describe what is being withheld so the claim can be tested. The Federal Rules of Civil Procedure require that a party expressly assert the privilege and describe the nature of the withheld material in a manner that, without revealing the protected content itself, enables other parties to assess the claim. The privilege log is the standard vehicle for meeting that requirement.
A traditional document-by-document log generally captures fields such as:
- A unique document identifier or control number
- Date of the document
- Author, recipients, and any copyees (including indications of who is an attorney)
- Document type (email, memorandum, draft contract, and so on)
- The privilege or protection asserted
- A non-privileged description of the subject matter sufficient to support the claim
The log must walk a careful line: enough detail to justify withholding, but not so much that it discloses the very content the privilege protects. Vague, boilerplate descriptions invite challenges and motions to compel, while overly revealing entries can themselves waive protection.
Categorical and Metadata-Based Logging
Because modern collections can contain millions of items, document-by-document logging is often impractical. Parties increasingly negotiate alternative approaches. A categorical log groups similar withheld materials—for example, “communications between in-house counsel and the compliance team regarding the internal investigation between two dates”—and describes them collectively rather than line by line.
Metadata-driven logs leverage the structured fields already captured by electronic systems, populating author, date, and recipient information directly from the documents’ metadata. The Sedona Conference and other practitioner bodies have long encouraged cooperation and proportionality in this area, urging parties to agree early on log format, scope, and the treatment of categories such as email threads and attachments. Reaching such agreements at the Rule 26(f) conference or in a protective order can dramatically reduce cost and downstream disputes.
Technology, Workflow, and Quality Control
Privilege review usually layers technology over human judgment. Search terms, sender-domain filters (for example, flagging messages involving known law-firm domains), and analytics such as email threading and near-duplicate detection help surface likely-privileged material and reduce redundant review. Technology-assisted review and predictive coding can prioritize documents, but privilege calls almost always require attorney review because the determinations are legal, fact-specific, and consequential.
Effective workflows include rigorous quality control: second-level review of close calls, consistency checks so that the same document is not treated differently across the collection, and reconciliation between the production set and the log so that every withheld item is accounted for. Redaction is a related discipline—partially privileged documents are often produced with protected portions removed rather than withheld entirely, and each redaction should be logged or coded consistently.
Inadvertent Disclosure and Clawback
No review is perfect, and privileged documents occasionally slip into a production. The Federal Rules of Evidence and the Federal Rules of Civil Procedure provide mechanisms to address this. Rule 502 of the Federal Rules of Evidence governs the effect of disclosure on waiver and allows courts to enter orders limiting waiver, while the civil rules establish a procedure for asserting a claim after production—commonly implemented through negotiated “clawback” agreements. These protections reduce, but do not eliminate, the risk, so they are best treated as a safety net rather than a substitute for careful review.
Records Management Foundations
The efficiency and defensibility of privilege review depend heavily on upstream information governance. Reliable metadata, consistent retention practices, defensible legal holds, and well-organized repositories make it far easier to identify custodians, locate counsel communications, and apply privilege screens accurately. Conversely, poor records hygiene—duplicative copies, missing metadata, and shadow systems—drives up cost and risk. While much records management guidance addresses public-sector records and disclosure regimes (for instance, the privilege-style exemptions familiar from freedom-of-information practice), the underlying lesson is universal: good recordkeeping is the precondition for handling privilege claims confidently. Standards bodies and practitioner groups continue to refine guidance as electronic recordkeeping evolves, reflecting the broader modernization seen across the field, including the shift away from older fixed certification models toward functional, requirements-based approaches to electronic records.
Sources & further reading
Authoritative government and non-profit references.
- Federal Rules of Civil Procedure — U.S. Courts
- The Sedona Conference publications — The Sedona Conference
- DOJ Office of Information Policy (FOIA guidance) — U.S. Department of Justice
How to cite this page
APA
RM University Editorial Team. (2026). Privilege Review and Privilege Logs. Records Management University. https://www.recordsmgmt.org/articles/privilege-review-and-privilege-logs/
MLA
RM University Editorial Team. "Privilege Review and Privilege Logs." Records Management University, 16 June 2026, www.recordsmgmt.org/articles/privilege-review-and-privilege-logs/.