> For the complete documentation index, see [llms.txt](https://revstack.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revstack.gitbook.io/docs/getting-started/inclusion-process/documents-inclusion.md).

# Documents inclusion

## Screening of documents

{% hint style="warning" %}
At this point, make sure that all [duplicates have been removed](/docs/getting-started/manage-duplicates.md).
{% endhint %}

The first phase of the inclusion process involves screening documents using their title and abstract. To screen documents:

{% stepper %}
{% step %}
Navigate to the "Documents" section of your collection.
{% endstep %}

{% step %}
Click the "Start inclusion" (ou "Resume inclusion") button.&#x20;
{% endstep %}
{% endstepper %}

Then you will be redirected to the first document to review.

<figure><img src="/files/EeJRodRhiDBmyXqObfH7" alt=""><figcaption></figcaption></figure>

To assign an inclusion decision based on the title and abstract click on "Title/Abstract inclusion" and then click "Include abstract" if the document meets the eligibility criteria or "Exclude abstract" if not. Optionally, you can provide a reason for exclusion to facilitate later disagreements management.

On the document page, several tools are available to assist you:

* **(1) Assign an inclusion decision** based on the title and abstract.&#x20;
* **(2) Manage document categories** to organize your documents effectively.
* **(3) Access fulltext providers** using the contextual link in the toolbar (see the [Manage Fulltext providers section](/docs/user-profile/fulltext-providers.md) for more details).
* **(4) View document metadata** (see the [Manage document metadata](/docs/getting-started/add-your-documents/manage-document-metadata.md) section for more details).
* **(5) Navigate between documents** within the collection.
* **(6) Translate the abstract** using DeepL (refer to the [Manage third-Party services section](/docs/user-profile/integrations.md) for more details).

## Retrieving fulltext documents

<figure><img src="/files/rPWntDBkedWl3uiAVIzU" alt=""><figcaption></figcaption></figure>

Once the initial screening is completed, the next step is to obtain the full-text version of the included documents. To do this, you can use the full-text providers toolbar (1) or use the "Auto-discovery" feature in the "PDF" tabs of the document page. If you already have the fulltext PDF you can upload it in the dropout zone (3).

{% hint style="info" %}
To make this step easier, you can customize the fulltext providers that are both displayed in the toolbar and used in the "Auto-discovery "feature. For more information, see the [Manage Fulltext providers section](/docs/user-profile/fulltext-providers.md)
{% endhint %}

## Final user inclusion decision

After reviewing the full text, a final inclusion decision must be made. To assign a final inclusion decision, click on "Fulltext Inclusion" and select either "Include Fulltext" or "Exclude Fulltext." In case of exclusion, providing a justification is mandatory to ensure transparency and reproducibility.&#x20;

{% hint style="info" %}
If the fulltext could not be retrieved and is not available in Revstack, the exclusion reason "Fulltext not found" will be the only option available.
{% endhint %}

## Disagreements managment

When multiple reviewers participate in the inclusion process, disagreements may arise.  Revstack identifies discrepancies in inclusion decisions and provides comprehensive information on reviewers' inclusion choices, comments, and reasons for exclusion to facilitate consensus.

<figure><img src="/files/GgQAjfSm9DPwPXqMCuwn" alt=""><figcaption></figcaption></figure>

Once the inclusion process is completed, navigate to the "Inclusions" section of your document collection.&#x20;

In case of disagreement, you can review each reviewer's inclusion status, access their comments and exclusion reasons (1). After discussing with team members and reaching a final inclusion resolution, you can apply it to the document (2).
