> 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/jobs/close-or-reopen-a-job.md).

# Close or reopen a job

Close a job when no more work is planned. This is optional: a job can still become Complete automatically when its visits and tasks are finished.

> **Where to find it:** Scheduling > Jobs, then open a job

1. Open **Job actions** (the three dots) on the job detail page and select **Close job**.
2. Enter a reason and select **Close job**. The reason is required and can be up to 1,000 characters.

You can close a job even when it has unfinished visits, open Jobs tasks, or technicians still clocked in.

Closing removes the job from backlog and marks untouched backlog visits and unstarted visits scheduled for today or later **Cancelled**. Those visits lose their schedule and technician assignments; affected estimated visits and drive times are recalculated. Past visits and visits with recorded work (such as time, notes, inspection reports, deficiencies, or a signed work acknowledgment) keep their current state. A visit also stays on the calendar when removing it would move work a technician has already started that day; the job timeline says how many visits were left scheduled. Tasks are not resolved automatically. Running clocks keep recording time until the technician clocks out; closing the job does not clock anyone out. If a technician clocked in while offline to a visit that closing then cancelled, that clock-in is refused when their phone reconnects. Reopen the job and schedule the visit again so they can record the time.

A closed job shows **Closed**, the reason, and who closed it and when. Its visit and task history remains available. Use the **Closed** view or the Status filter on the Jobs list to find closed jobs. Financial and deficiency follow-up and corrections to historical work remain available.

To add or schedule another visit, open the job, open **Job actions** (the three dots), and select **Reopen job** first. Reopening returns visits cancelled by that closure to backlog. Their former dates and technician assignments are not restored. Visits that were already cancelled are not changed by closing or reopening. Merging a closed job into another job also returns the visits its closure cancelled to backlog, because they now belong to an open job. The timeline keeps the closure and reopening history, including how many visits were cancelled or restored.

## Related guides

* [The job detail page: what it shows](https://learn.withessential.com/customers-and-work/jobs/the-job-detail-page-what-it-shows.md)
* [What is a job and how does the Jobs list work?](https://learn.withessential.com/customers-and-work/jobs/what-is-a-job-and-how-does-the-jobs-list-work.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/jobs/close-or-reopen-a-job.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.
