> For the complete documentation index, see [llms.txt](https://docs.labatlas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labatlas.com/using-lab-atlas/tasks.md).

# Tasks

Tracking and delegating work across projects, studies, and assays

Tasks are Lab Atlas's to-do list. They let you break work into steps, hand a step to a colleague, set a deadline, and — where it matters — capture data at the moment the work is signed off.

A task always belongs to a **project**, a **study**, or an **assay**. That parent decides who can see the task, since a task inherits the visibility of the record it hangs from.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FdDPCBDIcSosZE5VmlApU%2Fimage.png?alt=media&amp;token=25b0158f-f35c-4740-a5c8-560e32c83ddb" alt="" width="563"><figcaption><p>The tasks page</p></figcaption></figure>

## The Tasks page

Click **Tasks** in the sidebar to see every task you have access to in one place, rather than hunting through records one at a time.

Three tabs narrow the list:

* **All tasks** — everything you can see.
* **My tasks** — tasks assigned to you.
* **Created by me** — tasks you raised, whoever is doing them.

Two filters narrow it further: by **status**, and by **source** (project, study, or assay).

Tasks are grouped by deadline rather than by parent record, so the list reads as a schedule: **Overdue** first, then **Due today**, **Tomorrow**, **This week**, **Later**, and **No due date**. Closed tasks collapse into a **Closed** group at the bottom, out of the way but still there when you need them.

## Statuses

A task moves through four statuses.

| Status          | Meaning                                                                                           |
| --------------- | ------------------------------------------------------------------------------------------------- |
| **Open**        | Raised, not started.                                                                              |
| **In progress** | Someone has picked it up. Useful on long-running work so the rest of the team can see it moved.   |
| **Done**        | Finished.                                                                                         |
| **Incomplete**  | Closed without being finished — the work was abandoned, superseded, or turned out to be unneeded. |

**Incomplete** matters more than it looks. Deleting a task that was never done erases the fact that it was ever planned; marking it incomplete keeps the record honest, which is the point of an audit trail.

Open and In progress are *active* and appear in the due-date groups. Done and Incomplete are *closed* and collapse into the Closed group.

{% hint style="info" %}
The REST API and MCP server use the underlying values `TODO`, `IN_PROGRESS`, `COMPLETE`, and `INCOMPLETE`. The web interface shows `TODO` as "Open" and `COMPLETE` as "Done".
{% endhint %}

## Creating a task

Click **New task** on the Tasks page, or add one from the Tasks tab of any project, study, or assay. Tasks can also be created inline while filling in the New Study or New Assay form, or added to the tree on the [Planning](https://docs.labatlas.com/using-lab-atlas/planning.md) page with **+ Task**.

You will be asked for:

* **Title** — what needs doing.
* **Description** — optional detail, protocol steps, or links.
* **Attach to** — the project, study, or assay the task belongs to. Prefilled when you create the task from a record.
* **Assignee** — optional. Leave it unassigned if anyone can pick it up.
* **Due date** — optional. Tasks with a due date are flagged as overdue once it passes.

Assigning a task notifies that person and puts it in their **My tasks** list. It doesn't reserve the task: anyone with access to the parent record can still complete it.

Under **Required to complete**, click **Add field** to give the task [Results fields](#tasks-that-capture-data).

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FZoHycKYZcVGKT5AvOuYy%2Fimage.png?alt=media&amp;token=2451fd9c-b326-4607-a140-acda1ec20994" alt="" width="563"><figcaption><p>Creating a new task</p></figcaption></figure>

## Tasks that capture data

A task can have **Results fields**: values the assignee records when they finish. This turns a checklist item into a small record-keeping step, such as a reading to note, a batch number, or a confirmation that a control passed. It makes sure the information is captured when the work actually happened, rather than reconstructed later.

### Field types

| Type          | Use it for                      |
| ------------- | ------------------------------- |
| **Text**      | Short free text                 |
| **Paragraph** | Long-form notes or observations |
| **Integer**   | Whole numbers, such as counts   |
| **Decimal**   | Measured values with decimals   |
| **Yes / No**  | A single yes-or-no answer       |
| **Choice**    | Picking from a set list         |
| **Date**      | A calendar date                 |
| **File**      | An uploaded attachment          |

Each field can be required or optional, and can have helper text and a default value. A **Choice** field needs at least two different options, and its default value must be one of them.

### Adding Results fields

You can add Results fields in several places:

* On the **New Study** and **New Assay** forms: expand a task in the **Tasks** section and click **Add Results field**.
* On an [assay type](https://docs.labatlas.com/managing-your-organization/assay-types.md)'s default tasks, so every assay of that type gets them.
* In the task panel when you create or edit a task: click **Add field** under **Required to complete**.

### Completing a task with Results fields

When you open a task with Results fields, the panel shows a **Record to complete** card. Required fields are marked with an asterisk (\*), and optional ones say *optional*. The card shows how many required fields have a value, for example **1/3**.

The completion button reads **Record & complete** rather than **Mark complete**, and stays disabled until every required field has a value. The value recorded for a **Choice** field must be one of its current options. This is checked when the task is completed, including through the [REST API](https://docs.labatlas.com/developer-tools/rest-api-reference.md) and [MCP server](https://docs.labatlas.com/developer-tools/mcp-server.md).

The arrow next to the completion button has **Mark in progress** and **Mark incomplete**. Marking a task incomplete closes it without needing the required values.

Once the task is closed, the card is titled **Recorded values**. Click **Reset** to reopen the task.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FOPdaW7PijVLJNSuFvJUL%2Fimage.png?alt=media&amp;token=b2c89871-6d80-4a8b-b49d-6aebc9b35731" alt="" width="375"><figcaption><p>A task that requires user information before completion</p></figcaption></figure>

## Tasks from assay types

An [assay type](https://docs.labatlas.com/managing-your-organization/assay-types.md) can define a list of default tasks. Every assay created from that type starts with those tasks already in place, so a standard protocol arrives as a ready-made checklist and gets recorded the same way every time.

If you've already added your own tasks or field values on the New Assay form and then change the assay type, Lab Atlas asks whether to **Use \[type]'s tasks**, **Keep my tasks**, or **Don't change the type**. See [Choosing an assay type](https://docs.labatlas.com/using-lab-atlas/studies/assays.md#choosing-an-assay-type).

## Tasks on locked records

When a project, study, or assay is [locked](https://docs.labatlas.com/using-lab-atlas/locking-records.md), its tasks are locked too, along with the tasks of everything beneath it. On the record's **Tasks** tab:

* A message next to the buttons starts with **Locked by** and the code of the record that holds the lock.
* **New task** is disabled.
* Opening a task shows the same **Locked by** line under its status, and the buttons to complete it or change its status are hidden.

The same applies to tasks on the [Planning](https://docs.labatlas.com/using-lab-atlas/planning.md) page. To work on the tasks again, unlock the record.

## For administrators

* **Locks.** Who can lock and unlock a record is covered in [Locking Records](https://docs.labatlas.com/using-lab-atlas/locking-records.md#who-can-lock).
* **Default tasks.** Default tasks and their Results fields are set on [Assay Types](https://docs.labatlas.com/managing-your-organization/assay-types.md).
