> 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/add-a-visit-summary.md). # Add a visit summary on mobile Use the visit summary to tell the office what happened and what should happen next. ## Choose a job status Select one of the job status options: Job Complete (Ready to Invoice), Job Complete (No Invoice Needed), or Job Incomplete (Needs Another Visit). Your business may show extra fields based on the status you choose. ## Add notes and supporting records Enter Visit Notes. If the app has AI note help enabled, use Suggest note to draft cleaner wording from the context already on screen. The summary also shows Work Acknowledgments, Inspection Reports, Job Files & Photos, and invoice line items. Add job files or photos from this page when they should be sent back with the visit. ## Submit to the office If your office configured services to advance on Job Summary submission, a **Next Due Dates** card appears below Inspection Reports before the first submission. Each eligible service appears once, even when several recurring schedules use it. When those schedules have different dates, the date line begins with **Earliest** and shows the earliest result. Each row describes its impact. Services for tracked assets show the number of affected assets. An empty asset group reads **Schedule date only · no assets** for one schedule or **Schedule dates only · no assets** for several schedules. A mixed row shows both the asset count and the number of schedule-only updates. Services are selected by default. Turn off any service that was not completed. Turning one off leaves that service's recurring due dates unchanged for this submission; it does not undo a completion already recorded by an inspection report. Review the due-date choices, invoice items, and any custom fields. Tap Save & Submit to Office when the visit summary is ready. Submitting the Job/Visit Summary creates or updates a Jobs task for the office. If the inspection report recorded deficiencies, it may also create a separate Deficiencies task. Resubmitting updates the visit's existing Jobs task in place - it never creates a duplicate. By default you can edit and resubmit the summary until the end of the visit's day, and summaries from yesterday or earlier cannot be edited from mobile. If your office sets **Days in the past technicians can see** in Settings -> Team -> Technician App, you can reopen visits inside that window and add or correct their summaries too; for anything older, send updates to the office directly. > **Where to find it:** Mobile app > Visits > visit detail > Add Summary or Edit Summary ## Related guides * [Complete services and invoice items on mobile](/field-operations/mobile/complete-services-and-invoice-items.md) * [Add files, notes, and access info on mobile](/field-operations/mobile/add-files-notes-and-access-info.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/add-a-visit-summary.md?ask=&goal= ``` `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.