> 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/switch-how-the-schedule-is-shown-week-month-map.md).

# Switch how the schedule is shown

Open View Options at the top of the desktop Scheduling page to change how visits are shown. Under Views you can pick Day, Day (Map), Day (Schedule), Week, or Month. Your View Options stay saved in this browser when you log out and sign back in.

Day headings include the weekday, such as **Thu, Sep 10, 2026**. Visit and commute durations use hours and minutes, such as **1 hr 40 min**.

* **Day** lays one day's technician schedules out on a time-based calendar.
* **Day (Map)** plots one day's visits at their properties and can show where technicians are. On mobile, it also plots filtered backlog visits that have a property address; open a pin and look for **Unscheduled** to distinguish backlog work from the selected day's scheduled visits.
* **Day (Schedule)** shows the selected day as one visit-based list. On desktop, each sortable row includes the arrival window above the scheduled time, the customer and property, visit types, and assigned technicians. On mobile, visits appear in chronological order.
* **Week** places visits at their scheduled times on a seven-day hour grid.
* **Month** shows a full month grid with visit time and property labels inside each day. Drag a visit onto another day to move it there with the same technicians. Exact visits keep their start time; estimated visits go after that technician's last stop on the destination day. See [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).

Week and Month use the week start saved in **Settings → Personal Settings → Calendar**. The preference also controls date pickers throughout the web app. In Month, the technician color key and weekday labels stay visible while you scroll through later weeks.

On desktop, click a date number in Month to open that date in **Day (Map)**. Calendar dates follow your business timezone, even when your computer uses a different timezone.

Day (Schedule) follows the technicians selected under View Options. A multi-technician visit appears once, and it remains in Day (Schedule) when at least one of its technicians is visible. On desktop, select a column heading to sort the rows. To move a visit with drag and drop on desktop, switch to Day, Day (Map), Week, or Month.

On a mobile browser, use the compact calendar-view selector to switch among the same five views. Week is a seven-day hour grid with a current-time line that updates while the view stays open; tap a date heading to open Day. Month is a complete calendar grid with visit labels, including a **Continued** entry on every day an overnight visit overlaps; tap a date or **+N more** to open that day's Day view. Swipe a Week or Month calendar to move to the next or previous period, use the arrows for the same navigation, or tap **Today** to return to the current date. Multi-technician visits appear once in Day (Schedule), Week, and Month.

In the calendar views that support them, Technician View can give each technician a separate row or combine everyone onto one shared grid, and Visit Card switches cards between Detailed and Summary. On the shared grid, each card is tinted with its technician's color and shows the technician's name as the last line of the card, under the address and status icons (or under the title of a Tech Unavailable block). Short cards that don't have room for the extra line leave it off; the technician is still shown in the card's detail popover and by its color.

In both desktop Week layouts, stronger vertical dividers run from the date headers through the schedule. Shared Grid also leaves extra space between neighboring days' cards to make each day easier to follow. Time labels stay readable in both Light and Dark appearance.

Select **Weekend** beside **Backlog** to hide or show Saturday and Sunday. When hidden, the weekdays expand to use the space and a soft teal **X hidden** badge shows how many weekend visits are hidden for the selected technicians. Each visit counts once, including visits assigned to several technicians or continuing across both weekend days. Overnight visits continuing into the weekend are included. **0 hidden** means there are no weekend visits for the selected technicians.

Weekends are visible by default. Your choice is remembered in this browser and applies to both **Separate Rows** and **Shared Grid** in Week view. It does not change your saved week start, other calendar views, or any scheduled visits.

Technician names in the visit picker, selected technician chips, and **View Options → Technicians** have a small color dot matching their calendar color.

Visits assigned to multiple technicians appear as **one card** on the **Shared Grid**, with diagonal bands in those technicians' colors. Overnight continuations also appear once. Drafts keep their violet appearance and softer technician bands on every day they span. Filtering to just one assigned technician keeps the shared colors and hatching visible; hiding every assigned technician hides the visit.

Shared visits have one drive-time block sized to the longest commute among the visible technicians. Its label shows the range, such as **25 min–30 min**, or one value when their commutes match. Technicians who drive to the visit from the same previous stop share one drive time, even when one of them joined the visit later; a range means they are coming from different places, such as each technician's own starting location for the first visit of the day. Narrow blocks shorten overflowing text with an ellipsis. Filtering to one technician shows that technician's commute time. Click the block’s **✕** to choose which technicians’ drives to remove. Select one technician or several, then confirm. The chooser includes every assigned technician, even when a technician is filtered out. If any drive has been removed, the card’s restore icon lets you choose which drives to bring back.

![Shared grid cards naming their technicians](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-4c719cffa45fc68fa01fed14929c2f90c94c36c9%2Fscheduling-shared-grid-technician-names.png?alt=media)

The date range you're viewing drives what loads, and it's also the window Essential uses by default when you ask about the schedule.

> **Where to find it:** Scheduling page, the View Options control on desktop or the calendar-view selector on a mobile browser

## Related guides

* [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)
* [See and manage your schedule](/customers-and-work/scheduling/see-and-manage-your-schedule.md)
* [See technicians on the map with live GPS](/customers-and-work/scheduling/see-technicians-on-the-map-with-live-gps.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/switch-how-the-schedule-is-shown-week-month-map.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.