Whether uploading discovery documents into a consumer AI tool waives work-product protection is unsettled, and courts are not uniform. Work-product waiver generally turns on disclosure to an adversary or in a way that makes adversary access likely, while attorney-client privilege is more exposed to a disclosure to a third party. A tool without enterprise data safeguards raises the risk on both fronts, which is why the safeguards below matter.
The Morgan v. V2X order, issued in the District of Colorado in March 2026, addressed a related problem from the protective-order side: it amended a protective order so that confidential information can go into an AI platform only if the provider is contractually bound on storage, training, third-party disclosure and deletion, and it held that the name of an AI tool used with confidential information is not protected work product. The three legal mechanisms that protect against waiver are: FRE 502 clawback agreements (Federal Rule of Evidence 502(d) orders entered before production, which protect against inadvertent disclosure to AI platforms), the selective waiver doctrine (which some circuits recognize to protect disclosures made under controlled conditions, though its applicability to AI tools is unsettled), and tight Everlaw and Relativity data processing agreements, both platforms offer enterprise DPAs that establish vendor-as-agent status, which is the contractual basis for preserving privilege through a third-party platform. If your firm uses AI in discovery without these guardrails, privilege waiver isn't a theoretical risk. It's already being litigated.
How AI Creates Privilege Waiver Risk in Discovery
Attorney-client privilege and work-product doctrine both depend on maintaining confidentiality. Voluntarily sharing protected information with a third party who isn't covered by the privilege destroys the protection. AI tools operated by third-party vendors are, in every legal sense, third parties.
The analysis is straightforward. When an attorney inputs privileged case strategy, client communications, or litigation analysis into a consumer AI tool, that data flows to the vendor's servers. If the vendor's terms of service permit data retention, model training, or access by vendor employees, the confidentiality required for privilege is broken. The intent of the attorney doesn't matter. The disclosure happened.
Enterprise-tier AI tools change the analysis but don't eliminate the risk. ChatGPT Enterprise, Claude via API with enterprise terms, and legal-specific platforms like Harvey AI are sold with enterprise terms; we have not reviewed any vendor's contract, so check the training and retention terms in your own agreement. Whether a vendor under contract can count as the lawyer's agent (the Kovel line) is untested for AI: Heppner mentions it only as an open possibility. But the burden is on the producing party to prove those protections exist.
What the Morgan v. V2X Order Requires
The Morgan v. V2X protective order is an early judicial framework for AI in discovery. Issued in the District of Colorado in March 2026, it is one court's approach and is not binding elsewhere. The primary source is the court's order. It contains a disclosure ruling, three contractual conditions and a documentation duty.
Tool identification. The court held that the name of an AI platform used with information designated CONFIDENTIAL is not protected work product, and ordered the plaintiff to disclose it within 10 days. The disclosure ruling is tied to AI used with confidential information.
No storing or training. The AI provider must be contractually prohibited from storing inputs or using them to train or improve its model. This goes beyond the vendor's marketing claims: it requires contractual protection.
No third-party disclosure. The provider must be contractually prohibited from disclosing inputs to any third party, except where essential to delivering the service, and then the third party must be bound by obligations no less protective. The court said this would, for now, bar most mainstream low-cost and free AI tools for confidential information.
Deletion and documentation. The provider must contractually allow removal and deletion of all CONFIDENTIAL information on request, and a party relying on an AI tool must retain written documentation of these contractual protections.
Building a Privilege-Safe AI Discovery Workflow
The goal isn't to avoid AI in discovery: it's faster and often more accurate than manual review for large document sets. The goal is to build the workflow so privilege survives challenge.
A firm-wide workflow, starting with vendor selection, is laid out in protecting attorney-client privilege when using AI.
Use enterprise tools with signed vendor agreements. Every AI tool touching discovery materials needs a vendor contract with explicit terms: zero data retention, no model training on inputs, encryption at rest and in transit, an independent security report you have read (such as a SOC 2 report), and breach notification within 24 hours. No exceptions.
Document the chain of custody. For every batch of documents processed through AI, log the tool, date, operator, input count, and output. This creates an audit trail, which is our recommended practice. Morgan v. V2X itself requires written documentation of the vendor's contractual protections, not a processing log. Your firm's incident response plan should cover what happens if the audit trail reveals a problem.
Layer human review on privilege determinations. AI handles first-pass review to flag potentially privileged documents. A licensed attorney makes every final privilege call. Document that review.
Request a 502(d) order in every case. A Federal Rule of Evidence 502(d) order protects against inadvertent privilege waiver. Draft it to explicitly cover AI-related inadvertent disclosures, including scenarios where AI incorrectly designates a privileged document as non-privileged. This is your safety net, and it costs nothing to request.
What This Means for Your Firm
AI-assisted discovery reduces cost and improves accuracy on large document sets. But it introduces a privilege waiver vector that traditional review workflows don't have, and opposing counsel are learning to exploit it.
The playbook for challenging AI-assisted privilege is already emerging: subpoena the vendor agreement, demand the audit trail, challenge whether the AI tool's data handling met the protective order's confidentiality requirements. If your firm can't produce those records, the privilege argument collapses.
Review your current discovery workflow against the Morgan v. V2X conditions. Confirm every AI tool has a signed vendor agreement with data protection terms. Ensure your privilege review process includes documented attorney oversight. And request a 502(d) order in every case where AI touches discovery materials. These steps keep the privilege record documented. Without them, a motion to compel can put the privilege claim at risk.
The Bottom Line: AI in discovery isn't the risk. Ungoverned AI in discovery is. Build the workflow to survive a privilege challenge, or assume privilege is waived the moment you hit enter.
AI-Assisted Research. This piece was researched and written with AI assistance, reviewed and edited by Manu Ayala. For deeper takes and the perspective behind the research, follow me on LinkedIn or email me directly.