> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hud.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Task lifecycle and review

> Take tasks from authoring to verified: statuses, review decisions, custom review stages, Ready requirements, and the review queue.

Every task carries a review status. Authors work on a task and mark it ready; reviewers verify it,
ask for a revision, or reject it. A taskset can add its own stages before Ready, such as an expert
check, and each project collects the tasks waiting for review in one queue.

```mermaid theme={"dark"}
flowchart LR
    C["Created"] --> S["Your stages"] --> R["Ready"]
    R --> V["Verified"]
    R --> X["Revision"]
    R --> J["Rejected"]
    X -->|"resubmit"| R
```

## Statuses

| Status | Meaning |
| - | - |
| **Pending** | Being authored. In place of Pending, the task shows its current stage: **Created**, or one of the [stages](#add-review-stages) the taskset adds. |
| **Ready** | The author marked it complete. It waits in the [review queue](#the-review-queue). |
| **Verified** | A reviewer approved it. |
| **Revision** | A reviewer asked for changes. |
| **Rejected** | A reviewer decided not to use it. |

The status belongs to the task's latest version. Saving a new version keeps the status, including
**Verified**, so set the status again when an edit needs another review. A task in a custom
[review stage](#add-review-stages) is the exception: its new version goes back to **Created**.

Older tasks can show **Draft**: an idea brief without a template, from an earlier workflow. Drafts
are read-only.

## Change a status

Open the task's **Status** menu. It shows where the task is in the lifecycle and the actions you can
take from there.

| Action | From | Needs |
| - | - | - |
| **Mark ready** | Pending, at the last stage | Create |
| **Unmark ready** | Ready | Create |
| **Verify**, **Request revision**, **Reject** | Pending or Ready | Review |
| **Mark ready**, to resubmit | Revision | Create |
| **Return to ready** | Verified or Rejected | Review |
| **Clear status**, back to Pending | Verified, Revision, or Rejected | Review |

**Create** and **Review** are [taskset scopes](/platform/tasksets#share-a-taskset). The same scopes,
or **Manage**, on the taskset's [project](/platform/projects) also count, and team admins can review
in every project. In the Main project every team member has Create, so members can mark tasks ready
but need Review to decide on them.

To change many tasks at once, select them in the taskset grid and use **Set status** in the
selection bar. The [REST API](/platform/rest-api#authoring-and-review-state) changes statuses and
stages in bulk.

### Ready requirements

A taskset can have Ready requirements: checks a task should pass before it is marked ready. They
can require a minimum number of eligible traces (completed, without errors, with a submitted answer,
and without hitting the step limit), traces from a specific model or checkpoint, an average reward
or token usage within a range, and QA results.

While a task is Pending or in Revision, its **Overview** lists each requirement, whether it passes,
and how to fix it. **Mark ready** warns when a requirement fails, and **Mark Ready anyway**
overrides it. To set up Ready requirements for a taskset, [contact HUD](mailto:founders@hud.ai).

## Add review stages

Stages split Pending into the steps your process needs, such as **Draft written**, **Expert
check**, and **Solution verified**. Add them in the taskset's **Settings** → **Lifecycle stages**:
select **Add stage** and name it. **Created**, where new tasks start, comes first; **Ready** and
**Verified** always come last.

* Tasks move forward one stage at a time, and can be sent back to any earlier stage, including
  Created. The task's **Status** menu offers the next stage and **Previous stage**.
* A task must reach the last stage before it can be marked ready. **Unmark ready** returns it to
  the last stage.
* Removing a stage moves the tasks at that stage back to Created.

Anyone who can edit the taskset can change its stages and move tasks between them.

In the task grid, each row shows the task's progress as dots, one per stage plus Ready and
Verified. Revision shows amber and Rejected red. Hover the dots to see the full lifecycle.

## Owners, reviewers, and comments

Each task page shows:

* **Owner.** The team member responsible for the task. Creating or uploading a task makes you its
  owner; anyone who can edit the task can reassign it.
* **Reviewers.** The people who can review tasks in the taskset.
* **Activity.** Comments and replies, in Markdown, alongside the task's status changes.

## The review queue

Reviewers work from the **Review** tab of **Project Overview** in the sidebar, which appears when
you have Review or Manage on the current project. It lists every Ready task in the project's
tasksets that you can review, longest waiting first. Filter by taskset to focus on one.

Each entry shows the task's version, author, taskset, and how long it has waited, and a badge such
as **Verified at v2** when an earlier version was verified. **Review changes** shows which template
arguments changed since the previous version. Open the task to run it, read its [QA results](/platform/qa-results),
and decide.

With Manage, the same tab also tracks each contributor's work. See
[Project Overview](/platform/projects#project-overview).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.