The release of EDRM 2.0 on September 1, 2026, provided e-discovery teams with a more effective framework. The old linear diagram of nine boxes is replaced with a model showing eight interconnected phases, with Information Governance as the foundation and Analysis as a continuous thread. It's a conceptual framework, not an assembly line.
However, improved diagrams alone won't fix broken workflows. Teams that treat EDRM 2.0 as merely a cosmetic update will repeat the same mistakes that made the old model frustrating. Here's what goes wrong, why it happens, and how to fix it.
Why These Mistakes Keep Happening
Most e-discovery teams inherit their processes from predecessors who learned under the original EDRM. That model was released in 2005, when email lived on Exchange servers and "mobile device" meant a BlackBerry. Twenty years of habit creates organizational muscle memory. Teams see the new diagram, nod approvingly, then return to their established routines because changing a multi-department workflow is harder than updating a poster on the wall.
Another issue is that EDRM 2.0 requires coordination across functions that don't normally communicate. Information Governance underpins the entire model now, which means IT, Legal, Records Management, and Compliance need shared visibility into data sources. Most organizations lack that infrastructure. So teams adopt the vocabulary of EDRM 2.0 while continuing their siloed processes.
Mistake 1: Treating Data Acquisition as Four Sequential Steps
Why it happens: The new model groups Identification, Preservation, Collection, and Processing into a single Data Acquisition structure. Teams see four boxes inside a larger box and assume they still execute them in order: identify custodians, issue holds, collect devices, process files.
Real consequence: A departing employee's laptop gets wiped before Collection reaches it. Or Processing uncovers a new data source, collaborative workspaces, system logs, AI-generated summaries, that wasn't on the Identification list. Now you're explaining to opposing counsel why you need to re-collect, and to your CFO why the vendor invoice just doubled.
The fix: Run Identification and Preservation in parallel for high-risk custodians. When you identify someone whose role suggests they'll have relevant ESI, immediately check whether their devices are scheduled for routine wiping, whether they're using non-standard communication channels, and whether they've recently changed roles. Preservation decisions can't wait for a complete custodian list. EDRM 2.0 makes this explicit by nesting all four activities together, they inform each other, they don't queue.
Mistake 2: Ignoring the Information Governance Foundation Until Litigation Arrives
Why it happens: Information Governance now appears as a gray band beneath the entire EDRM 2.0 model, integrated with the Information Governance Reference Model (IGRM) v4.1 released in June 2026. But many teams still treat governance as a records-retention checkbox, not as the foundation for defensible e-discovery.
Real consequence: Litigation counsel asks IT where the Teams messages live. IT doesn't know, Teams is managed by a different group. That group explains the data sits in SharePoint, OneDrive, and Exchange, depending on how users configured their channels. Nobody documented this. Now you're three weeks into discovery and still mapping data sources, while opposing counsel questions whether your preservation was adequate.
The fix: Map your data sources before litigation triggers the duty to preserve. Document where each communication platform stores its data, how long it retains it, who has administrative access, and whether routine deletion processes run automatically. This is governance work, not discovery work, but it determines whether your Identification phase takes two days or two months. EDRM 2.0 puts governance at the bottom for a reason, it supports everything above it.
Mistake 3: Treating Analysis as a Phase That Happens After Review
Why it happens: The old EDRM showed Analysis as box seven of nine, between Review and Production. Teams built workflows around that sequence: collect everything, process it, review it, analyze what you found, then produce responsive documents.
Real consequence: You've already spent $200,000 on review before anyone analyzes whether you collected the right data sources. Analysis reveals that the key communications happened in a Slack workspace your Identification phase missed entirely. Or you discover during Production prep that the documents you've been reviewing don't actually address the claims in the complaint, you've been answering the wrong question.
The fix: EDRM 2.0 shows Analysis as a blue band beneath all eight phases because it should inform every decision. Before you collect, analyze what data sources are likely to contain relevant information. During Processing, analyze file types and metadata to spot gaps. During Review, analyze coding patterns to identify inconsistencies. Analysis isn't a discrete phase, it's continuous quality control that catches mistakes before they become expensive.
Mistake 4: Stopping at Production Instead of Planning for Disposition
Why it happens: The old EDRM ended with Presentation. Teams focused on getting documents out the door for production or trial, then moved on to the next matter. EDRM 2.0 adds Disposition as the final phase, but many teams haven't updated their workflows to include it.
Real consequence: Litigation data sits on vendor servers indefinitely because no one authorized its destruction. You're paying monthly hosting fees for matters that closed three years ago. Or worse: you destroy litigation data too early, before appeals are exhausted or related matters are resolved, and face spoliation allegations in a subsequent case.
The fix: Build Disposition into your matter-management process from the beginning. When you create a legal hold, document the triggering event and the criteria for lifting it. When the matter closes, determine whether appeals, related litigation, or regulatory requirements extend the preservation obligation. Only after you've cleared those hurdles should you authorize destruction. Disposition isn't an afterthought, it's how you defensibly end the e-discovery lifecycle and control costs.
Mistake 5: Assuming the Model Works the Same Way for Every Matter
Why it happens: EDRM 2.0 describes itself as a conceptual model, not a literal workflow. But teams want standardized procedures, so they build a single process and apply it to every matter regardless of size, complexity, or data sources involved.
Real consequence: You over-collect on a simple employment dispute because your standard process was designed for a multi-million-dollar breach-of-contract case. Or you under-collect on a complex regulatory investigation because you're following the same lightweight process you use for routine discovery requests. Neither approach is defensible, one wastes money, the other risks sanctions.
The fix: Treat EDRM 2.0 as a framework, not a checklist. For low-stakes matters with obvious custodians and straightforward data sources, you might move quickly through Identification and Collection with minimal Processing. For high-stakes matters involving novel data types, AI system logs, collaborative platforms, mobile communications, you'll need iterative Analysis and potentially multiple Collection rounds as you uncover new sources. The model's flexibility is the point. Your process should match the matter's risk profile and complexity.
Prevention Checklist
Before your next matter, verify:
- You've mapped enterprise data sources and documented retention policies (governance foundation)
- Your legal hold process can trigger Preservation immediately for high-risk custodians (Data Acquisition integration)
- You've defined Analysis checkpoints at Identification, Collection, Processing, and Review (continuous Analysis)
- Your matter-management system tracks Disposition criteria and Records Disposition Authority (lifecycle completion)
- You've documented how your process adapts based on matter complexity and risk (flexible application)
- Cross-functional teams (Legal, IT, Records, Compliance) have shared visibility into data sources and preservation status (governance coordination)
EDRM 2.0 reflects twenty years of hard-won experience. The mistakes that plagued the old model, treating discovery as linear, isolating Analysis, ignoring governance until litigation hits, are now structurally discouraged by the new design. But diagrams don't change behavior. You do.
