> 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/see-and-manage-your-schedule.md). # See and manage your schedule The Scheduling page is where you see and arrange your team's visits. Each visit is a trip to a customer's property to do work on a job, assigned to one or more technicians with a start time and an estimated duration. Visits that already have a time appear in the schedule views; visits that still need a time wait in the Backlog panel. Use View Options to choose Day, Day (Map), Day (Schedule), Week, or Month, move the date range forward or back, and drag visits in a supported desktop calendar view to schedule, reschedule, or reassign them. Day is a one-day technician time grid, while Day (Schedule) is a daily visit list. On desktop, the calendar toolbar keeps the active view, Drag, View Options, Backlog, and **Create Job / Visit** together. In **View Options**, use **Page Layout** to choose Full Screen or Classic. Full Screen hides the app header, Scheduling heading, and outer calendar frame so more of the day fits on screen. Essential remembers your choice in this browser until you change it. In the Day technician grid, the hour labels stay at the left edge while you scroll across technician columns, so each horizontal gridline keeps its time reference. In Month, the technician color key and weekday labels stay visible while you scroll through later weeks. Week and Month begin on the day selected under **Settings → Personal Settings → Calendar**. Deactivated technicians start hidden every time you open Scheduling, even if you showed them during an earlier visit to the page. Use the technician visibility checkboxes to show one again for the current session; a deactivated technician uses a gray avatar color and their name reads **Name (Deactivated)**, so they stay easy to identify. Once a deactivated technician has gone seven days without a visit, they leave Scheduling entirely: no column, no map pin, no technician key entry, and no row in **View Options**. They reappear on their own for any date range that still holds their visits, so paging back to an earlier week always shows the work they did, and a deactivated technician with visits still scheduled ahead stays on the calendar. On a phone-sized window, Scheduling always shows active technicians only. The colored edge on the left of a calendar visit shows field progress: gray is **Not Started**, blue is **En Route**, yellow is **In Progress**, and green is **Completed**. Violet identifies a draft, while the hatched edge identifies technician-unavailable time. When you open a scheduled visit, the pill beside the job number names the progress state for the whole visit across all assigned technicians. A visit opened from the Backlog is labeled **Unscheduled** instead. A calendar card that's tall enough shows a compact time range such as **9AM-10AM** or **9:35AM-10:35AM**; shorter cards skip it. When a visit has an arrival window, a tall-enough card adds a separate truck section with primary **Arrive** timing and a secondary shorthand duration such as **Duration 3 hr**; its scheduled-time row uses a neutral clock instead of an exact-time target. If the card only has room for one timing row, the customer-facing **Arrive** window takes priority over the internal scheduled time. The popover shows the full **Arrive between** wording and estimated duration above the neutral-clock scheduled time and date. If the scheduled start falls outside the arrival window, the Scheduling form's start-time step, card, and popover show an alert so you can correct it. Without an arrival window, cards and popovers do not get either arrival-window section or the neutral-clock override. Hover the icon controls in the popover's upper-right corner to identify **Edit**, **Duplicate**, **Delete**, and **Close**. When a visit has line items, the popover lists them under **Parts, Labor & Items** (count, then quantity × name for the first few rows). Below that, **Job Files** shows how many files are on the job with an **Add** link that attaches a file to the job without opening the visit form. You can ask Essential about a technician's day, who looks free, or what's in the backlog for whatever window you're viewing. > **Where to find it:** Scheduling page (main navigation, Scheduling) ## Related guides * [Draft visits and releasing them to the team](/customers-and-work/scheduling/draft-visits-and-releasing-them-to-the-team.md) * [Drag and drop to schedule, move, reassign, and handle conflicts](/customers-and-work/scheduling/drag-and-drop-to-schedule-move-reassign-and-handle-conflicts.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) * [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) --- # 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/see-and-manage-your-schedule.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.