<?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>E-Discovery LLC</title>
	<atom:link href="https://www.ediscoveryllc.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ediscoveryllc.com</link>
	<description>Mediation of E-Discovery Disputes</description>
	<lastBuildDate>Sun, 20 Sep 2026 09:34:48 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Litigant “Doubled Down” When Opponent Found Hallucinations—It Can’t “Amend Them Away”</title>
		<link>https://www.ediscoveryllc.com/litigant-doubled-down-when-opponent-found-hallucinations-it-cant-amend-them-away/</link>
		<pubDate>Sun, 20 Sep 2026 09:34:48 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5574</guid>
		<description><![CDATA[Youssian v. Village of Kings Point, 2026 WL 2795230 (Supreme Ct., Nassau Co., N.Y. Sep. 9, 2026), is an example of what not to do when an opponent points out that you cited hallucinated authorities in your lengthy Petition.  “The 64-page petition was accompanied by a 46-page memorandum of law in support.”<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p><em>Youssian v. Village of Kings Point</em>, 2026 WL 2795230 (Supreme Ct., Nassau Co., N.Y. Sep. 9, 2026), is an example of what not to do when an opponent points out that you cited hallucinated authorities in your lengthy Petition.  “The 64-page petition was accompanied by a 46-page memorandum of law in support.”</p>
<p>Counsel blamed the hallucinations on the use of <a href="https://spellbook.com/">Spellbook AI</a>. On its <a href="https://spellbook.com/">website</a>, Spellbook describes itself as: “The first AI system that powers contracts end-to-end….”</p>
<p>In summary, respondents notified petitioner that they found hallucinated authorities in connection with the Petition. Petitioner denied the allegation, “doubled down,” and counter-punched with a threatening response.</p>
<p>Petitioner later amended the Petition and admitted to hallucinations that it claimed were due to its use of Spellbook AI.  The court imposed monetary sanctions, awarded attorneys’ fees, and <em>struck the amended Petition, </em>writing that, what the court described as “fraud,” cannot be amended away.  The court appeared to leave open the door for a bona fide amendment.</p>
<p style="text-align: center;"><strong><u>THE “GLASS HOUSES” PRINCIPLE</u></strong></p>
<p>Counter-punching may be problematical.  Another court recently advised: “A well-known proverb warns those who live in a glass house not to throw stones. What Plaintiffs did here is worse than that. The proverb assumes a rough parity — two flawed parties, each exposed, the hypocrite merely imprudent for hurling what could be hurled back. That is not what happened here. Plaintiffs did not throw stones from a glass house at another glass house. They stood inside a house made entirely of glass, pointed at the brick house across the street, and declared that structure the fragile one…. Each charge, however, was not merely overstated, but rather exactly backwards.”  <a href="https://www.ediscoveryllc.com/glass-houses-proverb-dont-throw-stones-and-invective/">Glass Houses Proverb—Don’t Throw Stones and Invective</a> (Jul. 14, 2026)(citation omitted).</p>
<p style="text-align: center;"><strong><u>FACTS AND THE COUNTER-PUNCH</u></strong></p>
<p>In this challenge to an administrative decision, the court set the stage as follows:</p>
<blockquote><p>Unfortunately, shortly after commencement, issues regarding the contents of the petition and accompanying memorandum of law became the subject of litigation rather than the underlying merits. The short yet storied history of the case is as follows. On May 15, 2026, <em>counsels for respondents informed counsel for petitioners, Thomas A. Bizzaro, Esq., that the petition and accompanying memorandum of law contained a myriad of false citations to legal authority using artificial intelligence (”AI”).</em> A more detailed description of the hallucinated citations is contained infra. After discovering the AI errors<em>, respondents requested that Mr. Bizzaro respond with an explanation and/or withdraw the petition</em>; otherwise, they would notify the Court and seek sanctions, including striking the pleadings. <em>Mr. Bizzaro responded to counsels with an eight-page letter, the sum and substance of which was a categorical denial. Mr. Bizzaro stated that his firm undertook a full citation audit in response to respondents’ concerns. His firm identified seven issues which were minor citation and misapplication issues and did not involve fabricated authority. Mr. Bizzaro stressed that the errors were inadvertent and that opposing counsels failed to identify any specific erroneous citation.</em> He rejected respondents’ request that he withdraw the petition as well as any threat of sanctions<em>. <strong>In fact, Mr. Bizzaro threatened to seek sanctions and attorney’s fees himself</strong></em>, stating that the unfounded accusations by respondents violated Section 130-1.1 of the NY Compilation of Codes, Rules, and Regulations (”NYCRR”). [emphasis added].</p></blockquote>
<p>The parties agreed to meet and confer. However:</p>
<blockquote><p>Prior to that meeting, Mr. Bizzaro filed a letter to the Court, explaining all of the foregoing and annexing the correspondence between the attorneys. In conclusion, Mr. Bizzaro requested a conference with the Court. Thereafter, the Court learned that the May 18, 2026 meeting between the attorneys was unsuccessful. On May 18, 2026 and May 19, 2026 respondents filed additional letters to the docket, which laid out the purported fraud contained in the petition.</p></blockquote>
<p style="text-align: center;"><strong><u>THE ADMISSION AND DEFECTIVE AMENDED PETITION</u></strong></p>
<p>Respondents demanded withdrawal of the petition.  Mr. Bizzaro refused, offered to pay reasonable attorneys fees, and “informed the respondents he would be filing an amended petition and proceeding with the action….”</p>
<p>After a court conference, Mr. Bizzaro filed an amended petition. However, the court wrote: “A review of the 55 page petition reveals that it is essentially the same petition, which was filed upon commencement, less citation to the purported fraudulent legal authority as well as a few additional minor changes.”</p>
<p>Petitioner’s attorney also wrote to the court and the “letter conceded for the first time that the original petition contained ‘AI-citation errors.’ …  Mr. Bizzaro stated that he offered to reimburse respondents for their reasonable attorneys’ fees and costs in connection with the ‘letter exchanges and virtual conference.’”</p>
<p>Next, “Respondents both informed the Court of their intention to file a motion to strike the pleadings and for sanctions. Mr. Bizzaro responded to the foregoing by filing correspondence on June 2, 2026. Petitioner’s letter argues that there was no prejudice suffered as a result of the citation errors, that the amended petition was filed as a matter of right, and that his offer to reimburse respondents for fees and costs incurred in connection with the letter exchanges and the conference remains.”</p>
<p style="text-align: center;"><strong><u>THE COURT HEARING</u></strong></p>
<p>The court held a hearing:</p>
<blockquote><p>At the hearing, Mr. Bizzaro conceded that the underlying commencement documents contained citations to “hallucinated” quotations. He explained that his firm, of which he is the sole principal, uses Lexis and Westlaw. <em>The subscription to Westlaw contains certain AI tools which are linked to Microsoft Word. The program, “Spellbook AI,” is a tool embedded into Microsoft Word. It was represented to Mr. Bizzaro that the AI-tool enhanced writing and detected drafting errors. He was informed that Spellbook AI did not provide legal authorities or citations to work product, but only enhanced drafting. Mr. Bizzaro reviewed the petition prior to commencement but did not “re-run a cite check,” after accepting the changes made by Spellbook AI.</em> Mr. Bizzaro was apologetic and explained the steps he and his office have taken to ensure this does not happen again. Mr. Bizzaro has discontinued his subscription to Spellbook AI and has changed his office policy so that he is the only individual permitted to use AI features. Additionally, Mr. Bizzaro informed the Court that he has registered with the National Academy of Continuing Legal Education for classes dealing with AI issues in the court system. [emphasis added].</p></blockquote>
<p>The court described the use of AI as “all but unavoidable.”  However, it also wrote, misuse has become a “reoccurring problem….” It found that “petitioners included quotations from at least five otherwise legitimate cases which were either entirely fabricated, or which were altered from their original versions.” It added: “The nationwide imposition of monetary sanctions in similar cases ranges from mere warnings to tens of thousands of dollars….”</p>
<p style="text-align: center;"><strong><u>APOLOGIZING AFTER “DOUBLING DOWN” &amp; COUNTER-PUNCHING</u></strong></p>
<p>Instead of counter-punching, the court suggested that Petitioner should have gone “hat in hand” to Respondents.  The court wrote that, while five citations were inaccurate, the remainder were “legitimate,” and Mr. Bizzaro “apologized at length….”  He had explained the error and taken remedial action.</p>
<p>Nevertheless:</p>
<blockquote><p><strong><em>Importantly, when Mr. Bizzaro was confronted by counsel for respondents about the fabricated cases, he chose to essentially “double down” rather than to admit to the mistake</em>.</strong> Mr. Bizzaro contends that he never denied the use of AI and his response was merely a “preliminary reply under extreme time constraints.” The Court disagrees. The May 16, 2026 response from Mr. Bizzaro was a detailed eight-page letter where counsel argued that there were no fabricated, hallucinated, or erroneous quotations or citations identified by respondents, that he had undertaken a detailed review of all citations, and essentially only identified what he labeled “discrete errors.” Mr. Bizzaro then demanded that respondents identify any inaccuracies and bring them to his attention. <strong><em>Mr. Bizzaro</em></strong><em> concluded by stating that the accusations levied and the threat of sanctions, absent any proof of wrongdoing, <strong>raised an issue of respondents’ good faith and frivolous conduct which</strong> <strong>may warrant an application by him for sanctions and attorney’s fees.</strong></em> The Court mentions the foregoing only to emphasize that Mr. Bizzaro’s time would have been better spent combing his petition, which very well may have eliminated the need for his letter. [emphasis added].</p></blockquote>
<p>It added:</p>
<blockquote><p><em>In any event, what ensued was months of back and forth between the parties, a “meet and confer” with all counsels, extensive letter practice to the Court, two court appearances, and a substantial amount of work undertaken by all parties. <strong>This could have been easily avoided had Mr. Bizzaro acknowledged the fabrications and approached the dispute with hat in hand.</strong></em> Indeed, as discussed supra, <strong><em>Mr. Bizzaro threatened to request sanctions upon the respondents when they broached the issue of these hallucinations. For this reason, the Court finds that Mr. Bizzaro’s conduct was egregious </em></strong>and qualifies as a more significant violation of the Rules of Professional Conduct than it would otherwise. [emphasis added].</p></blockquote>
<p style="text-align: center;"><strong><u>MONETARY AWARD</u></strong></p>
<p>The court awarded a $5,000 sanction plus $10,000 for attorney’s fees, explaining:  “Respondents identified the fabrications, the parties engaged in significant letter practice, which included considerable research, the parties appeared before the Court for a conference on May 19, 2026 and a hearing on July 22, 2026, the respondents filed their respective motions to dismiss the petition and amended petition, and the petitioners filed their opposition papers.”</p>
<p style="text-align: center;"><strong><u>DENIAL OF THE AMENDMENT: CAN’T “AMEND AWAY” HALLUCINATIONS</u></strong></p>
<p>It then turned to a novel issue, specifically, respondents’ dismissal argument—that the original petition was defective and the amended petition was essentially a cut and paste, minus the erroneous citations.</p>
<blockquote><p>Generally, the pleadings rule provides that an amended complaint supersedes the original…. <em>The question is whether this principle should apply where the underlying petition is essentially permeated with fraud and petitioner seeks to amend solely to cure those defects. This Court’s research reveals that this question, under these circumstances, has not been previously addressed. <strong>Specifically: can a petitioner amend his or her pleadings as a matter of right to correct defects in the underlying petition where the allegations contained therein were at least partially based upon hallucinated citations to legal authority? This Court concludes that the principle does not apply where the original pleading is permeated with fraud, and the fraud cannot simply be amended away.</strong></em> [emphasis added].</p></blockquote>
<p>The court found that the first pleading was permeated by fraud. “Petitioners used multiple bogus quotations from the case and submitted a lengthy argument in support based thereon….  Accordingly, after reviewing the cases and the original pleadings, the Court can only conclude that a significant portion of the legal arguments which formed the cornerstone for this specific proceeding were based upon fraudulent legal authority, such that the pleadings were permeated with fraud.”</p>
<p>It then wrote: “<strong><em>The next question the Court must determine is whether petitioners are entitled to amend the petition to remediate the defects. This Court finds that they are not.</em></strong>” [emphasis added].  It cited a prior decision in which the court found sanctionable conduct and rejected a request for a “redo.” It wrote:</p>
<blockquote><p><strong><em>Aside from striking the amended petition as a sanction, the Court finds that permitting the petitioners to “amend away” the fraud here would be an improvident exercise of discretion</em></strong> for two reasons. The first reason is that the fraud and the pleadings are inseparable. This is not a matter where a party merely cited to a few fictitious cases. Rather, a significant foundation of this Article 78 proceeding was premised on the reliance of hallucinated quotations and bogus legal authority. <em>Moreover, the amended petition is essentially a replica of the original petition, less the hallucinated quotations. The amended petition includes assertions premised upon the fabricated legal authority. </em>Second, public policy bars the amended petition from standing. <em>Permitting the amendment would effectively reward careless legal drafting, and allow litigants to include false, misleading, and inaccurate allegations in their pleadings with the expectation that they could simply correct the defects through an amendment.</em> As an aside, this Court also gives credence to the respondents’ argument that permitting the amendment would require the respondents and the Court to essentially “Frankenstein” the 55-page petition to determine which allegations are based in legitimate law and which are not. This is an undue burden that the Court refuses to impose. [emphasis added].</p></blockquote>
<p>The court struck the amended petition, but declined to dismiss with prejudice.  Presumably, this left open the possibility of a new amendment.</p>
<p style="text-align: center;"><strong><u>ONE LAST ISSUE</u></strong></p>
<p>The court addressed one last issue: “In light of the foregoing, the Court need not reach the issue of the assertion that the signatures contained in the amended verified petition were falsely notarized. Briefly, the original verified petition includes a signature of petitioner Bobby Zargari, which was notarized by Mr. Bizzaro’s legal assistant on May 8, 2026. The amended verified petition dated May 20, 2026 is also signed by Zargari and notarized by Mr. Bizzaro’s legal assistant. A side-by-side review of the signatures reveals that they appear to be identical, and <em>at the hearing petitioner admitted to reusing the original signature. </em>Under ordinary circumstances, the Court would have set this matter down for a hearing on this specific issue. However, after reviewing the papers and addressing the matter on the record, the Court declines to render a decision on the issue of fraud regarding the notarization in light of its determination to issue sanctions and strike the petition and amended petition.” [emphasis added].</p>
<p style="text-align: center;"><strong><u>CONCLUSION</u></strong></p>
<p>The denial of the right to amend in <em>Youssian </em>is not a unicorn.  For another decision denying amendment after disclosure of hallucinations, please see <a href="https://www.ediscoveryllc.com/a-request-to-refile-brief-to-correct-hallucinations-was-denied/">A Request to Refile Brief to Correct Hallucinations Was Denied</a> (Aug. 30, 2026)(“we are denying the motion to withdraw the Opening Brief….”).</p>
<p>Sometimes, there is a duty to “’fess up.”  In a different context, please see <a href="https://www.ediscoveryllc.com/is-there-a-duty-to-fess-up-part-ii/">Is There a Duty to “’Fess Up?” – Part II</a> (Nov. 12, 2022).  <a href="https://www.ediscoveryllc.com/lack-of-candor-is-always-a-bad-idea/">Lack of Candor is “Always a bad idea.”</a> (Jul. 13, 2026).</p>
<p>For a discussion of counter-punching in a different context, please see <a href="https://www.ediscoveryllc.com/rule-11-sanctions-for-impugning-character-of-opposing-counsel/">Rule 11 Sanctions for Impugning Character of Opposing Counsel</a> (Apr. 20, 2022); <a href="https://www.ediscoveryllc.com/fraudulent-or-unsupported-allegations-of-misuse-of-a-i-can-be-sanctionable/">Fraudulent or Unsupported Allegations of Misuse of A.I. Can be Sanctionable</a> (Jun. 25, 2026); <a href="https://www.ediscoveryllc.com/conclusory-false-accusations-of-using-false-case-citations-are-sanctionable/">Conclusory (False?) Accusations of Using False Case Citations Are Sanctionable</a> (Apr. 12, 2026).</p>
]]></content:encoded>
			</item>
		<item>
		<title>Defendant’s Discovery Request Relating to Plaintiff’s Alleged Use of A.I. is Denied</title>
		<link>https://www.ediscoveryllc.com/defendants-discovery-request-relate-to-plaintiffs-alleged-use-of-a-i-is-denied/</link>
		<pubDate>Sat, 19 Sep 2026 17:00:45 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Discoverability]]></category>
		<category><![CDATA[Privilege]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5571</guid>
		<description><![CDATA[Defendant made “discovery requests related to Plaintiff’s alleged use of artificial intelligence (‘AI’)….” “Defendant’s motion will be DENIED, for the reasons set forth at the hearing and for Defendant’s failure to adequately support the requests.”  Cifuentes v. SID Tool Col, Inc., 2026 WL 2795597 (M.D. Fla Sep. 18, 2026)(emphasis added). The written<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Defendant made “discovery requests related to Plaintiff’s alleged use of artificial intelligence (‘AI’)….”</p>
<p>“Defendant’s motion will be <strong>DENIED</strong>, for the reasons set forth at the hearing and <em>for Defendant’s failure to adequately support the requests.</em>”  <em>Cifuentes v. SID Tool Col, Inc.,</em> 2026 WL 2795597 (M.D. Fla Sep. 18, 2026)(emphasis added).</p>
<p>The written opinion gave no reasons: “This Order memorializes the rulings made at the hearing.” <em>Id</em>.</p>
<p>The court added: “As discussed with Plaintiff at the hearing, the Court notes that while the use of AI is not prohibited, Plaintiff proceeds at his own peril by using it, such that he undertakes the risks and potential consequences associated with its use. See Fed. R. Civ. P. 11. Plaintiff’s pro se status does not absolve him of the requirement that he fully comply with all applicable Federal Rules of Civil Procedure and Local Rules.”</p>
<p>The hearing transcript was not available on Westlaw or Bloomberg Law.  Bloomberg reports that: “This case arises out of Defendant&#8217;s allegedly ‘discriminatory and retaliatory discipline and termination’ of Plaintiff…. Plaintiff claims that Defendant discriminated against him because of his ‘Hispanic and Middle Eastern ancestry’ and his ‘lifelong neurodevelopmental and anxiety-related disabilities, including [attention-deficit / hyperactivity disorder (ADHD)] and [a]utism / Asperger&#8217;s spectrum traits.’”  <em>Cifuentes v. Sid Tool Co., </em>No. 6:25-cv-1651-JSS-LHP, 2026 BL 262439 (M.D. Fla. July 13, 2026).</p>
<p>For more on discovery related to use of AI, please visit:</p>
<ul>
<li><a href="https://www.ediscoveryllc.com/a-i-privilege-heppner-and-how-did-the-court-learn-about-the-absence-of-certain-attorney-client-communications-between-mr-heppner-and-his-attorneys/">I. Privilege, Heppner, and How Did the Court Learn About the Absence of Certain Attorney-Client Communications Between Mr. Heppner and His Attorneys?</a></li>
<li><a href="https://www.ediscoveryllc.com/a-i-documents-deemed-not-privileged/">I. Documents Deemed Not Privileged</a></li>
<li><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></li>
<li><a href="https://www.ediscoveryllc.com/discovery-permitted-about-development-and-use-of-ai-program/">Discovery Permitted About Development and Use of AI Program</a></li>
<li><a href="https://www.ediscoveryllc.com/does-openai-provide-legal-assistance/">Does OpenAI Provide Legal Assistance?</a></li>
<li><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></li>
<li><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></li>
<li><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></li>
<li><a href="https://www.ediscoveryllc.com/upload-of-documents-to-anthropic-products-leads-to-denial-of-motion-to-seal-record/">Upload of Documents to Anthropic Products Leads to Denial of Motion to Seal Record</a></li>
</ul>
]]></content:encoded>
			</item>
		<item>
		<title>Unsupervised Self Collection—The Fox Guarding the Chicken Coop—Leads to Discovery on Discovery</title>
		<link>https://www.ediscoveryllc.com/unsupervised-self-collection-the-fox-guarding-the-chicken-coop-leads-to-discovery-on-discovery/</link>
		<pubDate>Sat, 19 Sep 2026 14:36:58 +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[Conference of Parties]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Discoverability]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[information governance]]></category>
		<category><![CDATA[Self Preservation]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5569</guid>
		<description><![CDATA[The plaintiff in EEOC v. Yas Caribe, Inc., 2026 WL 2593286 (D.P.R. Sep. 2, 2026), alleged “that defendants subjected Ms. Wilkerson to a hostile work environment and constructively discharged her after an incident involving Khalid Yassin, the pharmacy manager.”  Id. at *9.  Defendants denied the allegations.  After outlining the discovery disputes, the<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>The plaintiff in <em>EEOC v. Yas Caribe, Inc.,</em> 2026 WL 2593286 (D.P.R. Sep. 2, 2026), alleged “that defendants subjected Ms. Wilkerson to a hostile work environment and constructively discharged her after an incident involving Khalid Yassin, the pharmacy manager.”  <em>Id</em>. at *9.  Defendants denied the allegations.  After outlining the discovery disputes, the court wrote:</p>
<blockquote><p>What follows is a somewhat lengthy Opinion, which the Court deemed prudent to write in order to reaffirm the duties incumbent on parties and their attorneys during the discovery process, especially in the context of electronic discovery.</p></blockquote>
<p>In <em>Yas Caribe,</em> eight requests for production and four interrogatories were in dispute.  The issue that this blog post focuses on is unsupervised self-collection by Defendants.  “[T]he EEOC highlights that several of its document requests entailed the collection of ESI, but maintains that defendants’ collection efforts were unsupervised by counsel and demonstrably incomplete.”</p>
<p style="text-align: center;"><strong><u>WERE DEFENDANTS’ SELF-COLLECTION EFFORTS SUFFICIENT?</u></strong></p>
<p style="text-align: center;"><em><u>The Parties’ Contentions</u></em></p>
<p>EEOC challenged the sufficiency of Defendants’ search for documents.  Abdullah Yassin admitted that he failed to preserve ESI and failed to review his own the electronic devices, including email and texts, or those of Khalid Yassin, the alleged harasser.  Further, he had not directed any of his employees to do so.  And, the EEOC claimed “that deposition testimony revealed that relevant personnel files and employment-related documents may be stored in the offices of a non-party entity owned and operated by Abdullah Yassin, called Yassin Unlimited Drug Corp. d/b/a Droguería San Juan,” and none of this stored information had been disclosed. <em>Id</em>. at *5.</p>
<p>The EEOC sought two types of relief. <em>First</em>, it asked that “Defendants be required to amend all of their Responses to EEOC’s [document requests] to clearly state: (1) whether responsive documents exist; (2) what steps were taken to locate responsive documents; (3) whether any documents are being withheld.”  <em>Second</em>, it asked for forensic inspection of the cell phones of Abdullah Yassin and Khalid Yassin, and a re-opening of discovery.</p>
<p>Defendants responded that Abdullah Yassin testified that he had not deleted anything and had no responsive documents.  They asserted that the messages EEOC relied on to show insufficient production had eventually been produced.  Further “defendants produced a ‘Messages Search Certification’ subscribed by Abdullah Yassin to the effect that he personally supervised Khalid Yassin’s search of his cellphone for responsive messages exchanged with Ms. Wilkerson, and further produced three responsive pages.”  Finally, in what I suggest is an incorrect position:</p>
<blockquote><p>[D]efendants’ attorney argued in response to the motion to compel that directly supervising any search for responsive documents in his client’s files would make him a “potential witness” and would be “ethically inappropriate.”</p></blockquote>
<p>The EEOC challenged the sufficiency of the “Messages Search Certification” and it had obtained the messages independently from Ms. Wilkerson, not from Defendants. <em>Id</em>. at *10-11.</p>
<p style="text-align: center;"><em><u>Discovery on Discovery</u></em></p>
<p>There was a threshold issue.  The court described the EEOC’s position as a request for “discovery on discovery.”  This is sometimes called “satellite discovery” or “culpability discovery.”  The court enunciated several principles governing that process.</p>
<p>“Discovery on discovery has been described broadly as ‘any discovery seeking information regarding a party’s preservation, collection, and retention efforts.’ …  Although some trial courts have considered these types of discovery requests to be outside the scope of Rule 26(b)(1), others have not.” <em>Id</em>. at *6 (citations omitted).  The court continued:</p>
<blockquote><p><em>In any case, the general structure of the discovery process drawn into the Federal Rules of Civil Procedure strongly implies that such discovery should be the exception, not the rule.</em> “The federal discovery system in some ways resembles an ‘honor system,’ ” where the party seeking discovery “must generally ‘rely on the representations of the producing party or its representative that it is producing all responsive, relevant, and non-privileged discovery&#8230;.’  Casting doubt on a responding party’s efforts to provide full and complete discovery responses is by no means taboo, <em>but anyone attempting to obtain a remedy on that ground must overcome the default assumption of good-faith compliance.</em> <em>This is even more so when the attempted second-order discovery targets a person’s electronic systems or devices</em>….”</p></blockquote>
<p><em>Id</em>. (emphasis added; citations omitted).  Here, however, the threshold was crossed.  For more information about “discovery on discovery,” please see the citations at the end of this post.</p>
<p style="text-align: center;"><em><u>Defendants’ Efforts Were Insufficient</u></em></p>
<p>The court wrote: “Defendants’ initially deficient response to the document request and Abdullah Yassin’s deposition testimony as to the inadequacy of his search raise substantial doubts as to defendants’ compliance with their discovery obligations.”</p>
<p>While a single missing text message does not normally justify discovery on discovery, <em>id</em>. at *11, here there was also testimony that Abdullah Yassin had failed to preserve and collect documents related to the alleged harassment, had failed to search his own email and text messages, had failed to search the electronic devices of relevant custodians, including the alleged harasser, and had not instructed anyone else to do so.  <em>Id</em>. at *11.  Further, while the EEOC had suggested search terms that the court viewed as reasonable, “Defendants did not describe what, if any, search terms they used to find responsive documents….” <em>Id</em>.</p>
<p style="text-align: center;"><em><u>Self-Collection Should Be Supervised by Counsel</u></em></p>
<p>With limited exception, the requirement that an attorney supervise a client’s collection is well established:</p>
<ul>
<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>
<li>Losey, “Another ‘Fox Guarding the Hen House’ Case Shows the <a href="https://e-discoveryteam.com/2011/03/20/another-fox-guarding-the-hen-house-case-shows-the-dangers-of-self-collection/">Dangers of Self-Collection</a>” (Mar. 20, 2011).</li>
</ul>
<p>There is contrary authority, which may be limited to a situation where there is no indication that relevant information has gone missing. <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).</p>
<p>Further, there are defensible ways to conduct self-collection.  <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). However, that method was not used in <em>Yas Caribe.</em></p>
<p style="text-align: center;"><em><u>Defendants’ Attorney’s Argument That Supervising a Search Would be Improper</u></em></p>
<p>Defendants’ attorney in <em>Yas Caribe</em> wrote:</p>
<blockquote><p>It is my understanding that being with a witness while s/he searches for the requested records, explaining to the witness what is requested, verifying that the information is pertinent to the request, and asking the witness to produce everything he has, complies with a “reasonable inquiry” requirement. Otherwise, a counsel’s active search for those records will make a counsel a potential witness if a client misses a text message or for any other reason. I believe that my discussing every question or discovery request with my witnesses, while they are answering, producing documents, or giving instructions to their secretaries or assistants to look for and produce exactly what was asked for, is involvement that complies with Rule 26(g)&#8230;. And how would I remember what I saw? How would I know if they are showing me everything, or if messages were deleted, or if they have changed telephones? &#8230; Still, I believe it is inappropriate for me to get involved in the witnesses’ telephones, computers, etc., beyond what I already have.</p></blockquote>
<p>As noted above, he argued that supervising his client’s collection would make him a “potential witness” and that it would be “ethically inappropriate.”  <em>Id</em>. at *6.  In my opinion—and more importantly, the court’s opinion—he was incorrect.</p>
<p style="text-align: center;"><u>Supervising a Client’s Search Does Not Make an Attorney a Witness</u></p>
<p>In response to the argument that supervision would make the attorney a witness, the court wrote: “The Court first notes that neither supervising nor assisting a clients’ document search converts an attorney into a witness in a case. In fact, such supervision may be required in appropriate circumstances….  Indeed, the existence, relevance, and discoverability of ESI is one such circumstance that counsels in favor of attorneys exercising diligent supervision over their clients’ efforts to comply with discovery requests….”</p>
<p>Quoting a prior decision,<a href="#_ftn1" name="_ftnref1">[1]</a> it added: “Attorneys have a duty to oversee their clients’ collection of information and documents, especially when ESI is involved, during the discovery process. Although clients can certainly be tasked with searching for, collecting, and producing discovery, it must be accomplished under the advice and supervision of counsel, or at least with counsel possessing sufficient knowledge of the process utilized by the client. Parties and clients, who are often lay persons, do not normally have the knowledge and expertise to understand their discovery obligations, to conduct appropriate searches, to collect responsive discovery, and then to fully produce it, especially when dealing with ESI, without counsel’s guiding hand.”</p>
<p>Of course, where there is a prima facie showing of spoliation, an attorney may be compelled to disclose how the litigation hold was implemented and how the search was conducted. The Hon. Paul W. Grimm, M. Berman, <em>et al.,</em> “Discovery About Discovery Does the Attorney-Client Privilege Protect All Attorney-Client Communications Relating to the Preservation of Potentially Relevant Information?,” 37 U.Balt.L.Rev. 413 (2008).</p>
<p style="text-align: center;"><u>Failure to Supervise May Run Afoul of Fed.R.Civ.P. 26(g)</u></p>
<p>The <em>Yas Caribe</em> court also looked to Fed.R.Civ.P.26(g), the so-called “stop and think” rule:</p>
<blockquote><p>As to Attorney Mihailovich’s compliance with Rule 26(g)(1)’s reasonable inquiry requirement, his position warrants discussion. As mentioned above, <em>Rule 26(g)(1) imposes on the signer</em> of a discovery request, response, or objection <em>a duty</em> to perform a “reasonable inquiry.” Fed. R. Civ. P. 26(g)(1)….  In the case of a response to a document request, <em>this duty falls squarely on the attorney, </em>whereas interrogatory responses must be signed by both the attorney and the person who answers them. Fed. R Civ. P. 26(g)(1), 33(b)(5). [emphasis added].</p></blockquote>
<p>The <em>Yas Caribe</em> court added: “An attorney’s failure to adequately guide and supervise a client’s search for responsive ESI may run afoul of Rule 26(g).”  Quoting a prior decision, it wrote: “[A]n attorney cannot abandon his professional and ethical duties imposed by the applicable rules and case law and permit an interested party or person to ‘self-collect’ discovery without any attorney advice, supervision, or knowledge of the process utilized.”</p>
<p style="text-align: center;"><em><u>Application of Principles to Facts Presented</u></em></p>
<p>The court had little trouble rejecting the attorney’s argument on the facts presented:</p>
<blockquote><p>In this case, such supervision was objectively warranted. Abdullah Yassin testified that he did not perform an adequate search for responsive documents, even when his attorney represented that he was “with a witness while s/he searches for the requested records, explaining to the witness what is requested, verifying that the information is pertinent to the request, and asking the witness to produce everything he has &#8230;.”</p></blockquote>
<p>While, in making an inquiry, the court wrote that an attorney may rely on assertions of the client, that is permissible only “‘as long as that reliance is appropriate under the circumstances.’ 1983 Advisory Committee Notes to Rule 26(g).”  The court added:</p>
<blockquote><p>A discovery request for ESI in a party’s cellphones and computer systems is a circumstance that triggers an attorney’s need to, at a minimum, understand how a client stores and uses ESI and how and where the client is searching for responsive documents.</p>
<p>As officers of the court, attorneys have a duty to make legally sound arguments and good-faith factual representations to the court. If an attorney does not have sufficient information to know whether his client is being accurate or not in a discovery response, particularly one involving ESI, this duty requires that he or she inquire deeper. “[T]he ethical rules now require attorneys to be competent with technologies such as ESI.” <em>City of Rockford v. Mallinckrodt ARD Inc.</em>, 326 F.R.D. 489, 492 n.2 (N.D. Ill. 2018) (citing Model Rules of Pro. Conduct r. 1.1, comment 8 (A.B.A.)).<a href="#_ftn2" name="_ftnref2">[2]</a> <em>Attorney Mihailovich should have assumed a more active role in guiding defendants’ search beyond what he described in the opposition to the motion to compel. At the very least, he should have inquired into how and where the searches were being made so that he could give a reasonably informed certification of the thoroughness of what sources were and were not searched. Ideally, he would have discussed and run the keyword searches proposed by the EEOC or a mutually agreed upon version of them.</em> Judging from the subsequent interactions of the parties that are on record, defendants’ position has been to engage in piecemeal corrections to their deficient responses and only when specific deficiencies are revealed by the EEOC’s efforts. This is not the way. [emphasis added].</p></blockquote>
<p>The court provided “an admittedly extreme example: when attorneys receive documents that have been redacted by their clients and do not know what has been redacted, they cannot responsibly certify that the factual basis for a disclosure is compliant with Rule 26(g)(1).”</p>
<p>The court added that perfection is not the standard of review.  Instead, review is under an objective standard similar to Rule 11.</p>
<p style="text-align: center;"><strong><u>CONCLUSION</u></strong></p>
<p>Applying principles of proportionality, the court considered privacy interests related to a forensic copy of the cell phones, and concluded that the burden would outweigh the benefits:</p>
<blockquote><p>While there is certainly a well-founded suspicion that an adequate search was not carried out, and that defendants thus failed to comply with their discovery obligations, that does not necessarily mean that defendants are withholding responsive documents. After all, defendants represented that they had no messages between Abdullah and Khalid Yassin about Ms. Wilkerson or the alleged sexual harassment incident…, and the messages subsequently produced by defendants matched those in possession of the EEOC. In other words, there is no indication that, as of today, defendants have willfully withheld responsive documents or incurred in spoliation—only that they have not adequately searched for documents that may exist relating to the alleged sexual harassment incident at the center of the EEOC’s complaint.</p></blockquote>
<p>As such, the request for a forensic inspection was taken “off the table for now” and the EEOC’s alternative request to compel Defendants to run supervised searches was granted.  For example, “defendants are <strong>ORDERED</strong> to perform an attorney-supervised search of both Abdullah Yassin and Khalid Yassin’s cellphones for responsive communications (email, text messages, call logs, etc.) across all relevant e-mail and messaging platforms/applications for [specified] periods….” As to one search, the response must include “the persons assisting in said searches….”</p>
<p>While the <em>Yas Caribe</em> court addressed several other issues, it stands for the principle that unsupervised self-collection is insufficient, at least where there is a factual predicate showing that the searches were insufficient.</p>
<p>For more information on “discovery on discovery,” please visit:</p>
<ul>
<li><a href="https://www.ediscoveryllc.com/the-case-of-the-missing-lab-notebooks/">The Case of the Missing Lab Notebooks</a> (Aug. 28, 2026);</li>
<li><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.” – E-Discovery LLC</a> (Feb. 19, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/discovery-on-discovery-ordered-after-amazons-flawed-implementation-of-litigation-hold/">“Discovery on Discovery” Ordered After Amazon’s Flawed Implementation of Litigation Hold</a> (Oct. 15, 2025);</li>
<li><a href="https://www.ediscoveryllc.com/limited-discovery-on-discovery-permitted-judicial-definitions-of-hit-report-and-families-held-unnecessary/">Limited “Discovery on Discovery” Permitted; Judicial Definitions of “Hit Report” and “Families” Held Unnecessary</a> (Oct. 13, 2025);</li>
<li><a href="https://www.ediscoveryllc.com/discovery-on-discovery-permitted/">“Discovery on Discovery” Permitted</a> (Sep. 4, 2025);</li>
<li><a href="https://www.ediscoveryllc.com/guidelines-for-discovery-on-discovery/">Guidelines for “Discovery on Discovery”</a> (Aug. 5, 2025);</li>
<li><a href="https://www.ediscoveryllc.com/request-for-discovery-on-discovery-was-overbroad-uber-deponent-was-ordered-to-bring-uber-laptop-to-deposition-discovery-about-uber-information-governance-training-resolved/">Request for “Discovery on Discovery” Was Overbroad; Uber Deponent Was Ordered to Bring Uber Laptop to Deposition; Discovery About Uber Information Governance Training Resolved </a>(Jul. 4, 2025);</li>
<li><a href="https://www.ediscoveryllc.com/google-avoids-discovery-on-discovery-based-on-insufficient-foundation-for-request/">Google Avoids Discovery on Discovery Based on Insufficient Foundation for Request</a> (De. 18, 2024);</li>
<li>The Hon. Paul W. Grimm, M. Berman, <em>et al.,</em> “Discovery About Discovery Does the Attorney-Client Privilege Protect All Attorney-Client Communications Relating to the Preservation of Potentially Relevant Information?,” 37 U.Balt.L.Rev. 413 (2008).</li>
</ul>
<p>This blog was initially posted on  <a href="https://edrm.net/author/michaeldberman/">Electronic Discovery Reference Model</a> and  <a href="https://www.jdsupra.com/authors/michael-berman/">JD Supra</a>.</p>
<p>____</p>
<p><a href="#_ftnref1" name="_ftn1">[1]</a> For a discussion of the prior decision, please see <a href="https://www.ediscoveryllc.com/unsupervised-self-collection-predictably-led-to-problems/">Unsupervised Self-Collection Predictably Led to Problems</a> (Jan. 2021).</p>
<p><a href="#_ftnref2" name="_ftn2">[2]</a> For an update on the ethical duty of “technological competence,” please see <a href="https://www.ediscoveryllc.com/40th-state-adopts-a-duty-of-technological-competence-is-it-a-good-idea/">40th State Adopts a Duty of Technological Competence – Is It a Good Idea?</a> (Mar. 31, 2022); <a href="https://www.ediscoveryllc.com/proposed-changes-to-the-md-attorneys-rules-of-professional-conduct-re-ai/">Proposed Changes to the MD Attorneys’ Rules of Professional Conduct Re: AI</a> (Jul. 21, 2026).</p>
]]></content:encoded>
			</item>
		<item>
		<title>Search for Board of Director Documents from 1985 Ordered in Environmental Lawsuit</title>
		<link>https://www.ediscoveryllc.com/search-for-board-of-director-documents-from-1985-ordered-in-environmental-lawsuit/</link>
		<pubDate>Fri, 18 Sep 2026 09:35:04 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[Discoverability]]></category>
		<category><![CDATA[Litigation Hold: Proportionality]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5561</guid>
		<description><![CDATA[The State of Maryland and intervening plaintiffs sued W.L. Gore &#38; Associates, Inc. They alleged contamination of natural resources with toxic substances—specifically, “PFAS.” “Pending before the Court is a discovery dispute concerning Gore’s production of Board of Directors information.”  State v. W.L. Gore &#38; Associates, Inc,. 2026 WL 2730156 (D. Md. Sep.<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>The State of Maryland and intervening plaintiffs sued W.L. Gore &amp; Associates, Inc. They alleged contamination of natural resources with toxic substances—specifically, “PFAS.”</p>
<p>“Pending before the Court is a discovery dispute concerning Gore’s production of Board of Directors information.”  <em>State v. W.L. Gore &amp; Associates, Inc,.</em> 2026 WL 2730156 (D. Md. Sep. 16, 2026)(Aslan, J.).</p>
<p>Pursuant to an initial Court order directing Gore to search Board of Directors minutes “that are available in electronic form,” “Gore searched Board of Directors minutes from 2020 onwards and produced 15 sets of minutes and 41 additional Board documents.”</p>
<p>That production led to another dispute, with the Court writing that “the State and Gore again raised the issue of the sufficiency of Gore’s production, each contending that the limited production demonstrated why additional discovery specific to the Board of Directors is or is not required.”  Plaintiffs sought discovery from 1985.</p>
<p>The parties disputed the governing standard: “As a threshold matter, the State and Gore dispute the standard and burden governing analysis of the sufficiency of Gore’s production.”</p>
<p>“The State argues that as the party resisting discovery, Gore bears the burden of demonstrating that the requested discovery falls outside the scope of Rule 26, and that Gore has not articulated any burden associated with locating these records, assessing their volume, or reviewing their contents.” <em>Id</em>. at *2 (cleaned up).</p>
<p>“On the other hand, Gore contends that the State has the burden of showing how even more discovery into sensitive Board documents would not be duplicative or cumulative of the discovery already produced in this case….”  <em>Id</em>.</p>
<p>The Court rejected Gore’s position:  “Gore relies on an out-of-circuit decision for the proposition that parties seeking searches of additional custodians beyond those initially disclosed must demonstrate that the additional requested custodians would provide <em>unique </em>relevant information by providing evidence that there are unique responsive documents being missed in the current search scheme that would justify the inclusion of additional custodians.” <em>Id</em>. (cleaned up; emphasis in original).</p>
<p>The Court held that the out-of-circuit authority was distinguishable. It related to motions to compel production of ESI from additional custodians.  The <em>Gore</em> Court wrote: “In contrast, the question here is whether Gore must search Board of Directors materials specifically, as opposed to relying on other searches of negotiated terms and custodians.”  <em>Id</em>. at *2.</p>
<p>As to relevance, the Court noted that the PFAS-related documents requested were “certainly relevant….”  It explained that relevance “is not, on its own, a high bar.” <em>Id</em>.</p>
<p>As to proportionality, “the issues at stake in this action and the amount in controversy are significant.”  The Court wrote: “The question of the burden or expense of conducting an independent search of Board of Directors information is unclear. Gore does not address this issue in its filings, but represented at a prior discovery hearing that it was not relying on undue burden to resist production of Board of Directors information.”</p>
<p>The Court also wrote:</p>
<blockquote><p>Throughout the history of this dispute, Gore has argued that the sensitivity of the Board minutes, the decades-long timeframe, and the asserted cumulative nature of the discovery render a separate Board of Directors information search inappropriate…. These arguments are unpersuasive. First, the existing confidentiality order … will protect the sensitivity of the Board of Directors materials. Second, the timeframe in question is less than the “50 years” … originally contemplated because, by way of compromise, the State has asked Gore to search hard-copy Board of Director minutes back to 1985 to “target the most highly relevant information” &#8230; <em>When evaluating the proportionality of this 35-year timeframe, the undersigned notes that the State alleges that Gore released “PFAS into Maryland for more than 50 years.” &#8230;</em> <em>Discovery in this action will therefore necessarily encompass a broad timeframe</em>. [emphasis added].</p></blockquote>
<p>The Court rejected Gore’s argument concerning cumulative, duplicative discovery:</p>
<blockquote><p>To the extent that Gore relies on Federal Rule of Civil Procedure 26(b), the undersigned concludes that the Board of Directors information is not “cumulative or duplicative” and that the State has not “had ample opportunity to obtain the information by discovery.” Fed. R. Civ. P. 26(b)(2)(C)(i)-(ii). By Gore’s own admission, the targeted pilot search [from 2020] of electronic Board of Directors minutes resulted in the production of 15 sets of minutes and 41 additional responsive documents…. Following review of the parties’ filings, the undersigned cannot conclude that such information is needlessly cumulative of other discovery.</p></blockquote>
<p><em>Id</em>. at *3. The Court ordered that “Gore will search its Board of Directors minutes and other related information for the time period of 1985 through 2019 and produce any documents responsive to the State’s Request for Production No. 23” and that the parties meet and  confer regarding the time for production and any related issues.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Be Careful What You Ask For – Document Dump Deemed Permissible Response Under Criminal Rules</title>
		<link>https://www.ediscoveryllc.com/be-careful-what-you-ask-for-document-dump-deemed-permissible-response-under-criminal-rules/</link>
		<pubDate>Thu, 17 Sep 2026 09:26:59 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Cooperation]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5554</guid>
		<description><![CDATA[Mr. Thomas was convicted of conspiracy to commit misconduct in office and accessory before the fact to misconduct in office.  One issue presented on appeal was whether the prosecution had committed a discovery violation by providing an entire Cellebrite extraction report without indicating which parts were pertinent. The trial and Appellate Court<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Mr. Thomas was convicted of conspiracy to commit misconduct in office and accessory before the fact to misconduct in office.  One issue presented on appeal was whether the prosecution had committed a discovery violation by providing an entire Cellebrite extraction report without indicating which parts were pertinent. The trial and Appellate Court both held that there was no discovery violation.  <em>Rogers v. State</em>, 2026 WL 2686590 (Appl. Ct. Md. Sep. 14, 2026)(unreported).</p>
<p>The issue as framed by Mr. Thomas was: “Did the trial court err in admitting cell phone download reports which had not been disclosed in discovery?”</p>
<p style="text-align: center;"><strong><u>PRE-TRIAL FACTS</u></strong></p>
<p>Mr. Thomas was incarcerated on a different charge.  While incarcerated he had a sexual relationship with a correctional officer, Ms. Rivera.  He “was also informed that inmates are not allowed to have a personal cell phone on their person within MCCF because it poses a security risk.”</p>
<p>Officers entered his cell and: “When the officers entered the cell, Appellant threw an item into the toilet, which was found to be a cell phone.”</p>
<p>The Court explained: “The cell phone was recovered, and its contents were extracted and downloaded. The extraction revealed that the phone was set up on October 7, 2019. The cell phone&#8217;s contents showed that Appellant had called Ms. Rivera more than one hundred times.”</p>
<p>Further: “Detective Bullock listened to Appellant&#8217;s phone calls and concluded that in some calls Appellant and Ms. Rivera discussed acquiring a cell phone, expressed their love for each other, and discussed plans to meet up. Additionally, in one phone call, Ms. Rivera referred to putting something in her shoes on October 15, 2019, and she told Appellant that she bought him Under Armour clothing, which other witnesses testified is contraband because Under Armour clothing cannot be purchased at the MCCF commissary.”</p>
<p style="text-align: center;"><strong><u>TRIAL TESTIMONY &amp; OBJECTIONS</u></strong></p>
<p>“The State called Detective Michael Zito, of the Montgomery County Police Electronic Crimes Unit, to testify as an expert in digital forensics. Detective Zito examined devices in the case, including a phone with the number 240-805-3864. Detective Zito testified to a report generated from ‘PurpleBuddy activation and run times’ which has to do with setting up a device.”</p>
<p>Defense counsel objected: “I just, I&#8217;ve never received that actual report and I would like a minute to review it. I don&#8217;t know if the expert is –….  I never received the report in discovery.”  The objection was overruled.</p>
<blockquote><p>After the State offered the document into evidence, Appellant asked to <em>voir dire</em> the witness about the document on the record. Appellant confirmed that the document was provided to the State several weeks prior to trial, and then renewed the objection “based on failure to disclose.” The trial court overruled the objection and received the exhibit into evidence.</p>
<p>The State then offered a report containing user accounts on the device. Appellant again objected claiming that he had “never been provided this report.” The State responded that “the entire Cellebrite user report was provided” to Appellant. The trial court then admitted the exhibit.</p>
<p>When the State attempted to enter another set of images generated from the same report, Appellant&#8217;s counsel stated that she had “never been provided that before” and asked to <em>voir dire</em> the witness or see the exhibit.</p></blockquote>
<p>The State disagreed with the objection:</p>
<blockquote><p>The State responded that it had provided “the complete Cellebrite Reader Report used by the expert containing all of the possibile [sic] data[.]” During a bench conference, the State clarified that it had supplied the defense the entire file, which was “approximately four gigabytes.” The trial court allowed Appellant to review the documents before cross-examining the witness and overruled Appellant&#8217;s objection to the admission of the various documents into evidence.</p>
<p>As the direct proceeded, Appellant continued to object to the cell phone download records, which were each overruled in turn by the trial court.</p></blockquote>
<p style="text-align: center;"><strong><u>APPELLATE ISSUES</u></strong></p>
<p>Mr. Thomas “argues that the trial court erred when it admitted the various cell phone download reports because Appellant claims that the State did not disclose the reports in discovery. Appellant argues that the trial court should have determined if there was a discovery violation, and its failure to exercise that discretion constituted an abuse of discretion.”</p>
<p>“The State … claims that the entire extraction report with all the contents of the cell phone was disclosed, and the State had no burden beyond that to disclose what specific portions of the extraction it would be entering into evidence.”</p>
<p>“Under Maryland Rule 4-263, the State is required to ‘exercise due diligence to identify all of the material and information that must be disclosed under this Rule.’ Md. Rule 4-263(c)(1). Part of the State’s disclosure requirements includes ‘[t]he opportunity to inspect, copy, and photograph all documents, computer-generated evidence as defined in Rule 2-504.3(a), recordings, photographs, or other tangible things <em>that the State&#8217;s Attorney intends to use at a hearing or at trial</em>.’ Md. Rule 4-263(d)(9).” [emphasis added].</p>
<p style="text-align: center;"><strong><u>THE BROAD DISCOVERY REQUEST</u></strong></p>
<p>In discovery, Mr. Thomas requested that the State produce “any books, papers, documents, recording or photographs which the State intends to use at a hearing or trial.”</p>
<p>On appeal, he argued “that there was a discovery violation because the State failed to disclose what specific portions of the extraction report the State would use as exhibits in the trial.”</p>
<p>The Court wrote:</p>
<blockquote><p><em>However, the discovery rules do not require disclosing the portions of the discovery materials that the State will emphasize or enter in trial.</em> The rule only requires that the State provides the “opportunity to inspect &#8230; all documents &#8230; that the State&#8217;s Attorney intends to use &#8230; at trial.” Md. Rule 4-263(d)(9). The State complied with that requirement when it turned over the full discovery of the cell phone records…. To require the State to point to the particular pages of an extraction report it plans to enter into evidence would approach a request for the State&#8217;s “trial strategy,” which is specifically exempted from disclosure under the discovery rules. Md. Rule 4-263(g)(1)(A). [emphasis added].</p></blockquote>
<p>The Court held: “Given that the State provided all the material from the Cellebrite extraction report to Appellant prior to trial, there was no discovery violation. Thus, the trial court did not abuse its discretion in concluding that there was no discovery violation and in admitting the reports into evidence.”</p>
<p>See generally <a href="https://www.ediscoveryllc.com/discovery-from-cell-phones-differing-civil-and-criminal-protocols-in-maryland/">Discovery From Cell Phones – Differing Civil and Criminal Protocols in Maryland</a> (Nov. 14, 2022).</p>
]]></content:encoded>
			</item>
		<item>
		<title>Standing Order 2026-04 re: Electronic Devices in Courthouse</title>
		<link>https://www.ediscoveryllc.com/standing-order-2026-04-re-electronic-devices-in-courthouse/</link>
		<pubDate>Wed, 16 Sep 2026 21:02:14 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[News Stories]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Computer Usage Policies]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5556</guid>
		<description><![CDATA[The U.S. District Court for the District of Maryland has issued Standing Order 2026-04 re: Electronic Devices in Courthouse. The Court’s email lists a number of exceptions, including “Members of the Bar of the District of Maryland, pro hac vice attorneys, and counsel of record in scheduled proceedings, who must present an<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>The U.S. District Court for the District of Maryland has issued <a href="https://www.mdd.uscourts.gov/sites/mdd/files/2026-04.pdf">Standing Order 2026-04</a> re: Electronic Devices in Courthouse.</p>
<p>The Court’s email lists a number of exceptions, including “Members of the Bar of the District of Maryland, pro hac vice attorneys, and counsel of record in scheduled proceedings, who must present an electronic bar membership credential to court security personnel upon entry to the courthouse.  Attorneys authorized to practice will receive an email with instructions on obtaining their electronic bar credential.”</p>
<p>After listing those exceptions, it adds: “Excepted individuals other than those listed above, including accompanying members of an attorney’s staff, pro se litigants appearing for a scheduled proceeding, members of the media, and individuals with a special need, may obtain prior permission to bring an electronic device into the courthouse through the <a href="https://links-2.govdelivery.com/CL0/https:%2F%2Fwww.mdd.uscourts.gov%2Fcontent%2Felectronic-device-request/1/010101a0abed18af-4a33e275-cbcb-49e0-98d3-8982ce241a2b-000000/wLi8u6s2ne-nWRtXUAbrmR1odRvXfxxvJ715IiEB6Bg=452">Electronic Device Request form</a> on the Court’s website.”</p>
<p>Members of the Bar and staff may use the devices in witness conference rooms and attorney lounges. Use is prohibited inside courtrooms and in the presence of jurors outside of courtrooms.  Use is limited to that necessary to conduct court business.  Self represented litigants may request permission.</p>
<p>Counsel of record and their staff may use devices in courtrooms while at counsel table (unless ordered otherwise) provided that they are silent and not used for prohibited activity under Local Rule 506.</p>
<p><em>Clients are not considered staff and: “Excepted attorneys are responsible for advising their clients that the possession of portable electronic devices in the courthouse is generally prohibited.”</em></p>
<p>“Portable electronic devices” include laptop computers, cell phones, electronic tablets, cameras, smart watches, smart glasses, “and any other instruments capable of photograph, video recording, audio recording, or wireless communications (including earpieces and fitness trackers).”</p>
<p>Visitors permitted to bring devices into the courthouse “must keep these devices out of sight and either powered down or in silent mode….”</p>
<p>Visitors with special or disability-related needs, such as for medical monitoring purposes or to control hearing aids, must obtain limited authorization from the Clerk’s Office.</p>
<p>There are multiple exceptions for certain federal officials, jurors (with limitations), the news media and others.</p>
<p>The Court will provide lock boxes for excluded devices.  The order will take effect on November 2, 2026.</p>
<p>UPDATE: I. Round, <a href="https://thedailyrecord.com/2026/09/17/maryland-federal-court-tightens-cellphone-restrictions/?utm_term=Read%20More%20%5Cu2192&amp;utm_source_platform=Act-On%2BSoftware&amp;utm_campaign=DOJ%20blames%20ICE%20for%20%27sloppy%20recordkeeping%27%20on%20Baltimore%20facility%20overcrowding&amp;utm_medium=email&amp;ActOnUniqueID=MDDR151319&amp;utm_content=email&amp;utm_source=Act-On%2BSoftware">Phones further restricted in MD federal court under new order &#8211; Maryland Daily Record</a> (Sep. 17, 2026).</p>
]]></content:encoded>
			</item>
		<item>
		<title>Another AI Protective Order</title>
		<link>https://www.ediscoveryllc.com/another-ai-protective-order/</link>
		<pubDate>Wed, 16 Sep 2026 13:46:12 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[Commercial Litigation]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[Important Posts]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Cooperation]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5549</guid>
		<description><![CDATA[The following Stipulated Protective Order was entered in Rapacon v. Abbott  Laboratories, 2026 WL 2722543 (N.D. Cal. Sep. 15, 2026): USE OF GENERATIVE AI TOOLS “CONFIDENTIAL” Information or Items shall not be submitted to any Open Generative AI tool (e.g., Chat GPT) or any substantially similar tool that is available to the<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>The following Stipulated Protective Order was entered in <em>Rapacon v. Abbott  Laboratories,</em> 2026 WL 2722543 (N.D. Cal. Sep. 15, 2026):</p>
<ol start="12">
<li>
<blockquote><p><u>USE OF GENERATIVE AI TOOLS</u></p></blockquote>
</li>
</ol>
<blockquote><p>“CONFIDENTIAL” Information or Items shall not be submitted to any Open Generative AI tool (e.g., Chat GPT) or any substantially similar tool that is available to the public. Providing “CONFIDENTIAL” Information or Items to an Open Generative AI tool is considered disclosure to a third party. For purposes of this Protective Order, “Open Generative AI tool” means an artificial intelligence system that may be accessed by the public, or that allows for the underlying code and materials to be accessed by the public.</p>
<p>The Parties may only submit “CONFIDENTIAL” Information or Items to a Permitted Generative AI Tool. For purposes of this Protective Order, a “Permitted Generative AI Tool” includes the use of enterprise AI tools that: (i) restrict access to authorized users; (ii) do not use customer data to train, refine, fine-tune, or improve publicly available models; (iii) provide reasonable retention and deletion controls; and (iv) maintain commercially reasonable security and confidentiality protections. For the avoidance of doubt, enterprise legal and productivity platforms that satisfy the foregoing requirements, including Thomson Reuters CoCounsel, Microsoft 365 Copilot, and similar enterprise tools, are permitted.</p></blockquote>
<p>For more information on A.I. Protective Orders, please visit:</p>
<ul>
<li><a href="https://www.ediscoveryllc.com/a-i-protective-order-by-consent-in-google-case/">A.I. Protective Order by Consent in Google Case</a> (Sep. 13, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/no-violation-of-a-i-protective-order/">No Violation of A.I. Protective Order</a> (Sep. 11, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/another-dispute-over-a-i-protective-order/">Another Dispute over A.I. Protective Order</a> (Sep. 6, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/a-i-protective-orders-are-becoming-routine-2/">A.I. Protective Orders Are Becoming Routine</a>(Aug. 27 ,2026);</li>
<li><a href="https://www.ediscoveryllc.com/another-a-i-protective-order-part-10/">Another A.I. Protective Order – Part 10</a> (Aug. 21, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/restrictions-on-use-of-artificial-intelligence-tools-to-process-disclosure-materials/">Restrictions on Use of Artificial Intelligence Tools to Process Disclosure Materials</a>(Jul. 27, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/another-a-i-protective-order/">Another A.I. Protective Order</a>(Jul. 9, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/a-i-protective-order-again/">A.I. Protective Order—Again</a> (Jun. 18, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/unicorn-rejects-a-i-protectiveconfidentiality-order-order-entered-in-criminal-case/">Unicorn Rejects A.I. Protective/Confidentiality Order – Order Entered in Criminal Case</a>(Jun. 4, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/are-protective-orders-limiting-upload-to-ai-of-documents-produced-by-an-opponent-in-discovery-becoming-the-standard-of-care/">Are Protective Orders Limiting Upload to AI of Documents Produced by an Opponent in Discovery Becoming the Standard of Care?</a>(May 26, 2026), discussing <em>Rudasill v. Swiss Re American Holding Corporation</em>, 2026 WL 1329451 (S.D.N.Y. May 13, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/another-confidentiality-order-limiting-use-of-ai-to-analyze-protected-materials/">Another Confidentiality Order Limiting Use of AI to Analyze Protected Materials</a>(Apr. 27, 2026), discussing <em>In re: ByHeart, Inc., Infant Formula Marketing, Sales Practices, and Products Liability Litigation,</em>2026 WL 1103170 (S.D.N.Y. Apr. 23, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/a-i-protective-orders-are-becoming-routine/">A.I. Protective Orders Are Becoming Routine</a>(Apr. 20, 2026), discussing <em>Stansfield v. International Business Machines Corporation, </em>2026 WL 1031230, at *2 (D. Nev. Apr. 16, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/deepfake-executives-created-via-depositions-pose-grave-threat-protective-order-suggested/">“Deepfake Executives, Created Via Depositions, Pose Grave Threat”: Protective Order Suggested</a>(Apr. 5, 2026);</li>
<li><em>Morgan v. V2X, Inc.,</em>2026 WL 864223 (D. Col. Mar. 30, 2026), as also discussed in <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);</li>
<li><a href="https://www.ediscoveryllc.com/order-prohibiting-upload-of-confidential-discovery-documents-to-artificial-intelligence-ai/">Order Prohibiting Upload of Confidential Discovery Documents to Artificial Intelligence (“AI”)</a>(Nov. 3, 2025), based on <em>Warner v. Gilbarco, Inc., </em>2025 WL 3047881 (E.D. Mich. Oct. 30, 2025);</li>
<li><a href="https://www.ediscoveryllc.com/protective-order-limited-uploading-discovery-responses-to-open-a-i/">Protective Order Limited Uploading Discovery Responses to Open A.I.</a>(Mar. 26, 2026), discussing <em>Jeffries v. Harcros Chemicals, Inc.,</em>2026 WL 820218 (D. Kans. Mar. 25, 2026);</li>
<li><em>S.A. v. Jones</em>, 2026 WL 2607719, at *2 (S.D.N.Y. Sep. 3, 2026);</li>
<li><em>Doe v. Google LLC</em>, 2026 WL 2584519 (N.D. Cal. Sep. 1, 2026);</li>
<li><em>S.A. v. The New York and Presbyterian Hosp.</em>, 2026 WL 2547094, at *5 (S.D.N.Y. Aug. 28, 2026).</li>
</ul>
<p>UPDATE:  <em>ZL Technologies, Inc. v. KLDiscovery Ontrack, LLC,</em> 2026 WL 2731631, at *9 (S.D.N.Y. Sep. 16, 2026):</p>
<blockquote><p>Use of Artificial Intelligence Tools</p>
<p>(a) Scope: To protect the confidentiality and security of all information disclosed or produced in this proceeding (“Discovery Information”), any Party receiving Discovery Information from another Party (“Receiving Party”) shall comply with the following requirements governing the use of artificial intelligence (“AI”) tools with such information.</p>
<p>(b) Permitted AI Use: A Receiving Party may use AI tools to process Discovery Information solely for purposes of this proceeding, provided that the AI tool and its use collectively satisfy all of the following requirements:</p>
<p>i.  Restricted, Enterprise Environment: The AI tool is used pursuant to a written enterprise or professional agreement and is deployed within a secure, access-controlled environment.</p>
<p>ii.  No Model Training or External Use: Discovery Information is not used to train, fine-tune, improve, develop, benchmark, or otherwise contribute to any AI model or service accessible outside the Receiving Party’s environment, except to the limited extent necessary to provide the requested functionality for this proceeding.</p>
<p>iii. Data Retention and Deletion: Within 30 days after final disposition of this action, Discovery Information retained by the AI tool shall be destroyed or caused to be destroyed to the extent reasonably possible.</p>
<p>iv.  Security Safeguards: The AI tool is subject to technical and contractual safeguards reasonably designed to protect Discovery Information against unauthorized access, use, or disclosure, including encryption in transit and at rest and appropriate access controls.</p>
<p>(c) No Backdoor Access: Nothing in Section 23 permits a Party, Agent, Expert, or other person that is not able to access Confidential Discovery Information or Highly Confidential – Attorneys’ Eyes Only Information under this Order to use AI tools to query, analyze, search or otherwise process such information.</p>
<p>(d) Responsibility and Attribution: Each Receiving Party is responsible for compliance with this Order by its counsel, experts, consultants, vendors, or other agents using AI tools on its behalf.</p>
<p>(e) <strong>Attorney Work Product:</strong> Use of an AI tool shall not waive or diminish any applicable privilege or work-product protection, and prompts, instructions, workflows, chat histories, and outputs shall be treated the same as analogous attorney work product created without the use of AI tools.</p></blockquote>
<p>UPDATE: <em>U.S. v. Perez-Feliz,</em> 2026 WL 2754823 (S.D.N.Y. Sep. 17, 2026)(consent order):</p>
<blockquote><p>Restrictions on Use of Artificial Intelligence Tools to Process Disclosure Materials.</p>
<p>a. “AI tool” means any automated system that uses machine learning, or similar techniques to process inputs and generate outputs, recommendations, or predictions, including but not limited to large language models, generative AI services, or AI-assisted software tools, whether cloud-based or otherwise.</p>
<p>b. The defense team will not submit Disclosure Materials to a publicly accessible version of an AI tool (e.g., ChatGPT, Claude, Grok, Gemini, Copilot, Perplexity, Midjourney, Canva). The defense team will not submit Disclosure Materials to an AI tool for which the AI tool provider or vendor (e.g., OpenAI, Anthropic, Microsoft, Google) uses submitted data for its own model training, allows submitted data to be publicly accessed, discloses submitted data to third parties, or, except as specified below, retains submitted data.</p>
<p>c. The defense may submit Disclosure Materials to an AI tool (i) that maintains the confidentiality of Disclosure Materials; (ii) that will not expose any Disclosure Materials to third parties not authorized under this Protective Order to receive such materials; (iii) that will not retain or use any Disclosure Materials for model training; and (iv) all Disclosure Materials will be removed from the AI tool(s) at the conclusion of this case.</p>
<p>&nbsp;</p></blockquote>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			</item>
		<item>
		<title>Proposal to Use Unilaterally-Designed A.I. for Search Was Rejected</title>
		<link>https://www.ediscoveryllc.com/proposal-to-use-unilaterally-designed-a-i-for-search-was-rejected/</link>
		<pubDate>Tue, 15 Sep 2026 19:25:55 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[Commercial Litigation]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[Important Posts]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Search]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5546</guid>
		<description><![CDATA[The court in Goldstein v. RTX Corp., 2026 WL 2690139 (D. Del. Sep. 14, 2026), rejected a proposal to use a unilaterally-designed AI tool for a search. The case is a putative collective and class action alleging a “nationwide pattern, practice, and/or policy of discriminating against older workers &#8230; in their hiring<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>The court in <em>Goldstein v. RTX Corp.,</em> 2026 WL 2690139 (D. Del. Sep. 14, 2026), rejected a proposal to use a unilaterally-designed AI tool for a search.</p>
<p>The case is a putative collective and class action alleging a “nationwide pattern, practice, and/or policy of discriminating against older workers &#8230; in their hiring processes.”  At issue was the manner of collective notice procedures.</p>
<blockquote><p>The parties raise four primary disputes regarding the proposed collective notice procedures: (1) whether notice should be authorized for applicants of the non-RTX Defendants, (2) how to determine which job postings qualify as “Recent Graduate Positions,” (3) how to identify putative collective members, and (4) whether a website to return consent forms should be publicly available or password protected.</p></blockquote>
<p><em>Id</em>. at *2.</p>
<p>This post focuses on No. 2. The court wrote:</p>
<blockquote><p>Next, the parties dispute how to determine which job postings qualify as “Recent Graduate Positions” reserved for “those who have graduated in the prior year or two (or who will soon graduate), or applicants with college degrees who have less than 12 or 24 months of work experience.” &#8230; Plaintiffs propose negotiating search terms with Defendants that target experience and recent graduate limitations…. <em>In contrast, <strong>Defendants suggest filtering positions in their Workday database based on several data fields and then training an artificial intelligence model to identify job descriptions meeting Plaintiffs’ definition of “Recent Graduate Positions</strong></em><strong>.”</strong></p></blockquote>
<p><em>Id</em>. at *3 (emphasis added).</p>
<p>The court adopted Defendants’ proposal to employ the Workday database fields.  However, addressing the A.I. proposal, the court wrote:</p>
<blockquote><p>Plaintiffs’ proposal to negotiate appropriate search terms targeting experience and recent graduate limitations is ADOPTED-IN-PART, and <em>Defendants’ competing proposal to train an artificial intelligence model is REJECTED.</em> Defendants contend that the Workday database does not have a field that can cleanly isolate Recent Graduate Positions, and the requirements for these positions are phrased differently, posing the risk of an underinclusive search….  Plaintiffs note that they “requested the sample of job postings Defendants reviewed in reaching that conclusion[,]” but “Defendants have not produced any sample.” … <strong><em>A collaborative process to agree on search terms is preferable to the unilateral training of an artificial intelligence model, which is no less likely to raise issues of under-inclusiveness. </em></strong>However, Plaintiffs’ proposal is REJECTED to the extent that they seek to compel Defendants to produce a 30% sample of Recent Graduate job postings across the relevant time period. Plaintiffs provide no authority in support of this proposal, which is effectively a motion to compel discovery. Therefore, IT IS ORDERED that the parties shall meet and confer on search terms to employ in the search process within fourteen (14) days of this Memorandum Order.</p></blockquote>
<p><em>Id</em>. at *4 (emphasis added). The court ordered that:</p>
<blockquote><p>Defendants’ proposals to: (i) employ the Workday database fields identified in their supplemental submission to identify which positions quality as “Recent Graduate Positions,” and (ii) exclude from the realm of Recent Graduate Positions any positions open to recent master’s graduates or “degree equivalency” positions open to either recent college graduates or those with equivalent work experience are ADOPTED. Plaintiffs’ proposal to negotiate appropriate search terms targeting experience and recent graduate limitations to further identify Recent Graduate Positions is ADOPTED-IN-PART, and <strong><em>Defendants’ competing proposal to train an artificial intelligence model is REJECTED.</em></strong> Accordingly, IT IS ORDERED that the parties shall meet and confer to negotiate appropriate search terms within fourteen (14) days of this Memorandum Order.</p></blockquote>
<p><em>Id</em>. at *5 (emphasis added).</p>
]]></content:encoded>
			</item>
		<item>
		<title>Opposing Expert’s Allegedly Inaccurate Description of Use of A.I. Did Not Justify Modification of Scheduling Order on Facts Presented</title>
		<link>https://www.ediscoveryllc.com/opposing-experts-allegedly-inaccurate-description-of-use-of-a-i-did-not-justify-modification-of-scheduling-order-on-facts-presented/</link>
		<pubDate>Tue, 15 Sep 2026 17:00:33 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Rules]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5544</guid>
		<description><![CDATA[“This is a Federal Tort Claims Act case involving allegations of an unlawful shooting by a Bureau of Land Management ranger.”  Martin v. U.S.A., 2026 WL 2582963 (D. Nev. Sep. 1, 2026). Defendant moved to reopen and extend case management deadlines based on Plaintiffs’ expert’s having used AI, allegedly more extensively than<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>“This is a Federal Tort Claims Act case involving allegations of an unlawful shooting by a Bureau of Land Management ranger.”  <em>Martin v. U.S.A.,</em> 2026 WL 2582963 (D. Nev. Sep. 1, 2026).</p>
<p>Defendant moved to reopen and extend case management deadlines based on Plaintiffs’ expert’s having used AI, <em>allegedly</em> more extensively than disclosed. The motion was denied based on lack of diligence.</p>
<p>The chronology follows:</p>
<ul>
<li>February 10, 2025: The parties held a Rule 26(f) conference. The court wrote that there was “no impediment to proceeding with discovery.”</li>
<li>March 26, 2026: Plaintiffs disclosed Tom Melton as an expert and served his report.</li>
<li>May 1, 2026: The extended rebuttal expert deadline expired.</li>
<li>June 9, 2026: “Melton testified at his deposition that he used an artificial intelligence aid to assist him with grammar and sentence structure in his written report…. Defense counsel knew as of at least that date (June 9, 2026) that there may be an issue with the use of artificial intelligence. Indeed, counsel began researching the issue and looking for an expert at that time.”</li>
<li>July 16, 2026: “Apparently due to some sort of scheduling issue, Melton’s deposition was continued and eventually completed….”</li>
<li>August 10, 2026: The discovery cutoff expired.  “On the discovery cutoff, Defendant filed the instant motion seeking to reopen the rebuttal expert disclosure deadline and to extend the discovery cutoff (and subsequent case management deadlines) by 90 days.”</li>
</ul>
<p>The basis of the defense request was:</p>
<blockquote><p>Defendant explains that, based on the record in a different case involving Melton, counsel “believes that there is a possibility” that Melton has misrepresented the extent of his use of artificial intelligence.</p></blockquote>
<p>Defense counsel had “suspicions” of misrepresentation.</p>
<p>For the <em>unexpired</em> discovery cutoff, the court explained that good cause is required to modify an unexpired case management deadline.  Good cause “turns on whether the subject deadlines cannot reasonably be met through the exercise of diligence throughout the allotted period…. The diligence obligation is ongoing and the movant must have been diligent throughout the entire period already provided….  Courts may find a lack of good cause when, <em>inter alia</em>, the movant did not promptly seek judicial relief from the subject deadline.”  The burden of proof is on the movant and if it is not carried, “the inquiry should end.”</p>
<p>For the <em>expired</em> rebuttal expert deadline: “Seeking to revive already expired deadlines requires an additional showing of excusable neglect….  When there is no threshold showing of diligence for good cause, however, such request is properly denied without the need to separately address excusable neglect.”</p>
<p>Here, the inquiry ended:</p>
<blockquote><p>In this case with an already-extended discovery period, the record reflects that defense counsel was on notice of Melton’s testimony on his use of artificial intelligence since at least June 9, 2026. Although counsel represents that he began immediately researching the issue and trying to locate an expert, he did not file the instant motion until the last day of the discovery period more than two months later. The Court agrees with Plaintiffs…, that the failure to seek relief for two months shows that Defendant was not diligent….</p></blockquote>
<p>The court rejected the defense argument that the deposition was not concluded until July 16, 2026: “Defendant cites no legal authority and provides no meaningfully developed argument that a party can sit on its hands in seeking relief from an approaching case management deadline simply because a portion of a deposition is rescheduled. Again, counsel represents that he had spent the preceding weeks looking into the issue and trying to find an expert, so any need to seek relief from the case management schedule was known weeks before the second part of the deposition. Defendant fails to explain why counsel could not have conferred and sought relief from case management deadlines during the intervening period.”</p>
<p>The court added: “Defendant also cites no legal authority that a party must already find and retain a particular person to act as its expert before it can seek relief from the expert disclosure deadlines.”</p>
<p>In a footnote, the court wrote: “The lack of diligence is dispositive of this motion. The Court notes that there is also some force to Plaintiff’s additional argument that <u>speculation</u> as to the use of artificial intelligence seems a weak basis for an eleventh-hour request to extend case management deadlines yet again.”</p>
]]></content:encoded>
			</item>
		<item>
		<title>Dispositive Sanction Denied in Auto Tort—Defendants Failed to Request Lesser Sanctions</title>
		<link>https://www.ediscoveryllc.com/dispositive-sanction-denied-in-auto-tort-defendants-failed-to-request-lesser-sanctions/</link>
		<pubDate>Tue, 15 Sep 2026 09:09:26 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5537</guid>
		<description><![CDATA[Two defendants moved to dismiss an auto tort Complaint because of alleged spoliation of the Plaintiff’s automobile.  The motions were denied.  Baez v. Uber Technologies, Inc., 2026 WL 2603075 (D. Md. Sep. 3, 2026)(Sullivan, J.). On November 4, 2024, Defendant Jung, an Uber driver, rear-ended Plaintiff Baez’s 1999 Honda Accord, driving it<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Two defendants moved to dismiss an auto tort Complaint because of alleged spoliation of the Plaintiff’s automobile.  The motions were denied.  <em>Baez v. Uber Technologies, Inc.,</em> 2026 WL 2603075 (D. Md. Sep. 3, 2026)(Sullivan, J.).</p>
<p>On November 4, 2024, Defendant Jung, an Uber driver, rear-ended Plaintiff Baez’s 1999 Honda Accord, driving it into a guardrail. One factual dispute was whether the Honda was stopped in the left lane.  Jung said it was. Baez “states that he has no recollection of the vehicle being stopped, and that the vehicle was in proper working condition and not disabled at the time of the collision.”  The Honda was not preserved.</p>
<p>The preservation/spoliation facts were straightforward:</p>
<blockquote><p>Both vehicles were removed from the scene by N &amp; S Towing…. <em> </em>Plaintiff suffered serious bodily injuries and while he was in the hospital, his mother “independently ascertained” the location of his vehicle…. On November 8, 2024, she traveled to the N &amp; S Towing location and took photographs of his vehicle, which were later shared with defense counsel…. By November 12, 2024, Plaintiff had retained counsel…. And on November 20, 2024, Defendant Jung’s counsel provided a formal preservation request asking Plaintiff to preserve all relevant evidence, including the 1999 Honda Accord…. The request was sent to Plaintiff’s prior counsel, John Lyding of Morgan &amp; Morgan…. Plaintiff is currently represented by Terence Davis of the same firm…<em>. </em>Defendant Jung’s counsel contacted Morgan &amp; Morgan on three occasions about the status of the vehicle….</p></blockquote>
<p>Suit was filed on August 11, 2025.  The Court wrote: “<em>Finally, on August 15, 2025, Plaintiff’s counsel (through his paralegal) notified Defendant Jung’s counsel that the vehicle was a total loss and had been discarded on an unknown date.</em> [emphasis added].</p>
<p>First, the Court held that the defense motions to dismiss the Complaint were in fact “clearly intended to be motions for sanctions, the sanction requested being dismissal.”  This was significant because, instead of applying the Rule 12(b)(6) standard, it meant that “the Motions will be construed as motions for sanctions based on the destruction of Plaintiff’s vehicle.”</p>
<p>The Fourth Circuit long ago addressed the duty to preserve an automobile.  <em>Silvestri v. Gen. Motors Corp</em>., 271 F.3d 583 (4th Cir. 2001).  Spoliation includes “the failure to preserve property for another’s use as evidence in pending or reasonably foreseeable litigation.”  <em>Id</em>.  Because an automobile is not ESI, Fed.R.Civ.P. 37(e) is inapposite.  The <em>Baez </em>Court held that its inherent power governed the sanctions requests: “Here, Plaintiff failed to preserve a tangible piece of evidence and the Court’s inherent authority to impose sanctions is implicated.”</p>
<p>The <em>Baez</em> Court explained that a party seeking sanctions “must show that: (1) the 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>
<p style="text-align: center;"><strong><u>TRIGGER AND BREACH OF THE DUTY TO PRESERVE</u></strong></p>
<p style="text-align: center;"><em><u>Trigger of the Preservation Duty</u></em></p>
<p>The first step was to determine when the duty to preserve was triggered, i.e., when Baez reasonably anticipated litigation. <em>Id</em>. at *3.  At that time, a party must institute a litigation hold.  “And when a party cannot fulfill this duty to preserve because he does not own or control the evidence, he still has an obligation to give the opposing party notice of access to the evidence or of the possible destruction of the evidence if the party anticipates litigation involving that evidence.” <em>Id</em>. (citation and quotations omitted). The Court wrote:</p>
<blockquote><p><em>It cannot be disputed that Plaintiff had an obligation to preserve his vehicle.</em> The accident occurred on November 4, 2024, and only four days later Plaintiff’s mother had located the vehicle and visited N &amp; S Towing’s location to take photographs of it….  Less than ten days later, Plaintiff had retained counsel…. And sixteen days later, Defendant Jung’s counsel provided a formal preservation request asking Plaintiff to preserve all relevant evidence, including the 1999 Honda Accord…. Plaintiff’s duty to preserve arose on November 12, 2024, when he obtained counsel. Even had Plaintiff not obtained counsel, his duty to preserve would have been triggered on November 20, 2024, when Defendant Jung’s counsel sent him a preservation letter.<em>…  </em></p></blockquote>
<p><em>Id</em>. at *3.</p>
<p style="text-align: center;"><em><u>Breach of the Preservation Duty</u></em></p>
<p>The Court then addressed breach of the duty:</p>
<blockquote><p>Despite having a duty to preserve his vehicle, Plaintiff’s counsel failed to inquire about the vehicle’s status with N &amp; S Towing until almost a year after defense counsel sent the preservation letter…. The first step in the sanctions analysis is satisfied.</p></blockquote>
<p><em>Id</em>.  It added: “Plaintiff argues that because the preservation letter was sent to Plaintiff’s prior counsel, his current counsel was not aware of the Defendants’ desire to inspect the vehicle…. This argument borders on ridiculous. Morgan &amp; Morgan has represented Plaintiff since November 12, 2024, and both Plaintiff’s previous and current counsel are Morgan &amp; Morgan attorneys…. Any blame that Plaintiff directs at his former attorney is therefore properly attributed to Plaintiff himself.” <em>Id</em>. at n. 5.</p>
<p style="text-align: center;"><strong><u>CULPABLE STATE OF MIND</u></strong></p>
<p>The next step was to evaluate culpability. <em>Id</em>. at *4. Sanctions may be imposed for “any fault—be it bad faith, willfulness, gross negligence, or ordinary negligence….  In the context of spoliation, ordinary negligence is the failure to identify, locate, and preserve evidence, where a reasonably prudent person acting under like circumstances would have done so.”  <em>Id</em>.</p>
<p>However, the degree of culpability affects the severity of the possible sanction. <em>Id</em>.  Case-dispositive sanctions are reserved for the “most extreme circumstances.”  <em>Id</em>.</p>
<p style="text-align: center;"><strong><u>PREJUDICE AND SECONDARY EVIDENCE</u></strong></p>
<p>Here, the Defendants asked too much: “The only sanction requested by Defendants is dismissal. But because there is insufficient evidence to warrant such a sanction, the Motions are denied.”  <em>Id</em>. at *4.</p>
<p>The Court looked at what I call secondary evidence in deciding that Defendants could still defend the claims, writing: “Through the police report, vehicle images, the testimony of Plaintiff (who admits his memory of the collision is ‘hazy’ and contradicts the police report), Defendant Jung’s testimony, and any other materials produced throughout discovery, Defendants are able to build their defense without a forensic examination of Plaintiff’s vehicle.”</p>
<blockquote><p>Moreover, following the collision on November 4, 2024, Plaintiff spent several days in the hospital…. His mother, on her own accord and while he was in the hospital, located and photographed his vehicle on November 8, 2024…. <em>These photos were shared with defense counsel…</em>. [emphasis added].</p></blockquote>
<p>The Court also found, in my words, a lack of diligence by the defense:</p>
<blockquote><p>Additionally, the police report states that both vehicles were removed from the accident scene by “NS Towing” and removed to the tow lot…. But despite having the details of what company removed the vehicles and where that company took the vehicles, <em>neither party attempted to inspect or preserve Plaintiff’s vehicle while it sat in the tow lot.</em> <em>Defendant Jung’s counsel failed to follow up with Plaintiff’s counsel about the preservation of the vehicle until July 28, 2025, over eight months after the collision</em>.</p></blockquote>
<p><em>Id</em>. at *4 (emphasis added).</p>
<p style="text-align: center;"><strong><u>DATE OF LOSS?</u></strong></p>
<p>The first element of spoliation is that “the party having control over the evidence had an obligation to preserve it when it was destroyed or altered….”  Here, a key fact was absent—no one knew <em>when</em> the car went missing.  The Court wrote:</p>
<blockquote><p>Finally, the parties do not provide any information about when Plaintiff’s vehicle was destroyed. <em>It could be that N &amp; S Towing destroyed the vehicle after Plaintiff’s mother photographed it on November 8, 2024, and before Plaintiff retained counsel on November 12, 2024, or received Defendant Jung’s preservation request on November 20, 2024</em>….</p></blockquote>
<p><em>Id</em>. (emphasis added).  Further, this appeared to be relevant to culpability:</p>
<blockquote><p>There is no evidence that Plaintiff or his counsel purposefully deprived Defendants of the opportunity to examine the vehicle or facilitated its destruction. To the contrary, the record reflects a police report providing where the vehicle was towed and the Plaintiff’s mother locating and photographing Defendant’s vehicle in a tow lot, where both parties knew it to be located, and where it was eventually disposed of on an unknown date and time. These facts do not support dismissal.</p></blockquote>
<p><em>Id</em>.</p>
<p style="text-align: center;"><strong><u>CONDUCT OF PLAINTIFF’S COUNSEL WAS CONCERNING, BUT IRRELEVANT</u></strong></p>
<p>The Court wrote:  “<em>To be clear, Plaintiff’s counsel’s conduct is concerning</em>. Only sixteen days after the collision, Defendant Jung sent a preservation letter to Mr. Lyding requesting that Plaintiff preserve his 1999 Honda Accord that was involved in the accident…. <em>It is entirely unclear what Mr. Lyding did, if anything, to preserve this evidence. </em>At some point, another Morgan &amp; Morgan attorney, Mr. Davis, took over Plaintiff’s case and replaced Mr. Lyding. But despite both attorneys being from the same law firm and there being only one client, Mr. Davis now claims that he had no knowledge of the preservation letter sent to Mr. Lyding on November 20, 2024.” <em>Id</em>. at *5 (emphasis added).</p>
<p>However, that was irrelevant because Defendants asked only for dismissal, writing: “Any other remedy would be an unacceptable outcome and surely undermine the integrity of the judicial process.” <em>Id</em>. at *5.  Based on Defendants’ request, the Court wrote:  “While Plaintiff’s counsel’s failure to comply with the fundamental obligation to preserve material evidence may indeed be considered negligence or with a culpable state of mind, the Court does not need to reach this question. Defendants have not asked the Court to impose any lesser sanction than dismissal.”</p>
<p style="text-align: center;"><strong><u>CONCLUSION: THE DOOR WAS LEFT OPEN</u></strong></p>
<p>The Court held that:  “Because Defendants have not established that Plaintiff’s conduct was so egregious as to warrant dismissal, the vehicle’s relevance, as it relates to the sanctions analysis, is immaterial.” <em>Id</em>. at *5.</p>
<p>However, it left the door open to a lesser sanction, stating that “the Court need not reach the question of whether Plaintiff’s conduct warrants a lesser sanction. Instead, the Court retains the ability to consider this issue at trial, at which time the Court may order appropriate sanctions, including an adverse inference jury instruction.”</p>
<p>In prior decisional authority in this District, the Court has pointed out that a party asking only for game-ending sanctions may effectively waive lesser sanctions. <a href="https://www.ediscoveryllc.com/court-recommends-denial-of-rule-37e2-motion-while-providing-guidance-under-rule-37e1/">Court Recommends Denial of Rule 37(e)(2) Motion, While Providing Guidance Under Rule 37(e)(1)</a> (May 19, 2025)(Defendants moved for “game ending” sanctions under Fed.R.Civ.P. 37(e)(2); however, the United States Magistrate Judge recommended that the motion be denied.  The Court provided a Rule 37(e)(1) suggestion.); <a href="https://www.ediscoveryllc.com/rule-37e1-sanctions-for-breach-of-duty-to-preserve-communications/">Rule 37(e)(1) Sanctions for Breach of Duty to Preserve Communications</a> (Oct.11, 2025).</p>
]]></content:encoded>
			</item>
	</channel>
</rss>
