> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/add-rename-reorder-or-remove-task-statuses.md).

# Add, rename, reorder, or remove task statuses

Task Statuses settings controls the statuses a task moves through in each task folder. A folder is a task source — Jobs, Quotes, Invoices, Recurring Services, Deficiencies, and Service Requests — and each folder has its own statuses grouped into three categories: To Do, In Progress, and Done.

Pick a folder on the left to edit its statuses. Within a folder you can rename any status, add new In Progress or Done statuses, drag to reorder statuses inside a category, and remove statuses you no longer use. Your edits aren't saved until you use Save.

Every folder has exactly one To Do status — the status a task starts in when it's created. You can rename it, but you can't add a second To Do or delete it.

To remove a status, use the trash icon next to it. If the status still has tasks in it or a Task Automation rule points at it, a **Move work before deleting** dialog opens: pick another status in the **same category** (To Do, In Progress, or Done) to move that work to. When you Save, the tasks move to the status you chose and any automation rules that set tasks to the removed status are repointed to it, so nothing is stranded.

Each folder always keeps at least one Done status, so you can't delete the last one — add another Done status first if you want to swap it out. A removed status is hidden from the folder, from the task status pickers, and from the Task Automations dropdowns, and new tasks are never created into it.

This page has five tabs. Task Statuses is described above. Task Status Automations controls how a task's status changes automatically after your team takes the expected action. Task Documents controls which inspection reports and work acknowledgments are sent and attached when your team works from a task. Jobs lets you rename the Jobs folders and add close-out or standalone folders of your own; a folder you add there appears in the Jobs group on this tab with its own statuses. Custom Folders lets you create your own task categories and folders alongside the built-in ones. See the related guides for all four.

> **Where to find it:** Settings -> Work Management -> Tasks -> Task Statuses

## Related guides

* [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md)
* [Task Documents: send and attach supporting documents](/administration/settings/task-documents-send-and-attach-supporting-documents.md)
* [Customize your Jobs task folders](/administration/settings/customize-jobs-task-folders.md)
* [Organize task categories and folders](/administration/settings/organize-task-categories-and-folders.md)
* [Task folder and subfolder meanings](/field-operations/tasks/task-folder-and-subfolder-meanings.md)
* [Working a task: changing its status and saving notes](/field-operations/tasks/working-a-task-changing-its-status-and-saving-notes.md)
* [The Tasks inbox: folders, status filters, and search](/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.withessential.com/administration/settings/add-rename-reorder-or-remove-task-statuses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.