Rule 502 and Inadvertent Production: Waiver, Clawback Agreements, and Why Every Case Needs a 502(d) Order

It is a quarter past four on a Thursday. Your e-discovery vendor has just sent a polite email with a subject line that reads "question re prod vol 3." A paralegal on the other side of the case has flagged a document, the vendor says, and could you take a look? You open it. Bates number 41,207 is a five-page memo from your client's general counsel to the chief executive, candidly assessing the very contract your client is now suing on. Your name for this document, until about ninety seconds ago, was "the one thing they must never see."

Whether that memo can be recovered depends on a rule most lawyers meet only in a crisis, and on a one-page court order that takes about ten minutes to draft and had to be entered months ago. If it was, this is an annoying afternoon. If it was not, your client's fate now rests on a judge's after-the-fact opinion of how carefully somebody ran a privilege search, and the record the judge will read has not been written yet.

The short answer

Federal Rule of Evidence 502 does four things that matter in practice.

• It caps the damage. A disclosure in a federal proceeding waives protection for undisclosed material only if the waiver was intentional, the material concerns the same subject, and the two ought in fairness to be considered together. An honest mistake no longer opens the whole file.
• It forgives some mistakes. Under Rule 502(b), an inadvertent disclosure is not a waiver if the holder took reasonable steps to prevent it and promptly took reasonable steps to fix it. The producing party generally carries that burden, and courts have found waiver where nobody tested the search that was supposed to catch privileged documents.
• It lets a judge take the question off the table. Under Rule 502(d), a federal court can order that disclosure connected with the case is not a waiver, in that case or any other federal or state proceeding. The Advisory Committee's explanatory note says such an order may apply regardless of the care the producing party took.
• It limits private deals. Under Rule 502(e), a clawback agreement binds only the parties who signed it unless a court order incorporates it.

Get the order at the start of every case that will involve a meaningful document exchange. Word it to say that the disclosure is protected whether inadvertent or otherwise and regardless of care, and that Rule 502(b) does not apply. Then keep doing a sensible privilege review anyway, because the order does not stop your adversary from reading the document before you claw it back, and courts have found waiver when lawyers sat through a deposition without properly objecting to its use.

How a mistake could once cost everything

The attorney-client privilege protects confidential communications made to get legal advice. The Supreme Court's justification is instrumental: lawyers can give sound advice only if clients tell them the truth, so the law gives up some evidence to get better legal compliance. Upjohn Co. v. United States, 449 U.S. 383 (1981) extended that reasoning across the corporation, and warned that "[a]n uncertain privilege, or one which purports to be certain but results in widely varying applications by the courts, is little better than no privilege at all." The work-product doctrine, which protects material prepared in anticipation of litigation, has a different root. It protects the adversary system itself. "Not even the most liberal of discovery theories can justify unwarranted inquiries into the files and the mental impressions of an attorney," the Court wrote in Hickman v. Taylor, 329 U.S. 495 (1947). For a business-oriented treatment of what is covered in the first place, see Attorney-Client Privilege and Work Product for Businesses: Upjohn, In-House Counsel, and the Common Interest.

Privilege depends on secrecy, so disclosure has always threatened it. The question that divided courts for decades was what to do when disclosure was an accident. Three camps formed.

Strict waiver. Once the secret is out, it is out. The high-water mark is In re Sealed Case, 877 F.2d 976 (D.C. Cir. 1989), where a company's chief accounting officer handed a memo to a Defense Contract Audit Agency auditor. The company called it a bureaucratic error. The D.C. Circuit was unmoved: a client wishing to preserve the privilege "must treat the confidentiality of attorney-client communications like jewels," indeed like "crown jewels," and the court extended the waiver to other communications on the same subject. It conceded that this could cause grave injury to the organization, and added, "But that is as it should be."

Lenient. Waiver requires a knowing, intentional relinquishment. A lawyer's slip cannot give up a right that belongs to the client.

Balancing. Most courts looked at the circumstances. Lois Sportswear, U.S.A., Inc. v. Levi Strauss & Co., 104 F.R.D. 103 (S.D.N.Y. 1985) asked about the precautions taken, the time to rectify, the scope of discovery, the extent of disclosure, and an overarching question of fairness; there, 22 documents out of some 16,000 pages inspected tipped "[b]y a narrow margin" toward no waiver. Hartford Fire Insurance Co. v. Garvey, 109 F.R.D. 323 (N.D. Cal. 1985) used a similar list, and the Fifth Circuit approved analysis under it in Alldread v. City of Grenada, 988 F.2d 1425 (5th Cir. 1993), a case about audio tapes of a city's executive sessions.

Paper-era rules met terabytes. By the time Magistrate Judge Grimm wrote Hopson v. Mayor of Baltimore, 232 F.R.D. 228 (D. Md. 2005), the problem was the cost of being careful. Insisting in every case on "old world" record-by-record review, on pain of subject matter waiver, "would impose upon parties costs of production that bear no proportionality to what is at stake in the litigation." Parties were already signing what Zubulake v. UBS Warburg LLC, 216 F.R.D. 280 (S.D.N.Y. 2003) called "claw-back" agreements, but nobody knew whether such a deal would bind a stranger to the contract. A party could sign a clawback, produce a document, get it back, and then watch a different plaintiff in a different state argue the privilege had evaporated. Hopson's advice was to assume that full review was still required unless a party could show with particularity that it was unduly burdensome.

Only Congress could fix that. Under the Rules Enabling Act, 28 U.S.C. § 2074(b), a rule creating, abolishing, or modifying an evidentiary privilege has no force unless Congress approves it. So Rule 502 was enacted by statute, Pub. L. 110-322, signed on September 19, 2008. It applies to proceedings commenced after that date and, as far as just and practicable, to those then pending. The text has been restyled once, in 2011, with no intended change in result. The rule has two stated purposes in the Advisory Committee's explanatory note: to resolve disputes about inadvertent disclosure and subject matter waiver, and to respond to complaints that the cost of protecting against waiver had become prohibitive.

What each subdivision does

Four limits are easy to miss.

Rule 502 does not decide whether a document was privileged to begin with. That remains a question of common law or, where state law supplies the rule of decision, state law under Fed. R. Evid. 501. In Mt. Hawley Insurance Co. v. Felman Production, Inc., 271 F.R.D. 125 (S.D. W. Va. 2010), the court used West Virginia law for privilege and Rule 502 for waiver. A court will look at privilege first, because a waiver fight over a non-privileged document is a waste of everyone's morning.

It does not cover other privileges. The note says waiver for other evidentiary privileges remains a federal common law question, and that the rule does not touch the Fifth Amendment. The deliberative process and bank examination privileges at issue in Fairholme Funds, Inc. v. United States, 134 Fed. Cl. 680 (2017) are outside its definitions, whatever the parties' order may add.

It governs waiver by disclosure and nothing else. The note cites Nguyen v. Excel Corp., 197 F.3d 200 (5th Cir. 1999) to make the point that relying on advice of counsel still waives. The familiar rule that "[t]he privilege which protects attorney-client communications may not be used both as a sword and a shield," from Chevron Corp. v. Pennzoil Co., 974 F.2d 1156 (9th Cir. 1992), lives on alongside it. In re Kellogg Brown & Root, Inc., 796 F.3d 137 (D.C. Cir. 2015) shows how much those neighboring doctrines can do on their own, granting mandamus against orders that had found waiver through Fed. R. Evid. 612 and at-issue theories after a corporate witness reviewed protected documents to prepare. For the witness-preparation side of that problem, see Preparing a Witness for Deposition: What Is Proper, What Is Coaching, and What the Other Side Can Discover.

And it applies only to the settings it names. A disclosure in a business negotiation, to a consultant, or to a state agency is not "in a federal proceeding or to a federal office or agency." In Wi-LAN, Inc. v. Kilpatrick Townsend & Stockton LLP, 684 F.3d 1364 (Fed. Cir. 2012), a law firm's opinion letter was shared during settlement talks; the magistrate judge rejected the firm's Rule 502(a) argument and the Federal Circuit, applying Ninth Circuit law, predicted that fairness would limit the scope anyway, noting "the heavy weight of current authority." The First Circuit reached a similar place for out-of-court disclosures in In re Keeper of the Records (XYZ Corp.), 348 F.3d 16 (1st Cir. 2003). In Talismanic Properties, LLC v. Tipp City, 309 F. Supp. 3d 488 (S.D. Ohio 2017), a city's emails went out in response to Ohio public records requests. The court noted that Rule 502(b) arguably did not apply, ran the pre-rule factors in any event, and found waiver as to four emails, pointing to a keyword search of more than two million archived emails with no evidence of anyone reviewing the hits for privilege.

Subject matter waiver after Rule 502(a)

The rule's most important work may be the quietest. Under Rule 502(a), a waiver reaches undisclosed material only if three things are all true: the waiver was intentional, the disclosed and undisclosed material concern the same subject, and they "ought in fairness to be considered together." The language is borrowed from the rule of completeness in Fed. R. Evid. 106, and the note explains why: a party that makes a selective, misleading presentation opens itself to a fuller one.

The note then states the point that should calm anyone staring at document 41,207: "It follows that an inadvertent disclosure of protected information can never result in a subject matter waiver." It expressly rejects the result in Sealed Case. So the realistic worst case for a mistaken production, even a careless one, is loss of the documents actually produced. irth Solutions, LLC v. Windstream Communications LLC, No. 2:16-cv-219, 2017 WL 3276021 (S.D. Ohio Aug. 2, 2017) shows this holding working at the bottom of a very bad day: the producing party lost 43 documents, and the waiver stopped there.

Intentional use is different. If a company puts its lawyer's favorable memo into a summary judgment record and withholds the unfavorable follow-up, that is the selective presentation the rule describes. Rule 502(a) also keeps courts from treating every intentional disclosure as a floodgate: the note describes subject matter waiver as reserved for "unusual situations."

Why you cannot pick your audience: selective waiver

Companies under investigation often want to hand privileged material to the government and keep it from private plaintiffs. The theory is called selective waiver, and Rule 502 does not adopt it. The Ninth Circuit's In re Pacific Pictures Corp., 679 F.3d 1121 (9th Cir. 2012) rejected the doctrine, noting that only the Eighth Circuit's Diversified Industries, Inc. v. Meredith, 572 F.2d 596 (8th Cir. 1978) (en banc) had accepted it, and that every other circuit to consider the issue since had said no, including in In re Qwest Communications International Inc., 450 F.3d 1179 (10th Cir. 2006), In re Columbia/HCA Healthcare Corp. Billing Practices Litigation, 293 F.3d 289 (6th Cir. 2002), In re Steinhardt Partners, L.P., 9 F.3d 230 (2d Cir. 1993), Westinghouse Electric Corp. v. Republic of the Philippines, 951 F.2d 1414 (3d Cir. 1991), and Permian Corp. v. United States, 665 F.2d 1214 (D.C. Cir. 1981). Pacific Pictures also quotes the Statement of Congressional Intent, which says Rule 502 "does not provide a basis for a court to enable parties to agree to a selective waiver of the privilege, such as to a federal agency conducting an investigation." A confidentiality agreement with the agency did not change the result.

Potomac Electric Power Co. v. United States, 107 Fed. Cl. 725 (2012) applies the same logic to Rule 502(d). The taxpayer wanted an order saying that even intentional disclosures in the case, such as those made for an advice-of-counsel defense, would not waive anywhere else. The court refused: the rule does not override the "all purposes, all forums" principle for intentional waiver. If a government inquiry is your setting, Responding to a Government Subpoena or Civil Investigative Demand: A Practical Guide picks up the production mechanics. Work product has a more forgiving test, because the doctrine guards against adversaries rather than the world. Disclosure waives it only if made to an adversary or if it "has substantially increased the opportunities for potential adversaries to obtain the information," in the words of United States v. Sanmina Corp., 968 F.3d 1107 (9th Cir. 2020); see also United States v. Deloitte LLP, 610 F.3d 129 (D.C. Cir. 2010). That difference matters when your mistake involved a consultant rather than an opponent.

Rule 502(b): the three elements, read through the cases

Rule 502(b) is the default that applies when nobody obtained an order, or when the order does not reach the dispute. Each of its three elements has become its own small body of law.

Element one: was the disclosure inadvertent?

This should be, and in most courts is, the easy part. Coburn Group, LLC v. Whitecap Advisors LLC, 640 F. Supp. 2d 1032 (N.D. Ill. 2009) reads the rule's structure to mean that the inquiry essentially asks "whether the party intended a privileged or work-product protected document to be produced or whether the production was a mistake." If the reasonableness of the review were part of inadvertence, subparts (b)(2) and (b)(3) would do no work.

Datel Holdings Ltd. v. Microsoft Corp., No. C-09-05535 EDL, 2011 WL 866993 (N.D. Cal. Mar. 11, 2011) rejects a clever attempt to narrow the concept. Microsoft's review software had truncated an email chain about hacked Xbox memory units, removing the top of the thread where in-house counsel's request appeared. Reviewers looking at the shortened chain saw no privilege. At a deposition, defending counsel looked at the exhibit and said "I don't think there's a privilege assertion or redaction." A few hours later, having obtained the full versions, he clawed them back on the record. Datel argued that Rule 502 protects only unintended disclosure, and that Microsoft meant to produce what it produced. The court called the inquiry a simple one, whether the disclosure occurred by mistake, and said the requirement "was not designed to turn on fine distinctions based on the nature of the mistake."

Amobi v. District of Columbia Department of Corrections, 262 F.R.D. 45 (D.D.C. 2009) dispatched the argument that a lawyer's disclosure can never be a mistake: "Lawyers make inadvertent mistakes; it is judges who never make mistakes," and a contrary rule "would gut that rule like a fish." irth Solutions treats the question as a binary choice between intentional and inadvertent, so that even negligent production counts as inadvertent and the fight moves to element two. It also assumed inadvertence only arguendo, because the associate who did the review and the staff member who made the second error never testified. That detail is worth remembering when you choose your declarants.

There is one way to lose here that happens with some regularity. If someone decided to produce the document after thinking about it, the disclosure was deliberate, even if the decision was wrong. In Certain Underwriters at Lloyd's, London v. National Railroad Passenger Corp., 218 F. Supp. 3d 197 (E.D.N.Y. 2016), Amtrak had withdrawn its privilege claim over one document after what it called a detailed review of each challenged item, then tried to claw it back after it was used at a deposition. The court said this "was no mere inadvertence at work." Second thoughts are not mistakes, though the opinions draw some fine lines. Datel discusses Silverstein v. Federal Bureau of Prisons, 2009 WL 4949959 (D. Colo. Dec. 14, 2009), where a party knowingly produced a document on a mistaken view that it was not privileged, then failed to act when told otherwise.

Element two: reasonable steps to prevent disclosure

Almost all the money is here. The note says the rule "does not explicitly codify" the old multifactor test, because it is "really a set of non-determinative guidelines that vary from case to case." It adds that the number of documents and time constraints bear on reasonableness, that a party using "advanced analytical software applications and linguistic tools" may be found to have acted reasonably, and that efficient records management before litigation may be relevant.

Courts fill in the rest using five factors that vary a little in wording: the reasonableness of precautions, the number of inadvertent disclosures, the extent of disclosure, delay in rectifying, and overriding interests of justice. Those factors decided the cases below, and comparing them teaches more than the factors do.

Read that way, the table says something the factors obscure. Volume alone does not excuse a mistake, and a small number of errors does not condemn it. Courts want a process with a human in charge, a reason behind each choice, and a test of whether it worked.

Victor Stanley: the case that made sampling mandatory in spirit

Victor Stanley, Inc. v. Creative Pipe, Inc., 250 F.R.D. 251 (D. Md. 2008) was decided under the pre-rule balancing test a few months before enactment, and it still sets the agenda. Defendants' lawyers had asked for a clawback order, citing Judge Grimm's own Hopson opinion. When the discovery period was extended by four months, they told the court they could review document by document and dropped the request. Then the review ran short. A forensic expert applied about seventy keywords picked by the client and two lawyers to the text-searchable files, and a lawyer and the client looked only at the title pages of the rest. The plaintiff's own lawyers noticed the privileged documents and segregated them.

Judge Grimm's opinion is a short course in information retrieval. Defendants did not say what the keywords were, why they were chosen, who was qualified to choose them, whether they used proximity operators, or whether anyone analyzed the results. "[T]he only prudent way to test the reliability of the keyword search," he wrote, "is to perform some appropriate sampling of the documents determined to be privileged and those determined not to be." Having failed to explain themselves, defendants lost on their burden. The most painful passage is about the abandoned order: "Had they not voluntarily abandoned their request for a court-approved non-waiver agreement, they would have been protected from waiver." And on the plea of unfairness: "The only 'injustice' in this matter is that done by Defendants to themselves."

Rhoads: the hindsight objection

Two months after Rule 502 became law, Judge Baylson wrote Rhoads Industries, Inc. v. Building Materials Corp. of America, 254 F.R.D. 216 (E.D. Pa. 2008), an early and close application of the new rule to a large ESI production. Rhoads had bought software, tested a trial version, and then searched only the address lines of emails for its own domain combined with one of three other names. It did not search for the names of all its lawyers, leaving out two outside counsel, and it left out "privileged" and "confidential" because every company email footer contained those words. That last point is a useful reminder of how footers can blind a search term. The court found that the first four factors favored the defendants and the fifth strongly favored Rhoads. Loss of the privilege in hard-fought litigation, the court wrote, is a severe sanction, while the defendants had no right or expectation to see these documents in the first place. It also put the burden on the party claiming waiver.

Rhoads is remembered for its disagreement with Victor Stanley: Judge Grimm's analysis, it said, reflected too much "application of hindsight, which should not carry much weight, if any, because no matter what methods an attorney employed, an after-the-fact critique can always conclude that a better job could have been done." Datel landed in the same place: "perfection or anything close based on the clairvoyance of hindsight cannot be the standard." Coburn agrees that a review cannot be deemed unreasonable merely because a document slipped through; if that were the standard, "Rule 502(b) would have no purpose."

But don't over-read the mercy in Rhoads. About 120 privileged documents that Rhoads failed to log until November were ordered produced, with no Rule 502 analysis at all, because the log requirement in Fed. R. Civ. P. 26(b)(5)(A) is mandatory. The judge also refused to accept thrift as an excuse: a desire to save the client money "cannot be an after-the-fact excuse for a failed screening of privileged documents."

Mt. Hawley: the case that should keep vendors and their clients awake

Mt. Hawley has the best facts in this field and the most instructive failure. An insurance coverage plaintiff produced roughly a million pages, most of it in one large delivery, more than 30 percent of them irrelevant, every page stamped confidential. Its counsel had actually done a lot of what you would hope: hired a vendor, forensically imaged data, tested terms, and looked with human eyes at flagged documents. Then the review tool built an incomplete index for one of thirteen database files, for reasons the manufacturer could not explain. An email thread slipped out in which a company manager discussed the possibility of back-dated sales contracts with outside counsel.

The email surfaced when the defense attached it to a motion to amend. The producing party demanded it back four days later, satisfying the recall procedure in the parties' stipulation, which said compliance would satisfy Rule 502(b)(3). It lost anyway, because the stipulation said nothing about (b)(2). The court pointed out that nobody had sampled, that nobody had run a simple keyword search for copies of the email once it surfaced, and that the producing party's law firm "was counsel in the Victor Stanley case." The opinion observes that the May 14 email had become "a bell which cannot be unrung." Waiver of the email then fed the next step: because it had not been adjudicated privileged, the court considered it under United States v. Zolin, 491 U.S. 554 (1989) and ordered in camera review for the crime-fraud exception.

Two lessons sit side by side here. Software failure excused Microsoft in Datel and did not excuse the plaintiff in Mt. Hawley, and the difference was validation: Microsoft's layered attorney review had actually caught the full versions of the same thread, while the Mt. Hawley plaintiff had no sampling step that could have caught the bad index. And a stipulation does exactly what it says.

Who bears the burden?

Most courts put it on the holder. Williams v. District of Columbia, 806 F. Supp. 2d 44 (D.D.C. 2011) is emphatic, and adds a sentence every declarant should read: "The general statement that a privilege review was performed, without any supporting details, is completely uninformative." In re Testosterone Replacement Therapy Products Liability Litigation, 301 F. Supp. 3d 917 (N.D. Ill. 2018) and Board of Trustees v. Palladium Equity Partners, LLC, 722 F. Supp. 2d 845 (E.D. Mich. 2010) likewise place the burden on the producing party. Rhoads is the outlier in assigning it to the party claiming waiver. Plan on carrying it. Eden Isle Marina, Inc. v. United States, 89 Fed. Cl. 480 (2009) and D'Andrea Brothers LLC v. United States, No. 08-286C (Fed. Cl. June 4, 2010) show the Court of Federal Claims running the same inquiry for the government, with different results on different records.

Element three: promptly took reasonable steps to rectify

The clock starts when you learn of the problem. Coburn reasons from the note's statement that the rule does not require post-production review: the relevant time is how long the producing party took to act after it found out, not how long the document sat in the other side's hands. A four-month gap between production and discovery did not hurt Whitecap, whose lawyer objected on the spot, asked for return the next day, and followed up in writing.

But the note also requires a party to "follow up on any obvious indications" of a mistake. If the other side asks a question about a document that should not exist, or you notice one privileged email on an exhibit list, you have an indication. In Mt. Hawley, failing to look for other copies of the email counted against the producing party. Victor Stanley went further and counted the week before the plaintiff flagged the documents, a harder position to square with the note's language, in a case decided before the rule took effect.

What counts as reasonable after discovery? Written notice identifying the documents by Bates number, stating the basis, and following Rule 26(b)(5)(B) is the floor. Williams holds it may not be the ceiling. There, the District sent notice of the error, and the court said compliance with the civil rule will sometimes count as reasonable rectification but did not in that case. Rhoads shows delay in practice: three weeks to serve a letter and a log, during which the receiving side had to cross-reference every document, weighed against the producer. Delay in following through also matters. Courts differ on how quickly you must move for a ruling after a refusal, and Coburn excused five weeks only because the other side had agreed in writing to quarantine the documents and not to argue delay.

Worked example: Marlowe Freight

Suppose Marlowe Freight, a regional trucking company, sues a software vendor over a failed dispatch system. There is no Rule 502(d) order. Marlowe's lawyers collect 300,000 emails, cull to 60,000 with search terms, and run a privilege screen consisting of the names of outside counsel, the general counsel, and the word "privileged." A contract attorney team reviews the hits and logs 4,100 documents. The other 55,900 go out.

Three weeks later, the vendor's lawyer emails to say that document 41,207 "looks like it may be privileged, FYI." It is the general counsel's memo. It was missed because it was circulated by the chief executive's assistant, with counsel in the body and not the address line, and because the word "privileged" was not used.

Marlowe's team, on the same afternoon, sends a Rule 26(b)(5)(B) notice. It then runs the general counsel's name across the body text of the production and finds 23 more documents, and sends a second notice the next morning. It serves an updated log within the week. How does this go?

• Inadvertent? Yes, in nearly every court.
• Reasonable prevention? Contestable. Marlowe has real facts: a screen, attorney reviewers, a log. But it screened on address lines for at least some of the population, and it did not sample what it was about to produce. That is the Rhoads and Victor Stanley pattern. A test sample of 1,500 documents from the non-privileged pile, reviewed by a senior lawyer before production, could have caught the assistant-forwarding problem for a day's work. The court will notice.
• Prompt rectification? Strong. Same day, then a sweep. Note that the sweep itself is what the note's "obvious indications" language asks for.
• Balance? If the court follows Rhoads, Marlowe likely keeps the privilege. If it follows Victor Stanley and Mt. Hawley, it may not. Twenty-four documents out of 56,000 helps. The memo goes to the heart of the case, which cuts both ways: serious prejudice to Marlowe if lost, and an adversary who has already read it.

Now imagine the same facts with a one-page Rule 502(d) order that disclaims Rule 502(b). The analysis ends at the first sentence of the notice. Marlowe's only remaining fight is whether the memo is actually privileged.

Rule 502(d): the cheapest insurance in litigation

The text is one sentence. A federal court "may order that the privilege or protection is not waived by disclosure connected with the litigation pending before the court," and in that event "the disclosure is also not a waiver in any other federal or state proceeding." The note says what the sentence means: "the court order may provide for return of documents without waiver irrespective of the care taken by the disclosing party," and the rule "contemplates enforcement of 'claw-back' and 'quick peek' arrangements as a way to avoid the excessive costs of pre-production review."

Three features make it special.

It binds strangers. Without Rule 502(d), the plaintiff in the next case could argue waiver, and Rule 502(e) says your contract does not bind them. With it, a court order controls in other federal and state proceedings. Rule 502(f) closes the loop for state courts, and the statement of congressional intent says the rule supports entry on motion or on the court's own initiative.

It does not require a fight about care. The inquiry into reviewers' qualifications and keyword selection, the most expensive litigation-within-litigation in this field, can be avoided altogether. Courts routinely enter these orders on stipulation; see the short order in Wilbur-Ellis Co. v. Jens, No. 4:23-cv-04104 (D.S.D. Apr. 7, 2025). A nonparty can get the same protection, as the proposed supplemental third-party stipulated order in City of Sterling Heights Police & Fire Retirement System v. Reckitt Benckiser Group PLC, No. 1:20-cv-10041 (S.D.N.Y. Sept. 16, 2022) illustrates. Criminal cases use it too; the filter protocol reproduced in United States v. Fluitt, 99 F.4th 753 (5th Cir. 2024) recites Rule 502(d).

It does not need the other side's consent. The note says party agreement should not be a condition of enforceability, and Rajala v. McGuire Woods, LLP, 2010 WL 2949582 (D. Kan. July 22, 2010) is the standard citation. The trustee objected that a clawback would make him do the firm's privilege review and would deny him any chance to prove carelessness. Magistrate Judge Waxse located the authority in Rule 26(c)(1), found good cause on the volume of ESI and the risk to a large firm's other clients, and answered the objection directly: "The goal is not to encourage disputes regarding waiver and inadvertent production, but to prevent such disputes from arising in the first place." He kept a safety valve. If the firm abused the provision with a document dump and made no effort at all, relief remained available. Not every court reads the rule this way. Check your own district's practice before you rely on entry over objection.

Courts do retain discretion. United States v. Captive Alternatives, LLC, No. 8:22-cv-00406 (M.D. Fla. Aug. 29, 2023) quotes another court's remark that "[c]lawback orders are staples of modern complex commercial litigation," acknowledges that a court may enter one over objection, then refuses in an IRS summons enforcement proceeding, which is summary in nature and is not civil discovery. The court distinguished cases where the IRS had agreed to quick-peek orders. Anyone responding to an agency should not assume the order is available on request.

The scheduling rules now prompt everyone to do this. Rule 26(f)(3)(D) requires the discovery plan to address privilege claims, including the timing and method of complying with Rule 26(b)(5)(A) and "whether to ask the court to include their agreement in an order under Federal Rule of Evidence 502." Rule 16(b)(3)(B)(iv) lets the scheduling order include it. The 2025 amendments added the timing and method language, and the committee note warns that a privilege log near the close of discovery "can create serious problems" and suggests that "rolling" production may help. For the wider picture, see Negotiating an ESI Protocol and Managing E-Discovery Costs, and for the planning conference, Rule 26 Initial Disclosures and Discovery Planning: A Practical Checklist.

The open split: what does your order need to say?

The ten-minute order hides a trap. Courts disagree about whether a generic clawback displaces Rule 502(b). irth Solutions sorts the cases into three approaches, and it is the clearest map available.

1. The order or agreement always controls. Among the cases it cites are Rajala v. McGuire Woods, LLP, 2013 WL 50200 (D. Kan. Jan. 3, 2013), Tadayon v. Greyhound Lines, Inc., 2012 WL 2048257 (D.D.C. June 6, 2012), and BNP Paribas Mortgage Corp. v. Bank of America, N.A., 2013 WL 2322678 (S.D.N.Y. May 21, 2013). In re Testosterone falls in the same camp. Judge Kennelly held that an order saying it "is, and shall be construed as, an Order under Rule 502(d)" governed instead of Rule 502(b), rejecting the argument that this let parties act negligently, and rejecting a fairness argument even though the documents were said to be damaging.
2. It controls unless the producing party was completely reckless. Courts in the Second Circuit have largely taken this route, as Irth describes it, in cases such as United States v. Wells Fargo Bank, N.A., 2015 WL 5051679 (S.D.N.Y. Aug. 26, 2015).
3. It controls only to the extent it gives concrete directives. Maxtena, Inc. v. Marks, 289 F.R.D. 427 (D. Md. 2012) says the order must address what counts as inadvertence, what precautions are required, and what post-production steps must be taken; otherwise Rule 502(b) "will be used to fill in the gaps." Mt. Hawley is the root of this approach.

Irth found waiver under both the second and the third approaches without choosing between them. The agreement was a casual email between counsel, which said "a formal court order under Fed. R. Evid. 502(d) was not necessary based on the scale of the case" and that inadvertent production would not waive. The review missed documents bearing a signature block reading "Counsel to Director of Government Contract Compliance" and the line "Michelle, any guidance from legal . . . ?" Six weeks later, in the middle of the dispute, the same documents went out again. Calling the production completely reckless under the second approach, and treating the email as too cursory to displace Rule 502(b) under the third, the court held the 43 documents lost. Judge Graham overruled objections and then certified the question under 28 U.S.C. § 1292(b): what standard determines whether a clawback agreement displaces Rule 502(b)? The Sixth Circuit's docket (No. 18-305) reflects that permission to appeal was granted in 2018, but our research turned up no merits decision, and the question remains unresolved at the appellate level.

Northrop Grumman Systems Corp. v. United States, 120 Fed. Cl. 436 (2015) adds a warning about drafting within the order. The government clawed back at least 1,500 of millions of documents under a protective order, and then conceded it could not rely on the clawback if its review was unreasonable. The court noted that another paragraph of the order required each party to "review its documents for privileged information prior to production," which suggested reasonable effort. A sentence meant as good housekeeping became a condition. Potomac Electric is less generous to party autonomy, refusing a ten-day clawback that would have displaced the reasonableness standard, although the note and later decisions such as Testosterone cut the other way.

How do you draft through the split? Use the rule's own text and leave no gaps.

• Say the order is entered under Rule 502(d).
• Say production is protected "whether inadvertent or otherwise" and regardless of the care taken. Edgar v. Teva Pharmaceuticals Industries, Ltd., No. 2:22-cv-02501 (D. Kan. Aug. 5, 2024) adopted that language precisely because it "will avoid disputes over whether the parties' disclosure was inadvertent," and left any abuse for motion practice. Leise v. United States, No. 8:22-cv-00142 (D. Neb. Mar. 25, 2024) shows a similar order in operation.
• Say that Rule 502(b) does not apply. Irth quotes Great-West Life & Annuity Insurance Co. v. American Economy Insurance Co., 2013 WL 5332410 (D. Nev. Sept. 23, 2013): "It goes without saying that parties must adequately articulate the desire to supplant analysis under Rule 502(b) in any agreement under Rule 502(d) or (e)."
• Spell out post-notice steps, so a receiving party knows what to do and a court sees "concrete directives" if it wants them.
• Avoid promises about review that could be read as conditions, unless you mean them.

Where the order still fails

Deposition use. This is the most dangerous gap, and the courts are divided. In Amtrak, a broad Rule 502(d) order did not save documents used at a deposition. Counsel "reserve[d] Amtrak's rights" as to one and objected to other things while the witness was asked about the other. The court held that Rules 502(d) and (e) "apply only to waiver in connection with disclosures, and say nothing of waiver by other means," so a failure "to timely and specifically object" could waive. It relied on Wells Fargo and Hologram USA, Inc. v. Pulse Evolution Corp., 2016 WL 3654285 (D. Nev. July 5, 2016). In re Testosterone goes the other way, refusing to treat a seven-day gap after a deposition as a separate waiver because that would be Rule 502(b)(3) analysis under another name. Do not test this. If a privileged document appears in a deposition, object specifically, say it is privileged, instruct the witness under Rule 30(c)(2), and claw it back in writing that day. Checklists for the moment are in Defending a Deposition Checklist: A Practical Checklist and the sibling guide below.

Deliberate moves. Amtrak rejects the idea that an order lets parties "assert and retract claims of privilege at will," calling that reading an "absurd result" that would allow clawbacks through the close of litigation. Pepco rejects protection for intentional waiver as a tactic.

Disclosures outside the case. The order covers disclosure "connected with the litigation pending before the court." The note says subdivision (d) does not allow a court to determine the waiver effect of a separate disclosure of the same information in other proceedings. Pre-suit productions, the earlier government investigation, and the sister case in state court each need their own analysis. Edgar flags exactly this problem: plaintiffs feared a clawback of emails produced intentionally in other litigation, and the court left that for motion practice.

The information itself. An order restores a legal status. It cannot make your adversary forget. They may have read the memo, and it may shape the questions they ask, even if they can never use the document. That is why a careful review still matters for documents that would really hurt.

Rule 502(e): a contract is only a contract

Rule 502(e) says an agreement on the effect of disclosure "is binding only on the parties to the agreement, unless it is incorporated into a court order." It codifies what the courts already held. It has one job and a sharp edge: a clawback in an email or a stipulation can bind the opponent, and it will not bind a nonparty, a regulator, a co-defendant who did not sign, or a plaintiff in the next case. Irth's email is one failure mode. Mt. Hawley's stipulation, which the court noted "was not incorporated into a court order," is another. Getting it entered costs almost nothing. It takes the same page, plus a judge's signature.

State courts and Rule 502(c), (f)

Federal disclosures bind state courts: Rule 502(a), (b), and (d) all speak of waiver "in a federal or state proceeding," and Rule 502(f) overrides the usual limits in Rules 101 and 1101. The reverse is more complex. Under Rule 502(c), a disclosure in a state proceeding that is not subject to a state court order is not a waiver in federal court if it would not be a waiver under Rule 502 or under the law of the state where it occurred. The committee chose whichever law is most protective. A state court order is treated separately, under full faith and credit principles in 28 U.S.C. § 1738.

States have their own approaches, and a state-court producer should check them rather than assume the federal rule. Texas has a snap-back rule in Tex. R. Civ. P. 193.3(d). California's receiving-lawyer standard, discussed below, is more demanding than the Model Rule. Rule 502(f) reaches court-annexed and court-mandated arbitration, and the note says it raises no inference about other arbitrations, so a private arbitration needs its own agreement and, ideally, a tribunal order.

The procedure: Rule 26(b)(5)(B) and Rule 45(e)(2)(B)

Rule 502 decides waiver. Rule 26(b)(5)(B) tells people what to do while waiver is being decided. Added in 2006, it is procedural. The 2006 committee note says it "does not address whether the privilege or protection that is asserted after production was waived by the production." A parallel provision in Rule 45(e)(2)(B) covers subpoena productions.

Once notified, a party:

• must promptly return, sequester, or destroy the specified information and any copies;
• must not use or disclose it until the claim is resolved;
• must take reasonable steps to retrieve it if already disclosed; and
• may promptly present it to the court under seal for a determination.

The producing party must preserve the information until the claim is resolved. The 2006 note says notice should be in writing unless circumstances preclude it, and "as specific as possible."

Three questions have produced useful law.

Does the rule impose any duty before notice? No. Mt. Hawley says it "imposes no duty on a party receiving privileged information to do anything unless and until it is notified of the claim." That does not relieve the lawyer of ethics rules.

Can you keep reading after notice? No, according to EEOC v. George Washington University, No. 17-cv-1978 (D.D.C. Nov. 5, 2020), the most careful treatment. EEOC counsel read the disputed emails after being told privilege was claimed, then put a note on them saying "Do not look at." The agency argued that "sequester" concerns only possession. The magistrate judge held that sequestration must be read with "return" and "destroy," both of which end access, so further review violates the rule. The opinion also expresses disagreement with any suggestion that limiting access to attorneys' eyes alone satisfies it. No sanctions were imposed, because the material had not been used; courts have been reluctant to sanction absent dissemination or use, but the agency was warned. The court ordered the documents returned or destroyed, with redacted copies to be produced. Compare Irth, where the plaintiff's "attorneys' eyes only" sequestration passed muster given the clawback's ambiguous wording.

Does the rule apply to documents obtained outside discovery? Sometimes. Talismanic held that it applied to an email first obtained by public records request once the plaintiffs produced it back in discovery, but vacated a show-cause order because the contrary position was reasonable; the plaintiffs had filed the email on the public docket after notice. GWU applied the rule to emails a charging party gave the agency, relying on the phrase "any party that received the information," and noted courts' inherent power as a backstop. Rule 11 and Inherent-Power Sanctions: The Safe Harbor, Fee Awards, and Attorney Conduct covers that power generally.

The receiving lawyer's duties

The ethics rules and the procedure rule do different things, and the gap between them is where lawyers get into trouble.

ABA Model Rule 4.4(b) requires a lawyer who receives a document or electronically stored information relating to the representation, and who knows or reasonably should know it was inadvertently sent, to promptly notify the sender. That is all it requires. ABA Formal Opinion 05-437, as quoted in Mt. Hawley, says the rule "does not require the receiving lawyer either to refrain from examining the materials or to abide by the instructions of the sending lawyer." Formal Opinion 05-437 withdrew the older and stricter Opinion 92-368, and Formal Opinion 06-440 addresses materials sent deliberately by someone unauthorized.

Whether more is required is left to other law, and other law may require a lot more:

Gomez gives the best one-line advice in the field: "The path to ethical resolution is simple: when in doubt, ask the court."

Not every jurisdiction adopts the Model Rule. Mt. Hawley found no West Virginia notification rule at the time and declined to fault counsel for using a document without first saying so, while still ordering compliance with the procedure once notified. So check the rule in force where you practice, and check the local version of Rule 4.4.

Harleysville Insurance Co. v. Holding Funeral Home, Inc., No. 1:15cv00057 (W.D. Va.), offers a cautionary pair of rulings, often cited for only the first. A magistrate judge found waiver in 2017 when an insurer's investigator reached a claims file through an unprotected file-sharing link. According to published accounts of the order, the district judge reversed that October, finding no waiver because the long random link was not publicly discoverable, but faulted defense counsel for using the file without notice or a ruling, and barred its use. We could not obtain the order's full text, so read it before citing it. Anyone still repeating it for the proposition that cloud links always waive privilege has only read half the case.

TAR, generative AI, and what "reasonable steps" means when machines read first

The rule's note was written in 2007. Its phrase, "advanced analytical software applications and linguistic tools," has aged well, because it describes function rather than a product.

What actually happens in a review

A privilege screen is a classification problem. Every method sorts documents into "probably privileged" and "probably not," and every method has two error rates. Precision measures how much of what it flags is actually privileged; recall measures how much of the actually privileged material it catches. Recall is the one that matters here, because a document the screen misses goes out the door.

Search terms are the oldest classifier. They fail in predictable ways: a lawyer's name is misspelled or appears only as a first name ("Michelle, any guidance from legal"), counsel is on a forward not in the address block (Rhoads), the signature footer swamps every email with the word "confidential" (Rhoads again), or the text has not been extracted from an image at all (Victor Stanley). Technology-assisted review, or TAR, trains a statistical model on human coding decisions and ranks the rest. Courts have approved it for responsiveness; see Da Silva Moore v. Publicis Groupe, 287 F.R.D. 182 (S.D.N.Y. 2012) and Rio Tinto PLC v. Vale S.A., 306 F.R.D. 125 (S.D.N.Y. 2015), and Edgar shows courts still demanding transparency and cooperation when it is used. Privilege, though, turns on context more than topic: who the sender is, why the message was written, whether a third party is on the chain. A statistical model trained on topic can be weak on exactly those questions, which is why many teams use it to prioritize, not to decide.

Failures often live in the plumbing. A processing engine truncated a thread in Datel. A database built an incomplete index in Mt. Hawley. A staff member pulled the wrong folder in Irth, re-producing the withdrawn documents during the waiver fight. Each of these sits downstream of the legal judgment. Good teams test the production set itself, immediately before it leaves, with a final search against the privilege screen and the withheld list, including hash matches for documents coded privileged. A document withheld in one place and produced in another is the embarrassing case described in Thorncreek Apartments III, LLC v. Village of Park Forest, 2011 WL 3489828 (N.D. Ill. Aug. 9, 2011), which Testosterone quotes as involving "a screening procedure that fails to detect confidential documents that are actually listed as privileged."

Testing the process: the elusion sample

The standard validation is an elusion test. Draw a random sample from the set marked "not privileged," have a senior lawyer read it, and count the misses. That is the appropriate sampling Judge Grimm described, and its absence was the main reason for waiver in Mt. Hawley. Victor Stanley also cites In re Seroquel Products Liability Litigation, 244 F.R.D. 650 (M.D. Fla. 2007) on sampling and United States v. O'Keefe, 537 F. Supp. 2d 14 (D.D.C. 2008) on the science of search. The size of a sample depends on the rate of privileged documents in the set and the confidence you want, and a low prevalence of privileged material means a small sample can tell you less than it appears to. Keep a statistician or experienced vendor consultant in the conversation, and document why you stopped where you stopped.

Generative AI as a reviewer

Large language model tools can read an email thread and explain why it looks privileged, which is closer to what a contract attorney does than keyword or statistical ranking. As far as our research shows, no reported decision has yet ruled on whether an LLM-based privilege review satisfies Rule 502(b)(2). Courts will likely apply the same test. So expect these questions:

• Validation. Did a human test recall on a sample of this data, with this prompt and model version, or did someone rely on a vendor's benchmark? A model's general accuracy says nothing about your client's in-house lawyer who signs emails "M."
• Explainability under oath. Victor Stanley faulted failure to explain keywords. An LLM workflow needs a declarant who can describe the prompts, thresholds, and escalation path. Hallucinated rationale is a known risk; Hallucinated Citations, Rule 11, and Generative AI in Legal Filings: What Courts Are Actually Doing shows how courts treat unverified output.
• Lawyer supervision. ABA Formal Opinion 512 (July 29, 2024) ties generative AI use to the existing duties of competence, confidentiality, communication, and supervision. Model Rule 1.6(c) already requires reasonable efforts to prevent inadvertent disclosure.
• Consistency. Run the same document twice. Family and thread treatment must not differ by luck.

There's a second question: whether feeding the document to the tool endangers it. Morgan v. V2X, Inc., No. 25-cv-01991 (D. Colo. Mar. 30, 2026) is an instructive order. A magistrate judge amended a protective order to bar input of confidential information into an AI platform unless the provider is contractually barred from storing or using inputs to train its model and from disclosing them to third parties except where essential to the service, and must allow deletion on request. The court recognized this would for now bar most mainstream low-cost tools. On privilege itself, the same opinion discusses the February 2026 decisions: United States v. Heppner, 2026 WL 436479 (S.D.N.Y. Feb. 17, 2026), which it describes as holding that a represented criminal defendant who used an AI tool on his own initiative could not claim work product, and Warner v. Gilbarco, Inc., 2026 WL 373043 (E.D. Mich. Feb. 10, 2026), which found no waiver of work product by a pro se plaintiff's AI use. Morgan sides with the view that AI use does not automatically waive, reasoning that work product is typically waived by disclosure to an adversary. The law here is moving, and these are early trial-level rulings, but enterprise terms and documented data handling have become part of the reasonable-steps story. For the contract side, see AI Confidentiality Toolkit: Acceptable Use Policies, Vendor Term Reviews, and Incident Playbooks.

The new sequestration problem

Modern platforms make the old rule harder to obey. Rule 26(b)(5)(B) requires sequestering "the specified information and any copies." In a modern review database a document is not one thing. It may also exist as extracted text, a search index entry, a near-duplicate cluster, thread analytics, a machine-written summary, an embedding in a vector store, and a line in somebody's chronology. Nothing we have found squarely decides whether a derived AI summary or embedding is a "copy," but the text says "information," not "file," and the purpose is plain. A receiving party that clicks a "sequester" tag while the AI assistant can still answer questions drawn from the document has a problem. The careful move is to ask the vendor exactly what has to be purged, get it in writing, and make the clawback provision in your order cover derived data. Morgan's deletion requirement points the same way.

Quick peek: tempting, and rarely the right tool

A quick peek lets the requesting party look at a whole population before privilege review, select what it wants, and leave the producer to review only those. The note contemplates it, and Rajala quotes it. It can save real money. For a party with enormous low-risk data and an adversary it trusts, it may be sensible.

It also means your opponent reads everything. A court order can prevent waiver. It cannot prevent learning. The Sedona Conference's Commentary on Protection of Privileged ESI (2016), as quoted in Fairholme, argues that Rule 502(d) does not authorize compelled quick peeks and that compelled disclosure "forces a producing party to ring a bell that cannot be un-rung."

Courts have not all agreed. Fairholme ordered the government to submit to a quick peek over about 1,500 documents withheld under deliberative process and bank examination privileges, stressing that it was not a sanction but a way to finish jurisdictional discovery and spare the court in camera review, and that a protective order and clawback were already in place. Those were not attorney-client documents, and the government had already reviewed them multiple times, so the decision may not travel far. Fairholme described Summerville v. Moran, 2016 WL 233627 (S.D. Ind. Jan. 20, 2016), as ordering one as an alternative to sanctions. Treat a compelled quick peek as possible but rare, and oppose it with facts about harm. Captive Alternatives reports two instances where the IRS agreed to one, in Microsoft and Facebook enforcement proceedings, for documents the taxpayers had already identified as protected.

Worked example: Ostrander Valve

Suppose Ostrander Valve, a mid-size manufacturer, faces a products case with 2 terabytes of old engineering files going back fifteen years. Plaintiff's counsel offers a quick peek: dump the engineering share into a review room, plaintiffs tag what they want, and Ostrander reviews only those for privilege, all under a Rule 502(d) order. The estimate for full review is seven figures. The engineering share has few lawyers on it.

The trade looks good on paper, but ask three questions. What's actually in the share? If a sample shows that lawyers appear only in a handful of folders, carve those out for ordinary review and peek at the rest. Is there trade secret material a plaintiff's expert might see? Then the protective order needs tiers, and Protective Orders, Confidentiality Designations, and Sealing: Secrecy and Its Limits in Federal Court covers those. And what happens to knowledge? Plaintiffs will have seen documents they cannot use. Ostrander decides on a hybrid: search-term and sample-tested culling, screen for lawyer names, a Rule 502(d) order disclaiming Rule 502(b), and no peek. Review cost falls by most of the projected amount, because the order made it rational to run a lighter review on the low-risk population. That's what the order is for. In practice it replaces the peek far more often than it enables one.

Getting a ruling, and getting it reviewed

Most of these fights are decided by a magistrate judge. Objections go to the district judge under Rule 72(a) and 28 U.S.C. § 636(b)(1)(A), on a clearly erroneous or contrary to law standard. The court may review in camera, and fact-heavy hearings are common. Irth held one, and made a point of who failed to show up. Expect the judge to ask for declarations from people with knowledge, not from the lead partner who heard about it later. For how to brief these motions, see Bringing or Opposing a Motion to Compel Discovery: A Practical Guide.

Appeal is harder. Mohawk Industries, Inc. v. Carpenter, 558 U.S. 100 (2009) holds that disclosure orders adverse to the privilege do not qualify for immediate appeal under the collateral order doctrine. It lists what remains: certification under § 1292(b), mandamus in extraordinary cases, and defying the order and appealing a sanction. Mandamus can work. It is how Kellogg Brown & Root won in the D.C. Circuit, and Pacific Pictures also reached the Ninth Circuit by mandamus petition, though it lost. For a practical review of those paths, see Interlocutory Appeals and Mandamus: Getting Appellate Review Before Final Judgment. One effect of this structure is that the law of Rule 502(b) has been made mostly in district courts and magistrate judges' opinions, with few circuit decisions. Pre-rule circuit authority such as Judson Atkinson Candies, Inc. v. Latini-Hohberger Dhimantec, 529 F.3d 371 (7th Cir. 2008) and Gray v. Bicknell, 86 F.3d 1472 (8th Cir. 1996) remains useful background, and trial-level decisions disagree without much chance of correction. A lawyer has to read the local cases.

A party who prevails on privilege also has to remember that the receiving side keeps what it already knew. Rulings may address derivative use, as Coburn did in resolving the deposition testimony, and Harleysville is reported to have barred use of information derived from the file. Ask for that relief expressly.

What to do with all this

If you run a business, ask your litigation counsel one question at the first meeting of any federal case: "Will we have a Rule 502(d) order entered before we produce anything?" Then ask who, by name, is responsible for reviewing what goes out. Those two questions cost nothing and produce a lot of information about your lawyers.

If you are the lawyer, propose the order in the Rule 26(f) conference, with language that disclaims Rule 502(b), and make it mutual so your adversary has no reason to refuse. If they do, move under Rule 26(c) and cite Rajala. For related privilege work in a security incident, see Data Breach Class Actions: Article III Standing, Negligence Claims, and Forensic Report Privilege, where the fight is often over whether the report was privileged at all, and for the timing mechanics of acting fast, Missed Federal Deadlines: Rule 6, Excusable Neglect, and the Deadlines a Court Cannot Excuse.

If you are a judge, consider entering a short order on your own initiative, as the rule allows. The statement of congressional intent contemplates exactly that.

If you are receiving the document, the lunch-table version is this: stop reading, tell them, and ask the court if you think they are wrong. The lawyers who get disqualified in these cases are almost always the ones who kept going.

Everything above is general information about federal rules and reported decisions, and how it applies to your documents and your court is a conversation for a lawyer who has seen both. If you are working through a live clawback or building a discovery plan for a new case, we are glad to talk it through, and UpLaw (uplaw.us) is a good place to read these opinions in full.

Related Documents

Related Articles

• Attorney-Client Privilege and Work Product for Businesses: Upjohn, In-House Counsel, and the Common Interest: what is privileged before any question of waiver arises.
• Protective Orders, Confidentiality Designations, and Sealing: Secrecy and Its Limits in Federal Court: the companion order that usually carries the Rule 502(d) language.
• Motions to Compel and Discovery Sanctions Under Rule 37: From Meet and Confer to Default Judgment: the motion practice in which these disputes get decided.
• Interlocutory Appeals and Mandamus: Getting Appellate Review Before Final Judgment: review options after Mohawk.
• Preparing a Witness for Deposition: What Is Proper, What Is Coaching, and What the Other Side Can Discover: the Rule 612 side of privilege at deposition.
• Data Breach Class Actions: Article III Standing, Negligence Claims, and Forensic Report Privilege: privilege over incident reports, a frequent subject of clawback fights.
• Missed Federal Deadlines: Rule 6, Excusable Neglect, and the Deadlines a Court Cannot Excuse: what delay costs when the clock is running.

Related Guides

• Recovering an Inadvertently Produced Privileged Document: A Practical Guide: the step-by-step version of this article, for both the producing and receiving lawyer.
• Negotiating an ESI Protocol and Managing E-Discovery Costs: where the Rule 502(d) order and review methodology get negotiated.
• Negotiating a Protective Order and Filing Under Seal: A Practical Guide: how to present disputed material to the court.
• Bringing or Opposing a Motion to Compel Discovery: A Practical Guide: briefing a privilege or waiver dispute.
• Responding to a Government Subpoena or Civil Investigative Demand: A Practical Guide: productions to agencies, where selective waiver is unavailable.

Related Checklists

• Privilege Clawback and Rule 502 Checklist: A Practical Checklist: a desk reference for setup, review, and response.
• Preparing a Privilege Log: A Practical Checklist: the Rule 26(b)(5)(A) work that Rhoads punished when skipped.
• Rule 26 Initial Disclosures and Discovery Planning: A Practical Checklist: the conference where the order should be proposed.
• Defending a Deposition Checklist: A Practical Checklist: what to do when a privileged exhibit appears.

Related Toolkits

• Clawback Toolkit: 502(d) Orders, Clawback Notices, and Privilege Review Protocols: the forms: order, notice, sequestration response, reviewer protocol, declaration.
• AI Confidentiality Toolkit: Acceptable Use Policies, Vendor Term Reviews, and Incident Playbooks: the vendor terms that matter when review runs through an AI tool.