If you're managing eDiscovery operations, you've probably noticed that your current process map doesn't match how your team actually works anymore. The original EDRM diagram, while foundational, reflected a 2005 understanding of discovery as a linear, sequential process. EDRM 2.0 changes that model to reflect how discovery actually happens today: iterative, analytics-driven, and grounded in information governance from the start.
This matters because courts, opposing counsel, and regulators are already operating under these assumptions. When a judge asks about your preservation methodology or expects continuous proportionality analysis, they're expecting the integrated approach EDRM 2.0 formalizes. If your workflow is still structured around the old sequential model, you're creating risk.
Preparing for EDRM 2.0
Before restructuring your discovery operations around EDRM 2.0, audit what you already have:
Documentation of current state:
- Your existing discovery workflow diagrams
- Standard operating procedures for identification, preservation, collection, and processing
- Information governance policies (if they exist separately from discovery procedures)
- Analytics and review protocols
- Disposition procedures for closed matters
Team alignment:
- Identify who owns each phase in your current model (IT, legal ops, outside counsel, vendors)
- Map dependencies between phases
- Document where handoffs currently break down or create delays
Technical capabilities:
- Inventory your current eDiscovery platforms and their API capabilities
- Confirm whether your preservation tools can trigger collection workflows
- Check if your review platform supports continuous analytics (not just upfront TAR)
- Verify whether your matter management system tracks disposition separately
Governance foundation:
- Review your Records Control Schedule
- Confirm you have documented Legal Hold procedures
- Check whether your retention rules account for discovery obligations
You don't need perfect governance in place before starting. EDRM 2.0 positions governance as foundational, meaning implementing the model will expose gaps you need to fix.
Step-by-Step Implementation
Phase 1: Integrate Information Governance as Foundation (Weeks 1-4)
Start by connecting your Records and Information Management program to your discovery operations. In the old model, these ran parallel. In EDRM 2.0, governance grounds everything.
Create a working group that includes your records manager, legal ops lead, and IT. Map your Records Control Schedule against your typical discovery obligations. Where do retention periods conflict with standard preservation windows? Document those conflicts now.
Update your Legal Hold procedures to reference specific record series from your classification scheme. When you issue a hold, you should be able to point to the Business Classification Scheme categories affected. This makes preservation scope defensible and auditable.
If you don't have a formal Records Control Schedule, build a minimal viable version covering your most litigation-prone record types: email, contracts, HR files, financial records. You can expand later.
Phase 2: Unify Data Acquisition (Weeks 5-8)
EDRM 2.0 groups identification, preservation, collection, and processing into a unified Data Acquisition framework. This reflects reality: these activities increasingly happen together, not sequentially.
Reconfigure your matter intake process to trigger all four activities simultaneously when appropriate. For example, when a Legal Hold is issued:
- Identification happens via automated custodian interviews
- Preservation triggers immediately in your email system
- Collection begins for departed custodians or at-risk data
- Processing starts as soon as the first data arrives
This requires technical integration. If your Legal Hold platform can't trigger your collection vendor's API, you're still operating sequentially. Build that integration or switch tools.
Document your new Data Acquisition standard operating procedure. Specify when you'll collect immediately versus preserve-in-place. Define processing standards upfront (de-duplication, email threading, language detection) so you're not making those decisions ad hoc per matter.
Phase 3: Embed Continuous Analysis (Weeks 9-12)
Analysis is no longer a discrete phase that happens after processing. EDRM 2.0 represents it as connective tissue across the entire lifecycle.
Implement analytics at every phase:
- During identification: Use data mapping and custodian network analysis to scope preservation
- During collection: Run initial keyword and concept searches to validate scope
- During review: Apply continuous active learning, not just first-pass TAR
- During production: Analyze what you produced to refine future collection
- During disposition: Review what you retained versus what was actually used at trial
This requires changing how you contract with review vendors. Your statement of work should include continuous model refinement, not a single TAR workflow at the start of review.
Train your legal team to expect iterative analysis. The first production won't be the last. The first privilege log will get supplemented. This is defensible if you document the analytical process at each iteration.
Phase 4: Formalize Disposition (Weeks 13-16)
EDRM 2.0 adds disposition as a discrete phase. Most teams handle this informally or not at all. That's a risk.
Create a disposition protocol that answers:
- When can matter data be destroyed? (Check your Records Disposition Authority and any settlement agreements)
- What's the approval process? (Legal ops sign-off, records manager confirmation, IT execution)
- How do you document destruction? (Certificate of destruction, audit log entry)
- What do you preserve for precedent? (Key pleadings, work product, significant productions)
Build this into your matter management system. When a matter closes, it should trigger a disposition review workflow, not just sit in "closed" status indefinitely.
For matters where you collected from live systems, confirm that your Records Freeze has been lifted and normal retention rules have resumed. Document that confirmation.
Validation: How to Verify It Works
After implementation, test the new workflow with a representative matter:
Test scenario: Simulate a new litigation hold for a hypothetical employment dispute involving three custodians and a two-year time frame.
Verify:
- Legal Hold triggers identification, preservation, and initial collection within 24 hours
- Your Data Acquisition log shows unified tracking across all four activities
- Analytics run automatically during collection (keyword hit reports, data volume by custodian)
- Disposition protocol appears in your matter checklist from day one
Audit the documentation: Can you produce a defensible process map showing exactly what happened and when? If you can't explain your workflow to opposing counsel or a judge using EDRM 2.0 terminology, you haven't fully implemented it.
Maintenance and Ongoing Tasks
EDRM 2.0 isn't a one-time project. Maintain it through:
Quarterly reviews:
- Compare your actual discovery activities against the EDRM 2.0 phases
- Identify where you're still operating sequentially when you should be iterative
- Update your standard operating procedures to reflect process improvements
Annual governance alignment:
- Review whether your Records Control Schedule still supports your discovery obligations
- Update Business Classification Scheme categories based on new litigation trends
- Revise disposition protocols as case law evolves
Continuous training:
- When you onboard new legal ops staff, train them using EDRM 2.0 as the reference model
- When you engage new vendors, confirm their workflows align with the updated framework
- When you brief executives on discovery costs, use EDRM 2.0 to explain where resources go
The model will continue to evolve. EDRM released this update after public comment that ran through July 30, 2026, and the framework is licensed under Creative Commons to allow adaptation. Track updates at edrm.net and adjust your implementation accordingly.
Your discovery process should look different six months from now than it does today. If it doesn't, you're not actually implementing EDRM 2.0, you're just relabeling your old workflow with new terminology.
