> 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/deficiencies-clear-when-the-inspection-report-is-resubmitted-without-them.md).

# How tracked deficiencies resolve

Advanced tracking can be enabled on individual compliance items in an inspection report template. A deficiency created from one of those items is tracked: it has an Open or Resolved status and keeps its history across inspections. A deficiency from an item without advanced tracking is a standard finding. It has no Open or Resolved status, and it is removed from the current report's findings when that report is resubmitted with the item corrected.

The usual way to close a tracked deficiency is to fix the underlying compliance answer and resubmit the source report. When the item is no longer failing, the deficiency is marked resolved — it is not deleted. It keeps its history and shows the resolution date and how it resolved ("report resubmitted").

Resolution can also come from a later inspection. When another report of the same report type re-tests the same item on the same asset, a passing answer resolves the open deficiency ("passed retest") and a failing answer records the retest date while leaving it open. If a resubmission brings a previously resolved failure back, the same deficiency reopens rather than starting a new record.

Your office can also resolve a tracked deficiency by hand from the Deficiencies task or the Job page's **Deficiencies** table using **Mark Resolved** (or **Reopen**), which records it as "marked manually." On the Job page, these buttons are in the **Actions** column and update the row without opening another page. Standard findings do not show these controls. Manual resolution is for cases where the fix happened outside a report, like a repair confirmed over the phone.

The Deficiencies task reflects all of this: open tracked items stay listed, resolved tracked items move to a Resolved section with their resolution date and source, and standard findings remain in the main list without a status pill.

If you expected a deficiency to resolve and it hasn't, check that the report was actually resubmitted and that the specific failing item was changed away from its failing answer — or that the retest was answered Pass (an N/A or unanswered retest doesn't touch it).

> **Where to find it:** On a Deficiencies task or a Job page's **Deficiencies** tab. Tracked deficiencies show an Open or Resolved pill; resolved ones show the date and whether they resolved by resubmission, retest, or manually.

## Related guides

* [Working a deficiency task](/field-operations/deficiencies/working-a-deficiency-task.md)
* [What is a deficiency?](/field-operations/deficiencies/what-is-a-deficiency.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/deficiencies-clear-when-the-inspection-report-is-resubmitted-without-them.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.