> 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-use-the-camera-ready-revision-step-for-accepted-papers.md).
# How to use the Camera Ready Revision step for accepted papers
Venues created with the Conference Review Workflow include a **Camera Ready Revision** step by default. When it activates, OpenReview creates a camera-ready revision form for each submission with an accepted decision, and only that submission's authors can use it.
To make changes to the default settings:
1. Go to your venue's [Workflow Timeline](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#workflow-timeline) and find the **Camera Ready Revision** step.
2. Make sure the decision options that mean acceptance are set correctly. In the **Decision** step, click **Edit** next to **Decision Options** and check the **Accept Decision Options**. The default decision options are "Accept" and "Reject", and "Accept" is the only accept option. A submission is treated as accepted only if its decision is one of the accept options.
3. In the **Camera Ready Revision** step, click **Edit** next to **Dates** and set the dates:
* **Activation Date**: when the revision form opens to authors of accepted papers.
* **Due Date**: when camera-ready revisions are due.
* **Expiration Date**: when the revision form closes.
4. Click **Submit**.
5. (Optional) To change the fields on the camera-ready form, click **Edit** next to **Form Fields**. By default, the form contains the fields from the default submission form, without the `email_sharing` and `data_release` fields. See [Customizing Forms](/getting-started/customizing-forms.md) for how to edit form fields.
The Camera Ready Revision step, as Program Chairs see it.
{% hint style="info" %}
Post the decisions in the **Decision** step before the camera-ready **Activation Date**. The camera-ready form is created per submission, only for submissions that already have an accepted decision when the step runs. The step runs on the **Activation Date** and again each time you edit it, so if a decision is posted or changed later, click **Edit** next to **Dates** and submit the form again.
{% endhint %}
When an author submits a camera-ready revision, the changes are applied directly to the submission, so the submission always shows the latest version. To retrieve camera-ready submissions programmatically, see [How to get all notes for submissions, reviews, rebuttals, etc.](/how-to-guides/data-retrieval-and-modification/how-to-get-all-notes-for-submissions-reviews-rebuttals-etc.md)
---
# 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-use-the-camera-ready-revision-step-for-accepted-papers.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.
