> 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-technician-status-from-the-office-clocked-in-en-route-and-eta.md).

# See technician status from the office: clocked in, en route, and ETA

From the office you can see where each technician is in their day without calling them. On the calendar, a visit card's left edge is color-coded by status: one color while the technician is clocked in to that visit, another once they've clocked out, and a third while they're en route. A card with no status color simply hasn't started yet.

A technician shows as En Route (on their way) when they've started heading to a visit but haven't clocked in yet; this state clears on its own if it goes stale. Clocking in switches the card to the clocked-in color, clocking out switches it again, and clock-in always takes priority in what you see. These colored edges work from clock-in and en-route activity even without GPS.

Next to a technician you'll also see a short live-status line. If they've reported their position recently it reads Live with how long ago, alongside a label like Clocked In, En Route, or Clocked Out.

When a technician is en route and an estimated arrival is available, an ETA line shows the expected arrival time. If your business uses arrival windows, an Arrival Window banner at the top of Scheduling can warn when an ETA is at risk or will miss the promised window. It also flags a missed window when the end time passes without a clock-in, even if Technician GPS is off.

Live status only shows activity from the current day. The live timestamp, status label, and ETA appear only when your business has Technician GPS enabled and that technician hasn't turned off location sharing; with GPS off, that line is hidden. The separate Arrival Window banner can still show a missed-window warning.

> **Where to find it:** On the scheduling calendar, each technician's visit cards are color-coded by status, and live status text appears next to the technician.

## Related guides

* [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)
* [Deleting a scheduled visit is permanent](/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.md)
* [Draft visits and releasing them to the team](/customers-and-work/scheduling/draft-visits-and-releasing-them-to-the-team.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.withessential.com/customers-and-work/scheduling/see-technician-status-from-the-office-clocked-in-en-route-and-eta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.