> 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/submissions-comments-reviews-and-decisions/how-to-upload-paper-decisions-in-bulk.md).

# How to upload paper decisions in bulk

Program Chairs can post decisions one at a time on each submission, or upload them all at once with the **Create Decision Upload** step in the [Workflow Timeline](/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#workflow-timeline).

The upload posts through each submission's decision form, so the **Decision** step must already be open.

1. Create a CSV file with one decision per line: the paper number, the decision, and an optional comment. Don't add a header row. Each decision must be one of your **Decision Options**.

   ```
   1,Accept,Clear contribution.
   2,Reject,
   3,Accept,
   ```
2. In the Workflow Timeline, expand **Create Decision Upload**, click **Edit** next to **Decision CSV**, upload the file and click **Submit**.
3. Click **Edit** next to **Dates** and set the **Activation Date** to when the decisions should be posted. If that date has already passed, the upload runs shortly after you submit the file.

{% hint style="info" %}
Uploading a file again replaces the decisions of the papers in it. Rows that can't be posted, for example an unknown paper number, are skipped and listed only in the step's **logs**.
{% endhint %}

{% hint style="warning" %}
If the activation date arrives before a file is uploaded, no decisions are posted and a "Decision Upload Failed" comment is posted 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/submissions-comments-reviews-and-decisions/how-to-upload-paper-decisions-in-bulk.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 `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.