> 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/field-operations/mobile/see-your-visits.md).

# See your visits in the mobile app

The Visits tab shows work assigned to you. Use the Day, Week, and Month controls at the top to change how the schedule is displayed.

## Day view

Day view groups visits by status: On My Way, In Progress, Scheduled, and Completed. Pull down to refresh the list. If you are actively clocked into a visit from another day, the app keeps that active visit visible so you can get back to it.

In standard training, technicians are told to refresh the Visits screen when they have internet access so the app has the latest data before they go into the field. Depending on your configuration, the date picker may let technicians look ahead to upcoming scheduled work.

## Week and Month views

Week and Month views help you jump to another date. Select a day to return to the visit list for that date.

## Looking at past days

By default the schedule starts at today. If your office sets **Days in the past technicians can see** in Settings -> Team -> Technician App, you can also navigate back that many days (or without limit) in the Day, Week, and Month views — for example, to reopen an earlier visit, clock in to finish its work, or correct its summary. Days before the allowed window stay grayed out.

## Visit cards

Each card shows the scheduled time, property address, other assigned technicians, work type, and technician instructions. If Arrival Windows is enabled and the visit has a complete window, the card also shows that promised range below the scheduled time. Arrival-window visits use a neutral clock and standard-color scheduled time, even when their underlying scheduling type is exact. After the window ends, a scheduled visit that has not been clocked into shows the whole **Missed · Arrive between:&#x20;*****\[time range]*** line in bold red. Complete, incomplete, cancelled, and draft visits are not marked Missed. A partial window or a visit without the feature does not show this line. Use the map icon to open directions. Tap the card to open full visit details.

![Arrival window on a technician's visit card](/files/m8zBuLxnZfnjjb6QJmSl)

An exact-time visit without an arrival window shows a red target icon and its exact start time in red, bold text. An estimated visit without a window uses the approximate-time icon and standard time styling because its start can move with the technician's route. When an arrival window is shown, both types use the neutral clock and standard scheduled-time styling because the window is the range promised to the customer. The end time is calculated from the visit's estimated duration.

Teal icons and text generally indicate links. The map icon opens the device's default maps app.

When another crew is scheduled at the same property that day, the card also shows a line such as **2 other techs here today**. An amber pulse means at least one of those crews is currently in progress. Open the visit and expand the other-crews section to see each crew's work type, technicians, status, and arrival time when available.

> **Where to find it:** Mobile app > Visits

## Related guides

* [Open a visit in the mobile app](/field-operations/mobile/open-a-visit.md)
* [Use On My Way, Clock In, and Clock Out](/field-operations/mobile/on-my-way-clock-in-clock-out.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/field-operations/mobile/see-your-visits.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.
