> 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/gap-analysis.md).
# Gap Analysis
Learn how to set up a gap analysis in Nested Knowledge.
A gap analysis maps what evidence exists on a topic. Choose a gap analysis when you need to justify a future study, identify an underserved population or outcome, or scope a research agenda.
For general methodology guidance independent of the software, see [Gap analysis best practices](/best-practices/best-practices-by-review-type/gap-analyses.md).
### Run A Gap Analysis In Nested Knowledge
**Inputs:** a broad topic and the coverage dimensions you want to map (population, intervention, outcome, geography).
**Outputs:** an evidence map or coverage dashboard showing where research is dense, thin, or missing.
| Stage | Recommended tools | Why |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Search | [**Automatic Search**](/review-workflow/literature-search/add-search/automatic-search.md) across a broad set of databases | A gap analysis needs broad coverage to show what is and is not studied. A narrow search can make an unsearched topic look like an evidence gap. |
| Screening | [**Single Screening** and **Standard**](/review-workflow/screening/configure-screening.md) (abstract-level only, in most cases), [**Exclusion Reasons**](/review-workflow/screening/exclusion-based-screening.md) for off-topic records | Screening confirms whether a record belongs in the evidence landscape. It does not assess whether the study meets an effectiveness threshold. **Dual Screening** and **Two Pass Screening** usually add more rigor than this review type needs. |
| Tagging and extraction | [**Core Smart Tags**](/review-workflow/tagging/ai-tools-in-tagging/core-smart-tags.md) for an immediate PICO, Study Type, Study Location, and Study Size read across the whole corpus; [**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 custom set of coverage categories (population, intervention, outcome domain, geography) | Tags turn a set of studies into a map of coverage. **Core Smart Tags** provide a baseline description. A custom hierarchy captures the population, intervention, outcome, and geography dimensions your question needs. |
| Synthesis | [**Dashboard**](/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md)**,** [**Smart Insights**](/review-workflow/synthesis/set-up-synthesis-outputs/smart-insights.md) and [**Synthesis Chat**](/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-chat.md) for coverage summaries and evidence maps | A gap analysis shows where evidence clusters and where it is limited. A dashboard or evidence map makes that distribution visible. Meta-analysis does not apply because no single effect estimate is pooled. |
### Next Steps
:magnifying-glass-chart: Gap Analysis 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/gap-analysis.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.