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

# Task categories and statuses

> The categories tasks are grouped into, the type each task carries, and what Not started, In progress, Completed and Not applicable mean.

<Note>
  **Quick summary**

  * Every task has a category (where it belongs), a type (the kind of work) and a status.
  * Most tasks complete once their document is approved; you mark a record task done yourself.
  * Tasks in the *Product* category unlock once you map a framework to that product.
</Note>

## Task categories

| Category | Typical contents |
| - | - |
| *Setup* | Getting your workspace and company details in place |
| *Policies* | Documents like your Quality Manual, or a Password and PIN policy |
| *People* | Roles, training and checklist assignments |
| *Organisation* | Records and recurring organisational commitments |
| *Security Controls* | Technical and process controls |
| *Product* | [Work scoped to one product](/tasks/product-specific-tasks), unlocked once a framework is mapped to it |
| *Audit & Certification* | Internal audits, management review and certification-facing work |
| *Other* | Holds custom tasks that don't fit the categories above, and only appears on the Tasks page once a task uses it |

## Task types

A category says where a task belongs. Its type says what kind of work it is, and shows as a badge in the task list and at the top of its sheet. Types include:

* *Document*: a policy or procedure to write.
* *Record*: evidence you keep.
* *Personnel*: appointing someone or checking their details.
* *Action*, *Review* and *Risk*.

## Task statuses

| Status | What it means |
| - | - |
| *Not started* | No work recorded yet |
| *In progress* | Underway, not yet resolved |
| *Completed* | Done. Set automatically when the document behind it is approved, or marked directly for a record task |
| *Not applicable* | Doesn't apply to your organisation. Always set by hand |

If every task behind a requirement is *Not applicable*, you still set the requirement to *Not applicable* yourself.

## Related articles

<Columns cols={2}>
  <Card title="Completing a task" icon="square-check-big" href="/tasks/completing-a-task">
    Take the suggested action and move a task to Completed.
  </Card>

  <Card title="Framework progress" icon="circle-gauge" href="/frameworks/tracking-and-mapping">
    How task statuses roll up into a requirement's status.
  </Card>
</Columns>


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