A federal court just ordered a forensic capability test on hyperlinked document preservation. Not a definitional ruling on whether links are attachments. A practical test: process these emails through this tool, and show us what it recovers.
That order signals something broader. The gap between what standard eDiscovery preservation workflows deliver and what courts expect from collaborative evidence is no longer a theoretical concern. It's being tested on the record.
Three independent forces are converging- judicial action, industry guidance, and technical evidence- and together they leave very little room to argue that the old playbook still qualifies as reasonable.
For years, disputes over hyperlinked document preservation followed a predictable pattern: one side argued links should be treated as attachments, the other argued production was infeasible, and courts navigated between the positions without testing the underlying technical claims.
That pattern is changing. In In re Carvana Co. Securities Litigation (D. Ariz.), the court moved in two steps. In August 2025, it ordered a bounded pilot: plaintiffs could select up to two custodians, and defendants were directed to run Forensic Email Collector (FEC) to test whether historical hyperlinked documents could be retrieved, producing versions "as closely contemporaneous to, but preceding" the email as feasible. Following a compliance dispute, the court's January 2026 order expanded the exercise to 250 plaintiff-selected emails across all 25 ESI custodians, with a 10-day production deadline.
The court didn't resolve whether hyperlinks are attachments. It imposed a practical test- and when the pilot supported further testing, it escalated. That progression from capability test to expanded compliance requirement is the signal.
No blanket rule has emerged - Yotta Technologies v. Evolve Bancorp (N.D. Cal., Jan. 2026) reaffirmed that hyperlink relationships should be handled case by case. But the Carvana approach gives courts a template for testing infeasibility claims rather than accepting them. And the broader trajectory- from collaboration platform spoliation in Epic Games v. Google to contextual production requirements for Slack and Teams data- points the same direction: greater technical scrutiny of what preservation workflows actually capture.
For the full case law analysis, see: What FRCP Rule 37(e) Means for Modern Collaboration Platforms
For the complete case-by-case landscape, see: Judicial Signals and Case Developments
Courts aren't operating in a vacuum. The Sedona Conference- arguably the most influential voice in eDiscovery guidance, and one courts routinely cite- published its Commentary on Discovery of Collaboration Platforms Data in 2025. It catalogs the structural challenges: identifying relevant workspaces across applications, handling data stored in multiple locations, managing format and metadata for collaborative content, and preserving evidence where messages reference living documents rather than fixed attachments.
This matters because of the weight Sedona carries in practice. When Sedona publishes guidance acknowledging that collaboration platforms present distinct preservation challenges, that acknowledgment becomes part of the landscape against which "reasonable steps" will be evaluated. A party aware of these challenges faces increasing difficulty arguing that a traditional, email-era preservation workflow constitutes reasonable steps for evidence that behaves fundamentally differently.
It's no longer an edge case. It's the recognized landscape.
Our analysis of what Sedona identified- and how those problems map to architectural requirements- is here: Sedona Identified the Problems. Here's the Architectural Answer.
Here's a test anyone can run. It takes five minutes.
Share a document via a Teams message. Edit the document. Then collect the message using your standard preservation workflow. Now check: did you get the version of the document the recipient actually saw, or whatever version happened to exist at collection time?
In most environments, the answer is the latter. The workflow collected the current version of the document- not the version that existed when the message was sent. The message and the document it referenced are now mismatched. The recipient saw one thing; the collection reflects another.
That isn't a nuanced technical edge case. It's a fundamental gap between what the communication referenced and what the preservation captured. And it takes one test, on one document, to see it.
Most workflows, as typically configured, fail this- not because they're broken, but because they were built for an evidence model where messages carried frozen copies, not live references. That model hasn't been accurate for years. The test just makes it visible.
And if it does fail, that's not an indictment of your team. It's a gap in the tooling. Knowing it exists is the first step toward closing it.
The test, and what it reveals about the structural gap in most preservation workflows, is detailed here: The Simplest eDiscovery Test Most Tools Would Fail
Any one of these developments would be significant on its own.
A court ordering a practical demonstration of preservation capabilities
The industry's leading guidance body cataloging the structural challenges.
A simple test that makes the gap visible to anyone willing to run it.
Together, they close the exits.
The gap between what traditional preservation workflows deliver and what the legal process expects for collaborative evidence is now documented by industry authorities, provable in minutes, and being tested in federal court. That convergence makes it difficult to argue that the old playbook still qualifies as "reasonable steps"- and the timeline for that argument is compressing.
For litigation teams and eDiscovery providers, the question is no longer whether collaboration platforms create preservation challenges. That's settled. The question is whether your current workflow reflects what the industry now knows- or whether it's still calibrated for an evidence model that no longer exists.
Cloudficient builds Context-Aware eDiscovery for collaborative platforms. The Reconstruction-Grade eDiscovery Standard is the vendor-neutral, open-source conformance framework we published to give the industry a shared way to evaluate preservation capabilities.