> 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/work-with-the-scheduling-backlog.md).

# Work with the scheduling backlog

The Backlog panel holds visits that still need to be done but don't have a date and time yet. A visit lands in the backlog when it's created without a scheduled time, and it stays there until you place it on the calendar.

An unscheduled visit can already carry its visit type, estimated duration, technician count, contacts, reminders, inventory reservations, notes, scheduling instructions, and an optional due date. Each backlog card surfaces the customer, property, work, duration, and due date so you can decide what to schedule next.

The visit-type pills and job number share the bottom row of each job's backlog card, with the job number on the right. If there are more pills than fit, scroll the pills horizontally; the job number stays visible.

Use the backlog's filter and sort controls to find the work you want, then drag it onto a technician's calendar at the time you want. You can ask Essential what's waiting in the backlog.

To remove a scheduled time without deleting the visit, drag the visit from the calendar or map back to the Backlog. If that visit covers a recurring service marked **Awaiting Service Completion**, Essential first asks whether its automation should remain paused, start again, or resume using a future date.

Select **Backlog** at the top of the Scheduling page to show or hide the panel. Essential remembers that choice on this browser, so the panel stays shown or hidden when you return to the page.

> **Where to find it:** Scheduling page, the Backlog panel (heading reads Backlog)

## Related guides

* [Deleting a scheduled visit is permanent](/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.md)
* [Draft visits and releasing them to the team](/customers-and-work/scheduling/draft-visits-and-releasing-them-to-the-team.md)
* [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)
* [See and manage your schedule](/customers-and-work/scheduling/see-and-manage-your-schedule.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/work-with-the-scheduling-backlog.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.