> 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/multiple-technicians-on-mobile.md). # Work a visit with multiple technicians on mobile When a visit has multiple assigned technicians, each technician opens the same visit from their own mobile app. The visit card lists every assigned technician's full name, including your own, so you can see who is working with you before opening the visit. Each technician clocks in separately and clocks out separately. All assigned technicians can work on the same inspection report. If two technicians edit the same asset or field, the latest saved edit is what remains. Only one technician needs to submit the Job/Visit Summary. Its selected Job Status controls the shared Jobs task even if another assigned technician did not clock in or out. If a Never Clocked In or Missing Summary flag appeared before the summary arrived, submitting the summary replaces that flag with the selected Job Status. If more than one technician submits it, they update the same summary instead of creating separate summaries. > **Where to find it:** Mobile app > Visits > shared visit ## Related guides * [Use On My Way, Clock In, and Clock Out](/field-operations/mobile/on-my-way-clock-in-clock-out.md) * [Fill inspection reports on mobile](/field-operations/mobile/fill-inspection-reports.md) * [Add a visit summary on mobile](/field-operations/mobile/add-a-visit-summary.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/multiple-technicians-on-mobile.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.