> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/best-practices/best-practices-by-review-type/narrative-reviews.md).
# Narrative Reviews
Learn about the best practices for conducting narrative reviews.
Here the best practices in conducting a narrative review are covered.
For step-by-step instructions in **Nested Knowledge**, see the [Narrative Review](/guides/guidance-by-review-type/narrative-review.md) guide. The guidance below applies regardless of the software you use.
### Disclose Your Approach Honestly
State plainly that the review isn't systematic with no predefined protocol and no exhaustive search so a reader knows what evidentiary weight to give it. This disclosure is what keeps a narrative review credible.
### Ground Interpretation In Your Expertise, And Say So
A narrative review's value comes from an author's expert synthesis rather than exhaustive coverage. Be explicit about where your interpretation, rather than the underlying evidence alone, is driving a conclusion.
### Still Cite What You Include Accurately
The absence of a formal protocol doesn't lower the bar for representing individual studies correctly. Cite sources precisely and don't overstate a single study's findings just because there's no systematic appraisal step checking that claim.
### Know When A Narrative Review Isn't Enough
If your use case needs to be rigorous, for example in a regulatory submission, claims needs to withstand scrutiny, then a narrative review isn't the right tool. Use the [Targeted literature review](/guides/guidance-by-review-type/targeted-literature-review.md) or [Scoping review guide](/guides/guidance-by-review-type/scoping-review.md) instead.
### Next Steps
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nested-knowledge.com/best-practices/best-practices-by-review-type/narrative-reviews.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.