> 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/paper-matching-and-assignment/how-to-bid-on-submissions.md).
# How to Bid on Submissions
{% hint style="info" %}
This page also applies to Area Chairs and Senior Area Chairs.
{% endhint %}
When bidding opens, Reviewers will see a task labelled "Reviewers Bid" in either their Tasks page or the Reviewers Console for that particular venue.
Reviewers Bid task in the Reviewers Console.
The due date is shown in red next to the link to the task. To access the Bidding Console, click on Reviewers Bid, and the user will be redirected to the Bidding Console. Here Reviewers can read instructions on the bidding process, including the expected number of bids and tips on placing bids.
Reviewers can search for a particular paper or view papers by their bid scoring. As long as PCs computed conflicts, submissions that the reviewer has conflicts with won't appear as a submission to bid on.
Submissions listed in the Bidding Console sorted by affinity score
Reviewers can bid on a scale of Very High interest to Very Low interest, and they can modify these scores until Bidding closes.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.openreview.net/how-to-guides/paper-matching-and-assignment/how-to-bid-on-submissions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.