> 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/use-the-scheduling-map-and-technician-status.md). # Use the scheduling map and technician status Use the map and status indicators when the office needs to understand where technicians are and what stage each visit is in. ## Technician status Scheduling can show statuses such as scheduled, on the way, clocked in, completed, and ETA when those signals are available from the mobile app. ## Map view The map view helps dispatchers see technicians and work geographically. GPS visibility depends on your business settings, technician permissions, and whether the technician is en route or clocked in. If a technician does not appear live on the map, check whether GPS is enabled, whether they have location permission on the mobile device, and whether they are currently in a trackable state. If you need map or GPS visibility and it is missing for your role, contact your business's administrator to review your access. > **Where to find it:** Scheduling page > Map view and technician status indicators ## Related guides * [See technicians on the map with live GPS](/customers-and-work/scheduling/see-technicians-on-the-map-with-live-gps.md) * [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) * [Customer notifications for scheduled visits](/customers-and-work/scheduling/customer-notifications-for-scheduled-visits.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/use-the-scheduling-map-and-technician-status.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.