On this page
The core idea
Retrieval always returns something in many implementations, even when the collection lacks an answer. That does not mean the returned passages are sufficient. Define what counts as enough support and make absence of evidence a normal product state. A helpful response can explain what is known, what is missing and where the user can obtain confirmation.
A practical approach
Step 1
Add questions that the collection cannot answer to your evaluation set. Include plausible questions close to covered topics, not only unrelated nonsense.
Step 2
Design a concise response that identifies the missing information without claiming a broader limitation than the evidence supports.
Step 3
Offer a relevant next step, such as opening the source directory or contacting the document owner. Avoid inventing an availability date or promised response time.
Worked example
The site lists a planned webinar topic but no scheduled session. Asked for the next date, the assistant should say the available material does not confirm a date and point to the workshop or contact page. Turning a topic listing into an event booking would create false expectations.
A mistake to avoid
A blanket ‘I cannot help’ discards useful partial information. The opposite mistake is answering from general knowledge when the user asked about an organisation-specific policy. Make the scope of the answer explicit.
Try it yourself
Write five questions your collection cannot answer. Draft a response for each containing one supported fact, one clearly stated gap and one practical next step.
Your implementation checklist
- Unanswerable questions are tested deliberately.
- Partial knowledge is separated from missing facts.
- No dates or commitments are invented.
- The next step is relevant to the specific gap.
Share or cite this guide
Innovate with Ajay Editorial (2026-10-04). Design a Useful Response When the Knowledge Base Has No Answer. https://innovatewithajay.com/blogs/make-unanswerable-questions-useful
Editorial approach, sources and corrections
Apply this guide to your own work: build a project brief with inputs, test cases and review boundaries.
