// term 72 · Retrieval & Knowledge
Retrieval Recall
Broad Knowledge Retrieval
The fraction of all relevant documents that retrieval actually found — the metric of coverage. High recall means nothing important was missed; low recall means the model answers from an incomplete picture, however clean the retrieved context looks.
// Definition
found / existing
Of everything relevant in the corpus, how much retrieval surfaced — completeness of the evidence, expressed as a ratio.
// Failure mode
silent
Missed documents leave no trace in the answer — recall failures look like confident responses built on partial evidence.
// Stakes peak
compliance
Legal discovery, risk surveillance, and safety reviews — domains where the missed document is the costly one.
// full definition
What Retrieval Recall actually is
Recall asks the question precision can't: of everything in the corpus that bears on this query, how much did retrieval actually surface? A system can return ten perfectly relevant passages — pristine precision — while missing the one document that changes the answer. Recall failures are silent by nature: the model composes a confident response from what arrived, and nothing in the output reveals what didn't. The incomplete picture reads exactly like the complete one.
The stakes scale with the cost of missing. Conversational lookups tolerate imperfect recall — another phrasing finds the document next time. Legal discovery, compliance surveillance, contract analysis, and safety reviews do not: the missed clause, the unsurfaced incident, the overlooked exposure are precisely the failures these workloads exist to prevent. Recall requirements are use-case properties, and the high-stakes end demands engineering that casual search never needed.
Recall is won or lost early in the pipeline. Corpus coverage comes first — content never ingested can never be found, making ingestion completeness and parsing fidelity silent recall ceilings. Chunking decides whether relevant passages exist as findable units; embedding quality determines whether they land near the queries that seek them; ANN index settings trade exhaustiveness for speed; and search breadth (top-k, multi-query expansion, hybrid legs) sets how wide the net casts. Query reformulation helps recall most of all — relevant documents phrased differently from the question are recall's most common loss.
The architecture that resolves recall's tension with precision is staged: cast wide early, refine late. Retrieve generously — high k, multiple query formulations, hybrid signals — accepting noise in the candidate pool; then let reranking and cutoffs restore precision before context assembly. Measurement mirrors precision's discipline with one harder edge: recall ground truth requires knowing all relevant documents for test queries, an annotation investment that high-stakes domains justify and casual ones approximate with sampled audits.
// how it works
Making sure nothing important is missed
Recall is won early in the pipeline — corpus coverage, chunking, embeddings, and search breadth deciding what can be found at all.
Corpus Coverage
Everything findable must first be ingested and parsed — the silent ceiling recall inherits before any query runs.
Findable Units
Chunking determines whether relevant passages exist as retrievable segments — coverage decided at preprocessing.
Query Expansion
Reformulations and multi-query strategies bridge vocabulary gaps — recovering documents phrased unlike the question.
Wide Retrieval
Generous k, hybrid legs, and tuned index breadth cast the net — recall's stage, with noise accepted as the cost.
Precision Handoff
Reranking and cutoffs refine the wide pool — the staged architecture letting recall and precision each win their stage.
Recall Audit
Known-relevant test sets measure what the system finds versus what exists — the silent failure made visible.
// anatomy
The components teams must understand
01
Recall@k
The coverage metric
Relevant documents found within the top k — measured against ground truth of everything that should have surfaced.
02
Ingestion Completeness
The silent ceiling
Sources connected, formats parsed, updates synced — recall bounded before retrieval begins by what the index contains.
03
Query Reformulation
The vocabulary bridge
Expansions and rewrites finding documents phrased differently from questions — recall's highest-leverage front-end fix.
04
Search Breadth
The net's width
Top-k depth, hybrid legs, and ANN exhaustiveness settings — the dials that widen what retrieval considers.
05
Staged Refinement
Recall then precision
Wide candidate pools refined by reranking — the architecture dissolving the trade across stages instead of compromising in one.
06
Ground-Truth Burden
Measurement's hard edge
Knowing all relevant documents per test query — the annotation cost that high-stakes recall assurance requires.
// strategic implications
What this changes for the business
01 · Risk
Recall failures are invisible in the answer
Missed documents leave no trace — the model answers confidently from what arrived, and the gap surfaces only when consequences do. High-stakes retrieval (legal, compliance, safety) needs measured recall assurance, because the output will never volunteer what it didn't see.
02 · Architecture
Recall is won upstream
Ingestion gaps, parsing failures, and chunking choices cap recall before search runs — and no query-time tuning recovers content the index never held. Audit corpus coverage first; the most common recall failure is the document that was never indexed.
03 · Requirements
Specify recall per use case
Casual lookup and exhaustive discovery have different recall obligations, costs, and verification burdens. Make the requirement explicit per workload — and fund the ground-truth measurement where the missed document is the expensive one.
// common misconceptions
What Retrieval Recall is not
Myth
“If the answer looks complete, retrieval was complete.”
Reality
Models compose fluent answers from whatever arrives — partial evidence reads identically to full evidence. Recall is verified by measurement against known-relevant sets, never by inspecting the output.
Myth
“Raising top-k solves recall.”
Reality
Deeper result lists only help if relevant documents were ranked at all — vocabulary gaps, chunking fragmentation, and ingestion holes put content beyond any k. Recall engineering spans the pipeline, not one parameter.
Myth
“Recall matters less than precision in RAG.”
Reality
They fail differently: precision failures add noise; recall failures subtract truth. For analysis, discovery, and compliance workloads, the missed document is the catastrophic case — and it's recall's to prevent.
// from literacy to leverage
Know the term. Now build the strategy.
Vocabulary is the entry fee. Turning these primitives into pipeline, moats, and margin is the work. That's the conversation.