> 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/getting-started/frequently-asked-questions/how-do-i-complete-my-tasks.md).

# How do I complete my tasks?

Throughout the course of a conference/workshop, members of the committee groups are assigned tasks to complete, such as, Expertise Selection, Reviewing, and the Reviewer License Agreement. Users can find their tasks by clicking on the Tasks button (openreview\.net/tasks) on the red nav bar at the top of the page. They can also find these tasks in their respective venue consoles.

<figure><img src="/files/OdzF74U4bKexsMUVvDRW" alt="" width="375"><figcaption><p>Tasks button</p></figcaption></figure>

They'll see a list of different venue IDs and the number of pending and completed tasks.

<figure><img src="/files/ywni1arAhfK8GWybO8cY" alt="" width="375"><figcaption><p>Tasks page</p></figcaption></figure>

<figure><img src="/files/QsrbuhLa2uZbJtrKRDhR" alt="" width="375"><figcaption><p>Reviewer console listing tasks</p></figcaption></figure>

To view the tasks, click on the arrow next to the venue ID or "Show pending tasks and completed tasks". Clicking on a task link will redirect the user to another page to complete the task. When the task is completed it will be grayed out on the Tasks page. When the expiration date for that task expires the task will disappear from the Tasks page.

Note: Some tasks, such as Expertise Selection, will continue to show as pending until the task expires, at which time it will be removed from the queue.

See also: [I am a reviewer and I don't have papers for Expertise Selection, what do I do?](/getting-started/frequently-asked-questions/i-am-a-reviewer-and-i-dont-have-papers-for-expertise-selection-what-do-i-do.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 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/getting-started/frequently-asked-questions/how-do-i-complete-my-tasks.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.
