> 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/workflow-tips-and-tricks/nest-templates.md).

# Nest Templates

Learn how to reuse nests as a template.

While Nested Knowledge officially supports templates for three specific parts of a nest: Exclusion Reasons, Protocol, and Tag Hierarchies, this page covers how to reuse an entire nest.

Copying a nest carries over that nest's full activity log, including the actions taken in the nest you copied from. The new nest's audit trail doesn't start clean. Weigh this before using this method for any review where a clean audit trail matters, such as a regulatory submission.

### Copy An Existing Nest To Start From

Start from a nest you've already built, rather than creating a new one from scratch.

1. Open the nest you want to reuse as a template.
2. On **Nest Settings**, scroll to the bottom, and select **Copy Nest.**

Copying a nest brings over its search configuration, tag hierarchy, and dashboard structure — the parts worth reusing — along with everything else already in it, which is why the next step is cleanup.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FIQJF7HSyM3l7lQ1guqz7%2Fimage.png?alt=media&amp;token=7f010351-076a-4675-a7e0-0e5e1fee5cb0" alt="Nest Settings showing the Copy Nest button at the bottom of the page."><figcaption><p>Select <strong>Copy Nest</strong> in <strong>Nest Settings</strong> to create a reusable copy.</p></figcaption></figure>

### Clean Up The Copied Nest

Clear out everything specific to the review the copy came from before starting your new one.

1. Remove prior searches and file imports.
2. On **Nest Settings**, scroll to the bottom, and select **Reset Ref ID** to reset Ref IDs back to 1.
3. Remove any content specific to the prior project, such as disease state or previously extracted data.

Leave the search configuration, tag hierarchy, and dashboard structure in place — they're what makes the copy worth starting from.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2F264gbxCUFQTXud4zH42Y%2Fimage.png?alt=media&amp;token=2d21777f-739d-4420-a39f-2d6c89c5fd47" alt="Nest Settings showing the Reset Ref ID button at the bottom of the page."><figcaption><p>Select <strong>Reset Ref ID</strong> to restart Ref IDs at 1.</p></figcaption></figure>

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FSGgS6lLJlzgNTichAC9t%2Fimage.png?alt=media&amp;token=572cd12e-25da-41b8-b794-9daac9940af2" alt="Confirmation dialog for resetting Ref IDs in a copied nest."><figcaption><p>Confirm the reset after removing records from the copied nest.</p></figcaption></figure>

{% hint style="success" %}
After making a copy and resetting the nest, follow the rapid review workflow below. See [how to conduct a rapid review](/get-started/ai-documentation/conduct-a-rapid-review.md).
{% endhint %}

### Run Your Search

Use [**Smart Search**](/review-workflow/literature-search/ai-tools-in-search/smart-search.md) to search PubMed and any other databases your review calls for. Confirm the search queries still match your current research question before running them. See [**Automatic Search**](/review-workflow/literature-search/add-search/automatic-search.md) for the full set of supported databases.

### Configure And Screen

Use [**Smart Config: Screening**](/review-workflow/screening/criteria-based-screening/smart-config-screening.md) to set up screening criteria for your current review. Then run [**Smart Screener**](/review-workflow/screening/criteria-based-screening/smart-screener.md) on abstracts. Use [**Full Text Import**](/review-workflow/screening/full-text-import.md), then run **Smart Screener** on full texts after uploading them. Review **Smart Screener** answers for accuracy, as you would for any review. See [**Configure Screening**](/review-workflow/screening/configure-screening.md) and [**Smart Screener**](/review-workflow/screening/criteria-based-screening/smart-screener.md).

### Apply Your Tagging Framework

The tag hierarchy carried over from the template nest already covers the core concepts and extraction fields your reviews typically use. Add any additional tags your current review needs directly to the hierarchy. See [**Configure Tagging**](/review-workflow/tagging/configure-tagging.md).

{% hint style="info" %}
No tags will have attached data, including **Core Smart Tags**. Rerun all [**AI Tools in Tagging**](/review-workflow/tagging/ai-tools-in-tagging.md).
{% endhint %}

### Review In Study Inspector

After rerunning [**Adaptive Smart Tags**](/review-workflow/tagging/ai-tools-in-tagging/adaptive-smart-tags.md), review studies in [**Study Inspector**](/review-workflow/study-inspector.md).

### Generate Your Dashboard

The [**Dashboard**](/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md) carried over from the template nest is already built. Only included studies with extracted data will display. Add newly created and extracted tags to tables. Run [**Smart Insights**](/review-workflow/synthesis/set-up-synthesis-outputs/smart-insights.md), then open the dashboard to view your results. See [**Synthesis Outputs**](/review-workflow/synthesis.md).

### Save A Clean Copy For Future Reuse

Once your review is complete, prepare a copy to serve as your next template.

1. Copy the nest again — see Copy an existing nest to start from, above.
2. Remove all data specific to this project, the same way you cleaned the original copy.
3. Keep this clean copy as your ongoing template nest for future reviews.

### FAQs

<details>

<summary>Does copying a nest bring over its data, or only its structure?</summary>

Copying brings over everything in the source nest — search results, screening decisions, tags, and all. That's why cleanup is its own step: clear out project-specific data before you start, rather than working around it later.

</details>

<details>

<summary>Can I use Nested Knowledge's official template imports on a nest built this way?</summary>

Yes. Exclusion Reasons, Protocol, and Tag Hierarchy templates import into a nest built from a copy the same way they would into any other nest.

</details>

<details>

<summary>Why isn't this an official Nested Knowledge feature?</summary>

Official template support covers Exclusion Reasons, Protocol, and Tag Hierarchies individually. Reusing a whole nest isn't a packaged template feature — it depends on the general Copy Nest capability instead, which is why the audit log carries over rather than resetting.

</details>

<details>

<summary>Will my new nest's audit log look like a fresh nest's?</summary>

No. It includes the activity recorded in the nest you copied from. Keep this in mind if a clean audit trail matters for your review.

</details>

### 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-magnifying-glass">:magnifying-glass:</i><br><strong>Search</strong></td><td>Run searches for your new review.</td><td><a href="/review-workflow/literature-search/ai-tools-in-search/smart-search.md">Smart Search</a></td></tr><tr><td><i class="fa-list-check">:list-check:</i><br><strong>Criteria-Based Screening</strong></td><td>Set up eligibility questions for your review.</td><td><a href="/review-workflow/screening/criteria-based-screening.md">Criteria-Based Screening</a></td></tr><tr><td><i class="fa-tags">:tags:</i><br><strong>Tagging</strong></td><td>Apply your copied tagging framework.</td><td><a href="/review-workflow/tagging.md">Tagging</a></td></tr><tr><td><i class="fa-table-list">:table-list:</i><br><strong>Study Inspector</strong></td><td>Review and update individual studies.</td><td><a href="/review-workflow/study-inspector.md">Study Inspector</a></td></tr><tr><td><i class="fa-table-columns">:table-columns:</i><br><strong>Dashboard Editor</strong></td><td>Update the copied Dashboard with new data.</td><td><a href="/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md">Dashboard Editor</a></td></tr><tr><td><i class="fa-chart-pie">:chart-pie:</i><br><strong>Synthesis</strong></td><td>Publish outputs that stay current with your nest.</td><td><a href="/review-workflow/synthesis.md">Synthesis</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/review-workflow/workflow-tips-and-tricks/nest-templates.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.
