Recall and precision are the two metrics that measure how well a search or review process performs. Recall is the share of all relevant documents the process finds. Precision is the share of retrieved documents that are actually relevant. eDiscovery teams use both to validate search terms and TAR results.
Share
Recall and precision come from information retrieval, the field behind every search engine. eDiscovery borrowed them because discovery is, at its core, a retrieval problem: find the relevant documents in a large collection without producing the irrelevant ones.
The two metrics answer different questions. Recall measures completeness. Of all the relevant documents in the collection, what percentage did the process find? Precision measures accuracy. Of the documents the process retrieved, what percentage are actually relevant?
A short example makes the difference concrete. Suppose a collection holds 100 relevant documents, and a search returns 50 documents, 40 of them relevant. Recall is 40 percent, because 40 of the 100 relevant documents were found. Precision is 80 percent, because 40 of the 50 retrieved documents are relevant.
Recall and precision pull against each other. Broaden a search, and recall rises while precision falls, since more relevant documents surface along with more noise. Narrow it, and precision rises while recall falls, since cleaner results come at the cost of missed documents.
In eDiscovery, the two sides of that trade-off carry different weights. Recall is a defensibility question, because a missed responsive document is a production gap. Precision is a cost question, because every irrelevant document that reaches review is billable time spent on noise. Producing parties generally optimize for recall first, then use precision to control review spend.
The F1 score combines the two into a single number, the harmonic mean of recall and precision. It is standard in machine learning evaluation, though eDiscovery validation usually reports recall and precision separately, since they answer different legal questions.
No one knows the true number of relevant documents in a collection, so both metrics are estimated through statistical sampling.
Validation applies to TAR and search-term workflows alike. Parties increasingly negotiate the validation method, and sometimes a recall target, in the ESI protocol before review begins.
They are how a review process proves it worked. Courts accept technology assisted review when the process is transparent and validated, and recall is the metric that validation centers on. A documented recall estimate, built on defensible sampling, is what answers a challenge to the sufficiency of a production.
The metrics also frame the limits of search methods themselves. Research on keyword retrieval shows how much a review can miss without measurement, which is one reason meaning-based methods like concept search and active learning exist. Measuring recall and precision turns "we searched" into "we found what was there."
Recall is the percentage of all relevant documents in a collection that a process finds. Precision is the percentage of retrieved documents that are actually relevant. Recall measures completeness, and precision measures accuracy.
Recall usually carries more weight, because a missed responsive document creates a production gap and a defensibility risk. Precision matters for cost, since low precision sends irrelevant documents to billable review.
An elusion test samples the documents a review marked non-relevant or never reviewed. The share of that sample that turns out to be relevant is the elusion rate, which estimates what the process missed and supports the recall calculation.
The F1 score is the harmonic mean of recall and precision, combining both into a single number. It is standard in machine learning evaluation, though eDiscovery validation typically reports recall and precision separately.
Recall measures how many relevant documents a search finds; precision measures how many results are relevant. Learn how both validate eDiscovery revie
Read MoreActive learning lets a TAR model choose the documents it learns from as reviewers code. Learn how it powers TAR 2.0 and continuous active learning.
Read MoreConcept search retrieves documents by meaning, not exact keywords. Learn how it works in eDiscovery and when it outperforms keyword search.
Read MoreA Second Request is a demand for additional information the FTC or DOJ issues during HSR merger review. Learn how it works and what it means for eDisc
Read More