Recall: From Definition and Principles to Search and Recommendation Applications

Recall is a metric that measures the proportion of actual positives or items that should be returned that are successfully retrieved. It focuses on whether the system misses target results, and is suitable for understanding classification models, information retrieval, search relevance evaluation, and recommender systems.

What Is Recall?

Recall is a metric that measures how many of all actual positives or items that should be returned are successfully retrieved by a model or system. The core question it answers is not “Are all the returned results correct?” but “Have the targets that should have been found been missed?”

In classification tasks, Recall is also called the true positive rate, or TPR, and is used to observe a model’s ability to identify actual positive samples. In some materials, it is also called sensitivity. In this context, all three point to the same core meaning: among objects that are actually positive, how many are identified.

Key point: Recall focuses on “finding everything” or “missing less.” If a system misses many targets that should have been identified or returned, its recall may be low even if the part it returns looks good.

Understanding Recall with a Simple Analogy

Recall can be understood as the ability to “find all relevant documents from a pile of documents.” Suppose there are several truly relevant documents in a document library. The more relevant documents the system retrieves, the higher the recall; if a large number of relevant documents do not enter the result set, recall is low.

This analogy can also help explain the correspondence between classification and retrieval:

ScenarioWhat is the “target that should be retrieved”What recall focuses on
Classification modelSamples that actually belong to the positive classHow many actual positives are identified as positive
Information retrievalAll relevant items that should be returnedHow many relevant items are actually returned
Search systemThe documents or results the user truly wantsWhether these results enter the search result set
Recommender systemAll relevant items in the document library or candidate setHow much relevant content the system covers

Therefore, the intuitive focus of recall is “whether targets have been missed,” not “whether every retrieved item is accurate enough.” The latter usually needs to be judged together with other evaluation dimensions.

The Calculation Logic of Recall

When understanding recall, you can first grasp the denominator and numerator:

  • Denominator: All actual positives, or all items that should be returned and are relevant.
  • Numerator: Among these targets, the portion correctly identified or actually returned by the model or system.

In other words, recall measures the proportion of “retrieved targets” among “all targets.”

Calculation Meaning in Classification Tasks

In classification scenarios, the denominator is the samples that actually belong to the positive class, and the numerator is the samples among them that are correctly identified by the model as positive. The higher the recall, the more fully the model covers actual positives in identification.

For example, in a task that needs to discover a certain type of target, recall can help determine whether the model has missed many actual positive samples.

Calculation Meaning in Information Retrieval and Recommendation

In information retrieval and recommendation evaluation, recall can be understood as: the relevant items retrieved by the system as a proportion of all relevant items.

If there are multiple pieces of relevant content in a document library but the system returns only some of them, recall reflects the degree of coverage of that portion. It is suitable for measuring whether the system finds relevant content as completely as possible.

The Role of Recall in Classification Models

In classification model evaluation, recall is suitable for measuring a model’s ability to find positive targets. It is especially suitable for answering this type of question: among samples that are actually positive, how many are identified by the model?

Observation pointWhat recall can indicateWhat it cannot indicate on its own
Ability to identify actual positivesWhether the model retrieves more actual positive samplesWhether all samples returned as positive are reliable
Missed detectionsLow recall may indicate that many actual positives have been missedWhether the overall system quality is necessarily poor
Task fitWhether it is suitable for goals that focus on “missing less”Whether all evaluation goals have already been met

High recall usually means fewer actual positives are missed, but it cannot by itself prove that all positive results output by the model are correct. Therefore, when evaluating a model, recall should be understood within the specific task objective rather than used in isolation.

The Role of Recall in Search and Recommender Systems

In search relevance scenarios, recall is used to measure how many of the documents users truly want appear in the search results. If the results users expect to see do not enter the result set, there may be insufficient recall even if some of the top-ranked results look relevant.

For example, a query should have displayed three relevant products, but only two appear in the top 10 results. This example shows that the system has not completely failed to return relevant content; rather, it has not found all the relevant results that should appear, so there is insufficient recall.

User needSolutionEffect
Want to find as complete a set of relevant documents as possibleUse recall to observe the proportion of documents that should be returned that enter the result setDetermine whether search results miss important content
Want to evaluate a recommender system’s ability to cover relevant contentCompare the retrieved relevant items with all relevant itemsDiscover whether recommendation or retrieval coverage is insufficient
Want to analyze the problem of incomplete search resultsCheck whether the results users truly want enter the candidate or result listLocate the problem of “not being retrieved”

In recommendation or retrieval evaluation, recall can also represent the ratio of the number of relevant documents retrieved to the number of all relevant documents in the document library. This perspective emphasizes the system’s ability to cover relevant content.

How to Interpret High or Low Recall

High recall usually means that the system covers more actual positives or relevant results, and is suitable for tasks that focus on “finding everything.” Low recall often means that the system has missed many target objects, which may affect result completeness in classification, search, or recommendation scenarios.

In different scenarios, the focus of interpreting recall differs slightly:

ScenarioHigh recall usually meansLow recall may mean
Classification modelMore actual positive samples are identifiedMany actual positive samples are missed
Information retrievalMore items that should be returned are actually returnedRelevant items have not been sufficiently retrieved
Search relevanceResults users want are more likely to enter the result setImportant results do not appear in the search results
Recommender systemRelevant content coverage is more sufficientRecommendation or retrieval candidate coverage is insufficient

Key point: Higher recall does not automatically mean the overall system is better. It shows that the system performs more fully in “finding all targets,” but complete evaluation still needs to return to the specific task objective.

Common Misconceptions When Using Recall

Misconception 1: Interpreting recall as all results being correct

Recall mainly measures whether everything has been found, not whether all returned results are correct. A system may retrieve many target objects, but this does not mean every returned item is necessarily reliable.

Misconception 2: Ignoring the meaning of the positive class in different scenarios

In classification tasks, the positive class usually refers to samples that actually belong to the target category; in a retrieval context, relevant items can also correspond to items marked as positive. If the definition of “positive class” or “relevant” is not clarified first, recall can easily be misread.

Misconception 3: Judging the overall quality of a system based only on recall

Recall is suitable for answering “whether targets that should be retrieved have been missed.” But a system’s overall performance also depends on the task objective, result quality, and actual usage scenario. Especially in search, recommendation, and model evaluation, recall should usually be understood as one metric in an evaluation system.

Checklist Before Using Recall

  • Has it been clarified what counts as an “actual positive” or a “relevant item”?
  • Is the scope of all items that should be returned known?
  • Does the current task focus more on “missing less” rather than other goals?
  • Has recall been avoided being misunderstood as all results being correct?
  • Is the metric meaning interpreted in combination with specific business or evaluation goals?