> 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/inspection-reports/delete-an-inspection-report.md). # Delete an inspection report Delete removes an inspection report from the places where reports and their generated PDFs normally appear. Open the report in the web app, select **Delete**, type **DELETE**, and confirm. Essential returns you to the Inspection Reports list. ![Confirmation for deleting a submitted inspection report](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-75fc2d50cdbe2d780e68079dbf05521d7132ad84%2Finspection-report-delete-confirmation.png?alt=media) Draft deletion requires inspection-report write access. Deleting a submitted report requires the separate **Delete Submitted Inspection Report** permission, which an administrator can grant from Settings -> Team -> Roles & Permissions. Built-in default roles can't be edited directly — duplicate one to get an editable custom role, then grant the permission there. Mobile users can delete only their own synced drafts; submitted reports cannot be deleted from mobile. Deleting a submitted report hides the report; it does not make the submission's work disappear. Service completions, recurring-service history, deficiencies and their resolution state, the follow-up task, job files, sent-email records, timeline events, and compliance filings remain as recorded. The deletion itself is recorded on the timelines of the report's job and property, so the action stays visible after the report is gone. A report-generated deficiency task keeps its report reference and labels it **Deleted**, but the hidden report cannot be opened from that reference. ![The property timeline records who deleted an inspection report](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-3359e8c0f3476f0e7906289992e7ba2721549c5f%2Finspection-report-deleted-timeline-event.png?alt=media) ![A deficiency task labels its deleted inspection report reference](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-1463f5e14d4f0997492e20b521c53de7092d3525%2Fdeleted-inspection-report-task-reference.png?alt=media) If the report has filing activity in The Compliance Engine, the confirmation warns you that deleting the report will not remove or change those filings. ![Warning when deleting a report with Compliance Engine filing activity](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-564fddbb850353ac6659027a3f4af0281bfb0ae7%2Finspection-report-delete-compliance-fyi.png?alt=media) Use submitted deletion when the report itself should no longer be available. If the recorded service history, deficiency state, or compliance filing is wrong, correct that record separately instead of expecting report deletion to reverse it. > **Where to find it:** Open an inspection report in the web app -> Delete. For submitted reports, the role also needs Settings -> Team -> Roles & Permissions -> (a custom role) -> **Delete Submitted Inspection Report**. ## Related guides * [Save a draft and publish an inspection report](/field-operations/inspection-reports/save-a-draft-and-publish-an-inspection-report.md) * [Common inspection report questions](/field-operations/inspection-reports/common-inspection-report-questions.md) * [Working a deficiency task](/field-operations/deficiencies/working-a-deficiency-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/inspection-reports/delete-an-inspection-report.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.