> 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/exclusion-based-screening.md). # Exclusion-Based Screening Learn how to set up exclusion reasons for your screening. **Exclusion-Based Screening** records a screening decision as the specific reason a record isn't eligible. Reviewers either advance/include a record or exclude it under one configured reason. Use this paradigm when your review needs PRISMA exclusion counts by reason. It is also the only paradigm that supports **Robot Screener**, which learns from your team’s adjudicated decisions. **Exclusion Reasons** works in all Screening modes. If your protocol uses Yes/No eligibility questions, or you want AI to draft and answer those questions, use [**Criteria-Based Screening**](/review-workflow/screening/criteria-based-screening.md). See [**Configure Screening**](/review-workflow/screening/configure-screening.md) to compare the paradigms. ### Set Up Exclusion Reasons On Configure Screening , create one set of exclusion reasons for both Abstract Screening and Full Text Screening. ### Option 1: Add Reasons Manually 1. Select **Add**. 2. Enter an exclusion reason. 3. Repeat for each reason in your protocol. ### Option 2: Import A Template 1. Select **Import**. 2. Select your organization or **Public Templates**. 3. Select the template name. 4. Select **Import**. To create a reusable template, see [**Create organizational templates**](/account-management/organization-management/organization-settings/organizational-templates.md). Use the pencil icon to edit a reason. Drag its six-dot handle to reorder it. Use the trash icon to remove it. Indent a reason beneath another to create a hierarchy for your PRISMA diagram. Deleting a reason removes it permanently, including from every record where you applied it. If a reason is in use, edit its wording instead.

Configured exclusion reasons in Configure Screening, including options to add, edit, reorder, and nest reasons. — Configure exclusion reasons and their hierarchy in **Configure Screening**.

### Add AI Assistance The screening model learns from your team's adjudicated decisions. It assigns inclusion probabilities or powers Robot Screener, depending on your reviewer structure. In Single Screening, [**Screening Model**](/review-workflow/screening/exclusion-based-screening/screening-model.md) assigns each record an inclusion probability. Sort or filter your queue by this score to prioritize records. You still make and record every decision. In Dual Screening, the model powers [**Robot Screener**](/review-workflow/screening/exclusion-based-screening/robot-screener.md) after 50 adjudicated decisions, including 10 advancements. Robot Screener fills one reviewer seat. A second human reviewer and a human adjudicator remain required.

PRISMA Settings

Under **PRISMA Settings**, set **Display Depth** to control which level of your indented reason hierarchy appears in the PRISMA diagram. You can also assign an exclusion reason to categorize records as “Reports not retrieved” in the generated PRISMA diagram.

Keywords

Configure keywords to highlight them in record abstracts and full texts. Change the adjacent color to update the highlight. You can also open this setting from **Your Keywords** in any abstract view.

### FAQs

Can I nest exclusion reasons more than one level deep?

Yes. You can use up to 10 levels of indentation.

What happens to a record's history if I delete an exclusion reason it was assigned?

The reason is removed from that record and every other record where you applied it. Deletion is permanent, so edit the reason if it is still in use.

Can I add new exclusion reasons after screening has already started?

Yes. Return to **Configure Screening** to add reasons. To apply a new reason to the current record, open **Screening**, enter it in **Search Reasons**, then select **Add and Apply**.

### Next Steps


Screening Model	Prioritize records by their inclusion probability.	Screening Model
Robot Screener	Fill one Dual Screening reviewer seat.	Robot Screener
Screen Records	Review records against your exclusion reasons.	Screen Records

--- # 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/exclusion-based-screening.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.