AI Assistant Logs Will Trigger Rule 37(e) Motions by 2027

AI assistant logs refers to the interaction records generated every time an attorney, custodian, or litigation professional uses a generative AI tool: the prompts submitted, the outputs received, and the session metadata tying each exchange to a user and a timestamp. These records are the next major spoliation battleground in American civil discovery. Vendors auto-delete them. Legal holds do not name them. Courts are already ordering their preservation.

According to Adalat AI, judicial systems globally are actively deploying AI to process millions of case records, which means the intersection of AI tools and legal proceedings is no longer theoretical. It is operational. The same shift is reaching U.S. litigation, and it is reaching the record-keeping obligations that discovery imposes on every party in a covered matter.

Attorneys in active cases are already attempting to request opposing parties' AI chat logs in discovery. Those requests are landing. Whether the logs still exist when they do is a function of operational practices that most firms have not yet updated.

Why Does Existing Law Already Reach AI Assistant Logs?

The legal infrastructure for sanctioning AI-log deletion already exists. Rule 37(e), Model Rules 1.1 and 1.6, and ABA Formal Opinion 477R supply every hook a court needs.

An analysis of 23 sources on this question shows a consistent pattern: legal commentators and courts are applying decades-old e-discovery doctrine to a new category of electronically stored information, not waiting for new statutes. The doctrine is there. The only thing missing, so far, is a widely publicized sanctions ruling in an ordinary civil matter to make firms pay attention.

Start with Rule 37(e). Rule 37(e) governs the failure to preserve electronically stored information and authorizes sanctions ranging from an adverse inference instruction to case-dispositive sanctions when ESI is lost because a party failed to take reasonable steps to preserve it. The rule does not care what kind of ESI you destroyed. Email, text, Slack, SharePoint, and now ChatGPT conversation logs all qualify. The trigger is the same: a reasonably anticipated lawsuit, a failure to act, and prejudice to the opposing party.

According to a review of the NYT v. OpenAI copyright litigation, a U.S. court ordered OpenAI to preserve all ChatGPT and API logs, including conversations that were deleted or marked temporary. OpenAI reportedly could not, or would not, segregate and anonymize the data. The preservation order reached logs the vendor's own default settings would have purged on a rolling schedule. In practice, that means any organization whose staff used ChatGPT around the time litigation was reasonably anticipated now faces the possibility that a court reaches into those vendor logs.

According to Amy Swaner, writing in the AI For Lawyers newsletter, the same legal-hold frameworks courts have applied to cloud email and SaaS document platforms "will likely apply to AI vendors." She flags a harder problem: the Stored Communications Act, written in 1986 as part of the Electronic Communications Privacy Act, "was not written with AI prompt logs in mind, and its application here is unsettled." That statutory gap means the only reliable protection is not relying on a statute that was not designed for this context.

The ethics obligations run parallel. Model Rule 1.1 now requires lawyers to understand how AI tools handle client data, not just whether the output is accurate. Model Rule 1.6 requires confidentiality, which means knowing where prompts go, how long they are retained, and who can retrieve them. ABA Formal Opinion 477R confirmed that confidentiality obligations extend to electronic communications stored with third-party providers. A firm that feeds client information into a consumer AI tool and then fails to preserve the logs when litigation arises has potential exposure on two tracks simultaneously: discovery sanctions and professional discipline.

The takeaway is uncomfortable but simple. Courts are not writing new law about AI logs. They are applying existing law to a new kind of ESI that most legal teams have not yet named in their hold templates. The gap is operational, not statutory.

Are Attorneys Already Requesting AI Chat Logs in Active Cases?

Yes. It is already happening in state court, federal court, and even informal discovery disputes. The attempts are clumsy and not yet succeeding at scale, but the instinct is there.

Here is what I mean. According to a thread in the r/Lawyertalk community, an attorney opposing a pro se litigant filed a discovery request specifically seeking the opposing party's ChatGPT conversation logs, intending to use those logs as statements for cross-examination at deposition and trial. The request generated a long practitioner debate. The near-unanimous response was that the logs were probably not obtainable in state court, that work-product doctrine would complicate any effort to compel them, and that even getting access would not be worth the cost. But here is what that debate actually proves: litigants are already thinking about AI chat logs as a discovery target. The instinct has arrived. The legal infrastructure and practitioner knowledge to execute it have not caught up yet.

According to a discussion in the r/ChatGPT community, a self-identified attorney explained that AI chat logs are, in principle, discoverable in civil litigation once a lawsuit is filed. Relevant logs held by a party can be sought via a discovery request. Logs held by a non-party vendor can be sought via subpoena. The practical deterrent is cost. This commenter estimated that taking a case to trial costs $200,000 to $300,000 on average. That is prohibitive for most disputes. But for employment litigation, commercial contract fights, and antitrust matters where AI tools were actively used to draft or analyze documents, the cost of a targeted log-preservation request or subpoena is a rounding error against the overall budget. The same commenter noted that "the number of attorneys where this is on their radar is still extremely small." In my experience, that observation is accurate today. It will not be accurate after the first visible sanctions ruling.

What this means is that the early adoption curve for AI-log discovery looks exactly like the early adoption curve for email discovery in the 1990s and text-message discovery in the 2000s. The tools were new. The instinct that they might be relevant came first. The technical capability to compel and process them came second. The sanctions for failing to preserve them came third. We are somewhere between the first and second stages right now. The practitioner who waits for stage three to get ready is the one who ends up in the sanctions opinion.

The takeaway: current attempts to obtain AI logs face real barriers, but none of those barriers apply uniformly in federal court with a well-resourced opponent and a colorable claim of relevance.

Who Is Already Reading Your Team's AI Chat Logs?

AI chat logs are visible to platform administrators, security teams, and employers with appropriate access. Assuming they are private is a legal and operational mistake.

IT professionals routinely monitor employee AI tool usage for insider-threat detection and policy compliance, the same way they monitor email. What they are not doing is flagging those logs for legal hold when litigation begins. The two disciplines have not merged yet. Security treats the logs as an asset to monitor. Litigation counsel needs them treated as ESI to preserve. That gap is the exposure. Attorneys who have explored whether AI chat logs are obtainable in civil proceedings have found the question actively contested, with no clean procedural path established in most jurisdictions. The practitioner community has barely started working through the obligation. Until it does, the logs will keep rolling off vendor servers on default retention schedules, and firms will keep losing evidence they did not know they had.

Why Are E-Discovery Practitioners Not Yet Preparing for AI-Log Preservation?

The e-discovery community is using AI at massive scale. It is just not thinking about preserving the AI's own interaction logs. Those are two very different problems.

According to an r/ediscovery practitioner discussion, the largest GenAI-assisted document review in recent memory ran to approximately 2.5 million documents. The reported throughput was 250,000 to 500,000 documents per day. That is not a future capability. That is current production workflow. The same practitioners using AI to cut through enormous document sets in days have, by and large, not updated their legal hold templates to name the AI tools their custodians use every day to draft emails, summarize contracts, and research case strategy. In practice, the tool they are using to save money on document review may be the same tool generating the unpreserved logs that create a future spoliation problem.

The disconnect makes sense if you think about where practitioner attention naturally goes. If you have a two-and-a-half-million-document review, you are thinking about throughput, prompt engineering, and privilege quality. You are not thinking about whether the prompts your associates typed into ChatGPT last quarter are sitting in a vendor log that will auto-delete in 30 days. These are two different parts of the e-discovery problem. One is loud and urgent. The other is quiet until it isn't.

The IT side of the house has a parallel blind spot. When a CEO was discovered reading employee email logs without authorization, the r/ITManagers community focused almost entirely on insider-threat posture and the security risk of excessive admin access. Nobody in that conversation mentioned legal hold obligations. The organization could have been in active litigation, with a hold covering email, while the same admin access that alarmed security professionals was being used to access information outside the hold's scope. The AI-log problem is the same shape: a governance and access question that most organizations are solving from a security frame, not a discovery-preservation frame.

What this means is that two entirely separate communities, e-discovery practitioners and IT managers, are both dealing with AI log governance and neither is connecting it to Rule 37(e) yet. The legal team is focused on review volume. The IT team is focused on access control. Neither is focused on the 30-day auto-delete window on the generative AI tools that the attorneys and custodians use every day to think through cases. That is the gap.

The takeaway is structural, not behavioral. Nobody is being negligent. They are each solving the problem they can see. The Rule 37(e) problem requires all three teams to be in the same room.

What Does a Legal Hold Clause for AI Tools Actually Look Like?

A defensible hold notice names the AI tools explicitly. Generic "electronic communications" language does not cover them.

LEGAL HOLD ADDENDUM - GENERATIVE AI TOOLS

This hold extends to all interactions with generative AI assistants
including but not limited to: ChatGPT, Claude, Gemini, Copilot,
and any workplace AI integration. Preserve:
  - All prompts submitted related to the matter
  - All outputs received
  - All session logs, to the extent accessible

Do not change retention settings or delete conversation history
on any covered tool until this hold is lifted in writing.

Courts have already ordered AI vendors to preserve logs that their default settings would auto-delete. A one-paragraph hold addendum is the minimum defensible starting point.

What Three Categories of AI Artifacts Actually Need to Be Preserved?

The three preservable categories are the prompts you put in, the outputs you received, and any fine-tuning or training data your organization submitted to the vendor.

According to Dean Taylor writing in Legal AI Substack, organizations using generative AI tools "likely have the same duty to preserve this information for litigation" as they do for email and other ESI. He identifies three discrete artifact types: the prompts users input, the outputs the system returns, and any fine-tuning or training material the organization submitted to the model. Each category is different in structure and in the practical difficulty of preserving it across vendor systems that were not designed with litigation holds in mind.

Prompts are the most overlooked. They contain the implicit case theory, the facts the attorney considered relevant, and the framing choices the team made under pressure. When a custodian typed a question into ChatGPT about a contract dispute, that prompt is an artifact. It is not attorney work product by default just because an attorney wrote it. Whether it is privileged is a question for the court. Whether it exists at all after the vendor's auto-delete window closes is a question of operational practice.

Outputs carry their own preservation problem. A generative AI response cannot be natively authenticated the way an email header can. Source-traceable outputs, meaning outputs whose provenance is tied to a specific query, timestamp, and user session, are defensible. A screenshot is not. In our work building e-discovery software, the gap between "we saved the output as a PDF" and a chain-of-custody record that will survive a spoliation motion is enormous.

Fine-tuning and training data is the third category and the one most organizations have not considered at all. If your firm or your client submitted documents to a vendor to train or tune a model, that submission may be discoverable. The data left your environment. Whether it still exists, where it exists, and under what terms the vendor retains it are questions most engagement letters do not answer.

The defensible architecture for all three categories comes down to three controls. Processing runs single-tenant, inside your own infrastructure under your own keys, with no vendor retention and no model training on your data. Originals remain immutable, with content hashing and an append-only audit trail. A fail-closed privilege gate prevents any production that has not been explicitly cleared. In our approach to e-discovery, that architecture is not a premium option. It is the baseline for anything that has to survive a preservation challenge.

The takeaway is that the three-category framework exists. The technical controls to implement it exist. The obstacle is that most firms have not connected the framework to their current toolstack.

What Should Litigation Teams Do Right Now Before the First AI-Log Sanctions Motion Lands?

Start by testing your current AI toolstack against a real matter. Not a demo. Your own documents, your own custodians, your own hard preservation questions.

In our e-discovery software work, the firms that fare best on preservation challenges are not the ones with the longest policy documents. They are the ones who ran their platform through a real collection before opposing counsel asked about it. The difference is operational. You need to know, before the motion, whether your system produces an append-only audit trail, what happens when a custodian's AI tool auto-deletes, and whether your chain of custody holds under cross-examination. If you cannot answer those questions from your current workflow, that is the gap to close.

Cost is not the obstacle it used to be. AI-assisted review runs at cents per document on platforms designed for it. Manual review runs at dollars per document, and at roughly $19,000 per gigabyte when you account for attorney time. The cost argument for adopting a defensible AI-native system is not close. The reason firms wait is not money. It is inertia and the understandable assumption that the first case to get hit by this will be someone else's.

The concrete adoption path has three steps. First, map your AI tool exposure. Which generative AI tools do your attorneys and custodians use for case-related tasks? What are the retention settings on each? Where do the logs live and who controls deletion? Most firms cannot answer this in under a week. That is a problem. Second, update your legal hold templates to name AI tools explicitly, alongside email and messaging platforms. The hold has to reach the tool at the moment the duty triggers, not after someone remembers to add a line item. Third, move at least one active matter to a platform that runs single-tenant, hashes originals, and keeps a traceable record of every AI interaction during review.

The third step is where Relevant Discovery fits. Our platform runs processing inside a controlled environment with no vendor retention and no model training on your data. Every AI-assisted review interaction produces a source-traceable record. The privilege gate is fail-closed, which means nothing gets produced without an explicit clearance decision. In practice, that means you are building the chain of custody during review, not reconstructing it afterward when someone files a motion.

The takeaway is that the infrastructure already exists. What most firms are missing is a trigger to act before they are reactive. The first visible Rule 37(e) sanctions motion citing an AI assistant log will be that trigger for the firms who wait.

What Will Matter Most for AI Logs and Discovery in the Next 12 to 24 Months?

The issue that will define the next two years is this: courts have already crossed the line from recommending AI log preservation to ordering it, and the firms that treat that as an isolated copyright curiosity will be caught badly positioned when it happens in ordinary civil litigation.

I have been watching the signals for a while. Here is how I read them.

Here is what most people miss: the lag in practitioner awareness is not protection. Firms that treat "nobody is talking about this yet" as permission to wait are making the same mistake practitioners made with text messages in 2008 and with Slack logs in 2018. The tool changed. The obligation did not. The only thing that changed was how long it took courts to catch up, and they are already catching up on this one.

The first Rule 37(e) sanctions order specifically citing AI assistant log deletion will land before 2027, and it will not land quietly. It will change the calculus for every firm still treating AI tools as outside the discovery perimeter. Courts are already ordering AI vendor log preservation. Attorneys are already requesting opposing parties' AI chat histories. Most practitioners still have not updated a single legal hold template to name the tools their teams use every day.

From what I have seen building and advising on e-discovery systems, the firms that survive this transition are not the ones with the best response plan. They are the ones who never needed one. They preserved the logs. They documented the chain of custody. They did it before someone asked. That is the only posture that works when Rule 37(e) is the question.