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

# Import Screening Decisions

Learn how to import screening decisions into your nest.

**Import Screening Decisions** brings existing review decisions into your nest. It matches each decision to an imported record using bibliographic details. Use it when you want to continue a previous review without screening every record again.

Before you start, import your records through a [Literature Search](/review-workflow/literature-search.md). This import matches existing records. It doesn't create new ones.

Your nest must also use Exclusion-Based Screening. Import Screening Decisions isn't available for Criteria-Based Screening.

### Prepare Your Spreadsheet

Import reads an Excel or CSV file with specific column names. Download the template from the **Import** modal. This avoids formatting mismatches.

Your sheet needs the columns shown below. Use the template's column names exactly.

| Column                      | What it needs                                                                                                                                        |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| DOI, Title, PubMed ID       | At least one of the three, to match the row to a record already in your nest.                                                                        |
| Ref ID                      | Include only if you're matching records by Ref ID.                                                                                                   |
| External ID                 | Include only if you're matching records by an external ID system.                                                                                    |
| Exclusion Reason            | Leave blank for every Advanced or Included record. For every Excluded record, enter the exact Exclusion Reason text as it's configured in your nest. |
| Full Text Review (optional) | Enter "YES" or "TRUE" for any record that underwent Full Text Review; leave blank for records screened at Abstract only.                             |

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FbLUGIdQzPzmbMl10PYeq%2Fformated%20import%20screening.png?alt=media&amp;token=b7cf5999-81f0-4da9-8521-401f75276748" alt="Import Screening Decisions spreadsheet template showing required columns"><figcaption><p>Use these column names when importing screening decisions.</p></figcaption></figure>

### Importing at the Abstract or Full Text Stage

Import always uploads final screening decisions. In Two Pass Screening, the **Full Text Review** column determines the stage.

Omit the Full Text Review column, or leave every cell blank, to import final Abstract Screening decisions. Enter `YES` or `TRUE` to import a record as a final Full Text Screening decision.

Importing final Abstract Screening decisions can train **Robot Screener** in Dual Two Pass Screening. The model learns from adjudicated abstract-stage decisions before you screen new records. See [Robot Screener](/review-workflow/screening/exclusion-based-screening/robot-screener.md).

### Import Your Decisions

{% stepper %}
{% step %}

#### Open Nest Settings

On **Nest Settings**, select **Screening → Import → Upload data**. Then select **Begin**.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FXetOUA5MvoDzqQhuSXNL%2Fimport%20screening%20decisions.png?alt=media&amp;token=0395ee67-17a4-4092-8ffb-bedebc239faf" alt="Nest Settings navigation to Screening Import upload data"><figcaption><p>Open the upload workflow from <strong>Nest Settings</strong>.</p></figcaption></figure>

The **Import** modal opens. Download the template, upload your file, and choose the two settings below.

Screening and tagging decisions require separate files. To import tagging data, see [Import Tags](/review-workflow/tagging/import-applied-tags.md).
{% endstep %}

{% step %}

#### Set Allow Exclusion Reason Creation

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FSVs4iaPabhj4OsNk9T6V%2Fimport%20screening%20modal.png?alt=media&amp;token=6451f99a-b750-47af-b9fa-e918fdffecb4" alt="Import settings with Allow Exclusion Reason Creation"><figcaption><p>Choose whether the import can create new exclusion reasons.</p></figcaption></figure>

Enable **Allow Exclusion Reason Creation** to create exclusion reasons from your sheet. Disable it to use only existing reasons. With it disabled, records with unmatched exclusion reasons fail to import. The import returns a list of those records.
{% endstep %}

{% step %}

#### Set Allow Overwrite

Enable **Allow Overwrite** to replace existing decisions on matching records. Disable it to keep existing decisions.
{% endstep %}

{% step %}

#### Import Spreadsheet

Drag your formatted file into the upload area, or select the area to choose a file.

When the import finishes, it returns unmatched rows as a spreadsheet. Assign those decisions manually, or correct the sheet and upload it again.
{% endstep %}

{% step %}

#### Review Records

Bulk imports remove affected records from their previous screening queues. Review imported decisions in [Study Inspector](/review-workflow/study-inspector.md).

In Study Inspector, add a screening filter. For example, use Abstract Screening: Advanced or Final Screening: Excluded. Review records in the table or individually.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FeaZ56um6UWz07xYWy4ve%2Fstudy%20inspector%20screening.png?alt=media&amp;token=5d7fbb25-9a0c-402d-b1c7-581e3f70a79c" alt="Study Inspector filtered to review imported screening decisions"><figcaption><p>Use <strong>Study Inspector</strong> filters to review imported decisions.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

### FAQs

<details>

<summary>Can I import screening and tagging decisions in the same file?</summary>

No. Each module requires a separate import file.

</details>

<details>

<summary>What's the minimum information a row needs to import?</summary>

Use at least one bibliographic identifier: DOI, title, or PubMed ID. Also use a blank **Exclusion Reason** for Advanced or Included records, or the exact configured reason for Excluded records.

</details>

<details>

<summary>What happens to a row that doesn't match any record in the nest?</summary>

The import returns it as a spreadsheet. Assign the decision manually, or correct the format and upload it again.

</details>

<details>

<summary>Can I use Screening Import under Criteria-Based Screening?</summary>

No. **Import Screening Decisions** is available only for **Exclusion Reason Screening**.

</details>

<details>

<summary>Will importing overwrite decisions that are already in the nest?</summary>

Only when **Allow Overwrite** is enabled. Otherwise, existing decisions remain unchanged.

</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-file-import">:file-import:</i><br><strong>Import Tags</strong></td><td>Import data captured during a previous review.</td><td><a href="/review-workflow/tagging/import-applied-tags.md">Import Applied Tags</a></td></tr><tr><td><i class="fa-tags">:tags:</i><br><strong>Tagging</strong></td><td>Configure tags and capture data from included records.</td><td><a href="/review-workflow/tagging.md">Tagging</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/import-screening-decisions.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.