Checklist · Litigation

Building a Privilege Log: A Practical Checklist

Type
Checklist
Jurisdiction
National
Date
2026-06-02
Topic
Litigation

A privilege log is the document that lets a party lawfully keep privileged material out of an opponent's hands, and it is also one of the fastest ways to hand that protection away. This checklist rebuilds federal privilege-log practice from the ground up: confirming the privilege genuinely attaches before anything is withheld, planning the log's method and timing at the Rule 26(f) conference under the December 1, 2025 amendments, choosing between document-by-document and categorical formats, and writing descriptions that reveal enough to justify the claim without disclosing the advice itself. It pairs each move with governing authority, including Fed. R. Civ. P. 26(b)(5), the Upjohn and Hickman foundations, the primary-purpose problem after In re Kellogg Brown & Root, and the clawback machinery of Federal Rule of Evidence 502(b) and 502(d). It then walks through inadvertent production, subject-matter waiver, the Rule 26(g) signature, timing disputes under Burlington Northern, and defending the log on a motion to compel or in camera review. It is general information, not legal advice; the rules, local practice, and privilege law vary by jurisdiction and change.

Building a Privilege Log: A Practical Checklist

Litigation > Discovery | Published 2 June 2026 - Updated 12 June 2026 | UpLaw - uplaw.us

The privilege log is the one discovery document engineered to protect a right and just as capable of destroying it. Withhold too much information and you have not carried your burden; reveal too much and you have waived the very protection you were asserting. This checklist walks the tightrope, phase by phase, with the governing rules and cases at each step.

Keywords: privilege log, Rule 26(b)(5), attorney-client privilege, work product doctrine, Upjohn, Hickman v. Taylor, categorical privilege log, FRE 502(d), FRE 502(b), clawback, subject-matter waiver, Rule 26(g), Burlington Northern, primary purpose test, in camera review, ESI privilege review

Discovery in federal court is built on a simple premise: parties turn over what is relevant and proportional, and the fights are about the edges. Privilege is where that premise stops. The attorney-client privilege and the work-product doctrine let a litigant keep responsive, relevant, sometimes decisive material away from the other side entirely. But those protections do not enforce themselves. A party that withholds a document has to say so, describe what it is holding back, and explain why, all without spilling the secret it is trying to keep. That accounting is the privilege log, and Federal Rule of Civil Procedure 26(b)(5)(A) makes it mandatory for any party that withholds otherwise-discoverable material on a privilege or protection theory.

The log is deceptively hazardous. It looks like clerical work, a spreadsheet of dates and authors, and it is routinely delegated to the most junior person in the room. Yet a thin log can waive the privilege it was meant to preserve, an over-detailed log can waive it by disclosure, an unsigned log can waive it on a technicality, and a late log can waive it for tardiness. Few documents in litigation carry that much downside for so little apparent glamour.

This checklist treats log-building as a disciplined, seven-phase workflow, and it reflects the December 1, 2025 amendments that pull privilege planning forward to the opening days of a case. For the surrounding architecture of federal discovery, work through the federal civil discovery refresher; for the production mechanics that generate the withheld set in the first place, see the guide to objecting and responding to requests for production.

How to use this checklist

Each phase below opens with a checkbox list you can lift into a matter file, followed by an analysis of why the step matters and where litigators lose the protection. The phases run in order because the order is load-bearing: you cannot log what you have not correctly identified as privileged, you cannot pick a format you did not negotiate, and you cannot defend a log you did not sign. Read the doctrine section first. Most catastrophic log failures are not drafting failures; they are failures to confirm that a privilege ever attached.

The doctrine the log rests on

A privilege log is only as strong as the privilege behind each entry. Courts do not defer to the label a party puts on a document, and they construe both the attorney-client privilege and the work-product protection against the party asserting them, because each one removes relevant evidence from the search for truth. As the Supreme Court put it in Fisher v. United States, the privilege "applies only where necessary to achieve its purpose" and is narrowly confined. 425 U.S. 391, 403 (1976). Everything in this checklist assumes you have done the substantive work of confirming that the protection genuinely attaches. That work happens before a single log entry is drafted.

The attorney-client privilege, element by element

The classic formulation asks whether there was (1) a communication (2) between a client, or the client's agent, and a lawyer, or the lawyer's agent, (3) made in confidence (4) for the purpose of obtaining or providing legal advice, and (5) not waived. Each element is a place a claim can fail:

  • A document that is not a communication at all, for example a pre-existing business record, a bank statement, or an underlying contract, is not privileged just because it landed in a lawyer's inbox. The privilege protects the communication, not the facts inside it, and not documents that were never privileged to begin with.
  • The confidentiality element collapses if the communication was shared beyond the circle of those who needed it to give or receive the advice. Copying a lawyer on an email that also went to a public-relations vendor or an outside business partner can break confidentiality on the spot.
  • The legal-advice element is the one that generates the most log entries and the most losses, because so much corporate communication mixes business and law.

The primary-purpose problem

Executives and in-house counsel do not sort their emails into "legal" and "business" folders. A single message may forward a regulatory question, a pricing decision, and a scheduling note in the same thread. Courts resolve these mixed communications with a primary purpose test, sometimes called the predominant-purpose test: the privilege attaches if the communication's primary purpose was to obtain or provide legal advice, not business advice.

The wrinkle is that "primary" implies a single dominant purpose, and real communications often have several. In In re Kellogg Brown & Root, Inc., the D.C. Circuit reframed the inquiry, holding that the privilege protects a communication so long as "one of the significant purposes" of the communication was to obtain or provide legal advice; courts should not try to distill a single primary purpose or apply a "but-for" test. 756 F.3d 754, 759-60 (D.C. Cir. 2014); see also Restatement (Third) of the Law Governing Lawyers § 72 (2000). Some courts have adopted that "significant purpose" gloss, while others keep to a stricter predominant-purpose analysis. See Smith-Brown v. Ulta Beauty, Inc., No. 18-cv-610, 2019 WL 2644243, at *2-3 (N.D. Ill. June 27, 2019) (adopting the significant-purpose framing and cataloguing courts on both sides). For log-building, the practical lesson is that mixed-purpose documents demand individual judgment, and your description had better make the legal purpose visible.

Hypothetical. Meridian Foods' vice president of operations emails the general counsel: "Attached is the draft supplier contract and our margin model. Two questions: does the indemnity clause expose us under the new state labeling statute, and separately, should we push the vendor for net-60?" The indemnity-and-statute question is legal; the net-60 question is commercial. The whole email is not automatically privileged. A defensible log entry would describe it as a communication from a company officer to the general counsel seeking legal advice regarding contractual indemnity obligations under state labeling law, and counsel should be prepared to explain why the legal purpose predominates or is at least a significant purpose. If the email were mostly about payment terms with the statute mentioned in passing, the claim would be weak.

Upjohn and the corporate client

When the client is an organization, the privilege has to reach the employees who actually hold the information counsel needs. Upjohn Co. v. United States rejected the narrow "control group" test and held that the privilege can cover communications between corporate counsel and employees at any level of the hierarchy, where the communications concern matters within the scope of the employee's duties, are made at the direction of superiors so the company can obtain legal advice, and are treated as confidential. 449 U.S. 383, 394-95 (1981). A minority of states still apply a control-group test that limits the privilege to senior decision-makers, which matters whenever state privilege law governs under Federal Rule of Evidence 501.

The operational takeaway is that privilege in the corporate setting is manufactured or forfeited at the moment of the communication, not at the moment of logging. An internal investigation opened with proper Upjohn warnings, run at counsel's direction, can protect rank-and-file interview memos. The same investigation framed as routine business fact-finding, with no legal framing and no confidentiality discipline, may yield nothing to log. If you are logging investigation materials, the front-end hygiene, who directed the work, what warnings were given, how the results were circulated, is what your log entries are quietly asserting.

Work product: ordinary versus opinion

The work-product doctrine is a separate protection with a separate origin. Hickman v. Taylor recognized that materials an attorney prepares in anticipation of litigation are shielded from routine discovery, and Rule 26(b)(3) codified the protection. 329 U.S. 495, 510-11 (1947); Fed. R. Civ. P. 26(b)(3)(A). Two features distinguish it from the attorney-client privilege and reshape how you log it:

  • The trigger is litigation, not legal advice. Work product covers documents prepared "in anticipation of litigation or for trial," by or for a party or its representative, which sweeps in materials prepared by investigators, consultants, and insurers, not only lawyers.
  • There are two tiers. Ordinary (or fact) work product, such as witness-interview notes and factual compilations, is discoverable if the requesting party shows substantial need and an inability to obtain the substantial equivalent without undue hardship. Fed. R. Civ. P. 26(b)(3)(A)(ii). Opinion work product, the mental impressions, conclusions, opinions, and legal theories of counsel, receives near-absolute protection, and Rule 26(b)(3)(B) directs courts to guard against its disclosure even when fact work product is ordered produced.

Because work product can be overcome by a sufficient showing while the attorney-client privilege cannot, it is often worth asserting both protections for the same document where both plausibly apply. That belt-and-suspenders instinct feeds directly into a logging discipline discussed below: list every ground that supports withholding, because a ground you omit can be treated as waived.

Phase 1: Confirm the privilege actually applies

  • [ ] Review each withheld document individually; do not rely on a "Privileged & Confidential" stamp, a lawyer in the copy line, or a folder label to establish privilege.
  • [ ] For attorney-client claims, verify all five elements: communication, between client (or agent) and lawyer (or agent), in confidence, for legal advice, not waived.
  • [ ] For mixed business-and-legal communications, articulate why legal advice was the primary purpose, or at least a significant purpose under Kellogg Brown & Root.
  • [ ] For organizational clients, run the Upjohn analysis and confirm whether federal or state privilege law governs under Rule 501, because a control-group state may not protect lower-level employee communications.
  • [ ] For work product, classify each item as ordinary or opinion, and identify the litigation that was anticipated when the document was created.
  • [ ] Confirm no exception applies, most importantly the crime-fraud exception and any at-issue or subject-matter waiver already triggered by the client's own conduct.
  • [ ] Assert every applicable ground on each entry; an unlisted ground can be deemed waived.

Why this comes first. You cannot log your way out of a bad privilege claim. Because courts construe the privilege narrowly, a party that over-designates, sweeping in ordinary business records because a lawyer was nearby, invites a challenge that can spread to the whole log and, in the worst cases, produce a broad waiver. The single most common substantive error is treating the presence of a lawyer as dispositive. It is not. A routine commercial document does not become privileged by being routed through outside counsel, and a business decision does not become legal advice because the decision-maker happens to have a J.D. Get the substance right, document your reasoning while it is fresh, and only then start logging. For the front-end investigative and preservation choices that shape what ends up on the log, see the Rule 26 initial disclosures and discovery-plan checklist.

Phase 2: Plan the log at the Rule 26(f) conference

  • [ ] Put privilege-log method and timing on the Rule 26(f) agenda; the December 1, 2025 amendments direct parties to address the "timing and method" of privilege claims in the discovery plan (Fed. R. Civ. P. 26(f)(3)(D)).
  • [ ] Negotiate categorical logging, or a hybrid, wherever a document-by-document log would be disproportionate to the volume of withheld material.
  • [ ] Seek a court order under Federal Rule of Evidence 502(d) providing that production does not waive privilege in this or any other federal or state proceeding.
  • [ ] Ask the court to fold the agreed method, format, fields, and deadlines into the Rule 16(b) scheduling order (Fed. R. Civ. P. 16(b)(3)(B)(iv)).
  • [ ] Agree on rolling deadlines tied to production waves, rather than a single end-of-discovery due date, in document-intensive cases.
  • [ ] Agree on treatment of categories you can exclude from logging entirely, such as post-complaint communications with litigation counsel.

Why the front-of-case shift matters. For years, the privilege log was an afterthought, a task that surfaced at the close of document production when review budgets were exhausted and deadlines were near. The December 1, 2025 amendments push in the opposite direction, treating the method and timing of privilege claims as a discovery-planning subject to be resolved at the outset, alongside the Rule 26(f) discussion of electronically stored information and Rule 502 agreements. Two devices that experienced litigators already favored are now squarely on the opening agenda: categorical logging and the 502(d) order.

The 502(d) order deserves special emphasis because it is the strongest clawback protection the rules offer. Under Federal Rule of Evidence 502(d), a federal court may order that disclosure of privileged material in the litigation before it does not operate as a waiver "in any other federal or state proceeding." That order does two things a party cannot get from the default rules. First, it does not require the producing party to prove the disclosure was inadvertent or that it took reasonable precautions, the showing that Rule 502(b) demands. Second, its non-waiver effect travels with the documents into every other case, state or federal, by operation of Rule 502(d) and (e). A one-paragraph order entered at the scheduling conference can convert a later production of a hot privileged email from a disaster into a phone call. Skipping it is one of the least defensible economies in modern litigation. The planning steps that surround this negotiation are laid out in the Rule 26 discovery-plan checklist, and the broader sequence appears in the federal discovery toolkit.

Phase 3: Choose the logging format

  • [ ] Decide between a traditional (document-by-document) log, a categorical log, or a hybrid, based on volume, the parties' agreement, and local practice.
  • [ ] For a traditional log, capture for each item: a control or Bates number, document type, date, author, every recipient identified by name and role (never "et al." or "various"), any copyees, a subject-matter description, and the specific privilege or protection asserted.
  • [ ] For a categorical log, define categories narrow enough to be assessable, describe each category so the opponent can evaluate the claim, and state the privilege asserted for the category.
  • [ ] Confirm the local rules and the presiding judge's practices; some districts and judges expect individualized logs, while many now permit categorical logging where a full log would be unduly burdensome.
  • [ ] Do not serve an auto-generated log built solely from metadata fields; supplement every entry with a human-written subject-matter description.
  • [ ] For email threads, decide up front whether to log by thread or by message, and apply the choice consistently.

Why format is strategic, not clerical. The volume of modern electronically stored information has made document-by-document logging ruinously expensive in many cases. A production of several hundred thousand documents can generate tens of thousands of privileged hits, and logging each one individually can cost more than the underlying discovery. Categorical logging, grouping withheld documents into defined categories with a single description apiece, is the pressure-release valve, and it is exactly what the amended Rule 26(f) invites parties to negotiate. In some forums it is the default: New York's Commercial Division, for instance, presumes categorical logging and requires parties to meet and confer about it, precisely to spare litigants the cost of itemized logs. See N.Y. Comp. Codes R. & Regs. tit. 22, § 202.20-a; Commercial Division Rule 11-b.

Categorical logging is a bargain, not a license. A category has to be tight enough that the opposing party can actually assess whether the privilege holds. "All documents withheld as privileged" is not a category; it is a refusal to log. "Communications between [named outside counsel] and members of the Meridian legal department, dated after the complaint was filed, concerning litigation strategy in this action" is a category a court can evaluate. Draw categories too broadly and you get the worst of both worlds: the cost savings evaporate when the court orders you to break the category into a traditional log anyway.

The metadata trap is the other format hazard. Review platforms will happily generate a "log" by exporting the author, date, and recipient fields for every withheld document. That output is not a compliant privilege log. Counsel must add, for each entry or category, a substantive description of the subject matter that lets the requesting party and the court test the claim; a bare field dump does not satisfy Rule 26(b)(5)(A). Parties sometimes stipulate to an initial metadata-only log to be supplemented later, but absent that agreement, an unsupplemented auto-generated log is routinely held insufficient.

Traditional versus categorical: a side-by-side

Feature Traditional (document-by-document) Categorical
Unit logged Each withheld document A defined group of withheld documents
Cost High; scales with volume Lower; scales with number of categories
Best fit Modest volumes, targeted disputes High-volume ESI, defined communication streams
Risk Expense, delay, inconsistency across a long log Categories drawn too broadly, ordered re-logged
Negotiation Often the default expectation Usually requires agreement or a supportive local rule

Neither format is a safe harbor by itself. A traditional log full of parroted descriptions is as vulnerable as a categorical log built on vague buckets. The format sets the container; the descriptions, addressed next, determine whether the log survives.

Phase 4: Draft descriptions that say enough and no more

  • [ ] Do not merely restate the legal standard; a description like "document reflecting legal advice" or "privileged communication" is inadequate and can be treated as a failure to support the claim.
  • [ ] Do not disclose the substance of the advice; a description detailed enough to reveal what counsel actually advised can itself waive the privilege.
  • [ ] Aim for the middle register: identify the type of document, the participants and their roles, and the general legal subject, without narrating the legal analysis.
  • [ ] Identify authors and recipients by name and role so the opponent can test whether confidentiality was preserved and whether a lawyer was actually involved.
  • [ ] Where a document is withheld in part, coordinate the log entry with the redaction so the withheld portion is disclosed as withheld and the basis is stated.
  • [ ] Keep terminology consistent across the log; inconsistent labels invite line-by-line challenges.

Why the description is where logs live or die. Rule 26(b)(5)(A)(ii) sets the standard in a single, demanding sentence: the withholding party must describe the nature of the documents "in a manner that, without revealing information itself privileged or protected, will enable other parties to assess the claim." That sentence contains the entire tension of privilege logging. Say too little and you have not enabled the other side to assess the claim, so a court may find the privilege unsupported and order production. Say too much and you have revealed privileged information, waiving the protection by the very act of describing it.

The under-description failure is common and well-documented. Courts have repeatedly held that boilerplate descriptions that do no more than track the elements of the privilege, "confidential attorney-client communication," "prepared in anticipation of litigation," fail Rule 26(b)(5) because they give the requesting party nothing to evaluate. See Johnson v. Ford Motor Co., 309 F.R.D. 226, 240-41 (S.D. W. Va. 2015) (rejecting conclusory descriptions and ordering a supplemental log). The over-description failure is subtler and, because it is self-inflicted, more painful: a log entry that quotes or paraphrases the actual advice, "memo advising that the company should not disclose the defect because liability would attach under Section 12," has disclosed the privileged content on the face of the log. Courts treat that kind of narration as a waiver of the privilege for the document. Cf. Veolia Water Solutions & Techs. Support v. Siemens Indus., Inc., 63 F. Supp. 3d 621, 632-33 (E.D.N.C. 2014) (privilege can be waived where the description reveals the protected substance).

The target is a description that proves the elements without narrating the content. Compare three ways of logging the same document:

Too little: "Email — privileged and confidential — attorney-client privilege." This tells the reader nothing. It could describe anything.

Too much: "Email from GC advising CEO that the company's arbitration clause is probably unenforceable under state law and recommending the company settle the Ramirez matter for under $200,000 to avoid a class action." This narrates the advice and reveals the legal conclusion and the strategy. The description has become the disclosure.

Just right: "Email dated 3/14/2026 from Dana Osei (General Counsel) to Priya Rao (CEO) providing legal advice regarding the enforceability of the company's consumer arbitration clause and litigation strategy in the Ramirez matter. Withheld: attorney-client privilege; work product." This identifies the document, the participants and their roles, the general legal subject, and the grounds, and it lets the reader assess confidentiality and legal purpose without revealing the advice.

The recipient field is not a formality. Naming every recipient and copyee, with a role for each, is how the opposing party (and the court) tests two things at once: whether a lawyer was genuinely in the communication for a legal purpose, and whether the circle of recipients was tight enough to preserve confidentiality. A log that hides recipients behind "et al." or omits copyees is inviting the inference that the document was circulated too broadly to be confidential. Log the whole distribution, and log it accurately.

Phase 5: Handle redactions and partial withholdings

  • [ ] For any document produced in redacted form on privilege grounds, create a corresponding log entry (or note within the log) reflecting the redaction and stating the basis.
  • [ ] Ensure the redaction actually removes the privileged content and nothing more; over-redaction of non-privileged text is itself objectionable and often ordered undone.
  • [ ] Confirm redactions are burned into the production image so hidden text cannot be revealed by copying or extracting the underlying layer.
  • [ ] Track redaction reasons consistently, and be prepared to justify redactions the same way you justify fully withheld documents.

Why partial withholdings need the same rigor. A document that is mostly discoverable but contains one privileged paragraph is produced with that paragraph redacted, not withheld in full. The mistake litigators make is treating redactions as invisible to the log. Rule 26(b)(5)(A) applies to information withheld, whether the withholding is of a whole document or a portion, so a redaction is a withholding that must be disclosed and justified. Courts see over-redaction as a species of privilege overreach and treat it accordingly, ordering the material produced and, in aggravated cases, questioning the good faith of the whole review. The technical failure mode, redacting on the visible layer while leaving extractable text underneath, is its own disaster: a "redaction" that a paralegal can defeat with a copy-paste has disclosed the content and waived the claim. Redact the image, log the redaction, and move on.

Phase 6: Handle inadvertent production and clawback

  • [ ] If a 502(d) order is in place, invoke it: production does not waive, and you do not have to prove inadvertence or reasonable precautions.
  • [ ] Absent a 502(d) order, preserve the Rule 502(b) safe harbor by showing the disclosure was inadvertent, that reasonable steps were taken to prevent it, and that reasonable steps were taken promptly to rectify it once discovered.
  • [ ] On learning of an inadvertent production, notify the receiving party immediately and specify the basis for the privilege claim.
  • [ ] On receiving notice that the other side clawed back a document, promptly return, sequester, or destroy it and any copies, and do not use or further disclose it pending resolution (Fed. R. Civ. P. 26(b)(5)(B)).
  • [ ] Do not file inadvertently produced privileged material with the court; presenting it in open filings can compound the harm and draw sanctions.
  • [ ] Guard against subject-matter waiver: under Rule 502(a), an intentional disclosure extends to undisclosed material only when they concern the same subject and fairness requires considering them together.

Why clawback discipline matters. Privilege is fragile and non-self-executing. In a case where hundreds of thousands of documents change hands under deadline pressure, some privileged material will slip into a production no matter how careful the review. What separates a recoverable mistake from a waived privilege is the framework in place when it happens.

The default framework is Federal Rule of Evidence 502(b). It rescues an inadvertent disclosure only if the producing party clears three hurdles: the disclosure was inadvertent, the holder "took reasonable steps to prevent disclosure," and the holder "promptly took reasonable steps to rectify the error." Courts assess "reasonable steps" holistically, looking at the volume of the production, the review procedures used, the number of documents that slipped through, and the diligence of the effort, so the analysis turns into a fact fight about the adequacy of your review protocol. See Victor Stanley, Inc. v. Creative Pipe, Inc., 250 F.R.D. 251, 259-62 (D. Md. 2008) (Grimm, J.) (finding waiver where a party could not demonstrate the reasonableness of its keyword-based privilege screen). Winning that fight is expensive and uncertain.

The 502(d) order sidesteps the whole contest. Where the court has entered a non-waiver order, production does not waive, full stop, without any inquiry into inadvertence or the reasonableness of precautions, and the protection follows the documents into other proceedings. That is why Phase 2 puts the 502(d) order on the opening agenda: the time to secure clawback protection is before the accident, not after. A party that reaches Phase 6 without a 502(d) order is litigating its privilege from a much weaker position than one who spent a paragraph on it at the scheduling conference.

Subject-matter waiver is the multiplier that makes all of this frightening. Rule 502(a) confines the doctrine to intentional disclosures and applies it only where the disclosed and undisclosed communications "concern the same subject matter" and "ought in fairness to be considered together." That means an inadvertent slip, handled properly, generally does not spread beyond the produced document. But an intentional, selective disclosure, quoting a favorable snippet of a privileged memo in a brief while withholding the rest, can waive the privilege across the entire subject. The lesson runs in both directions: handle accidents under 502(b) or (d) and they stay contained; make strategic partial disclosures and you may forfeit far more than you meant to. These clawback mechanics are also central to the production-side checklist for responding to Rule 34 document requests.

Phase 7: Sign, serve, and defend the log

  • [ ] Have an attorney of record sign the log; a privilege log is a discovery response subject to the Rule 26(g) certification.
  • [ ] Serve the log on time, whether the deadline comes from the rules, a local rule, the scheduling order, or the parties' agreement; an untimely log risks waiver.
  • [ ] For rolling productions, supplement the log as additional withheld material is identified, and calendar each supplement.
  • [ ] Be ready to defend specific entries in a meet-and-confer, and to narrow or withdraw claims that will not hold.
  • [ ] If a dispute survives meet-and-confer, be prepared for a motion to compel and for the court to conduct in camera review of the disputed documents.
  • [ ] Preserve the withheld documents intact until every privilege dispute is finally resolved.

Why the signature and timing are traps. The signature is not a formality. Rule 26(g) requires an attorney to certify every discovery response, and a privilege log is a discovery response. Courts have held that serving an unsigned privilege log can waive the very protections the log asserts, because an unsigned log is, in effect, no proper assertion at all. See Rhodes v. Ingram, No. 5:14-CV-198, 2015 U.S. Dist. LEXIS (E.D.N.C. 2015) (treating an unsigned log as failing to preserve the claim). The fix costs nothing: an attorney of record signs the log before it goes out.

Timing is the messier trap because the rules do not fix a single deadline for serving a privilege log. Courts have divided on when the log is due. Some read the Federal Rules to require the log with the written responses to a document request; others tolerate a reasonable interval, especially in document-heavy cases; and many districts impose their own local deadlines, with the Southern and Eastern Districts of New York requiring the log at the same time as the responses and objections under Local Civil Rule 26.2, subject to case-specific relief. See, e.g., Williams v. Bridgeport Music, Inc., 300 F.R.D. 120, 123-24 (S.D.N.Y. 2014) (declining to enforce the local timing rule mechanically). Because of that uncertainty, parties in large cases routinely negotiate a longer or rolling log deadline at the Rule 26(f) conference and memorialize it in the scheduling order.

When a log is late, most courts do not apply a per se waiver rule. The Ninth Circuit's influential decision in Burlington Northern & Santa Fe Railway Co. v. United States District Court rejected a bright-line rule and directed courts to weigh a set of case-specific factors: the degree to which the withholding party's log and objections gave the requesting party the information needed to assess the claim, the timeliness of the log, the magnitude of the production, and other circumstances that make an itemized log more or less feasible, all applied in a way that avoids penalizing good-faith efforts. 408 F.3d 1142, 1149 (9th Cir. 2005). Courts applying Burlington Northern have declined to find waiver where the delay was modest and the party acted in good faith, see In re Universal Service Fund Telephone Billing Practices Litigation, 232 F.R.D. 669, 671-72 (D. Kan. 2005), while other courts have found waiver where the log was both late and inadequate, see In re Capital One Bank Credit Card Interest Rate Litigation, 286 F.R.D. 676, 679 (N.D. Ga. 2012). The through-line is that a prompt, careful log built in good faith is rarely fatal even if a deadline slips, while a late log that is also thin invites the harshest result.

Inadequacy, independent of timing, is its own path to waiver. A log so deficient that it does not enable the opposing party to assess the claims can forfeit the protections it purported to assert. See In re Grand Jury Subpoena, 274 F.3d 563, 575-76 (1st Cir. 2001) (a party that fails to provide the required information about withheld documents risks losing the privilege). Note, too, that the duty to log every ground is enforceable at the entry level: a court may treat a basis for withholding that the log omitted as waived, even if another asserted basis remains. Cf. Gama Aviation Inc. v. Sandton Capital Partners, L.P., 99 A.D.3d 423, 424 (N.Y. App. Div. 1st Dep't 2012) (unlisted grounds deemed waived). List everything; sign it; serve it on time; be ready to defend it.

When the fight goes to the judge

Meet-and-confer resolves most log disputes, and it should: narrowing categories, adding detail to weak entries, and withdrawing claims that will not survive is cheaper than motion practice and preserves credibility with the court. When it fails, the requesting party moves to compel, and the presiding judge frequently orders in camera review, inspecting the disputed documents privately to decide the claims. In camera review is a double-edged tool. It lets a producing party prove a close call without disclosing the documents to the opponent, but it also puts the actual documents in front of a skeptical judge, so the claim had better match the log. A document logged as "legal advice regarding regulatory compliance" that turns out, on inspection, to be a lunch invitation forwarded to counsel does more than lose one entry; it tells the court to distrust the entire log. Log honestly, and never designate a document you would be embarrassed to have the judge read.

A worked example: building a log end to end

Consider a hypothetical to see the phases connect. Larkspur Devices, Inc. is sued in federal court by a competitor alleging that Larkspur's flagship sensor infringes a patent and that Larkspur's marketing makes false performance claims. Discovery will be document-heavy: engineering files, marketing communications, regulatory correspondence, and a large volume of email.

  • Phase 1. Larkspur's counsel finds four buckets of arguably protected material: (a) emails between the engineering team and outside patent counsel about a pre-suit freedom-to-operate opinion; (b) an internal investigation into the accuracy of the marketing claims, opened by the general counsel after a customer complaint; (c) post-complaint communications with litigation counsel; and (d) a forensic vendor's report on a data-integrity question. Counsel confirms element by element that the patent-opinion emails are privileged, applies Kellogg Brown & Root to the investigation emails to isolate the ones where legal advice was a significant purpose, and classifies the investigation interview memos as work product, opinion where they contain counsel's assessments.
  • Phase 2. At the Rule 26(f) conference, Larkspur proposes categorical logging for the post-complaint litigation-counsel communications (bucket c) and a 502(d) order. Opposing counsel agrees; the court enters the 502(d) order and sets a rolling log deadline keyed to each production wave.
  • Phase 3. Larkspur uses a hybrid: a single category for bucket (c), and a traditional, itemized log for buckets (a), (b), and (d), where the claims are more contestable and individualized descriptions strengthen them.
  • Phase 4. Each traditional entry names the author and recipients with roles, dates the document, gives the legal subject, and lists every ground. The investigation memos are logged as work product and, where counsel's impressions appear, opinion work product; the forensic report is logged carefully, because whether it is protected depends on who directed it and why.
  • Phase 5. Several engineering emails are mostly technical with a single privileged paragraph seeking counsel's view; Larkspur produces them redacted and logs the redactions.
  • Phase 6. Mid-production, a privileged patent-opinion email is inadvertently produced. Because the 502(d) order is in place, counsel simply notifies the other side, claws it back under Rule 26(b)(5)(B), and the receiving party sequesters it, no fight about reasonable precautions.
  • Phase 7. An attorney of record signs each log and supplement, they are served on the rolling schedule, and when the competitor challenges the forensic-report entry, the parties meet and confer; the dispute narrows to a single document, which the court reviews in camera and rules protected.

The example is invented, but the sequence is the point: each phase makes the next one defensible, and the 502(d) order secured in Phase 2 is what makes the Phase 6 accident a non-event.

Special situations

Subpoenas to nonparties. A nonparty served with a Rule 45 document subpoena has its own logging obligation. To withhold subpoenaed material on privilege grounds, the nonparty must expressly make the claim and describe the withheld material well enough to let the requesting party assess it, mirroring Rule 26(b)(5)(A). Fed. R. Civ. P. 45(e)(2)(A). The timing conventions differ: courts generally expect the nonparty to serve its initial privilege-based objections within the time Rule 45 allows for objections, and to follow with a more detailed log within a reasonable time. If you represent a subpoenaed nonparty, calendar both steps.

Common-interest and joint-defense arrangements. Sharing privileged material with an aligned party, co-defendants coordinating a defense, or a company and its indemnitor, does not automatically waive the privilege if the parties share a common legal interest and a proper common-interest arrangement is in place. But those shared communications still have to be logged, and the log entry has to make the common-interest basis visible, identifying the parties and the shared legal interest, so the opponent can test whether the doctrine actually applies. A sloppy entry that hides the third-party recipient invites a waiver challenge on confidentiality grounds.

Data-breach forensic reports. Whether a post-incident forensic report is protected work product has become a heavily litigated question, and the answer turns on the same front-end facts the log quietly asserts: who engaged the forensic firm, whether the engagement ran through counsel for the purpose of legal advice or litigation, and whether the report was used for ordinary business remediation. A report commissioned by counsel, kept confidential, and directed at anticipated litigation is far more defensible than the same report circulated to the business for operational fixes. If you are logging one, make sure the underlying engagement supports the claim before you assert it. The interplay of privilege and incident response is developed in building IP into data-breach incident response and the companion crown-jewels incident-response checklist.

Government investigations and cooperation. Producing privileged material to a regulator or prosecutor, even under a confidentiality agreement, generally waives the privilege as to third parties, because most courts have rejected "selective waiver." A company weighing cooperation should understand that documents shared with the government may become discoverable by civil adversaries, and that its privilege log in the follow-on civil case will have to account for what was and was not disclosed. Rule 502 mitigates some of the sting for inadvertent and court-ordered disclosures, but it does not resurrect a privilege voluntarily surrendered to an agency.

State-court and choice-of-law overlays. Federal Rule of Evidence 501 makes state privilege law govern claims and defenses for which state law supplies the rule of decision, which is common in diversity cases. State logging requirements can differ from the federal model, on the elements of the privilege (control-group versus Upjohn states), the default log format (New York's Commercial Division presumes categorical logging), and timing. Confirm which sovereign's privilege law governs before you build the log, because the substantive privilege you are asserting, not just the procedure, may change.

Common mistakes that waive the protection

  • Conjuring privilege by ritual. A "Privileged & Confidential" stamp, a lawyer in the copy line, or a document routed through counsel does not make a business record privileged. Over-designation invites a challenge that can spread across the log.
  • Parroting the legal standard. "Reflecting legal advice" and "prepared in anticipation of litigation" describe nothing and can be treated as a failure to support the claim. See Johnson v. Ford Motor Co., 309 F.R.D. 226.
  • Over-describing. A log entry that narrates the actual advice discloses the privileged content and can waive it on the face of the log.
  • Hiding recipients. "Et al." and omitted copyees defeat the opponent's ability to test confidentiality and suggest the document was circulated too broadly.
  • Serving an auto-generated metadata log. A field dump from a review platform, without human subject-matter descriptions, is routinely held insufficient.
  • Skipping the 502(d) order. Forgoing the single strongest clawback protection turns every inadvertent production into a fact fight under Rule 502(b).
  • Forgetting the Rule 26(g) signature. An unsigned log can waive the protections it asserts.
  • Omitting a ground. A basis for withholding left off the entry can be deemed waived even if another ground survives.
  • Ignoring redactions. Partial withholdings must be logged and must actually remove the privileged text, image-burned so it cannot be extracted.
  • Leaving logging to the end. After the December 1, 2025 amendments, method and timing belong on the Rule 26(f) agenda, not in the last week of discovery.

Quick-reference checklist

  • [ ] Confirm each withheld item is genuinely privileged, element by element, before logging it.
  • [ ] Resolve mixed-purpose documents under the primary-purpose or significant-purpose test and be ready to explain the legal purpose.
  • [ ] Run the Upjohn analysis for organizational clients and confirm whether federal or state privilege law governs.
  • [ ] Classify work product as ordinary or opinion and assert both attorney-client and work-product grounds where both apply.
  • [ ] Put log method and timing on the Rule 26(f) agenda; negotiate categorical logging and a 502(d) order.
  • [ ] Choose a format, traditional, categorical, or hybrid, and confirm it against local rules and the judge's practices.
  • [ ] Draft descriptions in the middle register: enough to assess the claim, not enough to reveal the advice.
  • [ ] Name every author, recipient, and copyee with roles; never use "et al."
  • [ ] Log and justify every redaction; make sure redactions are burned into the image.
  • [ ] Rely on the 502(d) order for clawback; if none, preserve the 502(b) safe harbor and act promptly.
  • [ ] Have an attorney sign the log under Rule 26(g) and serve it on time.
  • [ ] Supplement on rolling productions; meet and confer; be ready for a motion to compel and in camera review.
  • [ ] Preserve withheld documents until every dispute is resolved.

Primary authority

Related UpLaw Resources

Related Checklists

Related Guides and Articles

Related Toolkits

This checklist is general legal information, not legal advice. The Federal Rules of Civil Procedure and Evidence, local rules, and privilege law vary by jurisdiction and change; consult the applicable rules and qualified counsel about your specific case.