> 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/submissions-comments-reviews-and-decisions/how-to-upload-paper-decisions-in-bulk.md).
# How to upload paper decisions in bulk
There are two possible ways to post decisions to papers:
1. Manually, using individual Decision buttons on each paper
2. In bulk, using the Decision Stage.
The first option will be automatically enabled after the [Decision Stage](/v1/reference/stages/decision-stage.md) is run.
To upload decisions in bulk, you can do the following:
1. Create your decisions csv. The csv should contain the paper\_number, decision, and comment for each paper, with one paper per line. It should not include column names. The comment field is optional, so you can leave that column empty if you wish. Your csv should look something like the following:
2.
```
Example of decision csv file
```
or like this:
```
1,Accept,A decision comment
2,Reject,
3,Accept,A decision comment
```
1. From your [venue request form](/v1/getting-started/hosting-a-venue-on-openreview/navigating-your-venue-pages.md#venue-request-form), click the Decision Stage button. Upload your decisions csv for the "Decisions File" field.
2. Click submit.
If you had already manually posted decisions, the bulk upload will overwrite them.
---
# 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/submissions-comments-reviews-and-decisions/how-to-upload-paper-decisions-in-bulk.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.
