> 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/reference/default-forms/default-review-form.md).
# Default Review Form
```json
{
"title": {
"order": 1,
"description": "Brief summary of your review.",
"value": {
"param": {
"type": "string",
"regex": ".{0,500}"
}
}
},
"review": {
"order": 2,
"description": "Please provide an evaluation of the quality, clarity, originality and significance of this work, including a list of its pros and cons (max 200000 characters). Add formatting using Markdown and formulas using LaTeX. For more information see https://openreview.net/faq",
"value": {
"param": {
"type": "string",
"maxLength": 200000,
"markdown": true,
"input": "textarea"
}
}
},
"rating": {
"order": 3,
"value": {
"param": {
"type": "integer",
"enum": [
{
"value": 10,
"description": "10: Top 5% of accepted papers, seminal paper"
},
{
"value": 9,
"description": "9: Top 15% of accepted papers, strong accept"
},
{
"value": 8,
"description": "8: Top 50% of accepted papers, clear accept"
},
{
"value": 7,
"description": "7: Good paper, accept"
},
{
"value": 6,
"description": "6: Marginally above acceptance threshold"
},
{
"value": 5,
"description": "5: Marginally below acceptance threshold"
},
{
"value": 4,
"description": "4: Ok but not good enough - rejection"
},
{
"value": 3,
"description": "3: Clear rejection"
},
{
"value": 2,
"description": "2: Strong rejection"
},
{
"value": 1,
"description": "1: Trivial or wrong"
}
],
"input": "radio"
}
}
},
"confidence": {
"order": 4,
"value": {
"param": {
"type": "integer",
"enum": [
{
"value": 5,
"description": "5: The reviewer is absolutely certain that the evaluation is correct and very familiar with the relevant literature"
},
{
"value": 4,
"description": "4: The reviewer is confident but not absolutely certain that the evaluation is correct"
},
{
"value": 3,
"description": "3: The reviewer is fairly confident that the evaluation is correct"
},
{
"value": 2,
"description": "2: The reviewer is willing to defend the evaluation, but it is quite likely that the reviewer did not understand central parts of the paper"
},
{
"value": 1,
"description": "1: The reviewer's evaluation is an educated guess"
}
],
"input": "radio"
}
}
}
}
```
#### Preview
The default review form as a reviewer sees it.
---
# 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/reference/default-forms/default-review-form.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 `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.
