Nobody talks about the cases that didn’t blow up dramatically. The ones where the outcome wasn’t decided by a smoking gun document or a star witness — but by a decision made quietly in week one, before anyone understood what was at stake. No courtroom theatrics. No last-minute revelation. Just a gap that opened early, widened slowly, and became impossible to close by the time anyone noticed it. This is one of those cases.
The Scenario
A mid-size company was hit with a commercial dispute. The legal team moved quickly — litigation hold notices went out to key custodians within days, IT was looped in to freeze the relevant email accounts, and the collection process kicked off inside two weeks of the complaint being filed. On paper, it looked right. The partner signed off. The client felt reassured.
What nobody flagged was this: eight months before the lawsuit, the company had migrated to a new cloud storage platform. The old system was still technically active. It was still holding two years of shared project files, collaborative drafts, and internal communications. But it wasn’t on anyone’s radar when the hold was designed. Nobody thought to ask about it. More accurately — nobody knew to ask.
By the time opposing counsel served discovery requests specifically targeting collaborative project documents from that period, the old system had been decommissioned. A scheduled auto-deletion had run its routine cleanup. The files were gone — not out of malice, not to hide anything, but because nobody connected the litigation hold to the full data history of the organization.
The company couldn’t produce the documents. They couldn’t explain where they went in a way that satisfied anyone. And from that point forward, the credibility problem was bigger than the legal problem.
The Insight
Here’s what rarely gets discussed in the post-mortem: the team didn’t fail because they were careless. They failed because they designed the hold around what they knew — and never asked what they didn’t know.
This is the quiet trap that catches organizations at the very start of a case. Legal identifies the obvious custodians. IT freezes the obvious systems. Everyone assumes the obvious places are the only places that matter. The hold goes out, the box gets checked, and the team moves on to the next thing.
But organizations aren’t built around litigation logic. They accumulate platforms over time — migrations, shadow IT, legacy tools that outlived their official retirement, cloud environments that one department adopted without telling anyone else. The data landscape is almost always messier than the org chart suggests, and the org chart is almost always what legal teams use to build their hold.
Before any collection begins, there’s a question worth asking — not “where do we keep our data?” but “where has our data ever lived, and where might it still exist?” That second question is different. It’s harder to answer. It requires conversations with IT, with department heads, sometimes with former employees. But it’s the question that changes outcomes.
At Sovereign Discovery, that conversation is where every engagement starts. A data map isn’t a luxury for complex cases — it’s the foundation of a defensible hold strategy for any case. Because a hold that only covers the obvious is only as strong as the last time the obvious was enough.
Closing
The case settled. On terms the client didn’t love. Not because the evidence was against them — but because the gap in the data created a credibility problem they couldn’t recover from once it surfaced. The missing files weren’t the issue. The inability to account for them was.
Discovery starts earlier than most teams think. And the decisions made in that first week — the ones that feel routine, administrative, low-stakes — are often the ones that define everything that follows.