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

<channel>
	<title>ESI Protocol a/k/a Discovery Plans &#8211; E-Discovery LLC</title>
	<atom:link href="https://www.ediscoveryllc.com/category/esi/esi-protocol-aka-discovery-plans/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ediscoveryllc.com</link>
	<description>Mediation of E-Discovery Disputes</description>
	<lastBuildDate>Sat, 10 Oct 2026 23:59:42 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>A Unique A.I. Protective Order</title>
		<link>https://www.ediscoveryllc.com/a-unique-a-i-protective-order/</link>
		<pubDate>Fri, 09 Oct 2026 20:52:43 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5633</guid>
		<description><![CDATA[A stipulated AI Protective Order in Dean &#38; Deluca Brands, Inc. v. Fire Brands Innovation, LLC, 2026 WL 2905875 (S.D.N.Y.  Sep. 29, 2026)(emphasis added), stated: A producing Party may utilize technology-assisted review, predictive coding, generative artificial intelligence, analytics, keyword searching, clustering, email threading, concept searching, active learning, or other automated or algorithmic<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>A stipulated<em> AI Protective Order in Dean &amp; Deluca Brands, Inc. v. Fire Brands Innovation, LLC,</em> 2026 WL 2905875 (S.D.N.Y.  Sep. 29, 2026)(emphasis added), stated:</p>
<blockquote><p>A producing Party may utilize technology-assisted review, predictive coding, generative artificial intelligence, analytics, keyword searching, clustering, email threading, concept searching, active learning, or other automated or algorithmic tools in connection with the collection, processing, search, review, redaction, privilege review, or production of documents and ESI. <em><strong>The producing Party shall have sole discretion regarding the selection, configuration, implementation, and use of such tools and methodologies. No producing Party shall be required to disclose</strong></em> the identity, version, prompts, workflows, <em><strong>training materials, validation procedures</strong></em>, review protocols, <strong><em>quality control measures, precision rates, recall rates, elusion testing</em></strong>, or other details concerning the use of such tools <strong><em>absent a showing of good cause</em></strong> by the receiving Party or an order of the Court. The use of such technologies shall not, by itself, provide a basis for challenging the adequacy of a Party’s collection, review, privilege determinations, or production.</p></blockquote>
<p>By comparison, please see <a href="https://www.ediscoveryllc.com/three-more-a-i-protective-orders/">Three More A.I. Protective Orders</a> (Oct. 9, 2026), and the posts listed therein.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Three More A.I. Protective Orders</title>
		<link>https://www.ediscoveryllc.com/three-more-a-i-protective-orders/</link>
		<pubDate>Fri, 09 Oct 2026 08:30:52 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[Commercial Litigation]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Important Posts]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Conference of Parties]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Objections]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5617</guid>
		<description><![CDATA[I have written a series of posts suggesting that AI protective orders are becoming the standard of care.  See A.I. Protective Order by Consent in Google Case (Sep. 13, 2026). The jointly requested A.I. protective order in Hoffman v. Univ. of Nebraska Medical Ctr., 2026 WL 2969621 (D. Neb. Oct. 2, 2026),<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>I have written a series of posts suggesting that AI protective orders are becoming the standard of care.  <em>See</em> <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).</p>
<p>The jointly requested A.I. protective order in <em>Hoffman v. Univ. of Nebraska Medical Ctr.,</em> 2026 WL 2969621 (D. Neb. Oct. 2, 2026), states:</p>
<blockquote><p>Artificial Intelligence. Qualified Recipients shall not, without the Producing Party’s express written consent, upload, submit, or otherwise provide Confidential Discovery Material (or any information extracted therefrom) or any deposition testimony taken in this matter to any open-source artificial intelligence platform or service including, but not limited to, platforms or services that use or assemble uploaded information to train or improve machine-learning models. This prohibition applies regardless of whether the artificial intelligence platform or service represents it will maintain the confidentiality of information submitted by the user. The parties and their counsel are not prohibited from uploading, submitting, or otherwise providing Confidential Discovery Material (or information extracted therefrom) or any deposition testimony taken in this matter to a closed-source artificial intelligence platform or service, including Harvey, Westlaw, LexisNexis, Servient’s AI Canvas, or any other closed-source artificial intelligence platform or service agreed to by the parties.</p></blockquote>
<p>In <em>ANR Pipeline Co., LLC v. B&amp;B Metal Processing Co., Inc.,</em> 2026 WL 2970050 (E.D. Wisc. Oct. 2, 2026), the court wrote:</p>
<blockquote><p>On September 22, 2026, the parties filed a joint motion for the entry of a protective order, with a stipulated proposed order…. The parties request that the Court enter such an order to “prevent public disclosure of nonpublic confidential technical, commercial, or business information that may be exchanged in discovery.” &#8230; Federal Rule of Civil Procedure Rule 26(c) allows for an order “to protect a party or person from annoyance, embarrassment, oppression, or undue burden or expense” including “requiring that a trade secret or other confidential research, development, or commercial information &#8230; be revealed only in a specified way.” Fed. R. Civ. P. 26(c)(1)(G); <em>see also</em> Civ. L.R. 26(e).</p>
<p>Protective orders are an exception to the general rule that pretrial discovery must occur in the public eye…. Litigation must be conducted in public to the maximum extent consistent with respecting trade secrets &#8230; and other facts that should be held in confidence….</p>
<p>Nonetheless, the Court can enter a protective order if the parties have shown good cause and that the order is narrowly tailored to serve that cause…. The Court can find that even broad, blanket orders are narrowly tailored and permissible when it finds that two factors are satisfied: (1) that the parties will act in good faith in designating the portions of the record that should be subject to the protective order; and (2) that the order explicitly allows the parties to the case and other interested members of the public to challenge the sealing of documents….</p>
<p>The Court finds that the parties have requested the protective order in this action in good faith. The parties report that this case will entail the disclosure of confidential technical information about the parties…. Thus, the Court is satisfied that there exists a sufficient basis for the requested protective order. [cleaned up].</p></blockquote>
<p>However, the court modified the parties’ request to establish parameters for the use of A.I. as it pertains to confidential documents.  <em>Id</em>. at *1.  The order states:</p>
<blockquote><p>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>
<p><em>Id</em>. at *5.</p>
<p>A protective order was also entered by consent in <em>U.S.A. v. Amanuel</em>, 2026 WL 2964210 (S.D.N.Y. Oct. 1, 2026):</p>
<blockquote><p><strong>Restrictions on Use of Artificial Intelligence Tools to Process Disclosure Materials.</strong></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 <u>not</u> 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 <u>may</u> 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></blockquote>
<p>Some prior posts are:</p>
<ul>
<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>U.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>U.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>U.S. v. Perez-Feliz,</em> 2026 WL 2754823 (S.D.N.Y. Sep. 17, 2026)(consent order);</li>
<li><em>U.S. v. Montes</em>, 2026 WL 2824059, at *1 (S.D.N.Y. Sep. 21, 2026)(by consent);</li>
<li><em>U.S. v. Hawkins,</em> 2026 WL 2825014, at *2 (S.D.N.Y. Sep. 21, 20260(same);</li>
<li><em>U.S.A. v Amanuel</em>, 2026 WL 2972618 (S.D.N.Y. Oct. 2, 2026)(by consent).</li>
</ul>
<p>This blog was initially posted on  <a href="https://edrm.net/author/michaeldberman/">Electronic Discovery Reference Model</a>.</p>
<p><strong>UPDATE</strong>:</p>
<p><em>White v. Chime Financial, Inc.,</em> 2026 WL 3000904 (W.D. Wash. Oct. 6, 2026)(stipulated):</p>
<blockquote><p>USE OF ARTIFICIAL INTELLIGENCE<br />
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>
<p><em>U.S.A.  v. Lockhart,</em> 2026 WL 3003727 (S.D.N.Y.  Oct. 6, 2026)(by consent):</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. 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>*2 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>
<p><em>U.S.A. v. Santos</em>, 2026 WL 3003653 (Oct. 6, 2026)(same, by consent); U.S.A. v. Robinson, 2026 WL 3003677 (Oct. 6, 2026)(same).</p>
<p><em>U.S.A. v. Peplow</em>, 2026 WL 3026474 (E.D. Cal. Oct. 8, 2026)(stipulation):</p>
<blockquote><p>Artificial Intelligence Tools<br />
15. 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—</p>
<p>a) is an enterprise-grade platform that counsel for the defendant has licensed;<br />
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<br />
c) employs technical and organizational security measures reasonably designed to prevent any unauthorized access, disclosure, or use of protected material.</p>
<p>16. 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>
<p>17. 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>
<p>18. 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>
<p><em>U.S.A. v. Sarris</em>, 2026 WL 2937892, at *2 (S.D.N.Y.  Sep 30, 2026)(by consent).</p>
]]></content:encoded>
			</item>
		<item>
		<title>Court Ordered a Framework Where Parties Were Unable to Agree on an ESI Protocol</title>
		<link>https://www.ediscoveryllc.com/court-ordered-a-framework-where-parties-were-unable-to-agree-on-an-esi-protocol/</link>
		<pubDate>Thu, 24 Sep 2026 15:33:18 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Conference of Parties]]></category>
		<category><![CDATA[Cooperation]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5591</guid>
		<description><![CDATA[In Tudor v. State Farm General Ins. Co., 2026 WL 2668435 (N.D. Cal. Sep. 10, 2026), the parties were unable to agree on an ESI Protocol.  The court established a framework for resolving the dispute.  I suggest that, in doing so, the court provided a strong incentive for the parties to resolve<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>In <em>Tudor v. State Farm General Ins. Co.,</em> 2026 WL 2668435 (N.D. Cal. Sep. 10, 2026), the parties were unable to agree on an ESI Protocol.  The court established a framework for resolving the dispute.  I suggest that, in doing so, the court provided a strong incentive for the parties to resolve their disputes.</p>
<p>The court entered the following order:</p>
<blockquote><p><strong>The Parties are ORDERED to continue to reasonably and promptly communicate and meet and confer to submit a Joint Proposed ESI Protocol by no later than September 23, 2026.</strong> <em>See Litton v. Roblox Corp.</em>, 2026 WL 1483493, at *4 (N.D. Cal. May 27, 2026). <strong>To the extent the Parties have remaining disputes over the ESI Protocol, the Parties SHALL file by no later than September 23, 2026:</strong> (1) a Joint Redline of the Joint Proposed <strong>ESI</strong> <strong>Protocol</strong> (compiled jointly in a single document showing the Parties respective competing proposed language next to each other at each disputed location and comparing the proposed <strong>ESI</strong> <strong>Protocol</strong> against the Court’s Model <strong>ESI</strong> <strong>Protocol</strong>), (2) declarations from counsel explaining the substantive differences between the Proposed Joint <strong>ESI</strong> <strong>Protocol</strong> from the Model <strong>ESI</strong> <strong>Protocol</strong>, and (3) a Further Joint Discovery Letter Brief (complying with the Court’s Standing Discovery Order) which sets forth the Parties’ arguments on the issues remaining in dispute as to the specific competing disputed language (including why that Party’s proposed edits should be adopted and not the competing language from the other Party). Any additions the Parties do not agree upon <strong>SHALL</strong> be denoted in the Joint Redline with different assigned colors for the Court’s ease of reference; one Party’s edits shall all be in green, the other Party’s shall all be in red. To the extent any edits from either Party do not have competing language from the other Party, the Court will construe such edits as unopposed.</p></blockquote>
<p><em>Id</em>. at *4 (emphasis in original).</p>
<p>The court added:</p>
<ul>
<li>“As noted at the hearing, the Court cautions against excessive or unnecessary deviations from the Model ESI Protocol.”</li>
<li>“The Court has broad authority and discretion to assist the Parties in resolving ESI disputes.”</li>
<li>If “the parties are unable to come to an agreement regarding all terms contained within an ESI discovery agreement, the Court will, in its discretion, assist the parties in doing so.”</li>
<li>“As part of our oversight responsibilities in discovery we have the discretion to modify ESI search term parameters.”</li>
</ul>
<p><em>Id</em>. (citations omitted).</p>
]]></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>Thank You &#8211; Citation Re AI Protective Orders</title>
		<link>https://www.ediscoveryllc.com/thank-you-citation-re-ai-protective-orders/</link>
		<pubDate>Mon, 14 Sep 2026 19:25:57 +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[News Stories]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Computer Usage Policies]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5535</guid>
		<description><![CDATA[Thank you to Cimplify for citing one of my blogs on protective orders.   Stepping Up to the Plate: Protective Orders to Restrict AI Training on Produced Data &#8211; Cimplifi Cimplify discussed a number of cases and wrote: As noted by Michael Berman in his blog for his site E-Discovery LLC, “Protective orders<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Thank you to Cimplify for citing one of my blogs on protective orders.   <a href="https://www.cimplifi.com/resources/stepping-up-to-the-plate-protective-orders-to-restrict-ai-training-on-produced-data/">Stepping Up to the Plate: Protective Orders to Restrict AI Training on Produced Data &#8211; Cimplifi</a></p>
<p>Cimplify discussed a number of cases and wrote:</p>
<blockquote><p>As noted by Michael Berman in his blog for his site <a href="https://www.ediscoveryllc.com/" target="_blank" rel="noopener">E-Discovery LLC</a>, “Protective orders addressing the use of A.I. to review materials produced to an opponent in discovery are becoming routine.”</p></blockquote>
<p>Cimplify concludes: &#8220;Given the risks associated with public AI platforms, protective orders that limit the ability of opposing parties to upload sensitive and confidential produced documents into a public AI tool are essential today. But the considerations associated with AI are changing rapidly. It’s important to keep that in mind when drafting your own protective order to protect your organization’s sensitive and confidential data.&#8221;</p>
]]></content:encoded>
			</item>
		<item>
		<title>A.I. Protective Order by Consent in Google Case</title>
		<link>https://www.ediscoveryllc.com/a-i-protective-order-by-consent-in-google-case/</link>
		<pubDate>Sun, 13 Sep 2026 09:19:26 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5529</guid>
		<description><![CDATA[The following AI Protective Order was stipulated in Skaf v. Google LLC, 2026 WL 2620563, at *10-11 (S.D.N.Y. Sep. 4, 2026): Use of Generative Artificial Intelligence Tools and Large Language Models. Protected Material, and all information derived therefrom, shall not be inputted, uploaded, or submitted to any open, publicly accessible or freely<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>The following AI Protective Order was stipulated in <em>Skaf v. Google LLC</em>, 2026 WL 2620563, at *10-11 (S.D.N.Y. Sep. 4, 2026):</p>
<blockquote><p><u>Use of Generative Artificial Intelligence Tools and Large Language Models.</u> Protected Material, and all information derived therefrom, shall not be inputted, uploaded, or submitted to any open, publicly accessible or freely available consumer-grade Large Language Model (“LLM”) or Artificial Intelligence (“AI”) tool (collectively, “AI Tools”). Protected Material may only be inputted, uploaded, or submitted to an AI Tool that is enterprise-grade and maintains confidential information using industry standard data security safeguards (“Confidential AI Tool”) after the Receiving Party first ensures that its contract with the AI Provider of the Confidential AI Tool:</p>
<p>(1) Prohibits the AI Provider from storing or using inputs to train, refine, or improve its model;</p>
<p>(2) Prohibits the AI Provider from disclosing inputs, metadata, and any information generated by the Confidential AI Tool to any third party, including integrated third party tools, except where such disclosure is essential to facilitating delivery of the service, in which case that third party shall be bound by obligations no less protective than those required by this Order; and</p>
<p>(3) Permits the Receiving Party to remove or delete the Protected Material, and any information generated by the Confidential AI Tool upon request.</p>
<p>A Receiving Party intending to use a Confidential AI Tool that it contends meets these requirements must retain written documentation of these contractual protections. In addition, the Protected Material, and any information generated by the Confidential AI Tool, including residual information stored in the Confidential AI Tool as a result of the submission of the Protected Material, must be deleted from the Confidential AI Tool at the close of the litigation, and in accordance with the Final Disposition section below. Any inputs, outputs, models, or other artifacts (e.g., embeddings, indexes, or logs) used in or created by a Confidential AI Tool that are derived from or contain Protected Material shall be subject to Section 7.1 and shall not be used for any purpose other than prosecuting or defending this litigation.</p>
<p>For the avoidance of doubt, submitting Protected Material, or excerpts therefrom, to any AI Tool that does not meet the requirements of this section is considered unauthorized disclosure to a third party under Section 10 of this Order. Nothing in this provision shall alter the obligations set forth in Section 1 (“Purposes and Limitations”) and Section 12.9 (“Data Security”) of this Order.</p></blockquote>
<p>For more information on A.I. Protective Orders, please visit:</p>
<ul>
<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>
</ul>
<p>UPDATE: &#8220;Use of Large Language Model or Generative AI. A Party must not load, upload, input, import, submit, or otherwise transfer Confidential Information, Highly Confidential Information, or Restricted Highly Confidential Information to a publicly accessible Large Language Model (“LLM”) or generative artificial intelligence (“GenAI”) platform. Before using Confidential Information, Highly Confidential Information, or Restricted Highly Confidential Information in any non-publicly accessible LLM or GenAI platform, a Party must ensure that the LLM or GenAI platform cannot and will not utilize Confidential Information, Highly Confidential Information, or Restricted Highly Confidential Information to train public models or otherwise disclose Confidential Information, Highly Confidential Information, or Restricted Highly Confidential Information to other users of the LLM or GenAI platform not authorized to receive such materials.&#8221;  <em>U.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).</p>
<p>UPDATE: <em>U.S.A. v. Jones</em>, 2026 WL 2607719, at *2 (S.D.N.Y. Sep. 3, 2026).</p>
<p>UPDATE: <em>Doe v. Google LLC</em>, 2026 WL 2584519 (N.D. Cal. Sep. 1, 2026):</p>
<blockquote><p>Any person in possession of Protected Material will maintain appropriate administrative, technical, and organizational safeguards (“Safeguards”) that protect the security and privacy of Protected Material, <em>including restrictions regarding the disclosure or use of Protected Material in any large language models or any artificial intelligence services.</em> The Safeguards will meet relevant industry standards and limit the collection, storage, disclosure, use of, or access to Protected Material solely to personnel and purposes authorized by this Order. As part of these Safeguards, each person will use a secure transfer method for all transfers or communication of Protected Material, and take reasonable measures to password protect and encrypt Protected Material. Each person will ensure that anyone acting on that person’s behalf is subject to the Safeguards or otherwise provides equivalent or greater protections for the security and privacy of Protected Material. [emphasis added].</p></blockquote>
<p>&#8220;Such restrictions shall, at a minimum, prohibit the disclosure or use of Protected Material in any large language models or artificial intelligence services that are accessible to the public or will capture entered data in order to train what is accessible by the public.&#8221;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			</item>
		<item>
		<title>No Violation of A.I. Protective Order</title>
		<link>https://www.ediscoveryllc.com/no-violation-of-a-i-protective-order/</link>
		<pubDate>Fri, 11 Sep 2026 20:30:43 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Conference of Parties]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Objections]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5519</guid>
		<description><![CDATA[Courts are routinely granting A.I. protective orders by consent.  U.S. v. Paula, 2026 WL 2665024, at *2 (S.D.N.Y.  Sep. 10, 2026). In Elgin v. Wells Fargo Bank, N.A., 2026 WL 2664674, at *1 (N.D. Cal. Sep. 9, 2026), Wells Fargo asserted that Plaintiff violated such a protective order.  “Specifically, Wells Fargo contends<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>Courts are routinely granting A.I. protective orders by consent.  <em>U.S. v. Paula</em>, 2026 WL 2665024, at *2 (S.D.N.Y.  Sep. 10, 2026).</p>
<p>In <em>Elgin v. Wells Fargo Bank, N.A.,</em> 2026 WL 2664674, at *1 (N.D. Cal. Sep. 9, 2026), Wells Fargo asserted that Plaintiff violated such a protective order.  “Specifically, Wells Fargo contends that Plaintiff violated the stipulated protective order by uploading Wells Fargo’s discovery requests into an AI tool and then responding to those rewritten requests rather than the requests propounded.”  <em>Id</em>.  Two weeks later, Plaintiff served corrected responses.</p>
<p>The court wrote:</p>
<blockquote><p>In opposition, Plaintiff clarifies that the stipulated protective order was not violated, because the material uploaded into the closed AI tool was not confidential and AI was not used to respond to the rewritten requests. Moreover, Plaintiff explains that Wells Fargo did not produce any documents marked “Confidential” until one week after the errant responses were served.…. <em>Plaintiff’s points are well taken. </em>Since Plaintiff provided corrected responses to all of the discovery devices within two weeks of the errant responses, and <em>Plaintiff did not violate the stipulated protective order</em>, the Court declines to find that Plaintiff waived all objections to the respective discovery devices or find that the requests for admission must be admitted.</p></blockquote>
<p><em>Id</em>. at *1 (emphasis added).</p>
<p>The court added: “Furthermore, the parties are advised that the Court has limited, judicial resources and does not appreciate unnecessary motion practice. Plaintiff served the corrected responses to all three discovery devices prior to the parties’ completion of the meet and confer process, which should have resolved this dispute informally. This is particularly true given the extreme relief sought by Wells Fargo. The Court trusts that, going forward, the parties will be more judicious in deciding which disputes require court intervention.”</p>
<p>For more information on AI Protective Orders, please visit:</p>
<ul>
<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>
</ul>
<p>&nbsp;</p>
]]></content:encoded>
			</item>
		<item>
		<title>Use of an A.I. Recorder in Depositions?  In a “Meet and Confer”?</title>
		<link>https://www.ediscoveryllc.com/use-of-an-a-i-recorder-in-depositions-in-a-meet-and-confer/</link>
		<pubDate>Thu, 03 Sep 2026 10:37:51 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Computer Usage Policies]]></category>
		<category><![CDATA[Conference of Parties]]></category>
		<category><![CDATA[Cooperation]]></category>

		<guid isPermaLink="false">https://www.ediscoveryllc.com/?p=5515</guid>
		<description><![CDATA[In Greco v. Hon. Robert W. Lane, 2026 WL 2446747 (D. Nev. Aug. 19, 2026), the court held that there was no procedural defect in a request to use AI to record a deposition. Substantive questions were left open. “Plaintiff served two Rule 30(b)(6) notices of deposition on Nye County. ECF No.<span class="excerpt-hellip"> […]</span>]]></description>
				<content:encoded><![CDATA[<p>In <em>Greco v. Hon. Robert W. Lane</em>, 2026 WL 2446747 (D. Nev. Aug. 19, 2026), the court held that there was no <em>procedural</em> defect in a request to use AI to record a deposition. Substantive questions were left open.</p>
<blockquote><p>“Plaintiff served two Rule 30(b)(6) notices of deposition on Nye County. ECF No. 58 Exhibits A and B. Both notices (1) name Mark Gancarz as the person to testify on the County’s behalf, (2) request the production of documents, and (3) designate the recording method by stenographic means and/or video recording.”</p>
<p>Plaintiff moves to use the <a href="https://www.mobvoi.com/us?im_ref=w%3ACwgD2OsxycUo-SfwQdtUDBUkrxCKUONwnV0s0&amp;utm_source=impact&amp;utm_campaign=Bing%20Rebates%20by%20Microsoft2003851&amp;utm_medium=affiliate&amp;sharedid=EdgeBingFlow&amp;irpid=2003851&amp;irgwc=1&amp;afsrc=1">Mobvoi TicNote</a>, an artificial-intelligence voice recorder, to maintain a secondary audio record of the depositions…. Rule 30(b)(3)(B) permits any party, with prior notice to the deponent and the other parties, to designate an additional method of recording the testimony. Plaintiff’s motion supplies the notice Rule 30(b)(3)(B) requires, so no procedural defect remains for this Court to resolve.</p></blockquote>
<p>Because the depositions noticed in Exhibits A and B will not proceed on the current notices, the motion is moot. Should Plaintiff re-notice his 30(b)(6) deposition and designate this methos of recording, Defendants may file the appropriate motion to address any concerns they might have.</p>
<p>Fed.R.Civ.P. 30(b)(3) states:</p>
<blockquote><p><strong>(3)<em> Method of Recording.</em></strong></p>
<p><strong>(A) </strong><em>Method Stated in the Notice.</em> The party who notices the deposition must state in the notice the method for recording the testimony. Unless the court orders otherwise, testimony may be recorded by audio, audiovisual, or stenographic means. The noticing party bears the recording costs. Any party may arrange to transcribe a deposition.</p>
<p><strong>(B) </strong><em>Additional Method.</em> With prior notice to the deponent and other parties, any party may designate another method for recording the testimony in addition to that specified in the original notice. That party bears the expense of the additional record or transcript unless the court orders otherwise.</p></blockquote>
<p>It is fairly easy to envision the same issue arising in, for example, a Rule 26(f) Conference of the Parties.</p>
<p>It will be interesting to see who bears the burden of persuasion to show that the specific AI tool is reliable.  Has it been tested?  Does it have a known error rate, for example? <em>See</em> <a href="https://www.ediscoveryllc.com/otter-ai-transcript-was-excluded-from-consideration/">Otter.ai “Transcript” Was Excluded From Consideration</a> (Apr. 25, 2026); <a href="https://www.ediscoveryllc.com/felder-part-1-of-4-court-ordered-transcription-of-meet-and-confer-session/">Felder: Part 1 of 4:  Court-Ordered Transcription of “Meet and Confer” Session</a> (Aug. 13, 2024); <a href="https://www.ediscoveryllc.com/sometimes-discovery-disputes-do-not-bring-out-the-best-in-us-part-ii/">Sometimes Discovery Disputes Do Not Bring Out the Best in Us – Part II</a> (Jun. 20, 2024)(“courts have ordered that the parties record – by video or court reporter – their Local Rule 37.2 meet-and-confer sessions for the court’s review”).</p>
]]></content:encoded>
			</item>
		<item>
		<title>A Request for “Three-Strata Validation” Was Denied</title>
		<link>https://www.ediscoveryllc.com/a-request-for-three-strata-validation-was-denied/</link>
		<pubDate>Thu, 27 Aug 2026 15:32:36 +0000</pubDate>
		<dc:creator><![CDATA[Michael Berman]]></dc:creator>
				<category><![CDATA[Commercial Litigation]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[ESI Protocol a/k/a Discovery Plans]]></category>
		<category><![CDATA[Important Posts]]></category>
		<category><![CDATA[Cooperation]]></category>
		<category><![CDATA[Discoverability]]></category>
		<category><![CDATA[Search]]></category>

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

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