> 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/scoping-reviews.md).
# Scoping Reviews
Learn about the best practices for conducting scoping reviews.
Here the best practices in conducting a scoping review are covered.
For step-by-step instructions in **Nested Knowledge**, see the [Scoping Review](/guides/guidance-by-review-type/scoping-review.md) guide. The guidance below applies regardless of the software you use.
### Register And Report Against PRISMA-ScR
Use the PRISMA-ScR checklist and register your protocol. A scoping review's search still needs to be comprehensive and reproducible, even though what happens after screening differs from an SLR.
### Set Broad, Explicit Eligibility Criteria
A scoping review typically includes a wider range of study designs and sources than an SLR so it is important to state that breadth explicitly in your criteria.
### Don't Default To Appraising Study Quality
PRISMA-ScR guidance doesn't require a risk-of-bias assessment, since a scoping review's goal is to map the field.
### Report The Nature Of The Evidence, Not Just Its Volume
A scoping review's value is in describing what kind of evidence exists—study designs, populations, contexts—not just how much of it there is. Structure your extraction and writeup around that descriptive goal from the start.
### 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/scoping-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.