> 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/scheduling-overview.md).

# Scheduling overview

Scheduling is where office staff turn unscheduled work into assigned visits, keep technician calendars current, and monitor field progress during the day.

## Core pieces

* **Schedule views:** Show scheduled visits in Day, Day (Map), Day (Schedule), Week, or Month.
* **Backlog:** Holds estimated or unscheduled visits that still need a time, technician, or both.
* **Visit detail:** Holds duration, technician count, work orders, contacts, reminders, inventory reservations, expected inspections, notes, and instructions.
* **Technician status:** Shows whether technicians are scheduled, on the way, clocked in, completed, or visible on the map when GPS is enabled.

Start with the backlog when the work is not scheduled yet. Use a calendar view when you need to move a scheduled visit or reassign a technician. Use Day (Schedule) when you want to scan one day's visits and open their details without navigating the calendar grid.

Common controls on the scheduling page let you change the date, show or hide the backlog, change the calendar view, show or hide technicians, and add a visit. Most jobs only contain one visit, but a job can have more when follow-up work or another trip is needed.

> **Where to find it:** Scheduling page

## Related guides

* [See and manage your schedule](/customers-and-work/scheduling/see-and-manage-your-schedule.md)
* [Switch how the schedule is shown](/customers-and-work/scheduling/switch-how-the-schedule-is-shown-week-month-map.md)
* [Work with the scheduling backlog](/customers-and-work/scheduling/work-with-the-scheduling-backlog.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.withessential.com/customers-and-work/scheduling/scheduling-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.