Privilege logs in federal court: the 2025 amendments put the method on the scheduling order
Federal procedure · Last verified August 17, 2026
Rule 26(b)(5)(A) has always required a party withholding documents on privilege grounds to describe what it is withholding. What it has never said is how, or when.
That gap produced a familiar pattern: a production goes out, a log arrives months later in whatever format the producing party chose, and the parties then litigate its adequacy. The December 1, 2025 amendments to Rules 16 and 26 are aimed squarely at it — by moving the question to the front of the case.
The underlying obligation
Rule 26(b)(5)(A): when a party withholds information otherwise discoverable by claiming privilege or trial-preparation protection, the party must:
(i) expressly make the claim; and (ii) describe the nature of the documents, communications, or tangible things not produced or disclosed — and do so in a manner that, without revealing information itself privileged or protected, will enable other parties to assess the claim.
Note what the rule does not say. It does not say "privilege log." It does not require a document-by-document listing, or specify fields, or set a deadline. What it requires is a description sufficient to let the other side assess the claim — a functional standard, not a format.
That flexibility is deliberate, and it is why practice diverged so widely. Categorical logging, metadata-only logging, and full document-by-document logs can all satisfy the rule depending on the case.
What changed on December 1, 2025
The amendments do not alter Rule 26(b)(5)(A). They change when the parties have to talk about it.
Rule 16(b)(3)(B)(iv) — the scheduling order may:
include the timing and method for complying with Rule 26(b)(5)(A) and any agreements the parties reach for asserting claims of privilege or of protection as trial-preparation material after information is produced, including agreements reached under Federal Rule of Evidence 502.
And Rule 26(f)(3)(D) — the discovery plan must state the parties' views and proposals on:
any issues about claims of privilege or of protection as trial-preparation materials, including the timing and method for complying with Rule 26(b)(5)(A) and — if the parties agree on a procedure to assert these claims after production — whether to ask the court to include their agreement in an order under Federal Rule of Evidence 502.
The words "timing and method" are the addition. The parties must address them in the Rule 26(f) report, and the court may fix them in the scheduling order.
Why this matters more than it sounds
Three consequences follow from moving the question to the outset.
The format becomes a scheduling issue rather than a motion. A categorical log, a metadata log, or an agreed set of fields can be settled at the Rule 26(f) conference — where nobody yet knows which side it will favour — instead of after a production, when positions have hardened.
Timing gets fixed. Rule 26(b)(5)(A) sets no deadline. Where the scheduling order fixes one, a late log is a violation of a court order, with Rule 16(f) and Rule 37(b) consequences attached.
And rolling productions become manageable. Large ESI productions go out in tranches; the amendments let the parties agree that logs follow on a stated schedule rather than arriving in one volume at the end.
For an MDL, where privilege review is often the single largest discovery cost, this is the change with the most money attached. New Rule 16.1, effective the same day, directs the parties' initial MDL report to address any matter in Rule 16 — which now includes the privilege-log method. The guide on Rule 16.1 covers that report.
Clawback: Rule 26(b)(5)(B)
The second half of the privilege framework governs what happens when protected material goes out by mistake.
If information produced in discovery is subject to a claim of privilege or of protection as trial-preparation material, the party making the claim may notify any party that received the information of the claim and the basis for it. After being notified, a party must:
- promptly return, sequester, or destroy the specified information and any copies it has; - must not use or disclose the information until the claim is resolved; - must take reasonable steps to retrieve the information if the party disclosed it before being notified; and - may promptly present the information to the court under seal for a determination of the claim.
The producing party must preserve the information until the claim is resolved.
Four duties on the receiving party and one on the producing party. Note that the receiving party's obligations are mandatory and immediate — they attach on notification, before any adjudication of whether the claim is good.
And note what the rule does not supply: a deadline for the receiving party to challenge the claim. California's CCP 2031.285(d)(1) gives 30 days; the federal rule leaves the timing to the parties or the court — which is precisely what Rule 16(b)(3)(B)(iv) now invites them to fix, "including agreements reached under Federal Rule of Evidence 502."
Evidence Rule 502(d) is the reason this matters. A court order under that rule can provide that production does not waive privilege in any federal or state proceeding — protection an agreement between the parties alone cannot achieve. Getting a 502(d) order into the scheduling order is the single most valuable thing the amended rules make routine.
What to bring to the Rule 26(f) conference
| Question | Why it belongs at the outset |
|---|---|
| Log format — document-by-document, categorical, or metadata | the most expensive variable in privilege review |
| Fields — author, recipient, date, type, basis | avoids a second pass to add fields later |
| Timing — with production, on a rolling schedule, or after substantial completion | Rule 26(b)(5)(A) sets no deadline |
| Carve-outs — post-complaint communications with counsel | often excluded by agreement, saving substantial cost |
| Clawback procedure — notice, response, challenge period | the federal rule supplies no deadline |
| A Rule 502(d) order | only a court order reaches other proceedings |
| Who resolves disputes — the judge, a magistrate judge, or a special master | Rule 16.1(b)(3)(F) asks this expressly in MDLs |
Protective orders, and the conferral requirement
Rule 26(c)(1): a party or any person from whom discovery is sought may move for a protective order in the court where the action is pending — "or as an alternative on matters relating to a deposition, in the court for the district where the deposition will be taken."
The motion must include a certification that the movant has in good faith conferred or attempted to confer with other affected parties in an effort to resolve the dispute without court action.
The court may, for good cause, issue an order protecting a party or person "from annoyance, embarrassment, oppression, or undue burden or expense," including by forbidding the disclosure or discovery, specifying terms including the allocation of expenses, or prescribing a different discovery method.
Cost allocation under Rule 26(c)(1)(B) is worth remembering in this context: where a log demand is disproportionate, shifting its cost is an available remedy short of refusing it.
How the federal approach compares
| Federal | California | Washington | |
|---|---|---|---|
| Log required by rule | no — a sufficient description is | codified — CCP 2031.240(c) | required in the objection — CR 26(g) |
| Format prescribed | no | no | no |
| Timing prescribed | no — but now fixed by the scheduling order | no | no |
| Addressed at the planning conference | yes, since Dec 1 2025 | no | no |
| Clawback procedure | Rule 26(b)(5)(B) | CCP 2031.285 | not addressed |
| Deadline to challenge a clawback | none in the rule | 30 days | — |
| Non-waiver beyond the case | Evidence Rule 502(d) order | — | — |
Washington's CR 26(g) takes the strictest line on the objection itself: a privilege objection must "identify all matters the objecting party contends are subject to the privilege including sufficient information to allow other parties to evaluate the claim of privilege without disclosing protected content" — and general objections are barred outright. The guide on Washington sanctions and motions to compel covers it.
A short checklist
- Put privilege on the Rule 26(f) agenda. The amended rule requires the discovery plan to address the timing and method of Rule 26(b)(5)(A) compliance.
- Propose a format that fits the case. Categorical or metadata logging may satisfy the rule, which asks only for enough to let the other side assess the claim.
- Fix a deadline. The rule has none; the scheduling order can supply one, and that converts a late log into an order violation.
- Agree carve-outs early — post-complaint communications with counsel are the usual one, and the savings are large.
- Ask for a Rule 502(d) order, not merely a party agreement. Only the order reaches other proceedings.
- Settle the clawback timetable, including how long the receiving party has to challenge a claim. The federal rule is silent.
- If you receive a clawback notice, act immediately — return, sequester or destroy; stop using it; retrieve what you disclosed. Those duties attach on notice, not on a ruling.
- If a log demand is disproportionate, consider Rule 26(c)(1)(B) cost allocation rather than a flat refusal.
Where these rules live
- FRCP 16 — Pretrial conferences; scheduling; management
- FRCP 16.1 — Multidistrict litigation
- FRCP 26 — Duty to disclose; general provisions governing discovery
- FRCP 33 — Interrogatories to parties
- FRCP 34 — Producing documents, electronically stored information, and tangible things
- FRCP 37 — Failure to make disclosures or to cooperate in discovery; sanctions
- FRCP 45 — Subpoena
Rules 16 and 26 were amended effective December 1, 2025. Federal Rule of Evidence 502, which governs waiver and non-waiver orders, is not reproduced on this site. This page explains what the rules say. It isn't legal advice.