In one reported case, a lawyer found out that privileged emails had been produced when her opponent marked them as exhibits. In another, the discovery came in the middle of preparing a privilege log. In a third, the other side's lawyers noticed first and said so, a courtesy that later hurt the producing party, because the court thought it noteworthy that the producing party had not found the problem itself. A clawback almost never begins at a time of anyone's choosing. What you do in the next few hours is evidence, and a judge may read it line by line in about four months.

This guide is written for both lawyers in that exchange, since the same few rules govern each side and the person who is producing today is usually receiving tomorrow.

The short answer

If you produced it: Confirm what regime applies, send a specific written notice the same day, stop any pending production, run a search for copies and siblings, and update your log. Write down what you did and when. Don't delete anything; you must preserve the material until the claim is resolved under Rule 26(b)(5)(B). If it surfaces during a deposition, object specifically on the record, instruct the witness, and follow up in writing that day. Under Fed. R. Evid. 502(b) you will have to prove reasonable steps both before and after the mistake, and a Rule 502(d) order, if you have one, may remove most of that burden.

If you received it: Stop reading once it looks privileged and appears inadvertent, notify the sender if your jurisdiction's Rule 4.4(b) applies, and, once you receive a claim, sequester every copy, stop using it, and retrieve what you passed along. You can disagree. The right way to disagree is to present the document to the court under seal, and the wrong way is to attach it to a public filing or ask a witness about it.

If you are the client: Expect a call from your lawyer. It should be prompt, candid, and followed by a plan. Don't try to fix it by contacting anyone on the other side yourself.

Step one for both sides: figure out which regime you are in

Everything downstream depends on this, and people skip it in the panic. Pull the protective order, the ESI protocol, the scheduling order, and any stipulation or email between counsel.

What you find What governs What it means for you
A court order under Rule 502(d) saying production is protected regardless of care The order. See In re Testosterone Replacement Therapy Products Liability Litigation, 301 F. Supp. 3d 917 (N.D. Ill. 2018) Follow its procedure exactly. Waiver from production is largely off the table in most courts, but use at a deposition can create a separate problem
An order with a clawback that speaks only of "inadvertent" production, or says nothing about care Depends on the court. Maxtena, Inc. v. Marks, 289 F.R.D. 427 (D. Md. 2012) and others may read Rule 502(b) into gaps Comply with the order and also build a Rule 502(b) record
A stipulation or email not entered as an order Rule 502(e): binds only the signers, and may be read narrowly Comply and build a record. See irth Solutions, LLC v. Windstream Communications LLC, 2017 WL 3276021 (S.D. Ohio Aug. 2, 2017)
Nothing Rule 502(b) and Rule 26(b)(5)(B) Every element is in play, and the producing party will likely carry the burden
Subpoena response Rule 45(e)(2)(B), the same procedure, with presentation to the court where compliance is required Same steps; check which court
Production to a federal agency outside litigation Rule 502(a) and (b) apply; a selective-waiver deal does not See Responding to a Government Subpoena or Civil Investigative Demand: A Practical Guide
State court case State procedure and state waiver law; Rule 502(c) matters later in federal court Check local rules, such as Texas's Tex. R. Civ. P. 193.3(d)

Read deadlines closely. The stipulation in Mt. Hawley Insurance Co. v. Felman Production, Inc., 271 F.R.D. 125 (S.D. W. Va. 2010) required notice of recall within ten business days of discovery and return within five, and it said compliance would satisfy Rule 502(b)(3). That second clause helped. It did not help with (b)(2), which the stipulation left alone. Knowing precisely what your paper does and does not cover is half the battle.

If you produced it: the first four hours

1. Get the facts, and write them down as you go

Assign one lawyer to run this. Open a running chronology with times: who noticed, how, what was seen. A privileged log of the response itself will be the backbone of your later declaration. Keep it factual. Treat it as work product, but draft on the assumption that you may need to put the same facts in a sworn declaration, because you will.

Answer five questions quickly:

  • What exactly went out? Bates range, volume, date, transmission method.
  • Is it actually privileged? If it isn't, there is nothing to recover. A court will look at this first. Coburn Group, LLC v. Whitecap Advisors LLC, 640 F. Supp. 2d 1032 (N.D. Ill. 2009) worked through whether an email was work product before reaching waiver, and distinguished ordinary from opinion work product.
  • Who has it? Opposing counsel, co-defendants, experts, a vendor, a shared repository, the court's docket?
  • Has it been used? Exhibit lists, filings, deposition outlines, correspondence.
  • How did it get out? Don't speculate in writing. Find out.

2. Freeze the pipeline

Stop any scheduled production. In irth Solutions, the same 43 documents went out again six weeks after the first clawback, because litigation support converted the wrong folder to searchable format while the waiver fight was already underway. The court noted that this happened in the midst of counsel asking for sanctions over the first production. Nothing you can write afterward repairs that record. Tell your vendor in writing that nothing leaves without lawyer sign-off until further notice, and have the vendor isolate the production set and preserve its logs.

3. Tell the right people

Who When Why
Lead counsel Immediately Owns the decision and the record
Client's general counsel or client contact Same day The privilege is the client's. Under Model Rule 1.4 and ABA Formal Opinion 481, a material error may have to be disclosed to a current client. Also ask about the document's business sensitivity
Vendor project manager Immediately Freeze, isolate, and preserve logs; investigate root cause
Firm general counsel or risk partner Same day if the document is significant Possible insurer notice and any conflict arising from the lawyer's own error
Co-counsel or joint-defense group Same day If the document is theirs or they received it, they have duties too
Opposing counsel Same day, by phone then in writing The Rule 502(b)(3) clock is running

Who shouldn't be told yet: the client's business team at large. A wide email about what the privileged memo says is a good way to make things worse. Keep the circle tight, and stay away from the content in non-privileged channels.

4. Call, then send the notice

A short call reduces the odds of an accident on the other side and builds goodwill you may need. It does not substitute for writing. The committee note to Rule 26(b)(5)(B) says notice "should be in writing unless the circumstances preclude it" and "as specific as possible." The next section tells you what to put in it.

The notice: what it must say

A good notice does six things.

  1. Identifies the documents by Bates number, including family members and known copies.
  2. States the claim and its basis. Say "attorney-client privilege" or "work product" or both, with enough detail for the other side to assess it, without giving away content.
  3. Invokes the governing paper. Cite the order paragraph, the stipulation section, Rule 26(b)(5)(B), and Rule 502.
  4. Lists the obligations. Return, sequester, or destroy; no use or disclosure; retrieve copies from others.
  5. Addresses derived data. Ask them to include copies held in review platforms, searchable text, analytics, AI summaries, deposition outlines, and expert files, and to describe what they did.
  6. Requests written confirmation by a date. State what you will do if the dispute continues.

Sample core language follows. The toolkit has a fuller form.

Pursuant to Federal Rule of Civil Procedure 26(b)(5)(B), Federal Rule of Evidence 502, and paragraph [] of the [Protective Order], [Client] gives notice that the documents listed in Attachment A, bearing Bates numbers [], are subject to [the attorney-client privilege and the work-product doctrine]. They were produced by mistake on [date]; we learned of the production on [date]. Attachment A states the basis for each claim. Please promptly return, sequester, or destroy these documents and all copies, including any extracted text or derived summaries; refrain from using or disclosing the information; and retrieve any copies provided to others. Please confirm in writing by [date]. We will provide replacement production media and an updated privilege log by [date].

Words to avoid. Don't describe the content. Don't say "we inadvertently produced a damaging memo." Don't concede anything about the review ("our search should have caught this"). Don't threaten sanctions in the first message unless the other side has already used the material after notice.

Should you say "inadvertent"? If your order protects production "whether inadvertent or otherwise," you don't need to fight about it, and you may prefer "produced by mistake" or simply "produced." If you are under Rule 502(b), you do need to claim it, because it is the first element. Datel Holdings Ltd. v. Microsoft Corp., 2011 WL 866993 (N.D. Cal. Mar. 11, 2011) treats the inquiry as a simple one: was the disclosure a mistake?

The sweep: following up on what you now know

The note accompanying Rule 502 says a party need not conduct a post-production review generally, but must "follow up on any obvious indications" of a mistake. Finding one privileged document is an obvious indication that there may be others. Mt. Hawley faulted the producing party for failing to run simple searches for copies of the disputed email, and for clawbacks that seemed to follow the opponent's notices and not its own review. Run the sweep within a day or two.

  • Exact and near duplicates. Search by hash value (a digital fingerprint of the file), then by near-duplicate clusters. In Mt. Hawley the same email was produced under two Bates numbers, and the second recall came weeks after the first.
  • Thread members. Pull every version of the chain. Datel involved repeated productions of truncated forms of one chain.
  • Family members. Attachments and parent emails.
  • The failure mode. If counsel's name was missed, search the name in body text. If a database failed, retest that whole database. If the review lacked a name, add it to the screen. In irth Solutions, the firm believed it knew all the in-house lawyers involved, and it did not.
  • The log, in reverse. Compare the privileged set against the produced set. Mt. Hawley found documents listed on the log but produced and never recalled.

Each new hit gets a supplemental notice. Serial notices are not a sin, provided each is prompt and you can explain why it followed the last. Keep a table: date found, document, date noticed, confirmation received.

Then find the root cause. Have a technically competent person (usually the vendor or your litigation support manager) write up what happened at the system level: load file, index, tag propagation, export profile, whichever step failed. Mt. Hawley and Datel both turned on software errors that manufacturers or counsel could not fully explain, with opposite results, in part because one party's process had other layers that would have caught the problem.

Update the log, and replace the production

Serve an updated privilege log promptly. Rhoads Industries, Inc. v. Building Materials Corp. of America, 254 F.R.D. 216 (E.D. Pa. 2008) shows the risk on both sides of the deadline: documents logged within about three weeks of the discovery kept protection, and documents not logged until months later were ordered produced under Rule 26(b)(5)(A), with no Rule 502 analysis. Rhoads also lost points for making the defendants cross-reference each document against a log instead of offering a clean copy of the production sooner.

Offer replacement media, or a replacement overlay, that omits or redacts the clawed-back documents. Quality-check it before it goes. That sentence would have changed the outcome in irth Solutions. Have a lawyer run the withheld list against the outgoing load file. A spot check will not do; a spot check was what happened there.

If a document is partly privileged, reproduce it redacted. The stipulation in Mt. Hawley gave 30 days for this; check yours.

Build your Rule 502(b) record now

If waiver may be contested, start assembling proof the same week. Courts have been explicit about what they want, and what they find useless. Williams v. District of Columbia, 806 F. Supp. 2d 44 (D.D.C. 2011) listed the basics missing from a failed showing: when review occurred, how much time was allocated, the reviewer's experience, attorney supervision, rounds of review, how privileged documents were segregated, and how many documents were reviewed relative to production. "The general statement that a privilege review was performed, without any supporting details, is completely uninformative."

From Victor Stanley, Inc. v. Creative Pipe, Inc., 250 F.R.D. 251 (D. Md. 2008), add: what search terms were used, why, who picked them, whether they were tested, and whether results were sampled. From Coburn, add the protocol itself, the reviewers' years of experience, and the lawyer's supervision. Whitecap won in part because its lawyer could describe a written protocol, two paralegals with 16 and 17 years of experience, five weeks of work, and a low error count.

Choose declarants with personal knowledge. In irth Solutions, the second-year associate who did the review and the staff member who made the second error did not testify, and the court said their absence was particularly troublesome. Think about privilege and work product for the declaration itself: you are describing process, not content, but the other side may argue you have opened the door, so stick to facts and don't include legal judgments about particular documents.

If the fight is a real one, consider who speaks for the review. A lawyer who is also trial counsel may become a witness on a collateral issue. A separate discovery counsel or vendor declarant can avoid that.

Tell the client what happens next

Your client's first question will be: can they use it? The honest answer has several parts. Whether the document can be used depends on the order and on the court's view of the review. Whether the other side can forget what it read is a separate matter, and the answer is no. Whether the mistake reaches beyond this document: almost certainly not. The explanatory note to Rule 502 says an inadvertent disclosure "can never result in a subject matter waiver," and irth Solutions limited waiver to the documents actually produced even after finding them recklessly handled.

If you're the client, ask your lawyer four things: what the document is, who has seen it, what the order says, and what will change so this doesn't recur. You do not need to contact the other side, and you should not. It's also a good moment to ask whether the mistake touches any other matter, since a waiver finding can have effects in other cases if no Rule 502(d) order is in place.

If you received it: the receiving lawyer's sequence

The receiving lawyer is often the most exposed person in this story. Producing lawyers lose documents. Receiving lawyers can lose cases: disqualification, sanctions, and exclusion all appear in the reported decisions. And the rules differ depending on whether notice has been given.

Before any notice: stop and assess

Say a reviewer on your team flags a memo from the other side's general counsel. Nobody has claimed anything yet. Rule 26(b)(5)(B) imposes no duty until notice; Mt. Hawley says as much. The ethics rules may.

Set up a triage path for your review team. A reviewer who sees something that looks privileged tags it, stops, and escalates to one designated lawyer. That lawyer decides, ideally without reading further than needed. Remove the rest of the trial team from the loop until it is decided, which lets you say later that the people trying the case never saw it.

Sample notification:

While reviewing your production, we encountered the document bearing Bates number [__], which may have been produced inadvertently. We have stopped review of it and limited access. Please let us know by [date] whether you claim privilege or protection. We reserve all rights, including the right to contest any such claim.

A word about tactics. Some receiving lawyers think silence is an advantage. The risks run the other way. If you sit on it and use it later, as in Rico, the question becomes your conduct, not their review. And Victor Stanley shows a receiving party that segregated documents and promptly flagged them, then won the waiver motion: "The Plaintiff is blameless." Courtesy cost that party nothing.

After notice: the rule's four verbs

Once notified, whether or not you agree with the claim, you must:

Return, sequester, or destroy. Sequester if you intend to contest; destruction forecloses presenting the document to the court, and return leaves you relying on the producing party's preservation duty. Check your order, which may be stricter. The stipulation in Mt. Hawley required return and confirmation of destruction, and the receiving parties who declined to comply were found out of compliance, even though they went on to win the waiver issue.

Sequestering means no further review. In GWU, EEOC counsel read the emails after notice, then attached a note saying "Do not look at," and the court held that she violated the rule. The opinion reasons that "sequester," read alongside "return" and "destroy," must also end access. It declined to impose sanctions because the material was not used, and warned the agency.

Don't use or disclose. That includes in a deposition, in a brief, in an expert's file, to your client, or in a public filing. Talismanic Properties, LLC v. Tipp City, 309 F. Supp. 3d 488 (S.D. Ohio 2017) shows a near miss: a plaintiff circulated a disputed email and counsel attached it to a public filing after a privilege claim, and the court issued a show-cause order before vacating it on the ground that the rule's application to documents first obtained through public records requests was reasonably debatable.

Retrieve. Identify everyone who received it, including experts, co-counsel, the client, and vendors. Ask for return, in writing, and record the answers. Rico involved copies shared with experts and cocounsel, and the disqualification order reached the experts too.

Decide whether to present it to the court. You "may promptly present the information to the court under seal." That is your route to a ruling.

What sequestration means on a modern platform

If you use a review platform, tagging a document "sequestered" may leave it searchable. Ask your vendor to:

  • remove it from all reviewer access, batches, and saved searches;
  • remove extracted text from the search index;
  • exclude it from analytics, concept clusters, thread visualizations, and TAR training sets;
  • remove or quarantine any AI-generated summaries, embeddings, or chat history containing it;
  • preserve a single locked copy, if you intend to present it to the court, under restricted access; and
  • confirm in writing, with a date.

No reported case we have found squarely decides whether an AI summary or embedding is a "copy," but the rule speaks of "information," and a chatbot that can still recite the memo is hard to describe as sequestration. If you've already fed it to a tool, tell the ethics lawyer, then look at AI Confidentiality Toolkit: Acceptable Use Policies, Vendor Term Reviews, and Incident Playbooks. Also look at your protective order: Morgan v. V2X, Inc., No. 25-cv-01991 (D. Colo. Mar. 30, 2026) shows a court restricting which AI tools may receive protected material at all.

Handwritten notes, outlines, and memos pose the same question. Segregate them. Note who has seen what. If your team has already absorbed the content, tell lead counsel so you can evaluate whether anyone must step back.

Should you contest?

Ask four questions before you spend the client's money.

  1. Is it really privileged on its face? Business advice copied to a lawyer often isn't. Upjohn Co. v. United States, 449 U.S. 383 (1981) protects communications made to obtain legal advice, not every email with a lawyer on it. You can argue this from the log and metadata without rereading the document.
  2. Was the production really a mistake? A document removed from a log after deliberate review isn't an accident. In Certain Underwriters at Lloyd's, London v. National Railroad Passenger Corp., 218 F. Supp. 3d 197 (E.D.N.Y. 2016) that weighed heavily toward waiver.
  3. Does the order foreclose the argument? If a Rule 502(d) order disclaims care, arguing the review was sloppy goes nowhere; see Testosterone and Edgar v. Teva Pharmaceuticals Industries, Ltd., No. 2:22-cv-02501 (D. Kan. Aug. 5, 2024). Deposition use, deliberate disclosure, and disclosure outside the case may still be arguable.
  4. Do you have an exception? Crime-fraud requires a showing under United States v. Zolin, 491 U.S. 554 (1989). Mt. Hawley reached in camera review on this basis after finding waiver. And for work product, even valid protection can yield to substantial need under Rule 26(b)(3)(A)(ii), although Coburn rejected that argument where the party just wanted the document for impeachment and could get the facts elsewhere.

Sometimes the correct answer is to concede. If the memo is obviously privileged and the producer's handling was decent, a fight may gain you nothing, cost a lot of money, and put your credibility at risk with the judge deciding your next discovery motion. Then return it, and write down what your team did.

The stakes table

Conduct Likely consequence Authority
Notify and sequester, then contest by sealed motion None, and you may win Victor Stanley; Coburn (quarantine treated as reasonable)
Read after notice, but no use Rule violation; order to return; warning GWU
Use after notice, or file publicly Show cause, sanctions, or exclusion Talismanic (vacated); Harleysville (use bar reported)
Knowingly exploit obviously privileged material Disqualification of counsel and experts Rico; Richards v. Jain, 168 F. Supp. 2d 1195 (W.D. Wash. 2001); Maldonado v. New Jersey, 225 F.R.D. 120 (D.N.J. 2004)
Improper acquisition of privileged material and use in litigation Sanctions Gomez v. Vernon, 255 F.3d 1118 (9th Cir. 2001)

A note on Harleysville

Harleysville Insurance Co. v. Holding Funeral Home, Inc., No. 1:15cv00057 (W.D. Va.), is widely cited, and many citations stop at the first ruling. Published accounts report that the magistrate judge found waiver in February 2017 based on an unprotected file-sharing link, and that the district judge reversed in October 2017 but faulted defense counsel under Rule 45(e)(2)(B) for using the material and barred its use. We could not get the opinion's full text. Read it before relying on it, and don't assume a link's lack of a password decides the case in either direction. For both sides, it's a reminder to tell the court about what you found, not to help yourself.

Presenting the dispute to the court

Who moves, and on what

Either side can tee it up.

  • Receiving party: present under seal and move for a determination that the document isn't privileged or that protection was waived, under Rule 26(b)(5)(B) and Rule 37(a).
  • Producing party: move for return and a protective order under Rule 26(c), to strike testimony if needed, and for an order barring use. Coburn arose this way, as a motion to compel return and strike deposition testimony. Bringing or Opposing a Motion to Compel Discovery: A Practical Guide covers meet-and-confer and briefing.

Producing parties shouldn't wait for the other side. Coburn excused about five weeks after a refusal, because the other side had agreed in writing to quarantine and not to argue delay, and the court said counsel for both sides acted reasonably and civilly. Without that agreement, ask for one or file. A good stipulation reads: "Pending resolution, Receiving Party will sequester the documents and will not contend that Producing Party's time to seek relief, through [date], reflects delay."

Filing under seal

Filing the document on the public docket can destroy what you are fighting about, whichever side you're on. The procedural rule gives the route, "under seal," but sealing mechanics come from the court's local rules, and many require a motion or leave.

  • Read the local rule and the judge's standing order first. Many courts want a letter or a joint submission for discovery disputes, and many want in camera submission rather than a filing.
  • Prefer in camera lodging. Offer to deliver the document to chambers; don't put it on ECF even in sealed form unless the rules require it. Rhoads and Datel each involved in camera review of the documents.
  • Keep the public brief clean. Describe the document by date, author, recipients, and general subject, in the terms of the log. No quotes. Sealing standards are stricter for material attached to dispositive motions, but a privilege dispute over a discovery document is usually easier. Negotiating a Protective Order and Filing Under Seal: A Practical Guide has the details.
  • Don't argue from content if you can avoid it. A receiving party that needs the content to make a crime-fraud argument should ask for leave and rely on what Zolin allows, in a sealed submission.

What the producing party has to show

Prepare for a mini-trial on review practice.

  • That the document is privileged: the party claiming privilege bears that burden. Provide a declaration from the lawyer or client who can establish the purpose of the communication.
  • Under Rule 502(b), or a narrow order: inadvertence, prevention, rectification. Williams places both of the latter on the holder. Rhoads is the notable contrary case on burden.
  • Under a Rule 502(d) order that disclaims care: that the order applies, and that you complied with its procedure.

Know your five factors and address each. If you have helpful comparative numbers, use them: Coburn (three items out of 40,000 pages), Datel (a low proportion in 119,000 documents on a short schedule). Don't rely on volume alone. Victor Stanley found the argument that volume and time gave defendants no choice "simply unpersuasive," since they had given up the order that would have protected them.

What the receiving party has to show

Under most courts' burden allocations, your task is to poke holes: an unexplained review, no sampling, a failure to act on obvious clues, delay. Identify what's missing from the declarations. Point to document facts that the review should have caught, in terms that don't quote the contents: for instance, that the sender's title on the log is "General Counsel," that the document carries a privilege legend, or that the name was on the log. Show any reliance you placed on the document before notice, since the Statement of Congressional Intent, quoted in Mt. Hawley, says fairness may inform whether rectification was sufficiently prompt where the receiving party has relied on the information.

After the ruling

Magistrate judge rulings can be challenged by objection under Rule 72(a) within 14 days, and the district judge reviews for clear error or conduct contrary to law. Mohawk Industries, Inc. v. Carpenter, 558 U.S. 100 (2009) closes the collateral order route, so if you lose a privilege ruling, you are looking at § 1292(b) certification, mandamus, or standing on the privilege and appealing the sanction. Irth obtained certification on the clawback standard. Ask for a stay at once: the producing party's whole point is that a compelled reading can't be undone. See Interlocutory Appeal Checklist: A Practical Checklist.

When the document appears at a deposition

Deposition clawbacks are the fastest way to lose an otherwise good position. Amtrak is the warning: the court, despite a broad Rule 502(d) order, found waiver when counsel merely said he would "reserve Amtrak's rights" as to one exhibit and let questions continue, and for another objected only as to other communications. The letter the next morning came too late. Testosterone disagrees, on an order that it read to cover this, and declined to treat a seven-day gap as waiver. Don't rely on being in that court.

If you are defending

The first three sentences matter most. Say:

Counsel, I object. Exhibit [] appears to be privileged and to have been produced by mistake. [Client] asserts the attorney-client privilege and work-product protection and invokes Rule 26(b)(5)(B) and paragraph [] of the Protective Order. Please stop questioning on this document and give me all copies in the room. I am instructing the witness not to answer questions about its contents, under Rule 30(c)(2), in order to preserve the privilege. We will follow up in writing today.

Then:

  1. Don't let the witness read it aloud or answer "just background." In Datel, counsel looked at a truncated email, said no privilege applied, and asked for the record to be corrected only hours later after seeing the full chain. The court excused that because of the glitch. It might not excuse you.
  2. Take a break if you need one. Ten minutes to verify beats an hour of unprivileged testimony. But make the objection before you leave.
  3. Mark the transcript pages for sequestration. Send the written notice before the end of the day, and include the court reporter's copy, video, and exhibits. D'Andrea Brothers LLC v. United States, No. 08-286C (Fed. Cl. June 4, 2010) is a good model: counsel objected at once and blocked testimony, followed up with a letter a week later, and provided redacted versions shortly after.
  4. Move to strike the testimony if any was given. Whitecap sought and got relief in Coburn.

If you don't know whether a document is privileged, you still have to do something. "I need to look at this; I object for now on privilege grounds pending review, and I ask that we move on" is more specific than a bare reservation. For more on managing deposition objections, see Defending a Deposition Checklist: A Practical Checklist. Prep your witnesses on this too, and see Preparing Yourself or Your Witness for a Deposition: A Practical Guide.

If you are taking

If the other side objects on privilege grounds, Rule 26(b)(5)(B) applies from that point: stop using the document. If you think the objection is wrong, make your record ("I'll note that this was produced to us on [date]") and move on. Keep the deposition open for the issue. You can't lose by waiting for a ruling. You can certainly lose by pressing, as Rico illustrates.

Rolling privilege review: reducing the odds of a repeat

A rolling review splits production into batches, with privilege review and logging tied to each. The 2025 committee note to Rule 26 says rolling production with an appropriate description of withheld material is often valuable, and warns against a log near the close of discovery. Done well, it means an error in volume 3 is caught before volume 4, and each lesson feeds the next round.

A practical protocol

  1. Build the name list early. Interview the client's legal department. Collect every in-house lawyer, paralegal, and outside firm, including former ones, plus domain names and nicknames. irth Solutions began with exactly this gap.
  2. Screen across body, header, and attachment text. Rhoads searched only address lines. Exclude footers that contain "privileged" from any keyword logic, or the signal disappears.
  3. Review in tiers. First-level reviewers code; a second level checks everything coded privileged, and a sample of what is not. Datel used three levels with written instructions and a tutorial.
  4. Sample the "not privileged" pile. That's the Victor Stanley lesson. Do it for each batch. Record the sample size and misses. Escalate if the miss rate is above whatever threshold you set in advance.
  5. Test the export. Immediately before release, run privilege terms and the withheld hash list against the actual outgoing set. Failures in Mt. Hawley (a bad index), Datel (truncation), and Irth (the wrong folder) all happened after the human judgment.
  6. Check text extraction. Confirm that images and PDFs have been OCR'd before running search. Victor Stanley turned partly on claims about non-searchable files.
  7. Log on a schedule. Agree with the other side on timing and method at the Rule 26(f) conference; that's what Rule 26(f)(3)(D) now expects.
  8. Keep a review diary. Dates, versions, decisions, QC results, changes to terms. It's your future declaration.

Choosing a method: costs and trade-offs

Prices vary so much by data type and market that any general figure would mislead you. Get a written estimate from your vendor based on a sample of your data. The relative comparison below tends to hold.

Approach Relative cost Main risk Fits when
Lawyer eyes on every responsive document Highest Time; reviewer fatigue; still imperfect Small sets, or very sensitive custodians
Search screen, then lawyer review of hits, sampling the remainder Moderate Misses from unlisted names or odd phrasing, if sampling is thin The most common defensible default
TAR or AI-ranked review with validation Moderate, often lower at scale Privilege is contextual; a declarant must explain and validate it Large sets with experienced consultants; see Rio Tinto PLC v. Vale S.A., 306 F.R.D. 125 (S.D.N.Y. 2015) on TAR generally
Light screen in reliance on a Rule 502(d) order Lowest Adversary reads what slips through; order does not stop learning Low-sensitivity data with a strong order
Quick peek Low up front Adversary sees everything Rarely; see the discussion in Rule 502 and Inadvertent Production: Waiver, Clawback Agreements, and Why Every Case Needs a 502(d) Order

If you use a generative AI tool in review, have someone test it on your data and be ready to explain the workflow under oath. Confidentiality comes first: check that vendor terms bar training on your inputs and allow deletion, the kind of conditions Morgan imposed. ABA Formal Opinion 512 covers the duties. And if you are drafting an AI policy for the client as well, see Building a Generative AI Use Policy That Protects Trade Secrets: A Practical Guide.

Can you get a Rule 502(d) order after the mistake?

Ask. The rule speaks of "disclosure connected with the litigation pending before the court" and has no explicit timing limit, and a court may enter one over objection, as Rajala v. McGuire Woods, LLP, 2010 WL 2949582 (D. Kan. July 22, 2010) did before production issues arose. We have not found a case squarely addressing an order applied retroactively to rescue a past production over objection, and a court may be unwilling to deprive the receiving party of a waiver argument it already holds. But an order covering all future productions is well within the rule, and it costs little. Don't repeat what happened in Victor Stanley, where the defendants abandoned their request and later, when the review ran short, neither sought more time nor renewed it. Note the limits, too: United States v. Captive Alternatives, LLC, No. 8:22-cv-00406 (M.D. Fla. Aug. 29, 2023) denied one in an IRS summons enforcement proceeding.

Two worked examples

Larkmoor Seafood: with an order, on a bad Tuesday

Suppose Larkmoor Seafood, a wholesale distributor, is defending a contract suit in federal court. Its protective order states that it "is entered under Rule 502(d)," that production of privileged material "whether inadvertent or otherwise" is not a waiver in this or any other federal or state proceeding, that Rule 502(b) does not apply, and that the receiving party shall sequester within three business days of notice.

At 11:00 a.m. Tuesday, during a contract analyst's deposition, plaintiff's counsel marks Exhibit 14, an email from the analyst to Larkmoor's in-house lawyer. Defending counsel looks up. She says: "Objection, Exhibit 14 is privileged and was produced by mistake. We invoke paragraph 12 of the Protective Order and Rule 26(b)(5)(B). I instruct the witness not to answer about it. Please hand me the copies." Plaintiff's counsel says he disagrees but moves on. By 5:00 p.m., the written notice is out, listing Exhibit 14 by Bates number and stating the basis. That evening, litigation support finds three thread members. A supplemental notice goes out Wednesday morning, with an updated log entry. Thursday, plaintiff's counsel confirms sequestration and says he will challenge the claim on the merits.

What can plaintiff argue? That the email isn't privileged, perhaps as a business communication. Larkmoor bears that burden, and the court reviews in camera. Waiver from production is gone, regardless of how the document slipped through, in nearly all courts. Waiver at the deposition is unavailable because the objection was immediate and specific. Total cost: a deposition interruption, a letter, and a short motion.

Brightwater Clinic: without one, from the other side of the table

Suppose you represent the plaintiff, Dr. Amara, against her former employer, Brightwater Clinic, in a federal employment case. No Rule 502(d) order was entered; counsel exchanged an email agreeing that inadvertent production "won't waive anything." Your paralegal finds a thread among Brightwater's executives with a forwarded message from its outside counsel about how to document your client's termination. Your client has not seen it. Your jurisdiction has adopted Rule 4.4(b).

Day 0. The paralegal stops and tells you. You read enough to confirm what it appears to be: a lawyer's message, on a live subject, in a production from a party who surely did not mean to send it. You limit access. You notify Brightwater's counsel that afternoon, citing the Bates number, and you reserve rights.

Day 1. Brightwater's counsel sends a Rule 26(b)(5)(B) notice. You remove the document from the platform's index and analytics, and lock a single copy. Your expert hasn't received anything, and you confirm that in writing.

Day 3. Brightwater cannot immediately explain how it happened. You ask a few questions by letter: what screen did you run, and how was it tested? (They'd have to answer in a declaration later anyway.)

Day 10. The meet-and-confer fails. You file a short public letter describing the document in log terms, and seek leave to lodge it in camera under seal.

The argument. You say the email agreement is a cursory contract under Irth that doesn't displace Rule 502(b), and it's a contract only under Rule 502(e). Brightwater's declaration says a paralegal reviewed. You point to Williams on unexplained reviews, and to Victor Stanley on sampling. Brightwater says its production was only 1,200 pages, so a mistake is small. You turn that around, since a small production means there was time to review. You may or may not win. But you can't lose the case by doing it this way, and in the meantime no one on your trial team has built anything on that message. If the court rules for Brightwater, you return it, and your client's case is untouched.

Notice what you did not do. You did not use the email in a deposition to "see what happens," or tell your client what it said, or attach it to a public motion. The lawyers whose names appear in the disqualification cases did some of those.

Timing table

When Producing side Receiving side
Discovery of the issue, within hours Freeze pipeline; identify; call; written notice; tell client Stop reading; escalate; limit access; notify if Rule 4.4(b) applies
Day 1 to 2 Sweep for duplicates, threads, families; supplemental notices On notice: sequester, stop use, retrieve; confirm in writing; purge derived data
Day 2 to 5 Root cause; replacement media after QC; updated log Decide whether to contest; ask process questions
Week 1 to 2 Declarations drafted; meet and confer; seek quarantine stipulation Meet and confer; propose joint in camera submission
Within any deadline in the order, or else promptly after impasse File for return and protective order Present under seal and move, or return
14 days after magistrate ruling Rule 72(a) objection; request for stay Same

If your order sets shorter times, the order controls. If you're not sure what a deadline in your order means, treat the shorter reading as the right one. For calendaring this kind of fast-moving obligation, see Federal Deadline Calendaring and Recovery Checklist: A Practical Checklist.

Special settings

Nonparties. A nonparty responding to a subpoena has the Rule 45(e)(2)(B) procedure. Ask for your own Rule 502(d) protection; the parties' order may not name you. See Nonparty Discovery Toolkit: Subpoenas, Third-Party Records, and Privilege and Responding to a Third-Party Subpoena: A Practical Guide for Businesses.

Agencies. Rule 502(b) covers mistaken disclosures to a federal office or agency, but Rule 26(b)(5)(B) is a discovery rule, so the agency's own process and any agreement you made are what you have to work with. Ask for a clawback in writing before production. Don't rely on a promise of confidentiality as protection against later plaintiffs. In re Pacific Pictures Corp., 679 F.3d 1121 (9th Cir. 2012) rejected that approach.

Filter teams in criminal cases. Protocols often contain their own clawback and Rule 502(d) language; United States v. Fluitt, 99 F.4th 753 (5th Cir. 2024) reproduces one. Read it as you would any order. Under Fed. R. Crim. P. 16, discovery is structured differently, so don't assume civil procedure applies.

Data incidents. When a breach forensic report gets produced by mistake, the privilege itself is often the contested issue. See Data Breach Litigation Toolkit: Privileged Investigation Protocols, Standing Motions, and Settlement Terms.

Documents from a whistleblower or leak. Rule 502(b) fits badly when the holder had nothing to do with the disclosure. GWU noted that a party can't be said to have failed to prevent what an employee did without authorization, and it weighed that fact heavily against waiver.

Common mistakes

Assuming the protective order has a Rule 502(d) clause. People confuse confidentiality orders with waiver orders. Read the actual text. A general non-waiver line may be treated differently from an order that disclaims Rule 502(b).

Sending a vague notice. "Some documents in Volume 3 may be privileged" gives the other side nothing to sequester and a chance to argue that you didn't take reasonable steps. Mt. Hawley included a recall of one version that left another copy outstanding for weeks.

Treating notice as the end of the job. Williams rejected the idea that a letter under Rule 26(b)(5)(B) was automatically enough. Follow up, sweep, log, and move for relief when needed.

Reservations of rights at a deposition. Vague reservations failed in Amtrak. Say "privileged," say why, and instruct.

Declarations from the wrong person. Lead counsel's generalities don't help. irth Solutions noted who was missing.

Reproducing the same problem. Recheck every replacement set. Irth is the cautionary tale, and it should be taped to the wall of every litigation support department.

Withdrawing a privilege claim and then trying to take it back. Deliberate choices are not mistakes. Amtrak so held.

Using a clawback to hide a bad document. A document isn't privileged because it hurts. Courts notice overreach. Mt. Hawley notes that fear of waiver may produce "extravagant claims of privilege" in the course of quoting the rules committee, and Fairholme Funds, Inc. v. United States, 134 Fed. Cl. 680 (2017) ordered a quick peek after the government kept releasing documents it had previously withheld.

On the receiving side: keeping on reading "to evaluate the claim." GWU rejected this. Evaluate from the log and what you already know.

On the receiving side: telling the client. The rule bars disclosure. That covers your client. If the client already knows, tell lead counsel and deal with the issue.

On the receiving side: treating the claim as an insult and refusing to sequester. In Mt. Hawley, refusal to return was held a breach of the stipulation even though that side won the waiver issue. You can be right about waiver and still be wrong about procedure.

On both sides: skipping the meet and confer. Most courts require one, and Rule 37(a)(1) requires a certification on a motion to compel. A short call often gets you a quarantine agreement and a joint in camera submission.

On both sides: losing your temper in writing. These letters become exhibits. Keep them dull. Coburn praised counsel for acting reasonably and civilly, which helped the party that needed time.

This guide offers general information and can't substitute for advice on your own order, documents, and court; a lawyer who has reviewed them should make the final call. If a live clawback is on your desk, we are happy to take a look.

Related Documents

Related Articles

Related Guides

Related Checklists

Related Toolkits