> 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-rebuttal-period.md).
# How to Enable the Rebuttal Period
Venues created with the Conference Review Workflow include an **Author Rebuttal** step in the [Workflow Timeline](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#workflow-timeline). Authors can post one rebuttal per submission, as a reply to the submission. By default, the rebuttal form opens 5.5 weeks after the submission deadline (the full submission deadline, if your venue has one) and is due 6.5 weeks after it.
Before the rebuttal period starts, make sure authors have [access to the reviews](/how-to-guides/workflow/how-to-release-reviews-decisions-and-metareviews.md). By default, the **Official Review Release** step releases reviews to the authors 5 weeks after the submission deadline.
## Set the rebuttal dates
1. From the Workflow Timeline, click **Author Rebuttal** to expand the step.
2. Next to **Dates**, click **Edit**.
3. Set the **Activation Date** (when authors can start posting rebuttals), the **Due Date** (the deadline shown to authors), and the **Expiration Date** (when the rebuttal form is no longer available).
4. Click **Submit**.
The Dates editor of the Author Rebuttal step, as Program Chairs see it.
## Other rebuttal settings
The **Author Rebuttal** step has these other controls, each with an **Edit** link:
* **Readers** – who can read the rebuttals. By default, the Program Chairs, the assigned Senior Area Chairs, Area Chairs, and reviewers, and the submission's authors.
* **Notifications** – who is emailed when a rebuttal is posted. By default, the assigned reviewers and the submission's authors. An email is only sent to a selected user if they are also a reader of the rebuttal.
* **Form Fields** – the fields of the rebuttal form. See [How to modify the Review, Meta Review, and Decision Forms](/how-to-guides/workflow/how-to-modify-the-review-meta-review-and-decision-forms.md) for how the form editor works.
{% hint style="info" %}
If you do not want a rebuttal period, click **Disable** next to the **Author Rebuttal** step before its activation date. A disabled step does not create the rebuttal forms, and you can turn it back on with **Enable**.
{% 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-rebuttal-period.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.
