The complaint arrives on a Wednesday. Your general counsel forwards it with one line: “Can you get us ready for discovery?” You have thirty days before the Rule 26(f) conference, a company that’s never been through major litigation, and a data environment that’s grown considerably since anyone last thought carefully about it.
Discovery is where most commercial litigation is actually won or lost. It’s also where in-house legal teams — even experienced ones — make preventable mistakes that compound in cost and consequence. Here are the seven most common ones.
1. Issuing the Litigation Hold Too Late
The most common — and most sanctioned — discovery mistake is also the most straightforward: waiting too long to issue a litigation hold.
The duty to preserve evidence does not begin when a complaint is served. It begins when litigation is reasonably anticipated — which courts have consistently interpreted to include: receiving a demand letter, learning of a regulatory investigation, receiving an internal complaint about conduct that could be litigated, or becoming aware of facts that make a lawsuit likely.
In-house teams who issue holds only after service of process are already late. Auto-delete systems that continued running after a demand letter arrived have cost companies adverse inference instructions — where juries are told they can assume the deleted evidence would have been harmful. In egregious cases, courts have entered default judgments.
“The hold that didn’t go out until after the complaint was served is the most expensive document your legal team never wrote.”
The fix is not complicated — it’s building a trigger framework that maps events (demand letters, regulatory inquiries, internal HR complaints above a certain severity level) to automatic escalation to in-house legal for preservation assessment. The hard part is operationalizing it before it matters.
2. Not Knowing Where the Data Actually Lives
Most in-house legal teams have gotten the message about email and chat. They issue holds against corporate email, Slack or Teams, and sometimes shared drives. That’s table stakes — and it still leaves enormous gaps.
The channel that routinely gets missed in 2026 is Zoom. Organizations run hundreds or thousands of recorded meetings per month. Those recordings — and the AI-generated transcripts that accompany them — contain board discussions, deal negotiations, performance conversations, and operational decisions that were never committed to email. Zoom’s automatic retention defaults often delete recordings within 30 days unless explicitly changed. If your litigation hold doesn’t cover the Zoom recording library and the transcript archive, you’ve left one of the richest evidence sources in the company entirely exposed.
The same logic applies to other frequently overlooked sources: voicemail-to-text transcripts, CRM activity logs, project management tool comments (Jira, Asana, Monday.com), shared document version histories, and personal devices used for work communication. Many companies also have legacy systems — a CRM they migrated away from, an archived Confluence instance, an old project tool — with years of relevant data that no one has thought about since they switched.
Courts expect companies to preserve evidence from all reasonably accessible custodians and data sources. “We didn’t know that data existed” is not a defense — it’s often treated as evidence of a deficient preservation program.
Before your company is in litigation, someone in legal should be able to answer: what is every platform where business communications or decisions occur, who controls it, what are the retention defaults, and how would we export from it if needed? That’s a data map. Without one, you don’t know what you’re not preserving.
3. Choosing Custodians Too Narrowly
The instinct when identifying custodians is to start with the obvious people: the named defendants, the direct supervisors, the employees closest to the events at issue. That list is necessary but rarely sufficient.
Some of the most damaging discovery in workplace litigation doesn’t come from the central actors — it comes from the HR manager who fielded the original complaint and wrote notes about it, the executive assistant who saw the emails the principals forgot about, the IT administrator who made the access change and logged it, or the colleague whose Slack thread with a named defendant documents what they actually thought about the plaintiff.
In-house teams who identify custodians solely by obvious relevance systematically under-collect. The better approach: map the events at issue to the organizational chart, and ask who else touched them — even tangentially. Then ask whether any of those people communicated about it on any platform.
4. Treating Keyword Search as Complete Discovery
Keyword search is a tool for finding documents you already know to look for. It is not a methodology for discovering what you don’t know is there.
In-house teams frequently present keyword hit reports as evidence that discovery has been thorough. The problem: the most damaging evidence in a lawsuit rarely uses the language that appears in your search terms. Nobody emails about “retaliation.” They email about moving someone off a project. Nobody writes about “fraudulent billing” — they write about “billing discretion” or use an internal shorthand that no outside attorney would ever think to search for.
This is especially acute in cases involving workplace misconduct, where coordinated behavior across multiple people and channels is often the heart of the claim — and where no single communication, taken alone, looks damaging. Keyword search reviews documents one at a time. It doesn’t surface patterns across documents.
How Overstand Fits Here
The Situation
Marcus Webb is a senior legal analyst at a mid-size manufacturing company facing a wrongful termination and retaliation claim. The company has produced 80,000 documents. Outside counsel ran keyword searches against the standard retaliation terms and found nothing damaging. But the plaintiff’s attorney is asking pointed questions about a series of personnel decisions made in the two months after a safety complaint was filed.
The Data Corpus
Corporate email, Slack exports, HR system records, and management meeting notes from the relevant period — unified in Overstand.
The Query
”Show me all communications involving the plaintiff’s direct management chain between the date of the safety complaint and her termination date, across all channels.”
What It Found
A Slack thread — never flagged by keyword search — where two managers discuss reassigning the plaintiff to a role she’d previously rejected, followed three weeks later by her receiving a negative performance review that contradicted her prior evaluations. No search term would have found it. The behavioral pattern across the timeline made it visible.
“Keyword search tells you what’s in the document. It doesn’t tell you what the document means — or what it looks like next to the forty others like it.”
5. Over-Producing Instead of Asserting Proportionality
There is a persistent belief in some in-house legal teams that producing everything is the safest strategy — that a massive, undifferentiated production demonstrates good faith and protects against sanctions. It’s rarely true, and it’s expensive.
Federal Rule of Civil Procedure 26(b)(1) limits the scope of discovery to what is proportional to the needs of the case. Courts take proportionality seriously, and in-house counsel who engage with it early — identifying the strongest arguments for narrowing scope before meeting and conferring with opposing counsel — can significantly reduce both the cost and the volume of what gets produced.
Beyond the cost argument: over-production creates tactical problems. When you produce 400,000 documents, the ten most important ones are hidden in that volume. A more disciplined, proportional production keeps the narrative cleaner, makes your strongest evidence easier to find and present, and avoids inadvertently gifting opposing counsel with documents they didn’t know to ask for.
6. Fumbling the Privilege Review
Inadvertent production of privileged documents is one of the most common and most preventable mistakes in discovery — and the volume of modern communications makes it more likely with each passing year.
The consequences range from bad to severe. Producing a single privileged document can, in some courts and on some facts, waive the privilege for the entire subject matter. While Federal Rule of Evidence 502(d) provides a mechanism for courts to issue clawback orders that limit subject-matter waiver, it requires proactive planning — you need to get the order before you produce, not after the other side has read the document.
In-house teams often under-resource privilege review because it feels like an administrative task rather than a legal one. It isn’t. Modern discovery volumes — emails, Slack threads, meeting notes, voice-to-text transcripts — make the privilege review problem genuinely hard. It requires clear guidance on what constitutes attorney-client communications when in-house counsel is involved (which is legally more complex than communications with outside counsel), careful review of anything touching legal topics, and a production protocol that includes a final privilege check before anything goes out the door.
7. Treating Every Lawsuit as the First One
Companies that get sued once tend to treat it as a crisis — something to survive and then put behind them. Companies that get sued regularly — large enterprises with mature legal functions — treat discovery as an operational function with repeatable processes, institutional knowledge, and pre-built infrastructure.
The difference in cost and outcome between these two approaches is significant. A company with:
- A current data map — knows within hours what custodians and systems need to be preserved
- Hold templates and escalation triggers — can issue a hold within the first business day after a triggering event
- A practiced outside counsel relationship — doesn’t have to spend three weeks briefing outside counsel on business context before they can begin case assessment
- A unified data environment — can run comprehensive evidence searches in hours instead of weeks
That last point is where technology has shifted the calculus considerably. The biggest operational bottleneck in most discovery programs used to be the time between data collection and actionable evidence — the weeks spent by vendors processing files, paralegals reviewing documents, and associates writing memos summarizing what was found. Systems like Overstand compress that window significantly by unifying communications across every data source and making them queryable in natural language from the moment they’re ingested. What used to take weeks of manual review can now surface key patterns in a single afternoon — freeing in-house teams to spend their time on strategy, not logistics.
“Discovery readiness isn’t something you build when the complaint arrives. It’s something you build between lawsuits — so that when the next one comes, you’re already prepared.”
The Common Thread
Most of these mistakes share a root cause: in-house legal teams that are staffed and budgeted for steady-state compliance work, not for the surge demands of litigation. When a lawsuit arrives, they’re in reactive mode — making decisions under pressure with incomplete information about their own data.
The remedies are mostly about infrastructure built before the crisis, not tools acquired during it. Data maps, hold triggers, privilege protocols, and a unified, queryable data environment aren’t expensive to build relative to what they save. They’re just easy to defer when nothing is on fire.
The companies that navigate discovery well don’t do it because they’re better litigators. They do it because they treated readiness as a management obligation, not a legal formality.