> 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/schedule-technician-time-off.md).

# Schedule technician time off

To block a technician from normal service work, use a scheduled internal visit as an unavailable-time block.

This works best when your business has a no-property visit type, such as Misc - Tech Unavailable. Choosing a no-property visit type hides the Property field entirely — there's no placeholder property to create or select.

If your business doesn't have a no-property visit type yet, ask an administrator or Essential to add one before using this workflow.

## Create the unavailable block

1. Open the Scheduling page.
2. Choose Add Visit.
3. Choose the unavailable visit category and type, such as Misc - Tech Unavailable. The Property field disappears once you've selected it.
4. Assign the technician and set the date, start time, and duration.
5. Save the visit.

## Why this works

The unavailable block appears on the schedule like other work, so dispatchers can see that the technician should not be assigned another visit during that time. Use clear descriptions for context, such as vacation, training, shop time, or unavailable.

Because this is still a scheduled visit, treat it like a schedule block, not a payroll or HR time-off record. If the time changes, reschedule or update the visit the same way you would move other scheduled work.

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

## Related guides

* [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md)
* [Schedule multi-technician visits](/customers-and-work/scheduling/schedule-multi-technician-visits.md)
* [Scheduling overview](/customers-and-work/scheduling/scheduling-overview.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/schedule-technician-time-off.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.