> 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/field-operations/tasks/what-creates-deficiencies-tasks.md).

# What creates Deficiencies tasks

A Deficiencies task is created when you submit an inspection report that has deficiencies recorded on it. The task gathers that report's deficiencies in one place so you can follow up, for example by quoting the corrective work. You can also create one directly, without an inspection report, using the pinned row at the top of the folder — see [Create a deficiency task](/field-operations/tasks/create-a-deficiency-task.md).

Technicians can create them from the mobile app too, when your settings allow it: from the **Deficiencies** section of a [Work Acknowledgment](/field-operations/mobile/create-a-work-acknowledgment.md) (Settings -> Work Acknowledgments -> Include deficiencies) or of the [job summary](/field-operations/mobile/add-a-visit-summary.md) (Settings -> Team -> Technician App -> Job summary -> Record deficiencies). Each submission creates one task per asset group the recorded deficiencies belong to; the task's timeline says which of the two it came from, and the deficiencies show on the job's Deficiencies tab because they're tied to the visit.

Deficiencies tasks sit in a single All folder. You work each one by moving it through its statuses. A Deficiencies task can also move into a custom folder your business has added, and back to All, using **Move to Folder** in Quick Actions — see [Organize task categories and folders](/administration/settings/organize-task-categories-and-folders.md).

> **Where to find it:** Tasks page, the Deficiencies group in the left sidebar (the All folder)

## Related guides

* [Create a deficiency task](/field-operations/tasks/create-a-deficiency-task.md)
* [Create a work acknowledgment on mobile](/field-operations/mobile/create-a-work-acknowledgment.md)
* [Add a visit summary on mobile](/field-operations/mobile/add-a-visit-summary.md)
* [How tasks are created and organized](/field-operations/tasks/how-tasks-are-created-and-organized.md)
* [The Tasks inbox: folders, status filters, and search](/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.md)
* [What creates Invoices tasks](/field-operations/tasks/what-creates-invoices-tasks.md)
* [What creates Jobs tasks (and moving them between folders)](/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.md)
* [What creates Quotes tasks](/field-operations/tasks/what-creates-quotes-tasks.md)
* [Organize task categories and folders](/administration/settings/organize-task-categories-and-folders.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/field-operations/tasks/what-creates-deficiencies-tasks.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.