> 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/review-workflow/tagging.md). # Tagging Learn how to extract data using tags and AI tools available. **Tagging** turns studies into usable data. A tag captures one datapoint, or a set of datapoints, from a study. It can be applied during screening or extraction by a person, by AI or both. [**Core concepts**](/get-started/core-concepts.md) explains how tags fit into a nest. Tagging matters at two distinct points in a review, for two different reasons. * **Screening**, tags help you sort and prioritize studies as you go — a fast way to categorize records well before every screening decision is final. You can [apply tags during screening.](/review-workflow/screening/screen-records.md#applying-tags-in-screening) * Once studies are included, tags become the backbone of extraction in **Tagging**: the structured, comparable framework that all living interactive outputs are built on. This is why it is important to create a reliable tag hierarchy to ensure ease of everything downstream. See below. Before starting the Tagging process, choose your path for building a tag hierarchy and from available AI tools. ### Tools Available Below is a summary of the Tagging/Extraction AI tools offered and what they do.

Tool	Builds the hierarchy	Extracts the data	Reads
Core Smart Tags	Yes — a fixed PICO, Study Type, Study Location, and Study Size set	Yes — immediately, for every applicable study	Abstracts only
Smart Config: Tagging	Yes — a custom hierarchy drafted from your research question	No (unless paired with ASTs)	—
Adaptive Smart Tags	No	Yes	Abstracts or Full Texts

Tool

Builds the hierarchy

Extracts the data

Reads

Core Smart

Tags

Yes — a fixed PICO, Study Type, Study Location, and Study Size set

Yes — immediately, for every applicable study

Abstracts only

Smart Config: Tagging

Yes — a custom hierarchy drafted from your research question

No (unless paired with ASTs)

—

Adaptive Smart Tags

Yes

Abstracts or Full Texts

### Choose Your Tagging Setup ### Configure Tagging Set your tagging mode and put a Tag Hierarchy in place — build it yourself, generate it with AI, or import a template. Start here before you tag your first study.


Configure Tagging	Set your tagging mode and tag hierarchy.	Configure Tagging

### AI Tools In Tagging Core Smart Tags builds and extracts a standard hierarchy in one step; Smart Config: Tagging drafts a custom hierarchy; Adaptive Smart Tags extracts whichever tags aren't Core Smart Tags.


Core Smart Tags	Build and extract a standard hierarchy in one step.	Core Smart Tags
Smart Config: Tagging	Draft a custom hierarchy from your research question.	Smart Config: Tagging
Adaptive Smart Tags	Extract data against your custom hierarchy.	Adaptive Smart Tags

### Import Tag Hierarchy Templates Bring in a vetted structure — your organization's own template, or one of Nested Knowledge's public templates for common frameworks like PICO or EU MDR — instead of building from a blank hierarchy.


Import Tag Hierarchy Templates	Start with a vetted hierarchy template.	Import Tag Hierarchy Templates

### Apply Tags The day-to-day work of capturing data: available from Screen Records, Study Inspector, or the dedicated Applying Tags workspace, any time after a search is in your nest.


Apply Tags	Capture data from studies in your nest.	Apply Tags

### Import Applied Tags Bringing a legacy review into Nested Knowledge? Import its existing tag data instead of re-extracting it from scratch.


Import Applied Tags	Import tag data captured outside Nested Knowledge.	Import Applied Tags

### What Happens After Tags Are Applied? Tagging sorts studies to easily filter, view, edit and export later. It extracts key data from your study abstracts and/or full texts to build living interactive outputs.


Filter Records In Study Inspector	Filter records by tags.	Study Inspector
View Synthesis Outputs	Interact with living data and export what you need.	Synthesis
Qualitative Synthesis	Explore synthesis generated from tagged data.	Qualitative Synthesis
Dashboard	Build interactive views of your review data.	Dashboard Editor
Manuscript	Write and organize your review manuscript.	Manuscript Editor
Smart Insights	Generate evidence-linked insights from your data.	Smart Insights
Synthesis Chat	Ask questions about your live review data.	Synthesis Chat

All data can be exported as Excel spreadsheets and Word documents. ### Next Steps


Configure Tagging	Understand how tags are used and configure your tagging mode.	Configure Tagging
AI Tools In Tagging	Choose AI tools to build tag hierarchies and extract data from studies.	AI Tools in Tagging
Match Tags To Your Exports	Plan a tag hierarchy that matches your export columns.	Match Tags to your Exports
Apply Tags	Capture data from your included studies.	Apply Tags
Import Applied Tags	Import tag data captured outside Nested Knowledge.	Import Applied Tags
Qualitative Synthesis	View and share synthesis generated from tagged data.	Qualitative Synthesis

--- # 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/review-workflow/tagging.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.