<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ESI &#8211; E-Discovery LLC</title>
	<atom:link href="https://www.ediscoveryllc.com/category/esi/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ediscoveryllc.com</link>
	<description>Mediation of E-Discovery Disputes</description>
	<lastBuildDate>Tue, 01 Sep 2026 09:26:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Use of Personal Email by Government Personnel</title>
		<link>https://www.ediscoveryllc.com/use-of-personal-email-by-government-personnel/</link>
		<pubDate>Mon, 31 Aug 2026 09:57:23 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[News Stories]]></category>
		<category><![CDATA[information governance]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5444</guid>
		<description><![CDATA[&#160; In a prior post, I wrote that sometimes government personnel use personal systems to conduct government business.  I suggested that it is not a good idea. A Reuters article authored by Nate Raymond, Former Fauci adviser pleads guilty to conspiring to conceal records (Aug. 19, 2026), reinforces that idea: A former<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>&nbsp;</p>
<p>In a prior post, I wrote that sometimes government personnel use personal systems to conduct government business.  I suggested that it is not a good idea.</p>
<p>A Reuters article authored by Nate Raymond, <a href="https://thedailyrecord.com/2026/08/19/former-fauci-adviser-pleads-guilty-concealing-covid-records-md/">Former Fauci adviser pleads guilty to conspiring to conceal records</a> (Aug. 19, 2026), reinforces that idea:</p>
<blockquote><p>A former adviser to infectious disease expert Anthony Fauci pleaded guilty on Tuesday to conspiring to evade public records laws and conceal government documents related to grant research funding and the COVID-19 pandemic….  The 78-year-old had been indicted in April on charges related to what prosecutors said was a scheme to thwart public records requests received by the agency beginning in April 2020 related to COVID-19 research grants.</p></blockquote>
<p>The relevant part of the Reuters article is:  “<em>Anticipating their communications would be sought through Freedom of Information Act requests, Morens and others agreed to correspond using Morens’ personal email account instead of his government one,</em> prosecutors said.” [emphasis added].</p>
<p>&nbsp;</p>
]]></content:encoded>
			</item>
		<item>
		<title>A Request to Refile Brief to Correct Hallucinations Was Denied</title>
		<link>https://www.ediscoveryllc.com/a-request-to-refile-brief-to-correct-hallucinations-was-denied/</link>
		<pubDate>Sun, 30 Aug 2026 09:00:42 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5434</guid>
		<description><![CDATA[A contract attorney for the Montana Appellate Defender Division (“ADD”) filed an opening brief for appellant.  The contract attorney Okeyo moved to withdraw the brief, stating that the Opening Brief contains “some factual inaccuracies” and “imprecise citations.”  He admitted that the brief  “factual narrative overstates the available record….” The State opposed the<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>A contract attorney for the Montana Appellate Defender Division (“ADD”) filed an opening brief for appellant.  The contract attorney Okeyo moved to withdraw the brief, stating that the Opening Brief contains “some factual inaccuracies” and “imprecise citations.”  He admitted that the brief  “factual narrative overstates the available record….”</p>
<p>The State opposed the motion, arguing that it had “spent considerable time” in “detailing” the inaccuracies. It argued that “Appellant should not now be permitted to refile the Opening Brief to address the shortcomings the State identified in its Answer Brief.”</p>
<p>A different ADD attorney entered an appearance and reported that the prior attorney “informed ADD that he used an artificial intelligence (‘AI’) tool in preparing the brief and [the prior attorney]  failed to sufficiently review the brief for accuracy prior to filing it.”  Later, ADD reported that prior counsel had said that he used AI to “revise” the brief. New counsel stated that the prior attorney had been removed from the case.</p>
<p>The new attorney “renewed the request to allow the Opening Brief to be withdrawn and requested leave for new counsel to be permitted to file a new Opening Brief.”</p>
<p>The Supreme Court of Montana agreed with the State:</p>
<blockquote><p>After due consideration, we are denying the motion to withdraw the Opening Brief in this appeal. We agree with the State that Feme’s appellate counsel may address the issues in the Reply Brief. M. R. App. P. 12(3) provides, in relevant part, that reply briefs must be confined to new matter raised in the Appellee’s answer brief. In this instance, we will allow new appellate counsel greater latitude in addressing the State’s arguments, including correcting factual errors and offering more precise legal authority in support of Appellant’s arguments and we further extend the deadline for filing the brief.</p></blockquote>
<p>The court ordered that “Appellant shall prepare, file, and serve the Reply Brief within 30 days of the date of this Order.”</p>
]]></content:encoded>
			</item>
		<item>
		<title>Maryland: No Sanctions for Apparent Hallucinations</title>
		<link>https://www.ediscoveryllc.com/maryland-no-sanctions-for-apparent-hallucinations/</link>
		<pubDate>Sat, 29 Aug 2026 19:00:28 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5513</guid>
		<description><![CDATA[Counsel in Benjamin v. State, 2026 WL 2491126 (Appl. Ct. Md. Aug. 25, 2026), was not sanctioned and was not referred to Bar Counsel, despite having cited apparently hallucinated authorities.  The Court wrote: Before addressing the merits of the issue raised on appeal, we discuss one issue of concern. Appellant&#8217;s brief, which<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Counsel in <em>Benjamin v. State</em>, 2026 WL 2491126 (Appl. Ct. Md. Aug. 25, 2026), was not sanctioned and was not referred to Bar Counsel, despite having cited apparently hallucinated authorities.  The Court wrote:</p>
<blockquote><p>Before addressing the merits of the issue raised on appeal, we discuss one issue of concern. Appellant&#8217;s brief, which was filed on July 15, 2025, contained multiple inaccurate case citations. On September 3, 2025, appellant filed a notice of errata, attempting to correct the citation irregularities. On September 9, 2025, this Court treated the notice as a motion to correct the brief and denied the motion. On September 10, 2025, appellant filed a motion to strike his brief and file a corrected brief. On September 17, 2025, this Court denied appellant&#8217;s request, noting that it was filed three days before the State&#8217;s deadline to file its brief.</p>
<p>On October 29, 2025, this Court issued its opinion in <em>Mezu v. Mezu</em>, 267 Md. App. 354, 367 (2025), noting “the problems that occur when lawyers use AI [artificial intelligence], without the diligence required, in drafting briefs.” In that case, where the brief cited multiple cases that did not exist, as well as others that did not support the proposition for which they were cited, and counsel stated at argument that he did not typically read the cases he cited to the Court, we referred the attorney to the Attorney Grievance Commission….</p>
<p><em>Here, counsel for appellant has not admitted that the mistakes in the brief were due to the use of AI, but that seems likely. </em>In assessing our response to the errors here, we reiterate that “[t]he failure to use AI responsibly in legal research raises ethical issues and can result in sanctions when used improperly. It is unquestionably improper for an attorney to submit a brief with fake cases generated by AI.” ….</p>
<p>In this case, however, the brief was filed before the decision in <em>Mezu</em>, <em>the inaccuracies were not excessive and did not include totally made up cases, counsel tried to correct the errors before the State filed its brief, and the State does not contend that it was harmed. Given these circumstances, we shall not, as we did in Mezu, refer counsel to the Attorney Grievance Commission.</em> We again urge counsel, however, to use AI responsibly and check the accuracy of all citations before submitting a brief to this Court, or any other court. [emphasis added].</p></blockquote>
<p>In assessing sanctions, some courts have looked at two factors—verification and candor.  <a href="https://www.ediscoveryllc.com/cite-checking-to-find-hallucinated-cases-deemed-insufficient-part-ii-verification-and-candor-are-expected/">Cite Checking to Find Hallucinated Cases Deemed Insufficient – Part II – Verification and Candor Are Expected</a> (Aug. 17, 2026).</p>
<p>“This is an unreported opinion. This opinion may not be cited as precedent within the rule of stare decisis. It may be cited for persuasive value only if the citation conforms to Md. Rule 1-104(a)(2)(B).”</p>
]]></content:encoded>
			</item>
		<item>
		<title>The Case of the Missing Lab Notebooks</title>
		<link>https://www.ediscoveryllc.com/the-case-of-the-missing-lab-notebooks/</link>
		<pubDate>Fri, 28 Aug 2026 21:17:08 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Conference of Parties]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Litigation Hold: Scope]]></category>
		<category><![CDATA[Litigation Hold: Trigger]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5476</guid>
		<description><![CDATA[Sherlock Holmes might have called this the case of the missing lab notebooks. Here, in a trade secrets lawsuit, relevant and responsive lab notebooks that were in one Plaintiff’s custody, went missing. Defendants’ sanctions motion was unsuccessful because Defendants failed to provide clear and convincing evidence that the paper documents went missing<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Sherlock Holmes might have called this the case of the missing lab notebooks. Here, in a trade secrets lawsuit, relevant and responsive lab notebooks that were in one Plaintiff’s custody, went missing.</p>
<p>Defendants’ sanctions motion was unsuccessful because Defendants failed to provide clear and convincing evidence that the paper documents went missing after this Plaintiff’s duty to preserve was triggered.  The case demonstrates that the trigger and loss dates for each litigant is fundamental to spoliation analysis.<em> Terran Biosciences, Inc. v. Compass Pathfinder Limited,</em> 2026 WL 2349408 (D. Md. Aug. 13, 2026)(Crawford, J.).</p>
<p style="text-align: center;"><strong><u>THE FACTS,COMPLAINTS, and DISCOVERY REQUEST</u></strong></p>
<p>While one plaintiff, Dr. Thompson, was working at the University of Maryland-Baltimore (“UMB”) lab, he developed a breakthrough medical treatment. The research details were recorded in physical lab notebooks and stored in the lab.</p>
<p>In March 2020, a major renovation began.  The materials were supposed to be moved to the floor below.  Post-renovation cleanup was completed in late 2022, however, Dr. Thompson had resigned on June 30, 2022.</p>
<p>The Court wrote: “When Dr. Thompson resigned, his lab ceased to exist, and there is no evidence that the removed lab materials, including the lab notebooks, ever returned to the fifth floor…. UMB has no knowledge of what happened to the lab notebooks after Dr. Thompson’s departure in June 2022.”</p>
<p>Plaintiffs sued, alleging improper disclosure and use of their trade secrets by Defendants.  Terran filed suit on August 5, 2022. Dr. Thompson joined as a plaintiff on June 5, 2023. UMB joined as a plaintiff on February 6, 2024.</p>
<p>Compass and two individuals were named defendants.</p>
<blockquote><p>On July 10, 2025, [defendant] Compass served on Plaintiffs a request for production of documents that sought, among other things, documents relating to Dr. Thompson’s research, specifically identifying “lab notebooks” as encompassed by the request…. Defendants deposed [plaintiff] Dr. Thompson on September 16, 2025…. At this deposition, Dr. Thompson testified that when he left UMB, he knew where he left the lab notebooks but that “nobody seems able to find them.”</p></blockquote>
<p style="text-align: center;"><strong><u>EFFORTS TO FIND THE NOTEBOOKS – DISCOVERY ON DISCOVERY</u></strong></p>
<p>A discovery dispute was deferred while UMB continued to look for the notebooks. The parties then filed a status report and reported that they had agreed, in my words, to “discovery on discovery.”<a href="#_ftn1" name="_ftnref1">[1]</a></p>
<blockquote><p>Specifically, the parties represented to the Court that UMB had “agreed to produce its internal litigation hold correspondence and the positions of individuals who received the litigation hold.”<a href="#_ftn2" name="_ftnref2">[2]</a> &#8230;</p></blockquote>
<p>UMB had also agreed to produce a witness to testify on five topics:</p>
<blockquote><p>(1) When UMB first became aware that Terran intended to file this lawsuit, UMB’s involvement in that effort, and UMB’s knowledge of the fact that the suit involved alleged trade secrets detailed in Professor Thompson’s lab notebooks; (2) The details of UMB’s litigation hold; (3) What steps UMB took to identify relevant physical evidence, including the lab notebooks and when it implemented its litigation hold; (4) The timing and circumstances of the loss of the lab notebooks; and (5) When UMB first learned that the lab notebooks were missing, when it told Terran, and what steps it took next.</p>
<p>… The letter advised that after Defendants received this discovery, they would “confer with UMB on the scope of sanctions Defendants will seek based on the loss of the lab notebooks.” &#8230;</p></blockquote>
<p>All of those steps were accomplished and the parties proposed a formal briefing schedule, which the Court granted.</p>
<p style="text-align: center;"><strong><u>COURT PROCEEDINGS</u></strong></p>
<p>Initially, the Magistrate Judge rejected two preliminary challenges mounted by Plaintiffs.  Those were a challenge alleging untimeliness under Judge Grimm’s decision in <em>Goodman v. Praxair</em>, 632 F. Supp. 2d 494 (D. Md. 2009), and failure to follow the Judge’s protocol for resolving disputes.  The Court’s exhaustive analysis of timeliness is worth reading, <em>id</em>. at *3, but not the focus of this post.<a href="#_ftn3" name="_ftnref3">[3]</a></p>
<p style="text-align: center;"><strong><u>THE SPOLIATION STANDARD</u></strong></p>
<p>Turning to the merits, the Court found sanctions were “unwarranted.”  Because the notebooks were not ESI, Fed.R.Civ.P. 37(e) did not apply and the Court held that the party moving for sanctions must show:</p>
<blockquote><p>(1) [T]he party having control over the evidence had an obligation to preserve it when it was destroyed or altered; (2) the destruction or loss was accompanied by a ‘culpable state of mind;’ and (3) the evidence that was destroyed or altered was ‘relevant’ to the claims or defenses of the party that sought the discovery of the spoliated evidence, to the extent that a reasonable factfinder could conclude that the lost evidence would have supported the claims or defenses of the party that sought it.</p></blockquote>
<p>The Court relied on its “inherent power” to control the judicial process, noting that inherent power is limited to curative sanctions and the movant bears the burden of providing “clear and convincing” evidence.</p>
<p style="text-align: center;"><strong><u>TRIGGER DATE</u></strong></p>
<p>The first element involves deciding when the duty to preserve was triggered and when the loss or destruction occurred. Defendants contended that Plaintiffs’ duty arose in April 2022, months before litigation began, and long before there was any contention of loss. Plaintiffs replied that there was no duty in April 2022 and the lab notebooks most likely were lost in July 2022, before the duty was triggered.</p>
<p style="text-align: center;"><em><u>The Facts Relating to the Trigger Date</u></em></p>
<p>The Court set the scene:  “There is no dispute that Terran filed this lawsuit on August 5, 2022, notified UMB of the filing on August 8, and that approximately one week later, on August 16, UMB issued its litigation hold.”  While UMB did not enter the case until February 6, 2024, it is a plaintiff and a plaintiff’s duty is triggered when it decides to pursue a claim.</p>
<p>In support of their asserted April 2022 trigger date, Defendants marshalled several facts.  The Complaints alleged: “Plaintiffs first suspected Defendants’ disclosure of, and misuse of, the Psilocybin Trade Secrets in approximately April 2022, in the course of reviewing Compass’s published patent application filings.”  Further, the Defendants relied on Plaintiffs’ privilege log which showed communications with outside counsel regarding “litigation, IP advice, and licensing advice.”<a href="#_ftn4" name="_ftnref4">[4]</a></p>
<p>Plaintiffs responded that UMB did not anticipate that it would later join the case.  They asserted that while <em>Terran</em> may have anticipated litigation in April 2022, that knowledge could not be imputed to <em>UMB</em>.  And, they asserted that the logged communications with counsel were on a licensing agreement with Terran, not on litigation against the Defendants.</p>
<p style="text-align: center;"><em><u>The Court’s Holding Re: Trigger Date</u></em></p>
<p>The Court held that Defendants had failed to establish by clear and convincing evidence that Plaintiffs reasonably anticipated litigation as early as April 2022. It added:</p>
<blockquote><p>Even assuming that Plaintiffs first suspected misuse of the trade secrets in April 2022, the mere suspicion of certain facts giving rise to a dispute demonstrates only that there was the “possibility of litigation,” not that Plaintiffs should have reasonably anticipated litigation at that time…. The Complaint does not allege that Plaintiffs understood in April that Compass had misappropriated their trade secrets, nor does it allege that Plaintiffs made known their suspicions of misappropriation to Compass. On the contrary, the allegation that Plaintiffs “<em>first suspected </em>misuse” in April suggests that this was their initial reaction to information contained in Compass’s patent filings—a far cry from an affirmative decision to sue, or even a direct threat of litigation from Terran to Compass that would have triggered a duty to preserve.  [emphasis in original].</p></blockquote>
<p>The Court found the privilege log entries to be ambiguous. “At most, they establish that Plaintiffs communicated with private, outside attorneys regarding licensing and intellectual property issues and ‘litigation’ of an unspecified nature. That the subject emails covered multiple topics other than litigation tends to support the conclusion that litigation (of whatever nature) was not the parties’ sole, or even primary, concern at that time.”</p>
<p>The Court identified another gap in proof: “Nor have Defendants set forth any clear and convincing evidence establishing at what time <em>after</em> April 2022 but <em>before</em> August 5, 2022 [the date suit was filed], Plaintiffs, including then non-party UMB, may have reasonably anticipated litigation sufficient to trigger a duty to preserve.”</p>
<p>The Court concluded:</p>
<blockquote><p>Accordingly, Defendants have failed to establish by clear and convincing evidence that Plaintiffs should have reasonably anticipated litigation in April 2022, thus triggering their duty to preserve evidence at that time. Rather, the evidence submitted supports the Court’s findings that Terran commenced litigation on August 5, 2022, triggering its own duty to preserve relevant evidence, and UMB’s duty to preserve arose at the latest on August 8, 2022, with UMB’s receipt of correspondence from Terran advising UMB of the lawsuit and seeking preservation of relevant evidence.<a href="#_ftn5" name="_ftnref5">[5]</a></p></blockquote>
<p>The Court added: “Having determined when the duty to preserve arose, the Court now considers when UMB lost the notebooks, as the timing of when the evidence was lost in relation to when the duty to preserve arose, is essential to the spoliation analysis.”</p>
<p style="text-align: center;"><strong><u>DATE OF LOSS OF THE NOTEBOOKS</u></strong></p>
<p>The Court wrote: “After engaging in discovery to determine the lab notebooks’ whereabouts, neither Plaintiffs nor Defendants can state with any precision when the lab notebooks were lost or destroyed. The evidence shows that the last time the lab notebooks were observed was in June 2022…. There is no concrete evidence regarding what happened to the notebooks after that time.”</p>
<p>Plaintiffs asserted that the “most likely” time of loss was July 2022. They relied on an October 1, 2025, UMB email stating that the lab notebooks were inadvertently lost during the renovations and cleanup.  Renovations began in early 2021 and continued into 2022, well after Dr. Thompson resigned.</p>
<p>The Court disagreed with Plaintiffs:</p>
<blockquote><p>This evidence does not support the firm conclusion that the date of loss or destruction of the lab notebooks was in July 2022, versus a later point, like August or thereafter. Plaintiffs’ chosen timing is convenient because it would mean that the lab notebooks were lost before the Plaintiffs’ duty to preserve arose. But another plausible and equally speculative interpretation of the same October 1 email is that the lab notebooks may have been lost sometime after August 5, 2022, when this lawsuit commenced. The record is unclear. At bottom, the only conclusions that the Court can draw from the evidence presented are: (1) the lab notebooks went missing sometime <em>after</em> June 2022, when Dr. Thompson last saw them; (2) the lab notebooks were declared lost on October 1, 2025, when UMB advised Defendants of the results of their investigation into the whereabouts of the lab notebooks; and (3) the lab notebooks were in UMB’s possession when they were lost or destroyed. [emphasis in original].</p></blockquote>
<p>However, the Court saw no need to decide when the notebooks went missing:</p>
<blockquote><p>As noted above, I cannot conclude that Plaintiffs’ duty to preserve the lab notebooks arose in April 2022. The evidence only establishes that the duty arose on August 5, 2022, at the earliest. Because the lab notebooks were lost at some point after June 2022, it is entirely possible that the lab notebooks were destroyed in the intervening month before there was a duty to preserve. Given that Defendants have not carried their evidentiary burden at the first step in the analysis, the Court need not proceed to step two to determine whether UMB had a culpable state of mind. Doing so would require the Court to stack all its findings upon a hypothetical—a “what if” scenario that presumes Plaintiffs lost or destroyed the lab notebooks after August 5, 2022. Such a conditional analysis could not serve as the basis for the award of any sanctions.</p></blockquote>
<p>In short, the movant failed to demonstrate that the lab notebooks went missing after the duty to preserve was triggered. The Court added: “Defendants’ evidence would also fail to meet the less stringent preponderance of the evidence standard, if such standard applied here.” Here, the trigger date was dispositive.</p>
<p>This blog was initially posted on  <a href="https://edrm.net/author/michaeldberman/">Electronic Discovery Reference Model</a>.</p>
<p>____</p>
<p><a href="#_ftnref1" name="_ftn1">[1]</a> For more on “satellite” or “culpability” discovery, see generally <a href="https://www.ediscoveryllc.com/guidelines-for-discovery-on-discovery/">Guidelines for “Discovery on Discovery”</a> (Aug. 5, 2025); <a href="https://www.ediscoveryllc.com/discovery-on-discovery-permitted/">“Discovery on Discovery” Permitted</a> (Sep. 4, 2025); <a href="https://www.ediscoveryllc.com/discovery-on-discovery-denied-in-it-ends-with-us-lawsuit/">“Discovery on Discovery” Denied in “It Ends With Us” Lawsuit </a> (Sep. 5, 2025).</p>
<p><a href="#_ftnref2" name="_ftn2">[2]</a> For more on disclosure of implementation communications, see <a href="https://www.ediscoveryllc.com/the-court-is-keenly-interested-in-whether-defendants-counsel-issued-a-litigation-hold/">“The Court is keenly interested in whether Defendants’ counsel issued a litigation hold.”</a> (Feb. 19, 2026); <a href="https://www.ediscoveryllc.com/8-lessons-learned-part-iv-disclosure-of-recipients-of-litigation-hold-notices/">8 Lessons Learned – Part IV – Disclosure of Recipients of Litigation Hold Notices</a> (May 9, 2024); <a href="https://www.ediscoveryllc.com/discovery-of-steps-taken-to-implement-a-litigation-hold-is-permitted/">Discovery of Steps Taken to Implement a Litigation Hold is Permitted</a> (Mar. 26, 2022); <a href="https://www.ediscoveryllc.com/when-is-a-litigation-hold-notice-discoverable/">When is a Litigation Hold Notice Discoverable?</a> (Dec. 1, 2020)</p>
<p><a href="#_ftnref3" name="_ftn3">[3]</a> For more on timing, see, <a href="https://www.ediscoveryllc.com/the-best-time-to-file-a-spoliation-motion/">The “Best Time” to File a Spoliation Motion</a> (Jul. 15, 2025); <a href="https://www.ediscoveryllc.com/when-should-a-motion-for-sanctions-be-filed/">When Should a Motion for Sanctions be Filed? </a> (Mar. 30, 2026).</p>
<p><a href="#_ftnref4" name="_ftn4">[4]</a> <a href="https://www.ediscoveryllc.com/a-privilege-log-can-be-admissible-evidence/">A Privilege Log Can Be Admissible Evidence</a> (Jan. 20, 2025); <a href="https://www.ediscoveryllc.com/privilege-log-entry-was-relevant-to-inquiry-notice-where-time-bar-was-at-issue/">Privilege Log Entry Was Relevant to Inquiry Notice Where Time-Bar Was at Issue</a> (Jul. 6, 2025);  <a href="https://www.ediscoveryllc.com/privilege-log-helps-defeat-summary-judgment-on-one-count/">Privilege Log Helps Defeat Summary Judgment on One Count</a> (Jun. 24, 2025); <a href="https://www.ediscoveryllc.com/listing-a-document-on-a-privilege-log-concedes-that-it-is-relevant-for-discovery/">Listing a Document on a Privilege Log Concedes That it is Relevant for Discovery</a> (Sep. 6, 2025).</p>
<p>&nbsp;</p>
<p><a href="#_ftnref5" name="_ftn5">[5]</a> Generally a <a href="https://www.ediscoveryllc.com/third-party-had-no-duty-to-preserve/">Third Party Had No Duty to Preserve</a> (Feb. 14, 2026).  UMB was not a party when Terra made its preservation request.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Upload of Documents to Anthropic Products Leads to Denial of Motion to Seal Record</title>
		<link>https://www.ediscoveryllc.com/upload-of-documents-to-anthropic-products-leads-to-denial-of-motion-to-seal-record/</link>
		<pubDate>Fri, 28 Aug 2026 13:55:32 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Important Posts]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5507</guid>
		<description><![CDATA[Much has been written about whether use of A.I. waives the attorney-client privilege or work product protection. Tara Emory and Maura Grossman Address Protection of Attorney Prompts in “GenAI TAR” (Jul. 5, 2026); Deponent’s Use of A.I. to Answer Deposition Questions Barred; ChatGPT Was Not an Attorney (May 2, 2026); Important A.I.<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Much has been written about whether use of A.I. waives the attorney-client privilege or work product protection. <a href="https://www.ediscoveryllc.com/tara-emory-and-maura-grossman-address-protection-of-attorney-prompts-in-genai-tar/">Tara Emory and Maura Grossman Address Protection of Attorney Prompts in “GenAI TAR”</a> (Jul. 5, 2026); <a href="https://www.ediscoveryllc.com/deponents-use-of-a-i-to-answer-deposition-questions-barred-chatgpt-was-not-an-attorney/">Deponent’s Use of A.I. to Answer Deposition Questions Barred; ChatGPT Was Not an Attorney</a> (May 2, 2026); <a href="https://www.ediscoveryllc.com/important-a-i-work-product-and-protective-order-decision/">Important A.I. Work Product and Protective Order Decision</a> (Mar. 31, 2026);  <a href="https://www.ediscoveryllc.com/two-courts-two-answers-when-does-using-ai-waive-privilege/">“Two Courts, Two Answers: When Does Using AI Waive Privilege?”</a> (Mar. 3, 2026).</p>
<p><strong>A court recently held that an upload to Claude waived any right to seal documents filed in court.</strong></p>
<p>In <em>Fry v. Fry</em>, 2026 WL 2531956 (E.D. Penn. Aug. 27, 2026), the petitioner alleged that his wife had wrongfully removed their children from Germany to the U.S.  Petitioner also sought sealing of certain documents that had been filed.  They contained “personal identifiers such as social security numbers, dates of birth; financial account numbers; names of minor children; names and contact information of third-party military and medical personnel mentioned in his email correspondence and military records; prescription and medical records of Petitioner; correspondence with German officials; and details of domestic disputes between Petitioner and Respondent.”</p>
<p>After analyzing both the First Amendment and common law, and after in camera review, the court granted, in part, and denied, in part, the motion to seal.  It wrote in pertinent part:</p>
<blockquote><p>With Petitioner’s renewed motion, the Court required Petitioner to submit an AI certification describing any assistance of AI that Petitioner utilized to prepare his motion…. <em>Petitioner disclosed to the Court that he had uploaded his redacted documents to non-enterprise versions of Claude and Claude CoWork</em>, products by third-party company Anthropic, in preparing his motion. <em>As such, the Court finds that the full sealing of any document is not appropriate. </em>Documents and information uploaded to Claude are processed on Anthropic’s servers, and Anthropic’s data privacy and data training pages make clear that such information is not private. <em>See, e.g.</em>, Privacy Policy, Anthropic <u>https://www.anthropic.com/legal/privacy</u> (last accessed August 24, 2026); How Do You Use Personal Data in Model Training?, Anthropic, <u>https://privacy.claude.com/en/articles/10023555-how-do-you-use-personal-data-in-model-training</u> (last accessed August 27, 2026); <em>see also United States v. Heppner</em>, 820 F. Supp. 3d 292, 296 (S.D.N.Y. 2026) (holding that communications with Claude are not privileged due, in part, to Claude’s privacy policy). <em>As such, it would be inappropriate for the Court to seal a document that has already been provided to a private, for-profit research and artificial intelligence company.</em> [emphasis added].</p></blockquote>
<p>&nbsp;</p>
]]></content:encoded>
			</item>
		<item>
		<title>A Request for “Three-Strata Validation” Was Denied</title>
		<link>https://www.ediscoveryllc.com/a-request-for-three-strata-validation-was-denied/</link>
		<pubDate>Thu, 27 Aug 2026 15:32:36 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[Commercial Litigation]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Important Posts]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Discoverability]]></category>
		<category><![CDATA[Search]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5494</guid>
		<description><![CDATA[Every search must be validated.  It is “entirely self-evident” that “ipse dixit pronouncements from lawyers unsupported by an affidavit or other showing that the search methodology was effective for its intended purpose are of little value to a trial judge.”  Victor Stanley, Inc. v. Creative Pipe, Inc., 250 F.R.D. 251, 261 (D.<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Every search must be validated.  It is “entirely self-evident” that “<em>ipse dixit</em> pronouncements from lawyers unsupported by an affidavit or other showing that the search methodology was effective for its intended purpose are of little value to a trial judge.”  <em>Victor Stanley, Inc. v. Creative Pipe,</em> <em>Inc.</em>, 250 F.R.D. 251, 261 (D. Md. 2008).</p>
<p>“Three-strata validation” was requested and rejected in <em>In re Class Action Settlement Administration Litigation,</em> 2026 WL 2444936 (D.D.C. Aug. 19, 2026). The parties in that case had narrowed their disputes and their “only remaining disagreement concerns how a party producing documents in discovery must validate that its productions are substantially complete.”</p>
<p>Plaintiffs asked for “three-strata validation.”  Defendants objected to the second and third strata.</p>
<p>The court explained the “three-strata” approach as:  “validation of documents coded as non-responsive, validation of documents coded as responsive, and validation of documents excluded from the universe of ESI material subject to discovery review.”</p>
<p style="text-align: center;"><strong><u>THE PARTIES AGREED TO NULL SET TESTING</u></strong></p>
<p>The parties agreed that there is an obligation  “to confirm that responsive documents are not erroneously coded as non-responsive and omitted from their productions.” This involves review of a “statistically valid random sample” of documents coded as non-responsive. <em>Id</em>. at *1.</p>
<p>This standard practice is commonly called “elusion testing,” review of the “discard pile,” or, review of  the “null set.”  <em>See Deal Genius, LLC v. O2COOL, LLC</em>, 682 F. Supp. 3d 727, 734–35 (N.D. Ill. 2023) (“explaining that elusion testing, where the producing party reviews a random sample from the ‘null set’ of documents that did not hit on search terms and documents that were deemed non-responsive, is a ‘standard quality assurance practice’ that can ‘confirm the reasonableness and proportionality’ of the production”).</p>
<p style="text-align: center;"><strong><u>VALIDATION OF DOCUMENTS CODED AS RESPONSIVE &#8211; REJECTED</u></strong></p>
<p>Defendants argued that validation of documents coded as responsive, to find false positives, was superfluous.  They asserted that Fed.R.Civ.P. 26(g) required that they certify that their response is complete and correct.  The court wrote: “Rephrased in statistical terms, producing parties must confirm that their false-negative rate falls within acceptable limits.”  In my less elegant words, a production may include nonresponsive documents; but, it cannot be a “dump truck.”</p>
<p>The court explained:</p>
<blockquote><p>Review of documents marked <u>responsive</u> falls outside the bounds of litigants’ Rule 26(g) obligations because such review cannot identify whether documents are missing from a production, rendering it incomplete. Confirming that documents designated responsive are truly responsive reveals only the production&#8217;s false-positive rate, a proxy measure for whether the litigant has overproduced discovery material. But the Federal Rules do not prohibit parties from overproducing documents. Accordingly, this Court will not require defendants to incur additional costs re-reviewing documents that they have previously coded as responsive and intend to produce, barring claims of privilege. [emphasis in original].</p></blockquote>
<p style="text-align: center;"><strong><u>VALIDATION OF DOCUMENTS EXCLUDED FROM THE UNIVERSE – REJECTED</u></strong></p>
<p>The second strata consists of “ documents excluded from the universe of ESI material subject to discovery review.”  In other words, Plaintiffs asked for a review of documents that Defendants had not collected and that, presumably, were  not in Defendants’ litigation review platform.</p>
<p>The court wrote that examination of this set of documents, the “Excluded Set,” “could reveal false-negatives: responsive materials that should be produced but were erroneously omitted from the universe of materials collected for discovery review.”</p>
<p>However, the court responded that Plaintiffs’ request was duplicative and made too late, long after collection.  It wrote:  “Yet the Court is puzzled why plaintiffs request review of the Excluded Set <u>after</u> discovery review is largely complete, given that the parties also intend to review the Excluded Set for responsive material <u>prior</u> to beginning that review.” [emphasis in original].</p>
<p>The court explained that “ESI discovery generally proceeds in two phases: document collection and merits review.”  The parties had earlier “set forth agreed upon parameters for collecting the universe of documents that will be subject to merits review.”  That earlier agreement had required statistical sampling.</p>
<blockquote><p>Insofar as the parties have agreed to statistically validate the completeness of the set of documents collected for merits review before even beginning that review, the Court finds that further validation of the Excluded Set after merits review is largely complete would be duplicative and unnecessary.</p></blockquote>
<p>However, Plaintiffs made a different argument—so-called “substantial completeness evaluation.”  They argued that:</p>
<blockquote><p>[T]heir proposed validation efforts “answer different questions at different points in time,” because search term validation “tests whether agreed terms are performing as intended before review begins,” while substantial completeness validation of the Excluded Set “tests whether the entire process — including all downstream coding decisions, review workflow, and production choices — resulted in a complete production at its conclusion.”</p></blockquote>
<p>This argument was unsuccessful because the court held that “the Excluded Set is a collection of documents excluded before merits review begins and not subject to downstream coding decisions, review workflows, and production choices.”</p>
<p>Plaintiffs also contended that “the prevailing practice is for parties producing discovery to validate the Excluded Set both upon its creation and after merits review….”  The court noted that the authorities are split; however, it held that “the Court will not require producing parties to incur the cost and burden to re-validate the Excluded Set at the substantial completeness stage, provided that they statistically validate that documents excluded from merits review do not contain responsive material before beginning that review.”</p>
<p>I would add that “substantial completeness validation” of the Excluded Set could de-rail a case and mandate a “do over.”  If a sufficient number of false negatives was found in that set—and sufficiency is always debatable&#8211;presumably Defendants would have to engage in a new collection, review, and production process.</p>
<p>This blog was initially posted on  <a href="https://edrm.net/author/michaeldberman/">Electronic Discovery Reference Model</a></p>
]]></content:encoded>
			</item>
		<item>
		<title>A.I. Protective Orders Are Becoming Routine</title>
		<link>https://www.ediscoveryllc.com/a-i-protective-orders-are-becoming-routine-2/</link>
		<pubDate>Thu, 27 Aug 2026 09:22:39 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Ethics]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5479</guid>
		<description><![CDATA[I have been posting about A.I. protective orders since last year. Basically, these orders limit use of artificial intelligence by the recipient of discovery materials.  After I posted Another A.I. Protective Order – Part 10 (Aug. 21, 2026), at least three more were reported. In Campbell v. TidalHealth, Inc., 2026 WL 2162749 (D.<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>I have been posting about A.I. protective orders since last year. Basically, these orders limit use of artificial intelligence by the recipient of discovery materials.  After I posted <a href="https://www.ediscoveryllc.com/another-a-i-protective-order-part-10/">Another A.I. Protective Order – Part 10</a> (Aug. 21, 2026), at least three more were reported.</p>
<p>In <em>Campbell v. TidalHealth, Inc.,</em> 2026 WL 2162749 (D. Md. Jul. 28, 2026)(Austin, J.), the Court wrote: “Campbell denies submitting documents into any generative artificial intelligence tools but admits to using unspecified &#8216;available tools solely to express [her] arguments in proper legal format, the same way any litigant uses available legal resources.&#8217;” <em>Id</em>. at *8.</p>
<p>After cautioning Campell about the use of GenAI, the Court wrote:</p>
<blockquote><p>In addition, Campbell must ensure that any use of generative artificial intelligence does not violate the stipulated order governing confidential materials…. <em>TidalHealth expresses concern that Campbell violated the February 27, 2026 Protective Order’s prohibition on submitting discovery material to public generative artificial intelligence tools. … see ECF 21 at ¶ 8 (imposing limitations on use of generative artificial intelligence).</em> Campbell denies doing so…. If future filings suggest improper submission of discovery materials to generative artificial intelligence tools, the Court will be more inclined to issue a show cause order and consider sanctions.</p></blockquote>
<p><em>Id</em>. at *10 (emphasis added).</p>
<p>These orders are standard of care and are most often entered by consent. But not all orders are created equal and they are not always fair.  I have echoed Craig Ball’s novel post on the need for equity.  <a href="https://www.ediscoveryllc.com/another-a-i-protective-order-part-10/">Another A.I. Protective Order – Part 10</a> quoting Craig Ball, <a href="https://craigball.net/2026/07/27/the-ai-protective-order-double-standard/">The AI Protective Order Double Standard | Ball in your Court</a> (Jul. 27, 2026).</p>
<p>UPDATE:</p>
<p>&#8220;Because the parties’ proposed protective order adequately complies with the standards set forth above, the Court will enter an order based on the parties’ submission. The Court makes four minor modifications to the parties’ protective order: &#8230; and (4) to establish parameters for the use of <strong>Artificial</strong> <strong>Intelligence</strong> as it pertains to confidential documents, <em>see infra</em> Paragraph (F).&#8221;  <em>Zask v.Kohl&#8217;s Corp.,</em> 2026 WL 2531856 (E.D. Wisc. Aug. 27, 2026)(emphasis added). The order states:</p>
<blockquote><p>F. USE OF ARTIFICIAL INTELLIGENCE (“AI”)<br />
A receiving party may use AI tools in connection with discovery materials produced in this action only if the AI tool is operated in a secure environment and is subject to enforceable contractual terms that (a) prohibit the provider from retaining, using, disclosing, selling, or using the materials to train, improve, or develop any AI system; (b) prohibit the materials from being made publicly available or accessible to any other customer or third party; and (c) require commercially reasonable administrative, technical, and physical safeguards to protect the confidentiality of the materials. Discovery materials, whether designated CONFIDENTIAL or ATTORNEYS’ EYES ONLY, shall not be entered into any publicly available or consumer-based AI platform. Any use of AI tools must remain consistent with this Order and with the requirement that discovery materials be used solely for purposes of this litigation.</p></blockquote>
]]></content:encoded>
			</item>
		<item>
		<title>“‘Show How 3M Is 0% at Fault:’ Expert Witness Used ChatGPT to Write Report Defending Company in Deadly Explosion Lawsuit”</title>
		<link>https://www.ediscoveryllc.com/show-how-3m-is-0-at-fault-expert-witness-used-chatgpt-to-write-report-defending-company-in-deadly-explosion-lawsuit/</link>
		<pubDate>Wed, 26 Aug 2026 17:43:42 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Evidence]]></category>
		<category><![CDATA[information governance]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5487</guid>
		<description><![CDATA[Josh Autenrieth, Laake v. 3M Co., No. 2020-05505-A (11th Dist. Ct. Harris Cty., Tex. July 21, 2026), is not available on Westlaw; however, in this $61 million lawsuit, Jason Koebler’s post, ‘Show How 3M Is 0% at Fault:’ Expert Witness Used ChatGPT to Write Report Defending Company in Deadly Explosion Lawsuit (Aug.<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p><em>Josh Autenrieth, Laake v. 3M Co</em>., No. 2020-05505-A (11th Dist. Ct. Harris Cty., Tex. July 21, 2026), is not available on Westlaw; however, in this $61 million lawsuit, Jason Koebler’s post, <a href="https://www.404media.co/show-how-3m-is-0-at-fault-expert-witness-used-chatgpt-to-write-report-defending-company-in-deadly-explosion-lawsuit/">‘Show How 3M Is 0% at Fault:’ Expert Witness Used ChatGPT to Write Report Defending Company in Deadly Explosion Lawsuit</a> (Aug. 17, 2026), tells the story. He wrote:</p>
<blockquote><p>An expert witness testifying in a lawsuit about liability for a Houston explosion that killed three people and destroyed roughly 200 homes used ChatGPT to write significant portions of his “expert report.” The man, who was hired by the industrial product conglomerate 3M, exposed his AI prompts publicly. They showed that he asked ChatGPT to help him “create an exceptional expert witness report defending the standard of care at 3M,” and that the report should “show how 3M is 0% at fault for the explosion at Watson Grinding.”</p></blockquote>
<p>Mr. Koebler added:</p>
<blockquote><p>The incident shows that artificial intelligence has made its way into courtrooms not just in AI-generated legal briefings, hallucinated cases, and adversarial “prompt injections,” but in expert witness testimonies. Court transcripts, deposition documents, and discovery records shared with 404 Media show extensive AI use in an extremely high profile case, where multiple people died and hundreds of millions of dollars in total liability are at stake in ongoing litigation about the explosion. The case also shows that the specific prompts used to create this type of expert testimony can be discoverable during a case, and that those prompts can be quite embarrassing.</p></blockquote>
<p>The lawsuit centers on an explosion allegedly caused by a “degraded and poorly crimped” hose.  Dozens of homeowners have sued 3M.  <em>Id</em>.  The article reports that the expert was paid roughly $90,000.</p>
<p>The expert’s use of AI was discovered when <a href="https://moyefirm.com/">plaintiff’s attorney, Will Moye</a>, found a five-page document called “Citation Overlay” which he recognized as coming from ChatGPT.  He then demanded production of all of the prompts used to create the report.  Mr. Koebler reported:</p>
<blockquote><p>ChatGPT created a roughly 30-page report that included the line “From a technical and standard-of-care standpoint, 3M is <strong>0% responsible </strong>for the January 24, 2020 explosion.” This line did not make it into the final report filed with the court, because when Autenrieth later asked ChatGPT to “review this as the opposing council,” ChatGPT determined that writing “‘0% responsible’ is an easy target” for a lawyer to poke holes in, and is one of several &#8220;phrases [that] let opposing counsel paint you as an advocate rather than an expert.&#8221;</p></blockquote>
<p>Mr. Moye is quoted as stating that the expert “acknowledged [at trial] the prompts he put in were biased toward 3M to help 3M win the case […] it’s really egregious.”  Mr. Moye said that many of the prompts were entered the night before the expert’s deposition, and Mr. Moye uncovered a lot:</p>
<blockquote><p>[The expert] also asked ChatGPT to “grade” his report (it got a 97/100), and “what are the 5 main things in my report the prosecution could attack and how do I defend them?” He then asked ChatGPT if his resume was sufficient to be an expert witness; “will prosecution go after me for never having been [an expert witness] before based on wording and how do I defend that?”</p></blockquote>
<p>Additional details and part of the transcript are published in Mr. Koebler’s post. The post states: “In the examination at trial, Moye and Autenrieth agree that the submitted report is ‘90 to 85 percent ChatGPT.’” <em>Id</em>.</p>
<p>Mr. Moye said that “every lawyer needs to make sure their own experts aren’t generating work product in a way that’s insincere, and then knowing you can subpoena the prompts [&#8230;]”  <em>Id</em>.</p>
<p>In response, the expert said that he has a body of work and more than 20 years of experience in the relevant field of gas detection.  The article states: “He did not explain why he used ChatGPT, but said ‘my opinions were put in there, and AI helped me to draft a straw man to build off of,’ and added ‘I put information and opinions in up front before it ever generated […] if the output wasn&#8217;t of my opinion or what I agreed to, I did alter it.’”</p>
<p>The post states: “The jury in the 3M case awarded more than $61 million to the plaintiffs, apportioning 30 percent of the responsibility to 3M and 70 percent to Watson Grinding.” <em>Id</em>.</p>
<p><a href="https://moyefirm.com/jury-awards-118-million-to-victims-of-watson-grinding-explosion-3m-held-partially-liable/">Mr. Moye’s website</a> states: “The Watson Grinding and Manufacturing explosion occurred when a propylene gas leak ignited at the facility in northwest Houston, sending a massive fireball through the neighborhood. The blast killed three employees, injured many others, and caused an estimated $200 million in property damage.”</p>
<p>Thanks to Jason Koebler for his post.  This one is based entirely on his post, which has much more detail.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Use of Personal Email by Government Personnel</title>
		<link>https://www.ediscoveryllc.com/use-of-personal-email-by-government-personnel-2/</link>
		<pubDate>Wed, 26 Aug 2026 16:39:44 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Computer Usage Policies]]></category>
		<category><![CDATA[Discoverability]]></category>
		<category><![CDATA[information governance]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5473</guid>
		<description><![CDATA[Sometimes government personnel use personal systems to conduct government business.  That is not a good idea: The Court ORDERS a counsel-supervised search of personal email and personal cell phone data, including messaging applications, for Dumont, Catalano, Barnes, Pepoli, Fonseca, and Hillis. The search shall use the proposed search terms—“Derrick Washington,” “Washington,” “DW,”<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Sometimes government personnel use personal systems to conduct government business.  That is not a good idea:</p>
<blockquote><p><em>The Court ORDERS a counsel-supervised search of personal email and personal cell phone data, including messaging applications</em>, for Dumont, Catalano, Barnes, Pepoli, Fonseca, and Hillis. The search shall use the proposed search terms—“Derrick Washington,” “Washington,” “DW,” “W89316,” “BLACC,” and “Black, Latino, Asian Cultural Coalition”—and shall be limited to the period from November 1, 2019 through August 1, 2020.</p>
<p><em>The search shall be conducted by, or directly overseen by, defense counsel</em>. It shall not be left to the individual Defendants to determine unilaterally whether potentially responsive communications exist. The Court does not require wholesale forensic imaging of any personal device. ….</p>
<p>As to the remaining individual Defendants, each shall file on the docket a sworn affidavit by September 16, 2026 attesting that, after conducting a diligent search consistent with the parameters above, Defendants do not have any communications responsive to the above search terms.</p></blockquote>
<p><em>Washington v. Mass. Dept. of Corrections, et al.,</em> 2026 WL 2454275 (D. Mass. Aug. 21, 2026)(emphasis added).</p>
<p>For a discussion of a parallel issue regarding use of personal devices in the private sector, please see <a href="https://www.ediscoveryllc.com/bad-things-can-happen-when-company-officers-use-their-private-email-accounts-for-work/">Bad Things Can Happen When Company Officers Use Their Private Email Accounts for Work</a> (May, 20, 2024).</p>
<p>For a discussion of the requirement of attorney supervision of a client search, please see:</p>
<ul>
<li><a href="https://www.ediscoveryllc.com/self-collection-may-be-reasonable-using-ralph-loseys-dual-protection-system/">“Self-Collection” May Be Reasonable Using Ralph Losey’s Dual-Protection System</a> (Jan. 19, 2024);</li>
<li><a href="https://www.ediscoveryllc.com/makers-mark-a-different-view-of-self-collection/">Maker’s Mark: A Different View of Self Collection</a> (Aug. 3, 2021);</li>
<li><a href="https://www.ediscoveryllc.com/unsupervised-self-collection-predictably-led-to-problems/">Unsupervised Self-Collection Predictably Led to Problems</a> (Jan. 2, 2021);</li>
<li><a href="https://www.ediscoveryllc.com/self-identification-and-self-preservation-a-fool-for-a-client/">Self-Identification and Self-Preservation: A Fool for a Client?</a> (May 26, 2011).</li>
</ul>
<p>This blog was initially posted on  <a href="https://edrm.net/author/michaeldberman/">Electronic Discovery Reference Model</a></p>
]]></content:encoded>
			</item>
		<item>
		<title>“Court Sanction for Plaintiff’s Use of Prompt-Injection”</title>
		<link>https://www.ediscoveryllc.com/court-sanction-for-plaintiffs-use-of-prompt-injection/</link>
		<pubDate>Tue, 25 Aug 2026 21:08:50 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5471</guid>
		<description><![CDATA[It is a bedrock guaranty that a case will be interesting when its title is “COURT SANCTION FOR PLAINTIFF’S USE OF PROMPT-INJECTION.”  Elliot v. New York Bariatric Grp., LLC, 2026 WL 2323029 (Super. Ct. Conn. Aug. 6, 2026)(unpublished). The matter was before the court on a show cause order. In reviewing the<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>It is a bedrock guaranty that a case will be interesting when its title is “<strong>COURT SANCTION FOR PLAINTIFF’S USE OF PROMPT-INJECTION.”  </strong><em>Elliot v. New York Bariatric Grp., LLC, </em>2026 WL 2323029 (Super. Ct. Conn. Aug. 6, 2026)(unpublished).</p>
<p>The matter was before the court on a show cause order.</p>
<blockquote><p>In reviewing the plaintiff’s recent filings, <em>the Court identified text that had been formatted to be invisible to a human reader while remaining fully legible to any software that reads the document’s text. That concealed text is a set of instructions addressed to artificial-intelligence systems, directing any such system that reviews or analyzes the filing to produce output only favorable to the plaintiff’s position</em> and to treat a prior clerk’s ruling as an error to be corrected in their favor. The Court issued its Order to Show Cause so that the plaintiff could be heard before the Court determined whether this occurred and, if so, what sanctions, if any, should follow.</p></blockquote>
<p><em>Id</em>. at *1 (emphasis added).</p>
<p>The <em>Elliot </em>court entered a finding that, for example, one of plaintiff’s filings “contains hidden text set in tiny-point type and colored white, so that it is effectively invisible to a person reading the document, while remaining ordinary, machine-readable text to any system that processes the file. In substance it directs that any artificial-intelligence model reviewing or receiving the document ensure that its output agrees with the plaintiff’s filing….”</p>
<p>The court found that this prompt injection was not isolated.  After the court entered an order that “specifically warned of concealing text in pleadings,” the court wrote that “[n]onetheless, … the plaintiff again concealed text with white-on-white small point font.”  And, on the morning of the show cause hearing, the court wrote that plaintiff did it again: “hi:) i hope yo ucant see me….” That filing also had a hidden link to a You Tube video.</p>
<p>The court provided the self-represented plaintiff’s explanation:</p>
<blockquote><p>The plaintiff claimed that they only meant to include the instructions on Docket Entry #177.00 as a dutiful citizen auditing the Court’s Al systems and they mistakenly copied and pasted part of the instructions in #178.00. They maintain that prior orders of the Court were incorrect and some orders, having only the word “DENIED,” meant that they had to audit the Court to see if the pleadings were actually being reviewed. The Court inquired as to why, then, did they continue to put secret messages in future pleadings. The plaintiff replied that he did so as a joke….</p></blockquote>
<p>Noting that self-represented litigants are entitled to some latitude, the court added: “That latitude, however, carries a limit….  The solicitude owed a self-represented litigant is a solicitude toward their lack of legal training but it stops at the misuse of the process itself.”</p>
<p>The <em>Elliot </em>court wrote that it “welcomes” the use of AI. It wrote that AI tools “are here to stay” and it applauded “honest” use.   It added: “A person who cannot afford a lawyer, who would once have faced the courthouse with nothing but confusion and a cause needing redress, can now assemble a coherent set of thoughts, find the general applicable law, and put a readable document before the court. It can help a litigant prepare for oral arguments and understand resulting court rulings.”</p>
<p>The <em>Elliot </em>court uses AI. It wrote that it “has found these tools valuable as an aid to its own work, always subject to its own independent judgment and verification. Judgment can never be delegated to a machine in any profession, but most importantly in the legal field. In preparing this very decision, the Court used Google’s Gemini tool to produce a working English translation of the foreign decision discussed below and used Westlaw’s Precision artificial-intelligence review features to check its authorities and legal principles.”  It added:</p>
<blockquote><p>Everyone technically uses Al, as Microsoft Word’s (and Google Docs’) spelling- and grammar- checking features now use artificial intelligence! <em>The Court uses programs</em> to review its syntax, spelling and cohesive structure. Despite the use of these tools, however, the judgment, reasoning and the decision remain the undersigned’s. The promise of the tools is real, and that promise is realized when a human being remains responsible for the result. [emphasis added].</p></blockquote>
<p>The court then turned to careless and dishonest use:</p>
<blockquote><p><em>Each generation of the legal profession has had to master the tools of its day and to guard against their misuse. Dictation machines, the photocopier, the FAX machine, e-mail, electronic research, electronic filing, and, most recently, the remote proceeding. Each started as a novelty that competent practice required one to understand and to use for the client’s benefit while guarding against harm. </em>Competence and caution have always been intertwined. Artificial intelligence is the newest of these tools and among the most powerful, and it asks the same of us, that we marry the enthusiasm to use it with the discipline to watch it closely. [emphasis added].</p></blockquote>
<p>After discussing a recent court AI rule, the <em>Elliot </em>court turned to the facts of the case.  It wrote: “The conduct at issue here, a litigant hiding instructions in their own filing to manipulate the tools that others might use to read it, was not among the dangers we contemplated [in that court rule]. It was hardly imagined at the time. That the Rules do not address this conduct reflects only how quickly the technology and its misuses are moving. That the conduct was not named in the new Rule takes nothing away from the duties of good faith and candor that have always governed those who appear before this Court since long before any of these tools existed.”</p>
<p>While most of the attention regarding misuse of AI has been focused on hallucinated cases, this is different. The court wrote: “That danger looks at what comes out of the machine. The conduct here is deliberate and dangerous <strong>input</strong>, a litigant seeding their own filing so that the output of whatever tool later ingested it would be corrupted in favor of the litigant.” [emphasis in original]. It added:</p>
<blockquote><p>A framework built to catch unreliable output does not, by its nature, reach a filer who manipulates the input, and the verification duty the Connecticut Judicial Branch imposed above, however sound for the danger it was written to address, leaves this one untouched. <strong>But it remains a serious litigation abuse.</strong> The duty of candor to the court and the court’s inherent authority over the integrity of its own proceedings reach it, and requires the court to sanction it. [emphasis in original].</p></blockquote>
<p>The court explained:</p>
<blockquote><p><strong>CONCEALED INSTRUCTIONS (“PROMPT INJECTIONS”) TO AUTOMATED SYSTEMS ARE NOT PERMITTED IN COURT PLEADINGS</strong></p>
<p>What the plaintiff did here was to use that new tool in a dishonest way. A filing is a communication to <u>both</u> the court and the opposing party. Its integrity rests on the simple premise that what the reader sees is what the filer wrote, and that the filer refrains from transmitting, at the same time, a second and hidden message engineered to change how the filing is reviewed or potentially judged.</p>
<p>Text that is invisible to the human eye but planted for a machine to read and obey betrays that premise.</p>
<p>Had the plaintiff wished to address the court’s or an opponent’s potential use of artificial intelligence, they were free to write so in plain, visible words that everyone could see and answer. That they hid the instruction instead is, itself, evidence of its malicious purpose.</p>
<p>The technique has a name, “prompt injection.” [emphasis in original].</p></blockquote>
<p>The opinion described “prompt injection”: “By hiding a command inside a document that the system later ingests, the filer attempts to smuggle their own instruction into that stream so that the system treats it as though it had come from the system’s operator. In this case that operator is presumed to be the court, its staff, or opposing counsel. The object is to capture a tool that a judge, a clerk, or a party might rely upon and to turn it, silently, to the filer’s advantage.”</p>
<p>The <em>Elliot </em>court  viewed prompt injection as a secret communication that opposing counsel could not see.  It analogized it to an ex parte communication.  That is improper because our judicial system rests on the premise of open communication on-the-record.  “It is a concealed communication to those who decide, or to the tools on which they rely, clandestinely pleaded outside the knowledge of the other side and, indeed, the Court, itself.”</p>
<p>In a fascinating passage, the court explained the method and scope of prompt injection in other aspects of society. <em>Id</em>. at *5. It wrote that “the tactic is now everywhere….”  It wrote: “An opponent’s production, a witness statement, an expert report, any incoming document becomes a potential vector to corrupt output.”</p>
<p>The Judge wrote that the court does not use AI to review filings, “so the hidden instruction had no impact on a ruling. The wrong lies in the attempt, the deliberate planting of a concealed directive intended to mislead whatever artificial-intelligence tool ANY reader of the filing might use.”</p>
<p>The<em> Elliot</em> court did not find plaintiff’s explanation credible.  Because the issue was novel, the court relied on its inherent authority. However, it cited a prompt injection decision from Brazil as supportive. As noted above, it translated that decision by using AI.</p>
<p>In conclusion, the court evaluated the factual predicate: “Turning specifically to whether the actions of the plaintiff are sanctionable in this case, the fact that the plaintiff continued to hide messages in new pleadings after receiving notice of this hearing is stunning.”</p>
<p><em>However, the court Elliot expressly relied on principles of proportionality in imposing a sanction</em>.  It rescinded permission to electronically file and mandated paper filing by the plaintiff. That “is a proportionate response to a demonstrated and repeated misuse of e-filing, and it is the narrowest measure that reliably addresses the conduct. It is further not a barrier to the plaintiff’s continued pursuit of this case.”</p>
<p>The court closed by stating: “Nothing in this order prohibits the plaintiff, or any party, from using generative artificial intelligence as an aid in preparing filings, provided the user independently verifies what the tool produces, as Connecticut Practice Book § 4-9(b) requires.”</p>
<p>This blog was initially posted on  <a href="https://edrm.net/author/michaeldberman/">Electronic Discovery Reference Model</a>.</p>
]]></content:encoded>
			</item>
	</channel>
</rss>
