Is a litigation hold notice enough to preserve electronic evidence?
A US federal court order filed on 17 August 2026 asks a practical question: what does it mean to preserve electronic evidence? In Cress v. Nexo Capital, a magistrate judge in the Northern District of California found that relevant material had been lost after retention settings were applied to email, Slack and Google Drive data, and recorded that no litigation hold had been issued for the purged information. Circulating a hold notice is only one part of preservation.
No. A hold notice tells people what to keep, but it does not change the systems that delete information. In Cress v. Nexo Capital (order filed 17 August 2026), a US federal court found that relevant email, Slack and Google Drive material had been lost after retention settings were applied, with no litigation hold issued for the purged information, and granted curative sanctions including an adverse-inference instruction and an award of US$439,267.21 in fees and expenses. Effective preservation also means identifying the systems that can delete or alter in-scope information, applying proportionate preservation measures, verifying that they work, and monitoring them as custodians, systems and issues change. Hong Kong courts apply their own rules; take advice.
What the court found
In Cress v. Nexo Capital, an order filed on 17 August 2026, a US magistrate judge in the Northern District of California granted in part the plaintiff’s motion for sanctions under Federal Rule of Civil Procedure 37(e). The court found that Nexo had spoliated electronically stored information with the intent to deprive the plaintiff of its use in the litigation. It found that relevant material had been lost after retention settings were applied to email, Slack and Google Drive data, and recorded that no litigation hold had been issued for the purged information and no attempt had been made to recover it.
The court granted curative sanctions, including a mandatory adverse-inference instruction incorporating four presumptions, permitted the destruction issue to be put before the jury, and awarded US$439,267.21 in attorneys’ fees and expenses. It denied terminating sanctions.
We make no comment on the unresolved merits of the underlying commercial claims. The preservation findings alone offer an important lesson for any organisation that may face litigation, a regulatory investigation or an internal inquiry. In practice, organisations must identify systems capable of deleting or altering in-scope information, apply proportionate preservation measures and verify that those measures are working, then monitor that work as custodians, systems and issues change.
Retention settings are active instructions
Retention settings can sound administrative. Thirty days for one category. Sixty days for another. Automatic deletion after a defined period. Technically, those settings are instructions executed by the system. They can determine whether potentially relevant information remains in the managed source when investigators, lawyers or experts later need it.
The order records that, on 4 December 2022, Nexo applied organisation-wide 30-day deletion rules to email sent to or from two managing partners and set Slack direct messages to four days, raising that period to 30 days on 7 December. On 1 March 2023 it set public and private Slack channels to 60 days. During discovery it also created one-day rules for labelled Google Drive items and specific emails.
The court also noted Nexo’s written retention policy, dated 27 March 2023, which required permanent retention of internal and external email and at least five years for electronic documents. That contrast matters. A policy can say one thing while the live systems do another. When preservation becomes necessary, policy and configuration must be reconciled.
A memo does not suspend deletion
Legal teams quite properly use hold notices to tell custodians that specified information must be retained. But a notice to people does not automatically change the settings of Microsoft 365, Google Workspace, Slack, Teams, a customer platform, a cloud archive or a personal messaging application. The practical preservation process has to connect the legal instruction to the technical environment.
For senior legal teams, the accountability split should be explicit. Legal defines the preservation trigger and scope. System owners implement the controls. eDiscovery or investigations personnel verify that the controls are operating. One named matter owner records exceptions, unresolved sources and later changes to scope. If those perspectives are not brought together, a hold can be legally well drafted and technically ineffective.
Prompt stabilisation and a source map
Fragile sources may need to be stabilised or collected immediately while the organisation maps where relevant information may exist and how it may be lost. Email is only one source. Depending on the matter, the map may need to include:
- collaboration channels and direct messages;
- cloud drives, shared folders and document-management systems;
- mobile phones and messaging applications;
- personal accounts used for business;
- customer relationship, trading or case-management platforms;
- backups, archives and disaster-recovery copies;
- system logs, audit trails and security telemetry;
- data held by service providers or other third parties.
Backups, personal accounts and third-party systems should be assessed rather than preserved indiscriminately. The map should also identify how each source loses data: by age, by user action, when an account closes, a licence changes, storage is reduced or a device synchronises. Preservation requires knowledge of both location and behaviour.
The change itself may become evidence
The order shows that configuration history can itself become evidence. Audit logs may establish when a rule changed and what it covered; administrator records and witness evidence may establish who could make the change and how it was authorised. That chronology can be compared with demand letters, complaints, disclosure requests and other litigation events.
Retention changes are not inherently suspicious. Organisations routinely adjust settings for legitimate security, privacy, cost and records-management reasons. But changes made when litigation is reasonably anticipated should be documented and capable of explanation, including who approved them and how relevant information remained protected.
Producing a large volume does not answer the preservation question
The order records that Nexo produced 63,866 documents spanning 370,488 pages. The court nevertheless found that relevant electronically stored information had been lost. Production volume and preservation completeness are not the same measure. The right question is not “How much did we produce?” but “Did we take reasonable steps to preserve the relevant sources, and can we demonstrate what those steps were?”
Verification should be designed into the hold
A defensible hold process needs evidence of implementation, not simply evidence of intention. Depending on legal advice, system design and proportionality, verification may include:
- recording the preservation trigger, scope and decision owner;
- listing custodians, systems, accounts and third-party sources;
- documenting the retention rules in force when the hold began;
- preserving administrator and audit logs through documented exports or other defensible methods before they rotate, without altering source evidence;
- recording each configuration change and its approver;
- confirming through administrator records or a controlled, non-destructive test that in-scope accounts and channels are no longer purging relevant material;
- collecting fragile sources early where settings cannot be controlled reliably;
- checking that new custodians, systems or claims are added as the matter develops;
- recording any failed collection, unavailable source or residual limitation.
This is not a call to preserve every byte indefinitely. Preservation should remain lawful, proportionate and tied to the reasonably anticipated issues; excessive preservation creates its own privacy, cost and security risks. The discipline lies in making the scope deliberate and the implementation demonstrable.
The corporate witness needs an evidential answer
When a dispute reaches a hearing or trial, a general assurance that “everything relevant was collected” may not withstand scrutiny. A corporate representative may need to explain when preservation began, which systems were assessed, who performed the work, what settings were changed, what exports were made, what checks were performed and what could not be recovered. Those answers should come from contemporaneous records rather than reconstructed memory.
For a general counsel or investigation lead, the management test is simple: ask for evidence of operation, not reassurance. The team should be able to produce a current source map, named owners, control status, an unresolved-source log, and the date and result of the latest verification.
The practical lesson
Electronic evidence is governed by systems that keep acting after lawyers become involved. Messages expire. Logs rotate. Files synchronise. Accounts close. Rules continue to execute until somebody with the right authority changes them. That is why a litigation hold should not remain a legal instruction alone: it should be translated into documented, proportionate and verified preservation measures. Hong Kong disclosure rules differ from the US rules applied in Cress; take advice on local obligations.
See preserve first, eDiscovery and Microsoft 365 and cloud investigations.
Sources
- Cress v. Nexo Capital Inc., No. 3:23-cv-00882-TSH, ECF No. 164, Order re Plaintiff's Motion for Sanctions (N.D. Cal., filed 17 Aug 2026)
- Public case docket: Cress v. Nexo Financial LLC et al., Case No. 3:23-cv-00882-TSH
- Servient, 20 Aug 2026: Shortening Retention Windows With No Litigation Hold Produced an Adverse Inference
General commentary on public reports, not legal advice and not a finding about any organisation or person named in those reports. Facts are as reported at the time of writing.
Frequently asked questions
Is a litigation hold notice enough to preserve electronic evidence?
No. A notice tells people what to keep but does not change the systems that delete information. In Cress v. Nexo Capital a US court found material lost after retention settings were applied, and granted sanctions. Preservation also means identifying systems that can delete in-scope data, applying proportionate controls and verifying they work.
Why do retention settings matter in litigation?
They are instructions the system carries out. Automatic deletion rules keep running until someone with authority changes them, so relevant email, chat and cloud documents can disappear after a dispute is anticipated.
What should a preservation source map include?
Email, collaboration channels and direct messages, cloud drives, phones and messaging apps, personal accounts used for business, business platforms, backups and archives, logs and audit trails, and data held by third parties, together with how each source loses data.
Does producing a large number of documents show preservation was adequate?
No. In Cress the defendant produced 63,866 documents, yet the court found relevant information had been lost. Volume and completeness are different measures.
How can a general counsel check a hold is working?
Ask for evidence of operation: a current source map, named owners, the status of each control, a log of unresolved sources, and the date and result of the latest verification.
Facing something like this?
The first discussion is confidential and free, and usually changes what you decide to do next. Call +852 5808 1071 or use the case review form.