---
title: "Comment by Ahmet Özel on \"What I learned building a RAG notes app (and the evals I skipped)\" | Hashnode"
description: "The keyword-only fallback to a note's first piece can lose a correct candidate even after retrieval succeeded. If the matching term and answer sit near the end"
url: "https://hashnode.com/posts/what-i-learned-building-a-rag-notes-app-and-the-evals-i-skipped/6aed9cf3af39498fe75b6f87/comment/6aef42d1b8079c2fa10e274d"
---

[Discussion](https://hashnode.com/posts/what-i-learned-building-a-rag-notes-app-and-the-evals-i-skipped/6aed9cf3af39498fe75b6f87)

Comment [What I learned building a RAG notes app (and the evals I skipped)](https://hashnode.com/posts/what-i-learned-building-a-rag-notes-app-and-the-evals-i-skipped/6aed9cf3af39498fe75b6f87)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Nov 7](https://hashnode.com/posts/what-i-learned-building-a-rag-notes-app-and-the-evals-i-skipped/6aed9cf3af39498fe75b6f87/comment/6aef42d1b8079c2fa10e274d)

The keyword-only fallback to a note's first piece can lose a correct candidate even after retrieval succeeded. If the matching term and answer sit near the end of a long note, the reranker sees its unrelated introduction and can discard the very note that keyword search found.

I would preserve the keyword match location and map it to the corresponding piece before reranking. One fixture with the answer only in the final piece would distinguish this from the separate top-20 candidate problem you described, and stage-level results would show whether the note disappeared before or during reranking.