Reference · How-to · ~12 min

How to evaluate RAG quality

Measure retrieval and answers separately — a eloquent lie is still a failure.

Measure retrieval and answers separately — a eloquent lie is still a failure.

Steps

1. Write **20–50 golden questions** from real users

2. For each, note the **expected source doc/section**

3. Run retrieval only — did the right chunk appear in top-k?

4. Run full RAG — is the answer **supported** by retrieved text?

5. Track metrics over time as you change chunking/models

Metrics

| Metric | Question |

|--------|----------|

| Retrieval hit@k | Is gold chunk in top k results? |

| Faithfulness | Is every claim in the answer backed by a chunk? |

| Refusal rate | Does it say "I don't know" when nothing matches? |

| Latency / cost | Acceptable for your product? |

Copy-paste eval row (spreadsheet)

question | expected_source | retrieved_top3 | answer_ok Y/N | notes

Quick manual test

Ask questions **outside** your corpus — bot should refuse, not invent.

**Try the lessons:** `eval-and-benchmarks` · `rag-pipeline-steps`