> 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/nest-setup.md). # Nest Setup Learn how to set up your review in Nested Knowledge and what route to take. Set up your nest before you add records. Your early choices determine the workflow, review roles, and modules available later. This page helps you choose a review route, record your protocol, and prepare each module. For account setup, see [Quickstart](/get-started/quickstart.md). ### The Shape of Every Nest Work happens in two places. In **AutoLit**, you build the review. In **Synthesis**, your review becomes outputs such as PRISMA diagrams, data extraction tables, analyses, dashboards, and manuscripts. See [Core concepts](/get-started/core-concepts.md) for an overview. AI-assisted tools support several stages. Human review remains essential for review decisions. **Study Inspector** provides a number of filters to find, view, and edit each record.

Diagram showing AutoLit as the review-building environment and Synthesis as the environment for review outputs. — **AutoLit** supports the review workflow, while **Synthesis** turns the review into outputs.

### Create Your First Nest 1. Navigate to the [**Nests**](/your-nests/nests.md) page. 2. Select **Create New Nest** and give it a name. 3. Select **Create**. 4. Your nest opens on the **Literature Search** page because this is the first review step. {% hint style="info" %} All users regardless of pilot or subscription status may create their first nest for free with limited access to AI features. Creating a demo nest counts as an individual nest. {% endhint %} ### Choose Your Review Route Nested Knowledge supports [several review types](/guides/guidance-by-review-type/systematic-literature-review.md). The type you're doing determines how you set the nest up. Start from what you're trying to produce, then use the setup that fits. Skip straight to conducting a rapid review

If you want to…	Review route	Best Practices
Answer a focused question with full rigor, for publication or guidelines	Systematic literature review (SLR)	Link
…and pool the numbers statistically, including across a treatment network	Meta-analysis / NMA	Link
Support a health-technology submission (clinical, epidemiological, or economic)	HTA submission	Link
Reach a defensible answer quickly for a time-sensitive decision	Targeted / rapid review	Link
Map how much and what kind of evidence exists on a broad topic	Scoping review	Link
Describe and interpret the literature in narrative prose	Narrative review	Link
Pinpoint where evidence is missing	Gap analysis	Link

### Add Your Protocol Capture your plan before you add records. In **Nest Home**, find **Protocol** and select **Edit** to open the Protocol Editor. Add your research question, eligibility criteria, and methods. The protocol stays beside your review work and remains visible to collaborators. ### Next Steps


Core Concepts	Learn the objects and terminology used in Nested Knowledge.	Core Concepts
Literature Search	Find, import, and organize literature for your review.	Literature Search
Build With AI	Use AI-assisted tools to build your nest.	Build With AI
Conduct A Rapid Review	Follow an AI-assisted workflow for a focused review.	Conduct A Rapid Review
Migrate To NK	Import records, screening decisions, and tags from another platform.	Migrate To NK

--- # 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/nest-setup.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.