> 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/guides/guidance-by-review-type/narrative-review.md).

# Narrative Review

Learn how to set up a narrative review in Nested Knowledge.

A narrative review summarizes and interprets the literature on a topic without a predefined protocol. Choose a narrative review when your goal is a synthesized, expert perspective. A narrative review doesn't follow a fixed methodology so it is faster to produce than other review types.

For general methodology guidance independent of the software, see [Narrative review best practices](/best-practices/best-practices-by-review-type/narrative-reviews.md).

### Run A Narrative Review In Nested Knowledge

**Inputs:** a topic and your own subject-matter expertise with no predefined protocol.

**Outputs:** an authored narrative writeup, optionally organized around AI-surfaced themes.

| Stage                  | Recommended tools                                                                                                                                                                                                                                                                                                                                  | Why                                                                                                                                                                                                                                         |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Search                 | [**Search Exploration**](/review-workflow/literature-search/ai-tools-in-search/search-exploration.md) or [**Smart Search**](/review-workflow/literature-search/ai-tools-in-search/smart-search.md) for a quick, targeted pass; [**Other Sources**](/review-workflow/literature-search/other-sources.md) for known or expert-recommended references | A narrative review does not require exhaustive, multi-database coverage. **Search Exploration** supports an author building a reading list around their expertise. **Other Sources** adds references you already know belong in the review. |
| Screening              | [**Single Screening** and **Standard**](/review-workflow/screening/configure-screening.md) (one pass)                                                                                                                                                                                                                                              | A narrative review has no fixed protocol to screen against. One reviewer can curate the literature in a single pass.                                                                                                                        |
| Tagging and extraction | Light manual tagging, or [**Core Smart Tags**](/review-workflow/tagging/ai-tools-in-tagging/core-smart-tags.md) for a quick organizing pass                                                                                                                                                                                                        | The output is authored prose, not a structured dataset. Use tags to organize studies by theme while you write.                                                                                                                              |
| Synthesis              | Authored narrative with [**Synthesis Chat**](/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-chat.md), optionally organized with [**Smart Insights**](/review-workflow/synthesis/set-up-synthesis-outputs/smart-insights.md)                                                                                                       | The narrative is the output. **Smart Insights** can surface themes across tagged studies, but it does not replace the authored interpretation.                                                                                              |

### Next Steps

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-book-open">:book-open:</i><br><strong>Narrative Review Best Practices</strong></td><td>Apply methodology guidance alongside this workflow.</td><td><a href="/best-practices/best-practices-by-review-type/narrative-reviews.md">Narrative Reviews</a></td></tr></tbody></table>


---

# 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/guides/guidance-by-review-type/narrative-review.md?ask=<question>&goal=<user_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.