What is context precision?

Context precision in RAG measures how much of the retrieved context is relevant to answering a user's question, with particular attention to whether useful passages appear near the top of the retrieved list. It helps reveal when a retriever sends too much irrelevant text to the generator.

Beginner-friendly example

A user asks: “How long is the warranty for Product A?”

The retriever returns four passages:

1. Product A has a two-year warranty. → Relevant
2. Product A is available in blue and black. → Irrelevant
3. Product A warranty covers manufacturing defects. → Relevant
4. The company opened a new office. → Irrelevant

Simple context precision at K=4 = 2 relevant passages / 4 retrieved passages = 0.50 (50%).

This is the basic Precision@K interpretation of context relevance. Some RAG evaluation frameworks use a rank-aware context precision metric that gives more credit when relevant passages appear earlier, so the exact formula depends on the framework.

Why does it matter?

• Irrelevant passages waste context-window tokens and increase latency or cost.
• Distracting content can make the model miss the useful evidence.
• High context precision often makes grounded answers easier, but it does not guarantee correctness.

Precision@K versus rank-aware context precision

Precision@K counts relevant items among the top K, regardless of their order.

A common rank-aware approach uses average precision over the retrieved list:

Context precision = (Σ precision@i × relevanceᵢ) / (number of relevant items in the evaluated list)

Here, relevanceᵢ is 1 for a relevant passage and 0 otherwise. Some frameworks apply additional definitions, reference-answer checks, or conventions for zero relevant passages; always inspect the metric implementation.

Example with relevance labels [1, 0, 1, 0]:

• Precision@1 = 1/1 = 1.00
• Precision@3 = 2/3 ≈ 0.67
• Rank-aware score = (1.00 + 0.67) / 2 ≈ 0.83

Moving the two relevant passages to ranks 3 and 4 would lower the rank-aware score even though ordinary Precision@4 stays at 0.50.

How to improve context precision

1. Use a better query representation and appropriate metadata filters.
2. Combine keyword and vector retrieval when the task benefits from both.
3. Rerank candidate passages by their relevance to the specific question.
4. Remove near-duplicate, stale, or clearly irrelevant chunks.
5. Evaluate on realistic labeled queries and compare quality against recall and latency.

Important distinction

Context precision evaluates retrieved evidence, not the final answer. Answer relevance asks whether the response addresses the user's question, while faithfulness asks whether the response's claims are supported by that evidence.

Interview takeaway

Context precision tells you whether retrieved passages are useful rather than noisy. Report the metric's exact definition—simple Precision@K or a rank-aware variant—because implementations are not interchangeable.