> 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. Use the arrows on either side of the date to move a day at a time, or tap the date to pick one. The app shows upcoming work up to 30 days ahead. ### Physical Items In the **Day** list, **Physical Items** combines physical items from the planned Parts, Labor & Items on your assigned jobs. Quantities for the same catalog item are added together. A job with several visits on the selected day is counted once. Services, labor, and custom items without a catalog type are excluded. Tap an item to see its code and the quantity needed for each job. Tap a job to open its visit. Tap the **Physical Items** heading to collapse or expand the checklist. Check items off as you load them, or use the list without checking anything. Checkoffs are personal to your technician account, selected day, and device; they also work offline after the schedule has loaded. They do not record item usage or affect clock-in, job completion, or inventory. A changed quantity or job allocation clears that item's checked appearance so you can review it again. The Physical Items card only appears when there are physical items or equipment to bring. Pull down to refresh after the office changes a job's plan. If saved checkoffs are damaged, the app asks you to check the loaded items again. You can keep using the checklist; your next checkoff saves a fresh record. ### Equipment If your business uses Equipment, the **Physical Items** card also lists the shared gear the office added to your visits that day, such as lifts, ladders, or access keys, under an **Equipment** heading after the items. Cancelled visits are not included. Each visit card in the list also shows the equipment that visit needs, next to a toolbox icon. Equipment goes with you from stop to stop, so each piece shows the most that any one visit needs, not the total across visits. If three visits each need one ladder, the card shows **×1**; if one of them needs two, it shows **×2**. Under each piece of equipment, the card names the one visit that needs it or counts the visits; two visits for the same job count as two. Tap it to see each visit that needs it and how many that visit needs. Tap a visit to open it. Check equipment off as you load it, the same way as items: checkoffs are optional, personal to your technician account, selected day, and device, and they don't notify the office. The progress at the top of the card counts items and equipment together. A changed quantity, or a visit gaining or losing that equipment, clears its checked appearance so you can review it again. The Physical Items card appears when your visits that day need physical items, equipment, or both. Pull down to refresh after the office changes a visit's equipment. If some of the day's visits come from an older copy saved before visits carried equipment, the card says **Equipment for some visits couldn't be loaded** and the equipment checkboxes stay unavailable until you pull down to refresh while online. Item checkoffs keep working. ## Week and Month views **Week** lists seven days starting with the selected day, with each day's visit cards under its heading. Tap a card to open the visit, or tap a day's heading to open that day in **Day**. The arrows beside the date range move a week at a time. **Month** shows a calendar with dots under the days that have visits. Tap a day to list its visits below the calendar, then tap a card to open the visit, or tap **Go to Day** to switch to that day's list. ## 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 -> Scheduling, 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 For visits with two or more assigned technicians, the card lists all of their full names, including your own. 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 leads with that promised **Arrive between** range and shows the visit's estimated on-site duration below it, labeled **Estimated time for visit** (for example, **2 hours**), so the customer-facing window is what the technician sees first. Arrival-window visits use a neutral clock, even when their underlying scheduling type is exact. After the window ends, any visit you haven't personally clocked into shows the whole **Missed · Arrive between: *****\[time range]*** line in bold red - even one already in progress for another technician on the visit. 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](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-01f6997ab09fac3bcc62be595a00e7560fc809fe%2Fmobile-visit-arrival-window.png?alt=media) 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, the **Arrive between** range is the emphasized line, and the **Estimated time for visit** row sits below it in muted text because the window is the range promised to the customer. That row shows the visit's estimated on-site duration (for example, **2 hours**), not a clock time — under an arrival window the scheduled start is not the promise, so only how long the visit takes is useful. 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) * [Add equipment to a visit](/customers-and-work/scheduling/add-equipment-to-a-visit.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/field-operations/mobile/see-your-visits.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.