> 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.md).

# Inclusion process

Before starting the inclusion process, it is important to define the inclusion and exclusion criteria for the documents, as well as the key information to be [collected during document review](/docs/getting-started/information-synthesis.md) (e.g., outcome measures, risk of bias assessment,...). This step is essential for establishing [annotation attributes](/docs/getting-started/inclusion-process/define-annotation-attributes.md) early on, which is one of Revstack's key features.

The [inclusion process](/docs/getting-started/inclusion-process/documents-inclusion.md) follows PRISMA recommendations and consists of two phases: an initial inclusion based on the title and abstract, followed by a final inclusion decision based on the full-text review. Justifications for full-text exclusions will be collected from all team members to facilitate disagreements management and automate the generation of the PRISMA flowchart.

The following sections will provide detailed explanations of the three key elements: defining annotation attributes, documents inclusion, and information gathering.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://revstack.gitbook.io/docs/getting-started/inclusion-process.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.