> 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/scoping-review.md).
# Scoping Review
Learn how to set up a scoping review in Nested Knowledge.
A scoping review maps the extent, range, and nature of research on a broad topic or question. Choose a scoping review when your question is exploratory or when the literature is too heterogeneous in design or outcome to support a standard SLR's synthesis. A scoping review typically produces a narrative writeup of the field alongside its descriptive summary.
For general methodology guidance independent of the software, see [Scoping review best practices](/best-practices/best-practices-by-review-type/scoping-reviews.md).
### Run A Scoping Review In Nested Knowledge
**Inputs:** a broad, exploratory question.
**Outputs:** a PRISMA flow diagram, a descriptive dashboard, and a narrative writeup of the field's extent, range, and nature.
| Stage | Recommended tools | Why |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Search | [**Automatic Search**](/review-workflow/literature-search/add-search/automatic-search.md) across multiple databases; [**Smart Search**](/review-workflow/literature-search/ai-tools-in-search/smart-search.md) or [**Search Exploration**](/review-workflow/literature-search/ai-tools-in-search/search-exploration.md) to build the query | A scoping review needs a broad, reproducible search to map the field. PRISMA-ScR expects the same search transparency as an SLR, even though later stages differ. |
| Screening | [**Dual Screening**](/review-workflow/screening/configure-screening.md), [**Exclusion Reasons**](/review-workflow/screening/exclusion-based-screening.md) | Two independent reviewers make the inclusion decisions more defensible. Choose **Two Pass Screening** or **Standard Screening** based on volume. Broader criteria often send more records to full-text review than an SLR. |
| Tagging and extraction | [**Smart Config: Tagging**](/review-workflow/tagging/ai-tools-in-tagging/smart-config-tagging.md) and [**Adaptive Smart Tags**](/review-workflow/tagging/ai-tools-in-tagging/adaptive-smart-tags.md) to build and extract a descriptive hierarchy (population, concept, context, and the nature of the evidence reported); [**Core Smart Tags**](/review-workflow/tagging/ai-tools-in-tagging/core-smart-tags.md) for an early baseline | Extraction describes the evidence that exists. Build a broad hierarchy for population, concept, context, and evidence type. Use **Core Smart Tags** for an early baseline. |
| Critical appraisal | Typically not performed, per PRISMA-ScR guidance | Scoping reviews map the evidence rather than assess its quality. Appraisal adds work your synthesis will not usually use. Skip it unless your protocol requires it. |
| Synthesis | [**Dashboards**](/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md)**,** [**Smart Insights**](/review-workflow/synthesis/set-up-synthesis-outputs/smart-insights.md)**,** [**Synthesis Chat**](/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-chat.md) for descriptive summaries, paired with a narrative writeup | A scoping review describes the field's extent, range, and nature. A dashboard supports that summary. The PRISMA-ScR writeup remains narrative rather than a pooled result. |
### Next Steps
:map: Scoping Review Best Practices
Apply methodology guidance alongside this workflow.
---
# 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/scoping-review.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.