> 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-technicians-on-the-map-with-live-gps.md). # See technicians on the map with live GPS The Day (Map) view, chosen from View Options under Views, plots each visit at its property's location. If your business has technician GPS turned on, it also shows where your technicians are right now, with a chip for each that reads Live when their location is current, or how long ago they were last seen (for example, about 10 minutes ago). A technician's live work status shows alongside, such as Clocked In, En Route with an ETA, or Clocked Out. Individual technicians can have GPS tracking turned off, in which case they don't appear on the map. When visits have arrival windows, an Arrival Window banner at the top of the page flags anyone who is at risk of missing, will miss, or has already missed their window. The missed-window warning only needs the scheduled window and clock-in record; the earlier at-risk and will-miss warnings use a live GPS ETA. > **Where to find it:** Scheduling page, View Options, then Views, then Day (Map) ## Related guides * [See technician status from the office: clocked in, en route, and ETA](/customers-and-work/scheduling/see-technician-status-from-the-office-clocked-in-en-route-and-eta.md) * [Switch how the schedule is shown](/customers-and-work/scheduling/switch-how-the-schedule-is-shown-week-month-map.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) * [Deleting a scheduled visit is permanent](/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.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-technicians-on-the-map-with-live-gps.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.