> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/how-to-guides/workflow/how-to-release-reviews-decisions-and-metareviews.md).
# How to release reviews, decisions, and metareviews
The **Official Review Release** step in your venue's [Workflow Timeline](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#workflow-timeline) runs automatically on its **Activation Date**. It changes the readers of all official reviews at once. When your venue is created, the step's Activation Date is the same as the Official Review due date, and the readers are:
* Program Chairs
* Assigned Senior Area Chairs, if your venue has Senior Area Chairs
* Assigned Area Chairs, if your venue has Area Chairs
* Assigned Reviewers
* Submission Authors
With these defaults, authors can read the reviews of their submission from the Activation Date.
{% hint style="info" %}
Meta reviews and decisions are released the same way, with the **Meta Review Release** and **Decision Release** steps. The **Meta Review Release** step exists only if your venue has Area Chairs.
{% endhint %}
To change who can read the reviews or when:
1. Go to the Workflow Timeline and find the **Official Review Release** step.
2. Click **Edit** next to **Readers** and select who should be able to read the reviews. Depending on your venue's roles, the options are Program Chairs, All Senior Area Chairs, Assigned Senior Area Chairs, All Area Chairs, Assigned Area Chairs, All Reviewers, Assigned Reviewers, Assigned Reviewers who already submitted their review, Reviewer who submitted the review, Submission Authors, and Public.
3. Click **Submit**.
4. Click **Edit** next to **Dates** and set the **Activation Date** to when the reviews should be released.
5. Click **Submit**.
The Readers editor of the Official Review Release step, as Program Chairs see it.
## Common errors
**`The "everyone" reader option cannot be included with other reader options.`**
**Public** makes the reviews readable by anyone, so it can't be combined with other readers. Select **Public** on its own.
**`If "everyone" is not selected as reader, the Program Chairs must be included as readers.`**
Unless you select **Public**, the readers must include **Program Chairs**. Add **Program Chairs** to your selection.
{% hint style="info" %}
After the Activation Date has passed, the step runs again each time you edit it. To change the readers of reviews that have already been released, edit **Readers** again.
{% endhint %}
{% hint style="info" %}
Authors are emailed that their reviews are available by a separate step, **Create Author Reviews Notification**, which runs on its own Activation Date. If you change the release date, check that step's date too.
{% endhint %}
{% hint style="warning" %}
If you select **Public**, reviews are only released on submissions that are already public. On private submissions, the readers of the reviews don't change, so authors don't get them either. Make the submissions public first, or don't select **Public**.
{% endhint %}
---
# 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.openreview.net/how-to-guides/workflow/how-to-release-reviews-decisions-and-metareviews.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.
