> 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-have-different-tracks-or-types-of-submissions-for-a-single-venue.md).

# How to support different tracks for a venue

OpenReview does support a limited functionality for "tracks". If your workflow requires different deadlines and different review forms for each track, then please fill out a separate venue request for each track.

What we currently support:

* Create reviewer, area chair, and senior area chair group roles for each track. Please limit the group roles to a maximum of 10 tracks.
* Assign reviewers and ACs in these independent pools to the submissions with their track selected.
* ACs can modify reviewer assignments after the PCs have initiated the assignments.
* All tracks follow the same workflow, including deadlines and forms.
* Currently, PCs are responsible for recruiting to all track roles, as well as the paper matching setup to compute conflicts and affinity scores and create matching configuration.

If the needs for your venue are not addressed here regarding tracks, please [Contact Support](https://openreview.net/contact). We can try to accommodate custom requests, however, we need to know at least one month before submissions open.

If you want to accept distinct types of submissions that will all follow the same workflow, you can [add a ‘track’ field to your submission form](/getting-started/hosting-a-venue-on-openreview/customizing-your-submission-form.md). If you reach out to [OpenReview support](https://openreview.net/contact), we can then customize your PC console to allow you to filter and sort by track or add roles for reviewers and ACs if you need a group per track.


---

# 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/workflow/how-to-have-different-tracks-or-types-of-submissions-for-a-single-venue.md?ask=<question>&goal=<endgoal>
```

`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.