> 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-enable-the-review-revision-stage.md).
# How to enable the Review Revision Stage
A review revision lets reviewers change a review they already posted after the review deadline has passed, for example after the rebuttal period. The revision form can include existing review fields, so reviewers can update them, and new fields, such as a `final_rating` and a `justification` for changing the rating.
Venues don't have a **Review Revision** step by default. You can create a review revision in one of two ways:
* Ask OpenReview Support by posting a comment on your [venue request form](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#venue-request-form).
* Create it yourself with the Python client, using the CustomStage. See the [Review Revision example](/how-to-guides/workflow/using-the-customstage.md#review-revision).
Once you create it, it appears in the Workflow Timeline as a **Review Revision** step, where you can change its dates (**Dates**) and its fields (**Form Fields**).
A review revision created with the CustomStage, as it appears in the Workflow Timeline.
{% hint style="info" %}
The **Rating Field Name** of the **Official Review** step must name a field of the review form itself, so a rating field that only the review revision adds cannot be selected there. To show a new rating field in the Program Chairs console, ask OpenReview Support by posting a comment on your venue request form.
{% 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-enable-the-review-revision-stage.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.
