> 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/deficiencies/working-a-deficiency-task.md). # Working a deficiency task A Deficiencies task is where your office acts on the problems a technician flagged. Open the task to see each deficiency's customer-facing **Report Description**, **Internal Description**, additional deficiency-field answers, and attached photos or files. The original Pass, Fail, Yes, or No compliance answer is not repeated. Deficiencies created from report items with advanced tracking carry an Open or Resolved pill; resolved ones show the resolution date and how they resolved—**(report resubmitted)**, **(passed retest)**, or **(marked manually)**—plus the last retest date when there is one. Resolved tracked items collect in their own Resolved section. Standard findings remain in the main list without a status pill. For a report-generated task, the Overview block ties the task to the property, visit, technician, visit type, and invoice items, and from the source inspection report shown on the task you can use **View Report** or, with the right permission, **Edit Report**. A [manually created deficiency task](/field-operations/tasks/create-a-deficiency-task.md) has no visit or report behind it, so its Overview has no visit details or report files — the property stays in the task header, and you work the findings right on the task. A task a technician filed from a work acknowledgment or job summary keeps its visit: the Overview shows the visit details, and when that visit has a signed work acknowledgment, a **Work Acknowledgment** row links to the signed PDF (with its submitted date) so you can open it without leaving the task. Use **Download All Reports** to download all report files at once. To email the report PDF directly, open the submitted report and use **Send Report**, or use **Send Report** in its Job task's Inspection Reports section. To share a broader recap link instead, use **Send Job Summary** from the report or the Job task's Quick Actions. These sharing methods are enabled separately; see [Download or email an inspection report](/field-operations/inspection-reports/download-or-email-an-inspection-report.md). If Edit Report or a follow-up Quick Action is missing but you need it for your work, contact your business's administrator to review your role. Quick Actions include **Move to Folder** — the same file-away action available on any task type, see [Quick Actions on a task](/field-operations/tasks/quick-actions-on-a-task-create-a-visit-invoice-or-quote-without-leaving-the-task.md) — plus the two follow-ups specific to a deficiency: **Create Quote** starts a new quote pre-linked to this deficiency task, so you can turn the findings into a priced proposal to fix them, and **Create Job / Visit** schedules the repair work. When the property has other deficiency tasks still open—or this task's findings are all resolved—Create Quote first shows a picker so you can choose which tasks to include. A resolved source task is marked **Not Included**. Creating the quote uses the selected tasks as source context, links their jobs, and can attach their inspection-report PDFs when report auto-attach is on for your business. It does not prefill line items. **Generate draft** creates the proposed line items afterward. Asset-backed findings are grouped by the report's asset-group type, with reports of the same type sharing a group; report-level findings without an asset may remain ungrouped. A configured task automation can update the selected tasks after quote creation. Use **Mark Resolved** on a tracked deficiency when the fix happened outside a report, and **Reopen** to undo that manual resolution. These controls live on the task and do not require inspection-report edit access. Standard findings do not show resolution controls; correct the source report and resubmit it to remove the finding. You can also set the task's status and keep an internal notes field on the task itself (separate from the per-deficiency notes), then Save. For report-generated deficiencies, if the report is later resubmitted with the issues fixed, or a later inspection passes the same tracked item, tracked deficiencies resolve on their own, so you're not chasing problems that are already fixed. Manually recorded deficiencies aren't tied to a report item, so **Mark Resolved** is how they resolve. > **Where to find it:** Open a Deficiencies task from Tasks. The detail view shows each deficiency, the source inspection report when the task came from one, and Quick Actions including Create Quote. ## Related guides * [How tracked deficiencies resolve](/field-operations/deficiencies/deficiencies-clear-when-the-inspection-report-is-resubmitted-without-them.md) * [What is a deficiency?](/field-operations/deficiencies/what-is-a-deficiency.md) * [Download or email an inspection report](/field-operations/inspection-reports/download-or-email-an-inspection-report.md) * [Create a deficiency task](/field-operations/tasks/create-a-deficiency-task.md) * [Quick Actions on a task](/field-operations/tasks/quick-actions-on-a-task-create-a-visit-invoice-or-quote-without-leaving-the-task.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/deficiencies/working-a-deficiency-task.md?ask=&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.