If your legal budget keeps climbing and you can't pinpoint why, the answer might be hiding in plain sight: your organization uses too many platforms, and nobody's tracking where relevant data lives.
This checklist helps you assess whether data fragmentation is driving your eDiscovery costs up and gives you concrete steps to regain control. Each item includes the specific requirement and what a passing grade looks like.
Checklist Overview
This assessment focuses on three areas where fragmented data sources create measurable cost increases: data identification, collection scope, and review efficiency. You'll evaluate your current state, identify gaps, and prioritize fixes that reduce spending without sacrificing defensibility.
Use this when you're preparing your annual legal operations budget, responding to a discovery request that feels too expensive, or building a business case for consolidation tools.
Prerequisites
Before you start, gather:
- Your organization's current list of collaboration and storage platforms (email, chat, shared drives, project management tools)
- Last year's eDiscovery spending broken down by matter, if available
- Your Records Control Schedule or data map showing where business records live
- Access to someone from IT who knows authentication and API capabilities for your platforms
If you don't have a complete platform inventory, that's your first red flag.
Assessment Checklist
1. Data Source Inventory
Do you maintain a current, documented list of every platform where business communications and records are created?
Requirement: Your inventory should include collaboration tools (Slack, Microsoft Teams), cloud storage (Google Drive, SharePoint), project management systems (Asana, Confluence), and any platform where employees discuss work or store files.
What good looks like: A spreadsheet or database updated quarterly, listing each platform, the business units using it, the data types it contains, and whether it's in-scope for Legal Hold. If someone asks "do we use Platform X?", you can answer in under two minutes.
2. Cross-Platform Communication Mapping
Can you trace a business conversation across multiple platforms without manual reconstruction?
Requirement: When a discussion starts in email, continues in Teams, references a Google Drive document, and assigns tasks in Asana, you need a way to connect those pieces during discovery.
What good looks like: Your collection process preserves threading, links, and attachments across platforms. Reviewers see the full context without asking "where's the rest of this conversation?"
3. Collection Capability Assessment
Do you know whether each platform supports programmatic data export via API, and have you tested it?
Requirement: Every platform on your inventory needs a documented collection method. If you can't export data defensibly, you can't use that platform for business records.
What good looks like: For each platform, you've documented: API availability, authentication requirements, export format, metadata preservation, and whether you need vendor assistance. You've run at least one test collection to confirm the process works.
4. Custodian Interview Efficiency
When you issue a Legal Hold, do custodians know which platforms to search without asking follow-up questions?
Requirement: Your hold notice should specify exactly which platforms are in-scope and provide clear instructions for each.
What good looks like: Custodians receive a notice that says "search your email, Teams channels in the Sales workspace, and any Google Drive folders you own or edit" rather than "preserve all relevant documents." Follow-up questions drop to near zero.
5. Duplicate Data Management
Have you quantified how much data you collect multiple times because it's synced or copied across platforms?
Requirement: The same file sitting in email, Slack, and Google Drive shouldn't be processed three times.
What good looks like: You use hash-based deduplication before processing starts, and you've measured the reduction. If you're not seeing at least 20% duplicate elimination on multi-platform collections, your process isn't working.
6. Review Time Benchmarking
Do you track how long reviewers spend reconstructing context versus making substantive decisions?
Requirement: If reviewers are hunting for missing pieces of conversations or trying to figure out which version of a document is authoritative, you're paying for inefficiency.
What good looks like: You measure review speed in documents per hour and can identify which data sources slow reviewers down. You've documented specific pain points ("Teams exports lose threading") and prioritized fixes.
7. Technology Integration
Can your eDiscovery platform search across all your collaboration tools from a single interface?
Requirement: Treating each platform as a separate collection creates silos. Your review tool should let you search Slack and Teams simultaneously.
What good looks like: One search query returns results from email, chat platforms, cloud storage, and project tools. Reviewers don't switch between systems to answer a single question.
8. Records Control Schedule Alignment
Does your Records Control Schedule account for every platform where records are created?
Requirement: If your schedule only covers email and network drives but employees use Slack for business decisions, you're not compliant with your own policy.
What good looks like: Every platform in your inventory maps to at least one record series. You've documented retention triggers and disposition authorities for each. When IT wants to add a new tool, Legal reviews it against the schedule first.
Common Mistakes
Assuming Email Captures Everything: Business communication no longer follows a predictable path. If your discovery process focuses primarily on email, you're missing conversations that happen in Teams channels, Slack threads, and document comments.
Over-Collecting to Compensate for Uncertainty: When you don't know where relevant data lives, you collect everything. This approach increases processing costs, creates massive review sets, and doesn't actually improve recall.
Ignoring Metadata Loss: Many platforms export data in formats that strip threading, timestamps, or edit history. If you're not validating what metadata survives collection, you can't reconstruct timelines or prove authenticity.
Treating Consolidation as an IT Project: Technology can solve fragmentation, but only if Legal Operations defines the requirements. Don't let IT choose an Accessioning solution without specifying what you need for discovery and compliance.
Next Steps
If you checked fewer than six items, data fragmentation is costing you money right now. Prioritize items 1, 3, and 7 first; they give you visibility and control.
If you checked six or seven items, focus on optimization. Measure your duplicate rates, benchmark review speeds, and build a business case for better integration.
If you checked all eight, you're ahead of most organizations. Your next challenge is maintaining this state as new platforms emerge and business units adopt tools without central approval.
Schedule a quarterly review of this checklist. The platforms your organization uses will change faster than your processes can keep up unless you make monitoring part of someone's job.
