Key takeaway

Establish the preservation scope with the responsible legal owner before optional cleanup or disclosure. Keeping evidence intact and approving a commercial use are separate decisions.

Find the preservation instruction before changing the records

A possible buyer may ask for cleaner notes, fewer attachments or a smaller history. Before commissioning that work, ask the records and legal owners whether the affected material is subject to a preservation obligation or instruction. The question concerns the source, related copies and actual proposed operations, not just a folder labelled legal hold.

For US federal civil proceedings, Rule 37(e) addresses lost electronically stored information that should have been preserved in anticipation or conduct of litigation, where reasonable preservation steps were not taken and the information cannot be restored or replaced. It distinguishes prejudice-based measures from measures requiring a finding of intent to deprive. The current December 2025 rules were read on 12 October 2026.

Have qualified counsel establish the actual trigger, material and instructions. Rule 37(e) is neither an automatic sanction for every edit nor a universal retention period. This record supports a US federal civil review; it does not settle a case-specific duty or disclosure permission.

Complete an operation-level hold record

Hypothetical example: fictional maintenance company M has a counsel-issued instruction H-22 covering 2024–2026 records relevant to a warranty dispute. The stipulated instruction covers identified job notes, attachments, revision history and related messages. M is considering an optional licensing package from a larger archive.

The completed record below translates the stipulated instruction into specific preparation questions. The commercial sponsor holds the affected preparation work until the legal owner resolves its interaction with H-22. A preservation action does not authorize a buyer sample; an unaffected category still needs its own rights and privacy review.

Surface / proposed changePreservation evidence in this exampleCompleted preparation decision
Job notes: replace source text with normalized textH-22 covers identified original notes and revisionsDo not overwrite originals; hold the proposed operation for the legal owner.
Attachments: remove files labelled duplicateMatter links and original versions not yet reconciledHold deletion; assess whether the copies differ or supply relevant context.
Closed-job retention job: delete by ageH-22 affected identifiers mapped to the scheduled jobApply counsel’s scoped preservation instruction and verify the affected execution path.
Collaboration messages: automatic expiryRelevant channel identified; preservation control unverifiedEscalate promptly to legal and system owners; expiry control remains unresolved.
Optional buyer export: selected notes and summariesCommercial permission separate; H-22 effect unresolvedHold sample/disclosure decision; preservation does not establish licensed use.
Unrelated archive categoryNot included in stipulated H-22 scopeNo blanket hold inferred; apply its actual retention and separate release review.

Trace the routine jobs that can remove the evidence

For each affected source, identify retention jobs, user deletion, revision compaction, attachment deduplication, mailbox rules and platform expiry settings. Ask who operates the relevant control and what evidence confirms its current state. A written hold acknowledgement can document receipt of an instruction while the scheduled deletion job remains active.

The DOJ and FTC’s January 2024 announcement describes updates to antitrust preservation letters and requests covering collaboration tools and ephemeral messaging. It explains that business communications on these platforms can be subject to the agencies’ requests. This is a government-investigation example, rechecked on 12 October 2026, rather than a new universal hold covering every company message.

In M’s illustration, the system owner identifies an expiring channel linked to H-22 but cannot yet demonstrate effective preservation. The row stays unresolved and is escalated promptly under counsel’s instruction. The commercial team does not declare the evidence safe because a separate export of the job database succeeded.

Separate preserved evidence from proposed transformations

Define whether preparation reads a source, changes it, deletes something, creates a derivative or sends material to another system. Record the input version, operation and intended destination. A normalized summary can omit a revision, attachment or relationship that the preserved evidence needs. Keep the transformation’s coverage limits visible instead of treating a cleaner file as a substitute for the original.

In the hypothetical case, M proposes a separate working copy of reviewed records. The legal owner must decide the preservation implications and permitted handling before that operation proceeds; a copy is not automatically safe merely because the original appears unchanged. The system owner separately checks whether the tool writes back to source fields or invokes deletion and compaction.

An internal test specification might require a read-only path and no mutation of held originals. Its successful technical execution would demonstrate those tested properties, not approve disclosure or show that every relevant evidence source was identified. Track preservation controls, technical findings and commercial permissions as separate entries with their responsible owners.

Keep release decisions under the responsible authority

The commercial sponsor should not lift H-22 because a licensing opportunity becomes attractive or because the dispute seems quiet. Obtain the responsible legal owner’s current instruction and review any other overlapping hold or duty before changing retention controls. Record the matter reference, affected scope, approved action, decision date and the system changes that implement it.

A change to preservation instructions does not mean the business should retain the whole archive indefinitely or disclose it automatically. Return records to the applicable assessed retention process, with the relevant owners resolving privacy, records and legal requirements together. If the material remains preserved, the separate disclosure review should examine rights, confidentiality, privilege questions and any case-specific restrictions.

The federal discovery-planning provisions explicitly address preservation issues and privilege/protection questions. They illustrate why those decisions should be named, not why a commercial worksheet can settle them. If an earlier license or refresh obligation already exists, take the conflict to counsel and the commercial owner before changing performance; do not silently ignore that agreement.

Give the sponsor a narrower next step

M’s completed decision is to hold the affected optional preparation and sample request while legal and system owners resolve H-22 controls. The sponsor can separately examine an unrelated category through ordinary inventory and rights review. Its description should avoid revealing the dispute, privileged material or confidential documents merely to explain that the original proposal is paused.

Use Inventory to identify related systems and Rights & privacy review for authority questions. The source-retirement guide tests retained information’s usability after shutdown; this record maps an active preservation instruction to proposed operations. Speculative license earnings do not justify an unauthorized destructive action.

VOID starts with approved descriptions, charges no upfront seller referral fee and discloses conditional receiving-program compensation separately. Each named introduction needs permission. Keep this hold record internal; samples, evaluations and licenses remain separate owner decisions.

Tools for this decision

Data inventory builder →Rights & privacy review →