> 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/remove-a-commute-from-the-schedule.md).

# Remove a commute from the schedule

Every scheduled visit shows the drive to get there as a block directly above the visit card. Sometimes that drive isn't real — the technician is already onsite, they're driving on their own time, or they're coming straight from home. You can take that drive off the schedule, and put it back later.

## Remove a drive

1. Hover the drive block above the visit and click the **✕** in its top-right corner. On a phone or tablet, tap the drive block itself.
2. In **Shared Grid**, select the technicians whose drives you want to remove. You can choose one or several, including technicians currently filtered out. For a single technician’s card, that drive is already selected. Technician colors match the calendar. If names match, an email address or technician ID helps you tell them apart.
3. Click **Remove commute** (or **Remove commutes**).

The action is hidden for zero-minute commutes, including back-to-back visits at the same location. Drives already removed are available through the restore icon instead.

## What removing does

The drive becomes zero minutes long:

* The drive block disappears from the calendar.
* The drive stops counting toward that technician's booked day, so their utilization drops.
* The drive can no longer collide with the technician's other visits.

**The schedule recalculates.** The visit moves up to close the gap the drive left, and any later visits on that technician's day move up with it — the same way they shift when you change a visit's duration.

**Visits with an exact start time don't move.** An exact time is what the customer was promised, so removing its drive only takes the block off the calendar. Later visits are still measured from when that visit ends, so they don't move either.

Removal applies only to the selected technicians’ assignments on that visit. Unselected drives stay on the schedule. If only some updates succeed, the chooser shows how many drives changed and explains any failures. Completed drives leave the chooser, and failed choices stay selected for retry. If someone reassigns a technician while the chooser is open, it closes and refreshes the schedule. Open it again to choose from the updated assignments; any completed changes are kept.

## Restore a drive

A visit with any removed drive has a dashed line across the top of its card and a **restore** icon in the top-left corner. Click that icon to put the drive back. On a shared card, select one or several technicians and confirm **Restore commute** (or **Restore commutes**).

The restore icon stays available when one technician’s drive has been removed and another technician’s drive is still visible. If you are viewing an overnight continuation, go to the visit’s starting day to use its commute controls.

Restoring puts the drive back and recalculates the technician's day. Estimated visits usually slide back down; if an exact-time visit constrains the available space, flexible visits move around that fixed time instead.

> **Where to find it:** Scheduling page — the drive block above a visit card, or the restore icon on the card

## Related guides

* [Resolve scheduling conflicts](/customers-and-work/scheduling/resolve-scheduling-conflicts.md)
* [See and manage your schedule](/customers-and-work/scheduling/see-and-manage-your-schedule.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)


---

# 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/remove-a-commute-from-the-schedule.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.