> 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/screening/configure-screening.md).

# Configure Screening

Learn how to configure screening for your nest.

Configure screening before reviewing your first record. Your setup determines the reviewer structure, pass structure, and screening paradigm.

Changing these settings after screening begins converts existing decisions to final screening decisions. Use [Bulk Actions](/review-workflow/study-inspector/bulk-actions.md) to reverse them in the new mode.

### Choose Your Screening Mode

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2F0cYzO8NjvyHTSYSuAW9p%2Fscreening%20modes%20flowchart.png?alt=media&amp;token=3030ba9e-130b-4bc6-9d81-56d51a3bff6e" alt="Decision tree for selecting a reviewer structure and pass structure: Single or Dual Screening, and Standard or Two Pass Screening."><figcaption><p>Choose a reviewer structure and pass structure before configuring Screening.</p></figcaption></figure>

Screening mode has two independent settings. Set both in Nest Settings before screening begins.

Reviewer structure determines how many reviewer seats assess each record.

* **Single Screening** uses one reviewer seat.
* **Dual Screening** uses two reviewer seats and human adjudication for disagreements.

Pass structure determines the number of screening rounds.

* **Standard Screening** uses one round for title, abstract, and, when applicable, full text.
* **Two Pass Screening** separates Abstract Screening from Full Text Screening.

Any pass structure can use either reviewer structure. See [**Screen Records**](/review-workflow/screening/screen-records.md) for each workflow.

### Choose Your Screening Paradigm

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FfSixDT0cZHkOGl4DMnkQ%2Fscreening%20decision%20tree.png?alt=media&amp;token=78a7e192-a589-47ff-b17e-2e608683d85b" alt="Screening workflow showing records moving through configuration, screening decisions, and review."><figcaption><p>Choose Criteria-Based Screening or Exclusion Reasons for your review.</p></figcaption></figure>

A screening paradigm determines how reviewers record each decision. Choose the paradigm that supports your review's reporting and workflow.

**Criteria-Based Screening** records a decision through Yes/No eligibility questions. Every Yes advances the record. Any No excludes it. Configure separate question sets for Abstract Screening and Full Text Screening. [Set up **Criteria-Based Screening**](/review-workflow/screening/criteria-based-screening.md) manually or with **Smart Config**.

**Exclusion Reasons** records the specific reason a record doesn't belong. Reviewers advance a record or exclude it under one configured reason. [Set up **Exclusion Reason Screening**](/review-workflow/screening/exclusion-based-screening.md) to create, order, and nest reasons.

| If you want to…                                            | Choose                                                        |
| ---------------------------------------------------------- | ------------------------------------------------------------- |
| Screen against Yes/No eligibility questions                | Criteria-Based Screening                                      |
| Draft and answer criteria with AI                          | Criteria-Based Screening with Smart Config and Smart Screener |
| Report exclusion counts by reason in a PRISMA flow diagram | Exclusion Reasons                                             |
| Use Robot Screener                                         | Exclusion Reasons                                             |
| Import existing screening decisions                        | Exclusion Reasons                                             |

### Add AI Tools

AI tools are optional. Each tool supports one screening paradigm.

Under **Exclusion Reasons**, the [**Screening Model**](/review-workflow/screening/exclusion-based-screening/screening-model.md) assigns inclusion probabilities in Single Screening. [**Robot Screener** ](/review-workflow/screening/exclusion-based-screening/robot-screener.md)can fill one reviewer seat in Dual Screening after your nest has 50 adjudicated decisions, including 10 advancements.

Under **Criteria-Based Screening**, [**Smart Screener**](/review-workflow/screening/criteria-based-screening/smart-screener.md) answers criteria in Single Screening or fills one reviewer seat in Dual Screening. An automated reviewer still requires a human co-reviewer and a human adjudicator. Neither tool makes a final decision on its own.

### Optional: Apply Tags In Screening

Tags in Nested Knowledge can be created and applied any time after records are in a nest, including during Screening. Use [Core Smart Tags](/review-workflow/tagging/ai-tools-in-tagging/core-smart-tags.md) to extract PICOs, Study Type, Location and Size from study abstracts to view alongside screening or [create tags](/review-workflow/tagging/configure-tagging.md) manually to sort studies as you screen. See the below decision tree for more.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FaoiC1gQeZY6ZbTjGEOwR%2Fapply%20tags%20screening%20decision%20tree.png?alt=media&amp;token=7e5820a4-0d3a-4937-951b-68256ea8e0d0" alt="Decision tree for applying tags during Screening."><figcaption><p>Use this decision tree to choose when to apply tags during Screening.</p></figcaption></figure>

### FAQs

<details>

<summary>Can I change my screening mode after I've started screening?</summary>

If screening began under a Single mode (Standard or Two Pass) and you now need a second reviewer seat, use **Convert Screening Decisions** under Bulk Actions to carry existing decisions into the equivalent Dual mode, rather than re-screening from scratch.

</details>

<details>

<summary>Can I switch paradigms partway through a review?</summary>

When you switch between **Exclusion Reasons** and **Criteria-Based Screening**, your existing reasons or criteria transform into the other format. The change doesn't remove your existing criteria. They remain available if you switch back.

Changing screening modes can affect your workflow, audit records, and ability to reproduce the review.

</details>

<details>

<summary>Can I run Robot Screener and Smart Screener in the same nest?</summary>

No. **Robot Screener** is available only with **Exclusion Reasons**. **Smart Screener** is available only with **Criteria-Based Screening**. A nest uses one paradigm at a time.

</details>

<details>

<summary>Do I have to use one of Nested Knowledge's AI tools?</summary>

No. AI tools are optional. You can screen records manually in [**Screen Records**](/review-workflow/screening/screen-records.md).

</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-list-check">:list-check:</i><br><strong>Criteria-Based Screening</strong></td><td>Configure eligibility questions for screening.</td><td><a href="/review-workflow/screening/criteria-based-screening.md">Criteria-Based Screening</a></td></tr><tr><td><i class="fa-list">:list:</i><br><strong>Exclusion Reason Screening</strong></td><td>Configure reasons for excluding records.</td><td><a href="/review-workflow/screening/exclusion-based-screening.md">Exclusion-Based Screening</a></td></tr><tr><td><i class="fa-file-import">:file-import:</i><br><strong>Import Screening Decisions</strong></td><td>Import decisions from another tool.</td><td><a href="/review-workflow/screening/import-screening-decisions.md">Import Screening Decisions</a></td></tr><tr><td><i class="fa-file-lines">:file-lines:</i><br><strong>Screen Records</strong></td><td>Review records and make screening decisions.</td><td><a href="/review-workflow/screening/screen-records.md">Screen Records</a></td></tr><tr><td><i class="fa-file-import">:file-import:</i><br><strong>Full Text Import</strong></td><td>Import PDFs before Full Text Screening.</td><td><a href="/review-workflow/screening/full-text-import.md">Full Text Import</a></td></tr><tr><td><i class="fa-scale-balanced">:scale-balanced:</i><br><strong>Adjudicate Records</strong></td><td>Resolve disagreements in Dual Screening.</td><td><a href="/review-workflow/screening/adjudicate-records.md">Adjudicate Records</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/screening/configure-screening.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.
