> 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-do-multiple-phase-review.md).

# How to do multiple phase review

If the same reviewers review both rounds, we recommend this workflow:

1. Run the first round of review as usual, with the **Official Review** step.
2. Post decisions only for the submissions you are rejecting, and run the **Create Rejected Submission Release** step for them. See [How to make papers public after decisions are made](/how-to-guides/workflow/how-to-make-papers-public-after-decisions-are-made.md).
3. Run the second round of review as a review revision, created with the CustomStage. See [How to enable the Review Revision Stage](/how-to-guides/workflow/how-to-enable-the-review-revision-stage.md).
4. Post remaining decisions and run the **Create Rejected Submission Release** and **Create Accepted Submission Release**

For other setups, contact OpenReview Support by adding a comment to your [venue request form](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#venue-request-form).


---

# 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-do-multiple-phase-review.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.