Discovery's reach stops at the privileged—but the attorney-client privilege and the work-product protection are, handled carelessly, among the most easily forfeited grounds for withholding material. The privilege log is where logs live or die: say too little and you waive; say too much and you waive. This checklist turns Rule 26(b)(5) privilege practice into ordered, actionable steps, reflecting the December 1, 2025 amendments that push privilege-log planning to the front of the case.

For the full architecture of federal discovery and privilege doctrine, see our practical discovery refresher; for the production side that surrounds logging, see mastering document discovery: objecting and responding to requests for production.

Phase 1: Confirm the privilege actually applies

  • For attorney-client privilege, confirm the communication is (1) between client and counsel (or agents), (2) made and intended to be confidential, and (3) made to obtain or provide legal advice.
  • Assess privilege document-by-document; do not assume a stamp of "privileged and confidential" or a lawyer copied on an email creates it.
  • For mixed business-and-legal communications, ask whether the primary purpose is legal advice.
  • For corporate clients, apply Upjohn Co. v. United States, 449 U.S. 383 (1981): protection reaches employees throughout the hierarchy when communications are made at the direction of superiors to secure legal advice.
  • For work product, distinguish ordinary (fact) work product—discoverable on substantial need and undue hardship—from opinion work product, which is near-absolutely protected (Hickman v. Taylor, 329 U.S. 495 (1947); Fed. R. Civ. P. 26(b)(3)).

Why this comes first. Courts construe the privilege narrowly because it withholds relevant evidence (Fisher v. United States, 425 U.S. 391 (1976)). You cannot create privilege by ritual—routing an ordinary commercial document through outside counsel does not protect it. A properly framed internal investigation with Upjohn warnings can shield rank-and-file interviews; one framed as routine business fact-finding may yield no privilege at all. Get the substance right before you log anything.

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

  • Raise privilege-log method and timing at the Rule 26(f) conference (now required by Rule 26(f)(3)(D), as amended Dec. 1, 2025).
  • Negotiate categorical logging where a document-by-document log would be unduly burdensome.
  • Seek a court order under Federal Rule of Evidence 502(d) rendering production non-waiving in this and every other federal and state proceeding.
  • Confirm the scheduling order addresses privilege-log timing and method (Rule 16(b)(3)(B)(iv)).
  • Agree on the format, fields, and deadline (or rolling deadlines) for the log.

Why the front-of-case shift matters. The 2025 amendments deliberately move privilege-log planning from an end-of-discovery chore to a front-of-case obligation, and nudge parties toward two devices experienced practitioners already favor: categorical logging and the 502(d) order. A 502(d) order is the single strongest clawback protection available—unlike FRE 502(b)'s safe harbor, it does not depend on proving the disclosure was inadvertent or that you took reasonable precautions, and it travels with the documents into every future case. See the planning steps in our Rule 26 initial disclosures and discovery planning checklist.

Phase 3: Choose the logging format

  • For a document-by-document log, capture for each item: document type, date, author, all recipients (by name and role—not "et al."), a subject-matter description, and the specific privilege asserted.
  • For categorical logging, define defensible categories and write category descriptions that still let the opponent assess the claims.
  • Check the jurisdiction: some districts (traditionally the Seventh Circuit's) insist on individualized logs; many now permit categorical logging where a full log would be unduly burdensome.
  • Do not rely on a review platform's auto-generated log without human-supplied descriptions.

Why format is strategic. Given the volume of modern ESI, categorical logging—grouping withheld documents into defined categories—has become increasingly accepted and is exactly what the 2025 amendments invite parties to negotiate. Agreeing up front to log, say, "all post-suit communications between a party and its litigation counsel" as a single category can spare both sides a fortune. Logs auto-generated by a review platform, without human descriptions, are routinely held insufficient.

Phase 4: Draft descriptions that say enough and no more

  • Avoid merely parroting the legal standard ("document reflecting legal advice")—inadequate, and risks waiver (Johnson v. Ford Motor Co., 309 F.R.D. 226 (S.D. W. Va. 2015)).
  • Avoid descriptions so detailed they disclose the actual advice—that can itself waive the privilege (Veolia Water Solutions v. Siemens Indus., Inc., 63 F. Supp. 3d 558 (E.D.N.C. 2014)).
  • Aim for the middle: e.g., "Memorandum from in-house counsel to CEO analyzing the company's legal obligations under new FDA regulations."
  • Identify recipients by name and role so the opponent can assess whether confidentiality was preserved.
  • Coordinate redactions with the log: anything withheld in part should be reflected and the basis stated.

Why the description is where logs live or die. The Rule 26(b)(5)(A) standard is to describe withheld material "in a manner that, without revealing information itself privileged or protected, will enable other parties to assess the claim." Too little and you forfeit the privilege; too much and you forfeit it. The art is to say enough and no more.

Phase 5: Handle inadvertent production and clawback

  • If you obtained a 502(d) order, rely on it: production does not waive, without any showing of inadvertence.
  • Absent a 502(d) order, preserve the FRE 502(b) safe harbor: show the disclosure was inadvertent, reasonable steps were taken to prevent it, and prompt steps were taken to rectify it.
  • On receiving notice of an inadvertent production, promptly return, sequester, or destroy the material (Rule 26(b)(5)(B)).
  • Guard against subject-matter waiver: under FRE 502(a), it is limited to intentional disclosures where fairness requires considering disclosed and undisclosed material together.

Why clawback discipline matters. Privilege is fragile and not self-executing—it must be affirmatively asserted or it is forfeited. In a case where hundreds of thousands of documents change hands, a few privileged ones inevitably slip through. A 502(d) order is the difference between a recoverable mistake and a catastrophe, which is why the amendments push parties to address it at the outset.

Phase 6: Sign, serve, and defend the log

  • Have an attorney sign the log under Rule 26(g)—a privilege log is itself a discovery response.
  • Serve the log timely; an untimely log can waive the protection, though most courts apply the multi-factor Burlington Northern test rather than a per se rule.
  • Be prepared to defend descriptions in a meet-and-confer and, if needed, on a motion to compel or for in camera review.
  • Supplement the log as additional withheld material is identified in rolling productions.

Why the signature and timing are traps. Serving an unsigned log has been held to waive the very protections it asserts (Rhodes v. Ingram (E.D.N.C. 2015)). An inadequate log can waive the privilege it was meant to protect (In re Grand Jury Subpoena, 274 F.3d 563 (1st Cir. 2001)), and so can an untimely one—courts weigh the adequacy of the information, the timeliness, the volume, and the difficulty of the task (Burlington N. & Santa Fe Ry. Co. v. U.S. Dist. Court, 408 F.3d 1142 (9th Cir. 2005)).

Common mistakes

  • Conjuring privilege by ritual. A "privileged" stamp or a copied lawyer does not protect a business document.
  • Parroting the legal standard. "Reflecting legal advice" is inadequate and risks waiver.
  • Over-describing. A description that discloses the advice waives it.
  • Auto-generated logs. Platform-generated descriptions without human input are routinely held insufficient.
  • Skipping the 502(d) order. Forgoing the strongest clawback protection available.
  • Forgetting the Rule 26(g) signature. An unsigned log can waive the protections it asserts.
  • Leaving logging to the end. After the 2025 amendments, plan method and timing at the Rule 26(f) conference.

Primary authority

  • Fed. R. Civ. P. 26(b)(5)(A) — express claim and description of withheld material (the privilege log).
  • Fed. R. Civ. P. 26(b)(5)(B) — clawback procedure for inadvertently produced material.
  • Fed. R. Civ. P. 26(b)(3) — work-product protection (ordinary vs. opinion).
  • Fed. R. Civ. P. 26(f)(3)(D) (as amended Dec. 1, 2025) — views on method and timing of privilege logging and FRE 502 agreements; Rule 16(b)(3)(B)(iv) — scheduling order.
  • Fed. R. Civ. P. 26(g) — attorney signature on discovery responses, including the log.
  • Fed. R. Evid. 502(a), 502(b), 502(d) — subject-matter waiver limits, inadvertent-disclosure safe harbor, and court-ordered non-waiver.
  • Key cases: Upjohn Co. v. United States, 449 U.S. 383 (1981); Hickman v. Taylor, 329 U.S. 495 (1947); Burlington N. & Santa Fe Ry. Co. v. U.S. Dist. Court, 408 F.3d 1142 (9th Cir. 2005); Johnson v. Ford Motor Co., 309 F.R.D. 226 (S.D. W. Va. 2015).

Related resources

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.