You're managing 200 opioid cases. Each one needs the same FDA correspondence, references the same clinical studies, and involves the same expert witnesses. Yet, you're paying to collect, host, and search that identical material 200 separate times.
The decision isn't whether master repositories make sense theoretically. It's whether the upfront investment and workflow change justify the cost savings across numerous cases.
Here's how to decide.
Key Factors That Affect Your Choice
Volume and repetition matter most. If you're handling a few cases with overlapping documents, a repository isn't necessary. But if you're managing 50 pharmaceutical matters with recurring medical literature, the math changes completely.
Platform pricing determines ROI. Most eDiscovery platforms charge by the gigabyte. Re-hosting the same 40GB of clinical studies in 75 separate case databases means paying 75 times for storage you only need once. This pricing model makes redundancy expensive.
Team maturity affects adoption. A master repository requires your team to search centrally before searching case-specific collections. If your litigation support staff resists process changes or lacks training on cross-matter search techniques, implementation will stall.
Jurisdiction complexity creates risk. Managing hundreds of cases across multiple jurisdictions requires tight version control. A master repository prevents scenarios where different teams use outdated or incorrect versions of documents.
Path A: Build the Repository Now
Choose this path when you meet these conditions:
Recurring document sets across at least 20 active matters. If the same materials appear repeatedly, you're already incurring redundancy costs.
Platform pricing penalizes duplicate hosting. Calculate what you're spending to host identical gigabytes across separate matters. If that number exceeds the cost of building and maintaining a central repository, you have a business case.
Dedicated governance resource. Master repositories need someone responsible for version control, metadata standards, and intake procedures. Without governance, your repository becomes disorganized.
Implementation steps:
Start with medical literature in pharmaceutical mass tort. This material changes rarely, appears in every case, and carries high hosting costs. Establish intake procedures and decide who manages updates and tagging.
Set search protocols before launch. Your team should search the master repository first, then case-specific collections. If they skip the repository and re-collect materials they already own, you've gained nothing.
Track cost avoidance monthly. Count gigabytes not re-hosted and measure hours not spent re-collecting known documents. Demonstrating ROI in specific numbers makes expansion easier to justify.
Path B: Wait and Optimize Your Current Workflow
Choose this path when:
Matter volume is too low. If you're managing fewer than 15 active cases with overlapping issues, the administrative overhead of repository governance exceeds the hosting savings. Optimize case-by-case workflows instead.
Platform pricing doesn't penalize redundancy. If duplicate hosting costs you nothing extra, your ROI calculation changes completely.
Lack of governance resources. A poorly maintained repository creates more problems than it solves. If you can't assign someone to manage intake and quality control, don't build the repository yet.
Immediate alternative:
Create case-closing checklists that identify reusable materials. When you close an opioid matter, flag the medical literature, expert reports, and regulatory filings for future use. Store them in a structured shared drive with clear version dates.
This isn't a true master repository, but it prevents your team from re-collecting materials from scratch. It's a stepping stone that requires minimal governance while reducing some redundancy costs.
Build relationships with providers who offer repository-friendly pricing. When your matter volume grows or your current contract renews, you'll be ready to negotiate terms that make centralized hosting viable.
Path C: Hybrid Approach for Growing Practices
You're between paths A and B. You have 25 active matters, enough volume to justify a repository, but you're not ready for full enterprise implementation.
Build a limited repository for your highest-volume document category only. In pharmaceutical mass tort, that's medical literature. In environmental cases, it might be regulatory correspondence. In product liability, it could be engineering specifications.
Set a six-month evaluation period. Track cost avoidance, measure user adoption, and identify governance pain points. If your limited repository demonstrates clear ROI and your team uses it, expand to additional document categories. If adoption is poor or costs exceed savings, you've learned without committing to full implementation.
Solve the pricing problem. Some platforms charge by the gigabyte in ways that make master repositories cost-prohibitive. Others structure pricing to encourage centralized hosting. During your evaluation period, assess whether your current platform supports repository economics or whether you need to consider alternatives.
Summary Matrix
| Factor | Build Now (Path A) | Wait (Path B) | Hybrid (Path C) |
|---|---|---|---|
| Active matters with overlap | 20+ | Fewer than 15 | 15-25 |
| Platform pricing model | Charges per GB | Flat fee or per-seat | Charges per GB |
| Governance capacity | Dedicated resource available | No resource available | Part-time resource available |
| Document repetition | High (same materials in 80%+ of cases) | Low (unique materials per case) | Moderate (recurring in 50-70% of cases) |
| Implementation timeline | Start with one document category this quarter | Optimize current workflow; revisit in 12 months | Six-month pilot with single category |
| Success metric | GB not re-hosted × cost per GB | Hours saved via case-closing checklists | User adoption rate + cost avoidance |
The decision isn't whether master repositories work in theory. It's whether your matter volume, platform economics, and governance capacity align to make them work in practice. Run the numbers. Count your overlapping gigabytes. Then choose the path that fits your current reality.
