How Long Does eDiscovery Take?

There is no standard eDiscovery timetable

A matter can take days, months or years. Duration depends on the legal deadline, number of custodians, data sources, volume, collection difficulty, processing complexity, review strategy, privilege issues, staffing and the number of productions required. The calendar is therefore a project-management question, not a fixed industry formula.

Start with the deadline and work backwards

Court orders, regulatory requests, investigation milestones and negotiated production dates often determine the outer boundary. A useful plan works backwards from delivery: production QC needs time; privilege and redaction need time; review must finish before that; processing and collection must feed review early enough. Working backwards exposes impossible assumptions before they become emergencies.

Identification and preservation

Initial identification can be quick when the organisation has good data maps and known custodians, or slow when systems are fragmented and facts are unclear. Preservation may need to begin immediately even while scope is still developing.

Custodian interviews and source mapping

Interviews may take days or weeks depending on availability and scale. They often reveal new sources, terminology and custodians. Scheduling senior employees across time zones can become a genuine critical-path issue.

Collection

Cloud collections may be rapid for standard sources, but throttling, permissions, export limitations, large mailboxes, mobile devices, remote locations and forensic requirements can slow the process. Collections can often be staged so priority custodians reach processing first.

Processing

Processing time depends on volume, infrastructure and data complexity. Straightforward email and office documents may move quickly; encrypted archives, corrupt files, large spreadsheets, audio/video and unusual application data can create exceptions.

Search, analytics and early case assessment

Search design should include testing and refinement. A term list that can be written in an hour may take much longer to validate responsibly. Analytics can accelerate understanding, but configuration, sampling and discussion with the legal team still require time.

Review

Review duration is driven by the number of reviewable documents, reviewer capacity, review speed and complexity of decisions. If 100,000 documents remain and a team completes 400 defensible decisions per reviewer per day, the arithmetic gives a starting point — not a promise.

Quality control and privilege

QC should run during review rather than wait until the last day. Calibration, sampling, second-level review and privilege checks consume time but can prevent far more expensive rework.

Production

Productions require preparation, validation and secure delivery. Native files, images, metadata, load files, numbering and redactions need to reconcile with the specification. Rolling productions can reduce deadline pressure but create repeated QC cycles and coordination overhead.

Parallel workstreams

The fastest responsible projects do not necessarily rush individual tasks; they overlap them intelligently. Priority custodians can be collected first. Processing can begin while later collections continue. Review can start on validated early data. Privilege teams can work alongside responsiveness review.

Building a realistic schedule

For each stage, estimate best case, expected case and risk case. Add dependencies, decision dates and contingency. Identify the true critical path and update the plan using actual collection volumes, processing throughput and review rates.

What usually causes delay

Late scoping, unavailable custodians, unexpected data sources, access problems, underestimated volumes, repeated search changes, unclear review protocols, slow legal decisions and late production specifications are common causes. Many are management problems rather than technology problems.

The practical answer

eDiscovery takes as long as the evidence and obligations reasonably require, constrained by the deadline. The best way to make it faster is to create visibility early, prioritise intelligently, work in parallel where safe and make decisions before they become bottlenecks.

Practitioner takeaways

Define the question before choosing the technology or workflow.
Make assumptions visible and revisit them as the evidence develops.
Use proportionate methods, but validate important exclusions and reductions.
Track cost, time, quality and risk together; improving one can affect the others.
Document material decisions so the process remains explainable and defensible.

Authoritative reference points

This is a vendor-neutral professional reference from the eDiscovery Certification Council Knowledge Hub. Jurisdiction-specific legal requirements should be checked against the current applicable rules and authoritative guidance.