<?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>District of MD &#8211; E-Discovery LLC</title>
	<atom:link href="https://www.ediscoveryllc.com/category/district-of-md/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ediscoveryllc.com</link>
	<description>Mediation of E-Discovery Disputes</description>
	<lastBuildDate>Sat, 31 Oct 2026 18:49:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Examples of a Very Detailed A.I. Protective Order and Less Detailed Agreements and Orders</title>
		<link>https://www.ediscoveryllc.com/examples-of-a-very-detailed-a-i-protective-order-and-less-detailed-agreements-and-orders/</link>
		<pubDate>Fri, 16 Oct 2026 22:38:06 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[Commercial Litigation]]></category>
		<category><![CDATA[District of MD]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Important Posts]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5656</guid>
		<description><![CDATA[I have suggested that AI protective orders are becoming the standard of care.[1]  These orders limit the use or uses of AI by a recipient of discovery materials to review the materials produced by an opponent.  They clearly are important and have value in appropriate instances. However, there is no standard form<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>I have suggested that AI protective orders are becoming the standard of care.<a href="#_ftn1" name="_ftnref1">[1]</a>  These orders limit the use or uses of AI by a <em>recipient</em> of discovery materials to review the materials produced by an <em>opponent</em>.  They clearly are important and have value in appropriate instances.</p>
<p>However, there is no standard form and the agreements vary greatly. Some cover only confidential information; others apply to all discovery material. Some list acceptable platforms by name; others describe functional requirements; and, some address named platforms and their configuration.  There has been discussion about the terms “consumer grade” AI v. “Enterprise” AI.  Thomsen-Reuters discusses <a href="https://www.thomsonreuters.com/en/insights/articles/fiduciary-grade-ai-what-it-is-why-it-matters-and-how-to-buy-it">Fiduciary-Grade AI</a>.  The terms &#8220;open&#8221; and &#8220;closed&#8221; AI have been used&#8211;and criticized.</p>
<p>All protective orders are not created equal and they are not always fair.  I have echoed Craig Ball’s novel post on the need for equity in limiting an opponent’s right to use AI.  <a href="https://www.ediscoveryllc.com/another-a-i-protective-order-part-10/">Another A.I. Protective Order – Part 10</a> quoting Craig Ball, <a href="https://craigball.net/2026/07/27/the-ai-protective-order-double-standard/">The AI Protective Order Double Standard | Ball in your Court</a> (Jul. 27, 2026).</p>
<p>One of the most detailed AI protective orders that I have seen was stipulated in <em>Corent Technology, Inc. v. Amazon Web Services, Inc., </em>2026 WL 2924482 (C.D. Cal. Sep. 28, 2026).  It deals with both the use of AI on source code and more generally.  At the end of this post, I cite a number of less detailed examples.</p>
<p>As to source code, the <em>Corent Technology</em> order states:</p>
<blockquote><p>Neither party shall use any software tools or applications on the Source Code Computer powered by or leveraging artificial intelligence or machine learning that automatically scan, analyze, or provide feedback on source code. The Producing Party shall accommodate reasonable requests by the Receiving Party that other mutually agreeable commercially available software tools for viewing and searching Source Code be installed on the Source Code Computer, provided that such other software tools are reasonably available to the Producing Party, non-destructive to the source code, and reasonably necessary for the Receiving Party to perform its review of the Source Code consistent with all the protections herein. The Receiving Party must provide the Producing Party with the licensed software tools at least three (3) business days in advance of the date upon which the Receiving Party wishes to have the additional software tools available for use on the Source Code Computer.</p></blockquote>
<p>As to A.I. in general, the <em>Corent Technology</em> order states:</p>
<blockquote><p><strong>USE OF AI TOOLS</strong></p>
<p>No party, and no person or entity authorized to receive materials under this Order, may input, upload, submit, or otherwise provide any Discovery Material—<em>whether or not designated as Protected Information</em>—into any <em>modern</em> artificial intelligence platform, including any generative, analytical, or large language model-based tool (“AI Tool”), unless all requirements of Section 12.1 and Section 12.2 are satisfied.</p>
<p>12.1 A party or person subject to this Order may use an AI Tool with Discovery Material only if the AI Tool is provided on an enterprise or commercial tier subscription and the Receiving Party has not configured the AI Tool to:</p>
<p>a) retain or store inputs (including prompts, documents, and metadata) for use beyond the session necessary to deliver the requested service, except as provided in Section 12.7.2, For clarity, this requirement does not prohibit the use of AI Tools that maintain a history of a user’s prompts and/or sessions, provided that any prompts containing Protected Information shall not be disclosed to any person not authorized to receive Protected Information under this Order;</p>
<p>b) use, incorporate, or reference inputs to train, fine-tune, retrain, or otherwise improve any AI model or system, whether that of the vendor or any third party, except as provided in Section 12.7.2, For clarity, this requirement does not prohibit the use of AI tools that incorporate or reference a user’s past prompts to optimize responses to subsequent prompts by the same user, provided that such AI tools (1) do not use, reference, or incorporate prompts or other inputs received from one user to respond to prompts from any other user; and (2) otherwise comply with all of the requirements in Section 12;</p>
<p>c) disclose inputs to any third party, except where strictly essential to facilitate delivery of the service; any such third party must be bound by confidentiality obligations no less protective than those required by this Order;</p>
<p>d) allow any human employee, contractor, or reviewer of the AI vendor to read, access, or review input content for any purpose other than immediate technical support explicitly requested by the party; and</p>
<p>e) make inputs or retained outputs accessible to any person not authorized to receive Protected Information under this Order.</p>
<p>12.2 In addition to the requirements of Section 12.1, a party or person may use an AI Tool with Discovery Material only if the AI vendor is contractually obligated to afford the Receiving Party the right to remove or delete all Discovery Material and AI-generated outputs from the vendor’s systems upon request, and in any event no later than sixty (60) days following the entry of a final non-appealable judgment or order, or the complete settlement of all claims asserted against all parties in this action (the “Conclusion of This Action”). The Receiving Party shall: (a) within fourteen (14) days following the Conclusion of This Action, take all reasonable steps necessary to ensure deletion of all Protected Material uploaded and/or output by AI tools during this action. The Receiving Party may meet this requirement by submitting a deletion request to the vendor if the vendor accepts deletion requests during the term of its vendor agreement with the Receiving Party; or, if the AI vendor does not accept such requests, by manually deleting all uploaded information over the AI tool’s user interface; and (b) within sixty (60) days following the Conclusion of This Action, provide the Producing Party with written certification and documentation demonstrating that the Receiving Party took all reasonable steps necessary to delete all Discovery Material uploaded to AI tools using the procedures and means provided by the vendor(s), as applicable.</p>
<p>12.3 Any party intending to use an AI Tool with Discovery Material must, prior to such use:</p>
<p>a) retain written documentation (including the vendor’s data processing agreement, terms of service, or equivalent contractual instrument) demonstrating that the vendor’s commitments satisfy Sections 12.1 and 12.2; and</p>
<p>b) make such documentation available to the Producing Party within five (5) business days of a written request.</p>
<p>12.4 A party that intends to use an AI Tool with Discovery Material produced by the other party must provide written notice to the Producing Party at least seven (7) business days before first use, except with respect to AI Tools pre-approved under Section 12.6. Such notice shall identify:</p>
<p>a) the name, version, and operator of the AI Tool;</p>
<p>b) <em>the categories of Discovery Material the Receiving Party intends to process</em>; and</p>
<p>c) a representation that Sections 12.1 and 12.2 are satisfied, accompanied by the documentation required by Section 12.3(a).</p>
<p>The Producing Party shall have five (5) business days to object in writing, stating with particularity the basis for objection. If a timely objection is served, the parties shall meet and confer within three (3) business days. If the dispute is not resolved, the Receiving Party may not proceed with such AI Tool use until the Court resolves the dispute pursuant to Local Rule 37-1 et seq. and Section 3 of Judge McCormick’s Procedures.</p>
<p>12.5 Notwithstanding any other provision of this Section 12, no party may use any AI Tool, regardless of vendor contractual protections, to review, analyze, summarize, or otherwise process any Discovery Material designated as HIGHLY CONFIDENTIAL—SOURCE CODE. This prohibition is absolute and applies whether such Source Code material is accessed on the Source Code Computer, in printed form, in electronic excerpts, or in any other form or medium.</p>
<p>12.6 The parties agree that the following AI Tools, when used at the enterprise or commercial tier identified below and subject to the configuration requirements in this subsection, satisfy the requirements of Sections 12.1 and 12.2 based on each vendor’s published enterprise terms of service, data processing addendum, and security certifications as of the Effective Date of this Order. Use of any AI Tool pre-approved under this Section 12.6 shall not require the pre-use notice otherwise required under Section 12.4.</p>
<p>a) Microsoft Copilot, including Microsoft 365 Copilot and Copilot Cowork, when deployed within a Microsoft 365 Enterprise or Business tenant governed by Microsoft’s enterprise Data Protection Addendum (and not the free or consumer-facing Copilot product available at copilot.microsoft.com), satisfies the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s tenant is configured to disable any consumer connectors or web-grounding features that would route Discovery Material outside the enterprise data-processing boundary; and (ii) the Receiving Party has not enabled any consumer-tier or non-Enterprise Copilot product for use with Discovery Material.</p>
<p>b) Lexis+ AI (LexisNexis), at the firm’s standard commercial or enterprise subscription tier, satisfies the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s account is configured under LexisNexis’s then-current commercial terms and its published zero-training and zero-retention commitments applicable to user-submitted content; and (ii) the Receiving Party has not enabled any consumer or free-tier LexisNexis AI product for use with Discovery Material.</p>
<p>c) Westlaw AI and CoCounsel (Thomson Reuters), at the firm’s standard commercial or enterprise subscription tier, satisfy the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s account is governed by Thomson Reuters’s then-current commercial terms, including its non-retention API arrangements with underlying model providers and its contractual prohibition on third-party model providers retaining or training on customer data; and (ii) the Receiving Party has not enabled any consumer or free-tier Westlaw AI or CoCounsel product for use with Discovery Material.</p>
<p>d) Patlytics (patlytics.ai), at the firm’s standard commercial or enterprise subscription tier, satisfies the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s account is configured under Patlytics’s then-current customer terms, including its published non-training commitment and its non-retention agreements with underlying third-party AI services; and (ii) the Receiving Party has not enabled any consumer or free-tier Patlytics product for use with Discovery Material.</p>
<p>e) Perplexity Enterprise (Pro or Max tier) satisfies the requirements of Sections 12.1 and 12.2, based on Perplexity’s Enterprise Terms of Service, Data Processing Addendum, and SOC 2 Type II attestation as of the Effective Date of this Order, provided that: (i) the Receiving Party’s Enterprise instance has Zero Data Retention enabled or, alternatively, has configured the shortest available data retention period; and (ii) the Receiving Party has not enabled any consumer-tier or non-Enterprise Perplexity product for use with Discovery Material.</p>
<p>f) Claude (Anthropic), at the firm’s standard commercial or enterprise subscription tier, satisfies the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s subscription is configured to disable any consumer connectors or web-grounding features that would route Discovery Material outside the enterprise data-processing boundary; and (ii) the Receiving Party has not enabled any consumer-tier or non-Enterprise Claude product for use with Discovery Material.</p>
<p>g) Harvey (harvey.ai) satisfies the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s subscription is configured to disable any consumer connectors or web-grounding features that would route Discovery Material outside the enterprise data-processing boundary; and (ii) the Receiving Party has not enabled any consumer-tier or non-Enterprise Harvey product for use with Discovery Material.</p>
<p>h) Legora aOS (Legora) satisfies the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s subscription is configured to disable any consumer connectors or web-grounding features that would route Discovery Material outside the enterprise data-processing boundary; and (ii) the Receiving Party has not enabled any consumer-tier or non-Enterprise Legora product for use with Discovery Material.</p>
<p>i) Crane Patents satisfies the requirements of Sections 12.1 and 12.2, provided that: (i) the Receiving Party’s subscription is configured to disable any consumer connectors or web-grounding features that would route Discovery Material outside the enterprise data-processing boundary; and (ii) the Receiving Party has not enabled any consumer-tier or non-Enterprise Crane Patents product for use with Discovery Material.</p>
<p>12.7.1 No party or authorized recipient of Discovery Material shall use any Discovery Material, or any AI-generated output derived therefrom, within any AI Tool workspace, project, index, session, or other AI-Tool-hosted environment that is accessed, maintained, or used for any matter other than this action. Each party shall configure its use of AI Tools such that Discovery Material and any AI-generated outputs derived therefrom are logically segregated from unrelated matters, and shall not carry over, migrate, or otherwise make available such Discovery Material or derived outputs to any workspace, project, index, or session unrelated to this action.</p>
<p>12.7.2 For the avoidance of doubt, nothing in this Section 12 prohibits an AI Tool from retaining Discovery Material or AI-generated outputs derived therefrom within a single matter-specific workspace, project, index, or session dedicated to this action for the purpose of enabling follow-up queries, retrieval-augmented generation, context-preserved analysis, or similar within-matter functionality, provided that (i) such retention is confined to the matter-specific environment and does not train, fine-tune, or otherwise update the underlying model or any model used by any other party, matter, or user; and (ii) the matter-specific environment remains subject to the deletion obligations set forth in Section 12.2. [emphasis added]</p></blockquote>
<p>For more information on, and examples of, less detailed A.I. protective orders, a discussion of standard of care, and a discussion of the possible equity impacts of such orders, please visit:</p>
<ul>
<li><a href="https://www.ediscoveryllc.com/a-unique-a-i-protective-order/">A Unique A.I. Protective Order</a> (Oct. 9, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/three-more-a-i-protective-orders/">Three More A.I. Protective Orders</a> (Oct. 9, 2026);</li>
<li><a href="https://www.ediscoveryllc.com/another-ai-protective-order/">Another AI Protective Order</a> (Sep. 16, 2026);</li>
<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. The New York and Presbyterian Hosp.</em>, 2026 WL 2547094, at *5 (S.D.N.Y. Aug. 28, 2026)(Amended Protective Order);</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>ZL Technologies, Inc. v. KLDiscovery Ontrack, LLC,</em> 2026 WL 2731631, at *9 (S.D.N.Y. Sep. 16, 2026);</li>
<li><em>S. v. Perez-Feliz,</em> 2026 WL 2754823 (S.D.N.Y. Sep. 17, 2026)(consent order);</li>
<li><em>S. v. Montes</em>, 2026 WL 2824059, at *1 (S.D.N.Y. Sep. 21, 2026)(by consent);</li>
<li><em>S. v. Hawkins,</em> 2026 WL 2825014, at *2 (S.D.N.Y. Sep. 21, 20260(same);</li>
<li><em>S.A. v Amanuel</em>, 2026 WL 2972618 (S.D.N.Y. Oct. 2, 2026)(by consent).</li>
<li><em>White v. Chime Financial, Inc.,</em> 2026 WL 3000904 (W.D. Wash. Oct. 6, 2026)(stipulated):</li>
</ul>
<blockquote><p>USE OF ARTIFICIAL INTELLIGENCE</p>
<p>Should a Party elect to utilize artificial intelligence (“AI”) to assist in reviewing, analyzing, or summarizing discovery material produced or exchanged in this litigation, the Party shall take all necessary steps to ensure that the application, service, or analytical software is fully containerized. “Fully containerized,” as used in this Order, means an AI tool that does not retain the substance of a prompt or documents reviewed, share the substance of a prompt or documents reviewed for training of large language models, or use the substance of a prompt or documents reviewed in any other matter or inquiry other than this litigation. For the avoidance of doubt, this restriction expressly applies to the use of non-containerized advanced large language models (such as publicly available large language models), generative AI tools, and other advanced AI systems, including, but not limited to, OpenAI, Gemini, LLAMA, MidJourney, and Stable Diffusion, but this provision does not limit the use of services leveraging the technology underlying these generative AI tools in a fully containerized environment, including, but not limited to, Copilot Harvey, Relativity aiR, DISCO Cecelia, Everlaw AI, Syllo, Alchemy, Lexis+ AI, Epiq AIDA, Lighthouse AI, Westlaw AI, ChatGPT Enterprise, Microsoft 365 Copilot Enterprise, Claude Enterprise, NotebookLM Pro and Ultra, and Gemini Pro and Ultra. Before submitting any Protected Material to a fully containerized AI tool, a receiving party shall ensure that it (or its vendor) can delete all such Protected Material from the AI tool at the conclusion of this matter, including any derivative information stored within the tool. The obligations and restrictions of this paragraph apply even where the Protected Material has been anonymized.</p></blockquote>
<ul>
<li><em>S.A.  v. Lockhart,</em> 2026 WL 3003727 (S.D.N.Y.  Oct. 6, 2026)(by consent):</li>
</ul>
<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. Publicly accessible AI tools pose unique risks to the security and integrity of Disclosure Materials, given the practical inability to claw back or delete data once it has been incorporated into a model.</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>d.  The Government will not submit any materials disclosed by the defense pursuant to Federal Rules of Criminal Procedure 26.2, 32.1 or other defense disclosure obligations (“Defense Materials”) to a publicly accessible version of an AI tool. The Government will not submit Defense Materials to an AI tool for which the AI tool provider or vendor 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>e.  The Government may submit Defense Materials to an AI tool (i) that maintains the confidentiality of Defense Materials; (ii) that will not expose any Defense Materials to third parties not authorized under this Protective Order to receive such materials; (iii) that will not retain or use any Defense Sealed Materials for model training; and (iv) all Defense Materials will be removed from the AI tool(s) at the conclusion of this case.</p></blockquote>
<ul>
<li><em>S.A. v. Santos</em>, 2026 WL 3003653 (Oct. 6, 2026)(same, by consent);</li>
<li>S.A. v. Robinson, 2026 WL 3003677 (Oct. 6, 2026)(same).</li>
<li><em>S.A. v. Peplow</em>, 2026 WL 3026474 (E.D. Cal. Oct. 8, 2026)(stipulation):</li>
</ul>
<blockquote><p>Artificial Intelligence Tools</p></blockquote>
<ol start="15">
<li>
<blockquote><p>No person or entity authorized to have access to protected material under the terms of the requested order shall input, transmit, upload, submit, quote, feed, process, generate output from, or otherwise expose any protected material received pursuant to the requested order to any artificial intelligence (“AI”) tool absent the prior written consent of the government or an order of the Court following a properly noticed motion to which the government has an opportunity to respond, unless that AI tool—a) is an enterprise-grade platform that counsel for the defendant has licensed; b) is subject to a binding written agreement that (i) requires the provider to keep all user-supplied data strictly confidential, and (ii) expressly prohibits the provider from using such data for training, fine-tuning, product improvement, or any purpose other than providing the contracted-for services; and c) employs technical and organizational security measures reasonably designed to prevent any unauthorized access, disclosure, or use of protected material.</p></blockquote>
</li>
<li>
<blockquote><p>The obligations and restrictions of this section apply even where the data or the protected material has been anonymized. “AI tool” means any automated system that uses statistical modeling, 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></blockquote>
</li>
<li>
<blockquote><p>By participating in this agreement, counsel for the defendant certifies: (i) they have implemented reasonable measures to ensure, if using any AI tool, it will maintain the protected discovery’s confidentiality as required by this Agreement and (ii) they will ensure all protected discovery is deleted from the tool once this case concludes.</p></blockquote>
</li>
<li>
<blockquote><p>Under no circumstances will any member of the defense team submit protected material to a publicly accessible AI system that retains and uses submitted data to train models. Such AI tools pose unique risks to the security and integrity of protected material, given the practical inability to claw back or delete data once it has been incorporated into a model.</p></blockquote>
</li>
</ol>
<ul>
<li><em>S.A. v. Sarris</em>, 2026 WL 2937892, at *2 (S.D.N.Y.  Sep 30, 2026)(by consent).</li>
<li><em>S.A. v. DeJesus</em>, 2026 WL 3034296 (S.D.N.Y. Oct. 9, 2026)(by consent).</li>
</ul>
<p><strong>Note</strong>: In a recent decision, the District of Maryland wrote: &#8220;In addition, Campbell must ensure that any use of generative artificial intelligence d<em>oes not violate the stipulated order governing confidential materials.</em> See ECF 21. TidalHealth expresses concern that Campbell violated the February 27, 2026 Protective Order’s <em>prohibition on submitting discovery material to public generative artificial intelligence tools.</em> ECF 41-1 at 11; see ECF 21 at ¶ 8 (imposing limitations on use of generative artificial intelligence). Campbell denies doing so. ECF 45 at 3. If future filings suggest improper submission of discovery materials to generative artificial intelligence tools, the Court will be more inclined to issue a show cause order and consider sanctions.&#8221; <em>Campbell v. TidalHealth, Inc.</em>, 2026 WL 2162749, at *10  (D. Md. Jul. 28, 2026)(Austin, J.)(emphasis added).  <a href="https://www.ediscoveryllc.com/a-i-protective-orders-are-becoming-routine-2/">This case was discussed in a prior post.</a></p>
<p>UPDATE:  STT Webos, Inc. v. ByteDance Ltd., 2026 WL 2138557, *13 (N.D. Cal. Jul. 24, 2026)(emphasis added):</p>
<blockquote><p>Artificial Intelligence Use. The Parties agree that <em>any documents</em>, electronically stored information (“ESI”), or other materials produced or exchanged in the course of this Action, <em>including but not limited to those designated</em> as “CONFIDENTIAL,” “HIGHLY CONFIDENTIAL – ATTORNEYS’ EYES ONLY,” or “HIGHLY CONFIDENTIAL – SOURCE CODE” under this Order, shall not be used, in whole or in part, <em>for prompts (inputs), completions (outputs), or embeddings</em> that are used to train, improve, re-train, or otherwise develop any artificial intelligence, foundation model, or large language model (collectively “AI Models”). This prohibition applies regardless of whether the AI Models are proprietary, open-source, or provided by a third party, and regardless of whether the use is for commercial, research, or any other purpose. The Parties further agree to take reasonable steps to ensure that their employees, counsel, agents, consultants, contractors, and any other persons or entities who may have access to such materials comply with this prohibition. Any violation of this provision may be addressed by the Court through appropriate remedies, including but not limited to sanctions.</p></blockquote>
<p>____</p>
<p><a href="#_ftnref1" name="_ftn1">[1]</a> <a href="https://www.ediscoveryllc.com/three-more-a-i-protective-orders/">Three More A.I. Protective Orders</a> (Oct. 9, 2026).</p>
]]></content:encoded>
			</item>
		<item>
		<title>Determining When the Duty to Preserve was Triggered is Critical to a Sanctions Analysis</title>
		<link>https://www.ediscoveryllc.com/determining-when-the-duty-to-preserve-was-triggered-is-critical-to-a-sanctions-analysis/</link>
		<pubDate>Sun, 04 Oct 2026 09:29:51 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[Litigation Hold: Trigger]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5605</guid>
		<description><![CDATA[Because a video of an alleged incident was destroyed pursuant to a reasonable information governance policy and before litigation was reasonably anticipated, spoliation sanctions were denied.  Acheneje v. Univ. of MD Medical Corp., 2026 WL 2880533 (D. Md. Sep 25, 2026)(Maddox, J.). Plaintiff’s employment claims arose out of her termination as a<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Because a video of an alleged incident was destroyed pursuant to a reasonable information governance policy and before litigation was reasonably anticipated, spoliation sanctions were denied<em>.  Acheneje v. Univ. of MD Medical Corp.,</em> 2026 WL 2880533 (D. Md. Sep 25, 2026)(Maddox, J.).</p>
<p>Plaintiff’s employment claims arose out of her termination as a clinical nurse. A series of interactions occurred, resulting in an investigation covering interviews of all staff and “review of video.”  “During and around the time of the two rapid responses, Plaintiff had a verbal interaction or altercation with another nurse, Gabrielle Spalt, and the two nurses have differing accounts of their encounter.”</p>
<p>Defendants moved for summary judgment.  The Court found no genuine dispute of material fact and granted the motion.</p>
<p>Plaintiff argued that summary judgment should be denied, in part, based on “potential spoliation of video evidence relevant to Plaintiff’s claims.  Specifically, Plaintiff contends that Defendants failed to preserve video footage of the interaction between her and Ms. Spalt during the rapid response events on September 16, 2023.”</p>
<p>Defendants relied on their information governance policy.  They told Plaintiff that the video footage was “retained for 30 days and was over-written pursuant to Defendants’ policy prior to notice of any legal claim and obligation to preserve footage.”</p>
<p>Plaintiff replied “that Defendant was on notice to preserve the video as of September 2023 because of the final written warning issued to Plaintiff and the specific request Plaintiff made to view the video during the investigation of the incident.”</p>
<p>Defendants responded “that there was no reason to anticipate litigation until Defendants received notice of Plaintiff’s filing of charges with the EEOC, in March 2024…. They contend that, pursuant to internal policy, the video footage from the September 16, 2023, incident was overwritten 30 days later, on or around October 15, 2023—well before they received notice of litigation.”</p>
<p>The Court wrote that “[s]poliation refers to the failure to preserve property for another’s use as evidence in pending or reasonably foreseeable litigation.” <em>Id</em>. (cleaned up; citation omitted).  The “mere existence” of a dispute does not trigger the duty to preserve.  The duty arises somewhere between knowledge of a dispute and direct, specific threats of litigation: “A non-exhaustive list of examples of events triggering the duty to preserve include the receipt of a demand letter, a request for evidence preservation, a threat of litigation, or a decision to pursue a claim.” <em>Id</em>. (cleaned up; citation omitted).</p>
<p>Applying those principles, the Court explained:</p>
<blockquote><p>Plaintiff cites no authority to support the proposition that her request to see the video of her interaction with Ms. Spalt and the final warning issued to her in September triggered a duty to preserve. Plaintiff did not issue any demand letter to Defendants, request preservation of the video, or threaten litigation at any point before the video was over-written in the normal course of Defendants’ business. In the grievance she submitted to HR in September 2023, Plaintiff alleged that video footage would show that she was not on her phone when Ms. Spalt confronted her, but the grievance contains no request for preservation or threat of litigation…. The disciplinary action and any request Plaintiff made to view the video footage could not, by themselves, make litigation reasonably foreseeable. The case upon which Plaintiff relies in her opposition indicates, contrary to her position, that the duty to preserve began when Defendants learned about Plaintiff’s filing with the EEOC. See <em>Membreno</em>, 338 F.R.D. at 72 (concluding that the defendants “should have reasonably anticipated litigation&#8230;when they received notice of” the plaintiff’s filing with the EEOC). Here, Plaintiff did not file a charge with the EEOC until March 2024, long after the video footage at issue would have been over-written in the normal course. Thus, Plaintiff fails to establish any entitlement to relief based on spoliation of evidence.</p></blockquote>
<p>Summary judgment followed.</p>
<p>The threshold inquiry for sanctions under Fed.R.Civ.P. 37(e) is whether “electronically stored information that should have been preserved in the anticipation or conduct of litigation” was “lost because a party failed to take reasonable steps to preserve it, and it cannot be restored or replaced through additional discovery….”  Here, Plaintiff failed to cross that threshold.</p>
<p>The Court wrote:</p>
<blockquote><p>Plaintiff argues that Defendants mishandled video evidence. However, one of Defendants’ employees reviewed the video footage of the September 2023 incident and concluded that it was “tough to see much” and that she “had a difficult time seeing anything in the nurses station.” &#8230; That employee did not see what Plaintiff alleged, namely that Ms. Spalt came towards Plaintiff “pointing her finger at her and yelling at her.”</p></blockquote>
<p>The Court did not address whether or not this showed a lack of prejudice. If so, it would have precluded Rule 37(e)(1) sanctions.</p>
<p>&nbsp;</p>
]]></content:encoded>
			</item>
		<item>
		<title>“MD lawyer scolded for fake citations after past AI issues”</title>
		<link>https://www.ediscoveryllc.com/md-lawyer-scolded-for-fake-citations-after-past-ai-issues/</link>
		<pubDate>Sat, 26 Sep 2026 20:35:25 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[News Stories]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5599</guid>
		<description><![CDATA[A Maryland attorney “is once again in hot water for filing a brief that included numerous false citations.”  I. Round, MD lawyer scolded for fake citations after past AI issues &#8211; Maryland Daily Record (Sep. 25, 2026). The article reports that: “U.S. District Judge Loren AliKhan is the latest in a string<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>A Maryland attorney “is <a href="https://thedailyrecord.com/2026/05/19/ai-hallucinations-lawyers-maryland/">once again</a> in hot water for filing a brief that included numerous false citations.”  I. Round, <a href="https://thedailyrecord.com/2026/09/25/ai-hallucinations-lawyers-quinn-patton/?utm_term=MD%20lawyer%20scolded%20for%20fake%20citations%20after%20past%20AI%20issues&amp;utm_source_platform=Act-On%2BSoftware&amp;utm_campaign=MD%20lawyer%20scolded%20for%20fake%20citations%20after%20past%20AI%20issues&amp;utm_medium=email&amp;ActOnUniqueID=MDDR151319&amp;utm_content=email&amp;utm_source=Act-On%2BSoftware">MD lawyer scolded for fake citations after past AI issues &#8211; Maryland Daily Record</a> (Sep. 25, 2026).</p>
<p>The article reports that: “U.S. District Judge Loren AliKhan is the latest in a string of judges and opposing lawyers in Maryland and Washington to call out [this named attorney’s] work.”  <em>Id</em>.</p>
<p>The Daily Record reported that, when it could not contact the attorney, it contacted the managing partner “who has also been scolded for false citations….” <em>Id</em>.</p>
<p>The article also states that one Judge wrote that Her Honor’s concerns “extend to counsel’s entire firm.”   <em>Id</em>.</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>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>
		<item>
		<title>Unilateral Deadlines</title>
		<link>https://www.ediscoveryllc.com/unilateral-deadlines/</link>
		<pubDate>Fri, 11 Sep 2026 23:55:08 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5521</guid>
		<description><![CDATA[Plaintiff filed a spoliation motion. The court deemed it “baseless.”  It wrote that the motion “faults Defendant for not certifying within forty-eight hours of service that it has preserved information relevant to this litigation.” The Court’s rejection of that motion was unequivocal: “Plaintiff cannot unilaterally set deadlines for Defendant and then seek<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Plaintiff filed a spoliation motion. The court deemed it “baseless.”  It wrote that the motion “faults Defendant for not certifying within forty-eight hours of service that it has preserved information relevant to this litigation.”</p>
<p>The Court’s rejection of that motion was unequivocal: “Plaintiff cannot unilaterally set deadlines for Defendant and then seek to sanction Defendant for failing to comply with them.”  <em>Dortie v. Marriott International, Inc.,</em> 2026 WL 2647599 (D. Md. Sep. 9, 2026)(Chasanow, J.).</p>
]]></content:encoded>
			</item>
		<item>
		<title>District of Maryland Hallucination Decision</title>
		<link>https://www.ediscoveryllc.com/district-of-maryland-hallucination-decision-2/</link>
		<pubDate>Mon, 07 Sep 2026 08:48:24 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5501</guid>
		<description><![CDATA[Because I practice in Maryland, I attempt to keep track of Maryland “hallucination” decisions. Johnson v. Nationstar Mortgage LLC, 2026 WL 2516390 (D. Md. Aug. 26, 2026), is a recent one. The Court had squarely warned plaintiff that Fed.R.Civ.P. 11 applied to unrepresented parties and attorneys in the context of “hallucinated” citations. <span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Because I practice in Maryland, I attempt to keep track of Maryland “hallucination” decisions. <em>Johnson v. Nationstar Mortgage LLC,</em> 2026 WL 2516390 (D. Md. Aug. 26, 2026), is a recent one.</p>
<p>The Court had squarely warned plaintiff that Fed.R.Civ.P. 11 applied to unrepresented parties and attorneys in the context of “hallucinated” citations.  Plaintiff apparently did not heed the warning.  However, plaintiff escaped sanctions because his case was dismissed on other grounds.</p>
<p>The Court wrote:</p>
<blockquote><p>Notwithstanding the foregoing admonition, it appears Plaintiff has once again cited a “hallucinated” case derived perhaps from use of a generative artificial intelligence (“AI”) tool (e.g., ChatGPT, Gemini, etc.). Specifically, Plaintiff cites to “Cooke v. Carrington Mortg. Servs., No. 22-1425 (4th Cir. 2023),”…. Plaintiff contends this case stands for the proposition that “servicer-imposed charges tied to improper insurance placement constitute a concrete injury.” … Upon challenge by Nationstar, Plaintiff later represented once again that “Cooke v. Carrington Mortg. Servs., No. 22-1425 (4th Cir. 2023)” is an “unpublished case” available at “2023 WL 3010355.” … Based on the court’s review, this case does not exist. The court has checked the Fourth Circuit case number—22-1425, and Westlaw citation—2023 WL 3010355—offered by Plaintiff to identify this case; neither directs the court to the referenced opinion. Indeed, the court further observes two decisions of this court bearing this caption: Cooke v. Carrington Mortg. Servs., No. CV TDC-18-0205, 2019 WL 3241128, at *1 (D. Md. July 18, 2019), and Cooke v. Carrington Mortg. Servs., No. CV TDC-18-0205, 2018 WL 6323116, at *7 (D. Md. Dec. 3, 2018)—neither of which pertains to “improper insurance placement.”</p>
<p><em>While this court has already cautioned Plaintiff that continued citation to hallucinated authorities or the like risks issuance of an order to show cause why he should not face sanctions under Rule 11, the court declines to take further action in the instant matter where Plaintiff’s case will be dismissed in full</em>. [emphasis added].</p></blockquote>
<p>For more District of Maryland AI decisions, please use the “category” District of Maryland, above.  For example, please see <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), <a href="https://www.ediscoveryllc.com/district-of-maryland-hallucination-decision/">District of Maryland “Hallucination” Decision</a> (May 5, 2026), and <a href="https://www.ediscoveryllc.com/district-of-md-standing-order-re-genai-in-court-filings/">District of MD Standing Order re GenAI in Court Filings</a> (Aug. 10, 2026).</p>
<p>For Maryland State court decisions, please see <a href="https://www.ediscoveryllc.com/maryland-copy-and-paste-hallucinations-case/">Maryland Copy and Paste “Hallucinations” Case – </a>(Jun. 17, 2026), <a href="https://www.ediscoveryllc.com/hallucinations-are-old-news-but-a-recent-maryland-decision-addresses-ethical-contours/">Hallucinations Are “Old News,” But a Recent Maryland Decision Addresses Ethical Contours</a> (Jan. 17, 2025), <a href="https://www.ediscoveryllc.com/maryland-fake-citation-case-court-issues-a-warning-referral-to-atty-grievance-commn/">Maryland Fake Citation Case – Court Issues a Warning – Referral to Atty. Grievance Comm’n.</a> (Nov. 2, 2025), and <a href="https://www.ediscoveryllc.com/marylands-proposed-anti-hallucination-rule/">Maryland’s Proposed Anti-Hallucination Rule</a> (Mar. 16, 2026).</p>
<p>UPDATE: <em>Aziz v. USA</em>, 2026 WL 2633445 (D. Md. Sep. 4, 2026)(Abelson, J.)(&#8220;The Court warned Plaintiffs about their high-volume approach in its previous opinion: &#8216;If Plaintiffs continue to file frivolous motions or include fabricated citations, and/or violate the [four-]page limitation set forth in the accompanying order, the Court may enjoin them from submitting further filings or consider imposing other sanctions.&#8217; <em>Aziz</em>, 2026 WL 1132884 at *3. As a review of the docket will indicate, Plaintiffs did not heed this warning, and have continued filing numerous motions. Many of these filings were over four pages, included hallucinated or fabricated citations, and contained frivolous arguments that misstated the law and/or facts. See, e.g., ECF No. 114 (&#8216;Plaintiff’s Emergency Motion to Compel Ruling on Pending § 1292(b) Motion; For Stay; And For Reconsideration of Orders Entered Without Jurisdiction&#8217;). The Court has nonetheless reviewed these motions and will deny all of them as either moot in light of the instant dismissal or denied for the reasons provided in the previous memorandum opinions. The Court will not issue an order to show cause regarding sanctions because it is dismissing this case. However, Plaintiffs are forewarned that similar conduct in this case or others may result in sanctions.&#8221;).</p>
]]></content:encoded>
			</item>
		<item>
		<title>A.I. Protective Orders Are Becoming Routine</title>
		<link>https://www.ediscoveryllc.com/a-i-protective-orders-are-becoming-routine-2/</link>
		<pubDate>Thu, 27 Aug 2026 09:22:39 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[District of MD]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Ethics]]></category>

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

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5458</guid>
		<description><![CDATA[Survivor A sued a school board and others arising out of alleged sexual abuse by the person who was then plaintiff’s teacher.  Survivor A v. Anne Arundel Co. Bd. of Education, 2026 WL 2326237 (D. Md. Aug. 11, 2026)(Aslan, J.). A series of discovery disputes followed. Because defense counsel improperly instructed a<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Survivor A sued a school board and others arising out of alleged sexual abuse by the person who was then plaintiff’s teacher.  <em>Survivor A v. Anne Arundel Co. Bd. of Education,</em> 2026 WL 2326237 (D. Md. Aug. 11, 2026)(Aslan, J.). A series of discovery disputes followed.</p>
<p>Because defense counsel improperly instructed a defense deponent not to answer questions, the Court ordered the deposition to be re-opened and cautioned counsel.  Because the requestor failed to establish a foundation, the request for a forensic examination of the opponent’s cell phone was denied.  Because one party impeded discovery, the opponent was awarded additional deposition hours.  Because one party produced 1,600 pages of text messages after deposition, the deposition was re-opened.</p>
<p style="text-align: center;"><strong><u>INSTRUCTIONS NOT TO ANSWER DEPOSITION QUESTIONS</u></strong></p>
<p>Plaintiff deposed school board employees. The Court wrote:  “Survivor A contends that counsel for the School Board improperly instructed a witness ‘not to answer a basic question’ and tendered an excerpt of the deposition transcript in support of his claim…. The transcript excerpt reveals an unnecessarily contentious exchange between counsel, both in and outside the presence of the witness.”</p>
<p>The Court noted that, under Fed.R.Civ.P. 30(c)(2), deposition testimony is generally taken subject to objection.  Instructions not to answer are limited to privilege, enforcement of a court order, and to present a Rule 30(d)(3) motion based on bad faith or an effort to harass.  The Court also noted its Discovery Guideline which made it presumptively improper to instruct a witness not to answer, except under Rule 30(d)(3).</p>
<p>So, here is what the Court said happened:</p>
<blockquote><p>Here, the deposition transcript reflects that the School Board’s counsel objected to Plaintiff’s counsel’s proposed line of questioning regarding text messages between Survivor A and Ms. Arnold [who was the “then-wife” of Survivor A’s “then-teacher”]  and repeatedly instructed the witness not to respond….</p></blockquote>
<p>The Court added:</p>
<blockquote><p>When there is an objection to a deposition question, counsel are expected to rise above their roles as advocates for a particular party, and, acting as officers of the court, resolve their differences on the spot without outside intervention.… The transcript reflects that rather than “rise above,” counsel argued back-and-forth in front of the witness regarding the propriety of the questioning and the basis for instructing the witness not to respond and, ultimately, the School Board’s counsel contacted the undersigned’s Chambers. [cleaned up].</p></blockquote>
<p>The ruling was unsurprising:</p>
<blockquote><p>Nearly two decades ago this Court noted that “[i]t has been the law in this circuit for 20 years that lawyers may not instruct witnesses not to answer questions during a deposition unless to assert a privilege.” <em>Boyd</em>, 173 F.R.D. at 144 (citing <em>Ralston Purina Co. v. McFarland, </em>550 F.2d 967 (4th Cir. 1977)). The School Board’s counsel did not assert privilege as the basis for his objection. Rather, he contended that Plaintiff’s counsel was asking about documents the witness had not seen previously … and was attempting to elicit an improper opinion…. The School Board’s counsel also argued that the question had no foundation … and asserted without particularity that Plaintiff’s counsel had been “badgering” the witness “all day with questions” …. <em>None of these objections support an instruction that the witness should not respond to the questions posed. Counsel for the School Board’s instructions in that regard were therefore improper. Moreover, his behavior and language were unacceptable</em> and inconsistent with this Court’s Discovery Guidelines, which require attorneys “to behave professionally and with courtesy towards all involved in the discovery process.” Local Rules, Appx. A, Guideline 1 ¶ d. Counsel for the School Board is cautioned that he must advocate within the bounds of this governing framework. <em>The witness’s deposition will be reopened so that Survivor A may complete his questioning</em>. [emphasis added].</p></blockquote>
<p style="text-align: center;"><strong><u>FORENSIC EXAMINTION OF SURVIVOR A’S CELL PHONE</u></strong></p>
<p>The school board sought a forensic examination of Survivor A’s cell phone.  Survivor A’s counsel replied that the existence of that phone was known to defense counsel before Survivor A was deposed. Additionally: “Survivor A’s cellular telephone contains 1,428 text chains and approximately 7,000 photographs and 3,000 videos that span approximately eight years, and that some of the material is protected by privilege.”</p>
<p>Further, Survivor A reported that “Survivor A has worked with Defendants to find and produce voluminous discovery from the cellular telephone, including using 34 search terms, ‘most of which came directly from Defendants’ counsel.’”</p>
<p>The school board asserted that a forensic examination was needed for a complete record.  But the Court wrote: “The School Board does not, however, identify any gap in Survivor A’s production….  Instead, the School Board posits that some material on the cellular telephone was deleted.”</p>
<p>The defense argument fell flat: “This argument carries little weight because it lacks an articulated foundation or timeline.”</p>
<p>In an argument that in my opinion borders on frivolous: “The School Board further contends that ‘Plaintiff’s counsel should not be the determinator [of] what information&#8230;should be disclosed to the defendants.’”</p>
<p>The Court wrote: “Yet, that is precisely how discovery operates. The discovery process is designed to be extrajudicial, and it relies on responding parties to search their own records and produce documents or other data.” [cleaned up].<a href="#_ftn1" name="_ftnref1">[1]</a></p>
<p>It also provided a detailed analysis of the predicate for requesting a forensic examination:</p>
<blockquote><p>Federal Rule of Civil Procedure 34 governs, among other things, a request to “inspect, copy, test, or sample” electronically stored information, which includes forensic examination of electronic devices. Fed. R. Civ. P. 34(a)(1)(A)…. Making forensic image backups of computers is only the first step of an expensive, complex, and difficult process of data analysis that can divert litigation into side issues and satellite disputes involving the interpretation of potentially ambiguous forensic evidence…. What is more, the Advisory Committee on Civil Rules has cautioned that “[<em>c</em>]<em>ourts should guard against undue intrusiveness</em> resulting from inspecting or testing [electronic information] systems.”…. A forensic examination of electronically stored information—something sister courts in this Circuit have described as “a drastic discovery measure,” <em>… </em>must therefore be proportional to the needs of the case. …  A request for forensic examination is, among other things, “subject to the proportionality limitations applicable to all discovery under Rule 26(b)(2)(C), including the prohibition of discovery that is unreasonably cumulative, duplicative or seeks discovery that could be obtained from some more convenient, less burdensome[,] or less expensive source”. [cleaned up]</p></blockquote>
<p>Applying those principles, the Court rejected the school board’s request:</p>
<blockquote><p>Here, the School Board has not explained how Survivor A’s discovery responses are insufficient or why forensic imaging is warranted and proportionate to the needs of this case, particularly in light of the intrusive nature of a forensic examination of a personal cellular telephone.</p></blockquote>
<p>The Court resolved other disputes, including one over additional deposition hours based on a post-deposition disclosure by Survivor A of 1,600 pages of text messages, resulting in an additional 3.5 hours of deposition.</p>
<p>Because of the school board’s “animosity” and because it had “foreclosed questioning altogether in at least one deposition,” Survivor A was granted 35 additional deposition hours.</p>
<p>For related information, see also:</p>
<ul>
<li><a href="https://www.ediscoveryllc.com/request-to-appoint-neutral-forensic-expert-denied-as-speculative-and-unsupported/">Request to Appoint Neutral Forensic Expert Denied as Speculative and Unsupported</a></li>
<li><a href="https://www.ediscoveryllc.com/standard-for-court-ordered-forensic-examinations-when-does-misconduct-cross-the-rubicon/">Standard for Court-Ordered Forensic Examinations – When Does Misconduct “Cross the Rubicon”?</a></li>
<li><a href="https://www.ediscoveryllc.com/motion-to-compel-forensic-image-of-cell-phone-granted-in-part-denied-in-part/">Motion to Compel Forensic Image of Cell Phone: Granted in Part; Denied in Part</a></li>
<li><a href="https://www.ediscoveryllc.com/another-decision-on-forensic-imaging-of-an-opponents-cell-phone/">Another Decision on Forensic Imaging of an Opponent’s Cell Phone</a></li>
<li><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></li>
<li><a href="https://www.ediscoveryllc.com/district-of-maryland-sets-guidelines-for-cell-phone-preservation-in-place/">District of Maryland Sets Guidelines for Cell Phone Preservation in Place</a></li>
</ul>
<p>_____</p>
<p><a href="#_ftnref1" name="_ftn1">[1]</a> See generally <a href="https://www.ediscoveryllc.com/unsupervised-self-collection-predictably-led-to-problems/">Unsupervised Self-Collection Predictably Led to Problems</a> and <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>.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Don’t Sue the Judge</title>
		<link>https://www.ediscoveryllc.com/dont-sue-the-judge/</link>
		<pubDate>Tue, 11 Aug 2026 16:14:34 +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=5410</guid>
		<description><![CDATA[&#8220;A lawsuit by an attorney against a state judge who sanctioned him should be dismissed, a federal magistrate judge recommended Friday.” I. Round, MD attorney’s lawsuit against judge should be thrown out, magistrate says &#8211; Maryland Daily Record (Aug. 10, 2026). [Attorney Nathan] Charles sued [Judge Louis] Leibowitz last October after the<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>&#8220;A lawsuit by an attorney against a state judge who sanctioned him should be dismissed, a federal magistrate judge recommended Friday.” I. Round, <a href="https://thedailyrecord.com/2026/08/10/lawyer-lawsuit-against-judge-maryland/?utm_medium=email&amp;utm_source=Act-On+Software&amp;utm_content=Editorial&amp;utm_term=MD%20attorney%5Cu2019s%20lawsuit%20against%20judge%20should%20be%20thrown%20out%20magistrate%20says&amp;utm_campaign=MD%20attorney%5Cu2019s%20lawsuit%20against%20judge%20should%20be%20thrown%20out%20magistrate%20says&amp;ActOnUniqueID=MDDR151319">MD attorney’s lawsuit against judge should be thrown out, magistrate says &#8211; Maryland Daily Record</a> (Aug. 10, 2026).</p>
<blockquote><p>[Attorney Nathan] Charles sued [Judge Louis] Leibowitz last October after the judge, who presided over some proceedings in his divorce, twice sanctioned him and warned him to control his anger after he threatened to sue a loan officer. Charles argued the orders and warnings violated his rights to free speech and due process because he hadn’t committed misconduct.</p>
<p>Leibowitz ordered him to pay $23,680 in attorneys’ fees to his ex-wife for his appeal of another judge’s custody order, as well as $1,222 as a sanction for a contempt petition Charles had filed. The judge later withdrew the fine, and Charles withdrew the contempt petition.</p></blockquote>
<p><em>Id</em>.  The article states that Mr. Charles sought leave to add five circuit court and three Appellate Court judges.</p>
<blockquote><p>[U.S. Magistrate Judge Timothy] Sullivan recommended that the case be dismissed and that Charles not be allowed to amend his complaint [because amendment was futile]. He wrote that the lawsuit clearly ran afoul of the Rooker-Feldman doctrine, which prevents “state-court losers” from asking federal judges to review and reject judgments with which they disagree. He was not persuaded that the complaint raised legitimate constitutional issues that were separate from the divorce case.</p>
<p>“During this case, the Plaintiff has endeavored to frame his case as one that involves independent and separate issues from that of the state court divorce and custody proceedings,” Sullivan wrote.</p>
<p>“Yet it is apparent from his Complaint that he is asking this Court to review the sanctions orders, find them unconstitutional, and enjoin Judge Leibowitz from imposing any similar orders in the future.”</p></blockquote>
<p>The Daily Record reports: “This is his second lawsuit against a judge arising from the divorce case; the first was against Montgomery County Circuit Judge Christopher Fogleman. Charles voluntarily dismissed that case shortly after he sued Leibowitz.”</p>
<p>The decision is <em>Charles v. Hon. Louis M. Leibowitz,</em> 2026 WL 2279325, at *1 (D. Md. Aug. 7, 2026).  “Before Judge Leibowitz issued the sanctions, he warned that if Plaintiff continued to maintain an angry attitude and instigate additional issues (like threatening a loan officer that he would sue her), making the case more difficult and heightening the existing tension in the case, then Plaintiff would be forced to pay attorney&#8217;s fees.” <em>Id</em>. at *1.</p>
<p>Mr. Charles’ demand for relief was: “a. Issue a declaratory judgment that sanctions imposed against Plaintiff based on his speech violate the First and Fourteenth Amendments; b. Enter a preliminary and permanent injunction prohibiting Defendant from imposing attorney&#8217;s fees sanctions against Plaintiff based on the content or tone of his communications, filings, or criticisms,” and for costs. <em>Id</em>. at *2.</p>
<p>The federal Court wrote: “For the reasons set forth below, I recommend that the Motion be granted because the Court lacks subject matter jurisdiction. The Court need not reach the issue of whether Plaintiff has properly stated a claim under Rule 12(b)(6).”  <em>Id</em>. at *2.  “The Supreme Court has consistently held firm to these principles, creating what has become known as the <em>Rooker-Feldman</em> doctrine and making it clear that federal district courts lack subject matter jurisdiction to review state court judgments.”  <em>Id</em>. at *3.</p>
<p>&nbsp;</p>
]]></content:encoded>
			</item>
	</channel>
</rss>
