> 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/v1/how-to-guides/workflow/how-to-modify-the-review-meta-review-and-decision-forms.md).

# How to modify the Review, Meta Review, and Decision Forms

The review, meta review, and decision forms should be modified only through the [venue request form](/v1/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#venue-request-form). Do not edit the review, meta review, or decision invitations directly from the invitation editor, or your changes will be overwritten.

Example: In order to edit the review form, run the [Review Stage](/v1/reference/stages/review-stage.md) from the venue request form. Any additional fields can be added in valid JSON to the ‘Additional Review Form Options’ field, and any fields can be removed using the ‘Remove Review Form Options’ field. A similar process can be followed for meta-reviews and decisions using the Meta Review and Decision stages.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openreview.net/v1/how-to-guides/workflow/how-to-modify-the-review-meta-review-and-decision-forms.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 `build a script that syncs our docs to a CMS` 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.