Compliance decisions
Employee AI chats under US legal hold
When litigation is anticipated or underway, identify relevant AI material and obtain the responsible legal team’s preservation direction before routine deletion. Rule 37(e) concerns loss of ESI that should have been preserved and the conditions for court measures; it does not create a universal keep-all-prompts rule or an automatic hold feature.
For Legal operations, litigation counsel, IT records and security teams
A conversation, uploaded file and exported copy can require separate preservation steps.
Fictional matter, custodians, dates and records. No real litigation hold, preservation action, rights-request decision or court finding is represented.01
Establish the matter and preservation scope
Current Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved in anticipation or conduct of litigation, was lost because reasonable steps were not taken, and cannot be restored or replaced through additional discovery. Its committee note explains that the rule does not itself create a new preservation duty.
Have the responsible legal owner identify the matter, relevant issues, custodians, time period and material to preserve. Do not issue an indefinite hold on every employee AI interaction merely because the company uses AI. Equally, do not assume a chat is irrelevant because it was informal or labelled a draft.
Source context: Federal Rule of Civil Procedure 37
02
Find the records beyond the visible conversation
Map relevant conversations, attachments, generated drafts, project or shared files, local downloads and exported activity evidence. Identify who controls each location and which service or account actually holds it. A chat-delete action may leave other copies, while deletion of a source file may not remove an exported copy.
Keep the content needed to understand the relevant record and its provenance. An activity log may show that an interaction occurred without containing the communication itself. Do not describe a metadata export as a complete preserved conversation unless it actually contains the required material.
Source context: Federal Rule of Civil Procedure 37
03
Resolve deletion and rights-request conflicts
Identify scheduled retention, offboarding or user-requested deletion that could affect the scoped records. Ask the legal and records owners to decide what must be preserved and how to restrict access and unnecessary use. A preservation instruction is not a reason to retain unrelated material forever.
Where other laws or rights requests apply, coordinate the analysis instead of assuming US litigation needs automatically displace every duty. GDPR, for example, has a legal-claims exception with its own conditions. Keep the actual legal basis, scope and response obligations documented by the responsible team.
Source context: Federal Rule of Civil Procedure 37 · EU GDPR: Regulation (EU) 2016/679
04
Record reasonable preservation actions and limitations
Rule 37(e) focuses on reasonable steps and the ability to restore or replace lost information. It is not a demand for technical perfection. Document the actual preservation action, affected account, time, owner and verification, including any provider limits or missing records.
The rule distinguishes measures addressing prejudice from specified measures requiring an intent-to-deprive finding. Do not predict sanctions from a single deletion event or declare that an export guarantees a court will find preservation adequate. Those conclusions depend on the legal facts.
Source context: Federal Rule of Civil Procedure 37
05
Make the hold reviewable and releasable
The synthetic handoff below gives a matter reference, custodians, issue scope, time range and known record locations. It identifies a routine-deletion conflict and assigns resolution to legal and IT owners. It is a teaching draft, not a hold imposed on a real account.
Keep acknowledgements, completed actions, checks and release instructions in the appropriate process. Review scope as the matter develops. When an authorised release occurs, reconcile it with the normal retention policy rather than leaving an unexplained permanent exception.
Source context: Federal Rule of Civil Procedure 37
Put it into practice
Synthetic AI preservation handoff
An invented contract dispute involves employee AI drafts and copied documents. The handoff identifies what legal and IT owners must resolve before deletion.
Fictional matter, custodians, dates and records. No real litigation hold, preservation action, rights-request decision or court finding is represented.
Legal scope
Matter, issues, custodians and period
AI records
Conversation and uploaded file
Other copies
Shared draft, local file and relevant event evidence
Handoff
Actual preservation, verification and authorised release
| Handoff field | Populated fictional scope | Owner or unresolved question |
|---|---|---|
| Matter | MATTER-EX-30: invented dispute about delivery commitments. | Legal owner confirms the real issues and preservation duty. |
| Custodians | Fictional support lead and operations lead roles. | Identify actual custodians and relevant accounts; do not include every employee by default. |
| Time range | 1 June to 31 July 2026, invented scope. | Legal owner confirms and revisits the actual relevant period. |
| AI locations | Conversation TEST-CHAT-30 and uploaded file TEST-FILE-30. | Workspace owner identifies actual preservation/export capabilities and limitations. |
| Other copies | Draft copied to a shared document and local download. | Document/endpoint owners preserve the relevant copies and provenance as directed. |
| Deletion conflict | Routine expiry and proposed offboarding could remove relevant material. | Resolve with legal and IT before the affected deletion; no live setting is changed here. |
| Verification and release | No preservation action or release has occurred in the exercise. | Record actual checks and later authorised release instructions. |
Work through your review
Use the checks to organise the evidence you need. Your selections stay in this tab.
0 of 3 reviewed
Example files for this task
Keep the source material and the instructions together. You can also download the complete worksheet or matrix as CSV.
employee-ai-preservation-handoff.mdInspect
# Synthetic AI preservation handoff
Fictional matter, custodians, dates and records. No real litigation hold, preservation action, rights-request decision or court finding is represented.
An invented contract dispute involves employee AI drafts and copied documents. The handoff identifies what legal and IT owners must resolve before deletion.
| Handoff field | Populated fictional scope | Owner or unresolved question |
| --- | --- | --- |
| Matter | MATTER-EX-30: invented dispute about delivery commitments. | Legal owner confirms the real issues and preservation duty. |
| Custodians | Fictional support lead and operations lead roles. | Identify actual custodians and relevant accounts; do not include every employee by default. |
| Time range | 1 June to 31 July 2026, invented scope. | Legal owner confirms and revisits the actual relevant period. |
| AI locations | Conversation TEST-CHAT-30 and uploaded file TEST-FILE-30. | Workspace owner identifies actual preservation/export capabilities and limitations. |
| Other copies | Draft copied to a shared document and local download. | Document/endpoint owners preserve the relevant copies and provenance as directed. |
| Deletion conflict | Routine expiry and proposed offboarding could remove relevant material. | Resolve with legal and IT before the affected deletion; no live setting is changed here. |
| Verification and release | No preservation action or release has occurred in the exercise. | Record actual checks and later authorised release instructions. |
## Review steps
- Obtain the matter-specific direction: Identify issues, custodians, time range and the relevant information before applying a real hold.
- Map every relevant location: Distinguish chat content, uploads, copied outputs, local files and activity evidence.
- Resolve deletion conflicts: Coordinate scheduled deletion, rights requests, verification and eventual release with the responsible legal and records owners.
## Draft teaching handoff
Matter: MATTER-EX-30, entirely fictional.
Issue: representations about delivery commitments in an invented contract dispute.
Custodians: support lead and operations lead roles.
Period: 1 June to 31 July 2026, invented.
Relevant locations: TEST-CHAT-30, TEST-FILE-30, shared draft TEST-DOC-30 and a local exported copy.
Conflict: routine expiry/offboarding may affect these hypothetical records.
Action requested in a real case: obtain authorised legal direction, identify available preservation methods, document completed actions and verify their scope.
Actions actually performed here: none.
Release: only after the responsible legal owner’s actual instruction.
This specimen is not a legal hold notice and does not change any user account or retention setting.
## Source and scope
Guide: https://aona.ai/resources/guides/employee-ai-chats-legal-hold/
Source check: 21 September 2026. General information, not professional approval or a completed control test.
- Federal Rule of Civil Procedure 37: https://www.law.cornell.edu/rules/frcp/rule_37
- EU GDPR: Regulation (EU) 2016/679: https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
employee-ai-preservation-handoff.csvInspect
Handoff field,Populated fictional scope,Owner or unresolved question
Matter,MATTER-EX-30: invented dispute about delivery commitments.,Legal owner confirms the real issues and preservation duty.
Custodians,Fictional support lead and operations lead roles.,Identify actual custodians and relevant accounts; do not include every employee by default.
Time range,"1 June to 31 July 2026, invented scope.",Legal owner confirms and revisits the actual relevant period.
AI locations,Conversation TEST-CHAT-30 and uploaded file TEST-FILE-30.,Workspace owner identifies actual preservation/export capabilities and limitations.
Other copies,Draft copied to a shared document and local download.,Document/endpoint owners preserve the relevant copies and provenance as directed.
Deletion conflict,Routine expiry and proposed offboarding could remove relevant material.,Resolve with legal and IT before the affected deletion; no live setting is changed here.
Verification and release,No preservation action or release has occurred in the exercise.,Record actual checks and later authorised release instructions.
synthetic-ai-preservation-locations.csvInspect
record_ref,location,custodian_role,conflict,status
TEST-CHAT-30,AI workspace conversation,support lead,routine expiry,fictional; not preserved
TEST-FILE-30,AI uploaded file,support lead,separate file lifecycle,fictional; not preserved
TEST-DOC-30,shared document,operations lead,offboarding,fictional; not preserved
TEST-EXPORT-30,local download,operations lead,device cleanup,fictional; not preserved
Before you proceed
Keep these distinctions clear
- A chat export may not preserve every relevant record
- Check uploads, copied outputs and the metadata needed to understand them.
- A hold is not a blanket retention policy
- Keep the matter-specific scope and release process with the responsible legal owner.
Apply it to employee AI use
Bring your actual data path.
Supported employee-AI activity evidence may help identify a relevant application or interaction for the legal team’s investigation.
Aona is not represented as a litigation-hold, e-discovery or compliant records-archive system and does not decide preservation duties.
Use the fictional matter to identify what scoped event evidence exists and which records require separate preservation systems.
Review your use caseFAQ
Questions for this decision
Does Rule 37 require keeping every AI chat?
Does deleting a chat automatically mean sanctions?
Can routine retention continue unchanged during a matter?
Does this handoff impose a legal hold?
Evidence behind the guide
Sources and scope
Prepared by Aona. Sources checked 2026-09-21. The cited material supports the specific points below; it does not certify a product or your use case.
- Federal Rule of Civil Procedure 37
Current Rule 37(e) and 2015 committee note on lost ESI, reasonable preservation steps, restoration/replacement, prejudice and intent findings; not a new universal retention duty.
law · checked 2026-09-21 - EU GDPR: Regulation (EU) 2016/679
Articles 5, 6, 9, 12, 17, 19, 28, 32, 35 and 36 establish the relevant processing, rights, processor and risk-assessment requirements.
law · checked 2026-09-21