> 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/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.md). # Deleting a scheduled visit is permanent Deleting a visit removes it for good, and a deleted visit does not drop back into the Backlog. If you only want to take a visit off a technician's day without losing it, drag it back to the Backlog instead of deleting; that clears its time but keeps the visit. Right after you delete a visit, an Undo button appears at the bottom of the screen for a few seconds - click it to recreate the visit with the same property, technicians, duration, contacts, and notes. Once the Undo button disappears or you navigate away, the deletion is final and there is no trash to recover it from. To review a deleted visit, open its Job Timeline and select **View changes** on **Visit deleted**. The retained details include assigned technicians, work orders, instructions, notes, scheduled start and end, duration, scheduling type, due date, arrival window, required crew size, contacts and reminders, expected assets, line items, and self-scheduling settings. This history lets you review the deleted information; it does not restore the visit. There is no separate list of deleted visits to browse. Retained line items appear in a separate **Deleted visit line items** entry, available when your business has Inventory turned on, or you have permission to view enabled Job Costing data. Reports, work acknowledgments, and manually filed deficiencies removed with the visit also retain their saved contents and attachments in the timeline, subject to the same access permissions. Because it is permanent once the Undo window passes, treat Delete as different from rescheduling or moving a visit to the Backlog, which are always reversible. A visit with recorded time cannot be deleted. If the time was added by hand, remove the entry from the technician's timecard or from the job's **Clock In / Clock Out** tab first. Phone clock history is kept as a permanent audit trail even after its effective hours are removed; contact Essential support if a visit carrying that history truly has to be removed. ## When it was the job's last visit Deleting a job's last visit from the Scheduling page also removes the job when nothing else is on it. A job is kept if it has any quotes, invoices, files, tasks, job costing or planned items, manual revenue, inventory usage, or filled-in job custom fields, so you can schedule a new visit for it later. If the job was removed with the visit, Undo brings the visit back on a new job for the same property. Deleting a visit from a job's own page never removes the job. ## When the visit was covering a recurring service If the visit you're deleting or moving to the Backlog covers a recurring service that shows "Awaiting Service Completion", Essential asks what should happen to that service's automation before removing its scheduled coverage: * **Keep Awaiting Service Completion** — nothing changes; the service stays paused until a completion is recorded (or you clear the status from the asset group page later). * **Start the automation again** — the status clears and automation resumes. The dialog shows when the next outreach would send (or when the Custom Task would be created); if the due date already passed, that can be as soon as the next send window. * **Resume automation using a future date** — the status clears. For automated outreach, the date you select becomes the service due date, and outreach may begin earlier based on your configured schedule. For Custom Tasks, the task is created on the selected date. When another scheduled visit also covers the service, the dialog adds that note under the service — you still choose what happens; nothing is decided for you. The extra note is omitted when the deleted visit is the only one covering it. Each affected service is labeled as **Asset group type (asset group name): Visit type / Service**. The asset group name is omitted when that group has no name. > **Where to find it:** Scheduling page -> open a visit -> the trash icon deletes it, with an Undo option appearing briefly after. To only clear its time instead of deleting, drag it from the calendar or map to the Backlog; the same automation choices appear when needed. ## Related guides * [Exact time vs. estimated, duration, technician count, and due date](/customers-and-work/scheduling/exact-time-vs-estimated-duration-technician-count-and-due-date.md) * [Filter and sort the backlog](/customers-and-work/scheduling/filter-and-sort-the-backlog.md) * [Work with the scheduling backlog](/customers-and-work/scheduling/work-with-the-scheduling-backlog.md) * [Add work orders (visit types) and contacts with reminders to a visit](/customers-and-work/scheduling/add-work-orders-visit-types-and-contacts-with-reminders-to-a-visit.md) * [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.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/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.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.