> 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 also provide custom closeout statuses and show extra fields based on the status you choose. ## Add notes and supporting records Enter Visit Notes. Once you're online and have typed a note, tap **Suggest** to open the **Suggest note** sheet and 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. Before the first summary submission, the current visit's work acknowledgment can prefill empty Visit Notes and suggest invoice items. Review the notes, part numbers, and quantities before saving. Documents that finish loading while the summary is open can fill an untouched draft; they will not overwrite notes or item quantities you have edited. Existing Visit Notes stay in place, so update them if the acknowledgment describes newer work. When editing a summary that has already been submitted, review and correct its notes and recorded items directly. Acknowledgment notes and items are not imported again automatically, even when the saved summary is blank. ## Record deficiencies If your office turned on **Record deficiencies** in Settings -> Team -> Technician App -> Job summary, the summary has a **Deficiencies** section. Tap **Add** next to it, then pick the **Asset group** (or **Another type — not set up on this property** and its type — Essential creates the group when you submit), optionally the **Asset**, enter the customer-facing **Description of defects or malfunctions**, add optional **Internal notes about the deficiency**, and add **Photos** (take or select photos and videos, the same picker as an inspection report deficiency). Tap **Add** again for more, or the trash icon to drop one. Every deficiency needs its asset group and customer-facing description before you can save, and photos and videos must finish uploading first. Submitting creates a Deficiencies task for the office for each asset group, and the photos and videos are saved with the job's files. The section starts empty each time you open the summary — editing the summary later only adds the new deficiencies you record then. When you edit a summary and add deficiencies, the app saves the update on your device before syncing it to the office. Pending updates resume automatically if the connection drops or you restart the app. Let syncing finish before expecting the new tasks to appear in the office. ## 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. For a service that uses due-date mode with a single cadence shared by every schedule of that service, tap the enabled service card before submitting. Choose **Move to \[date]** to move the next due date forward by one full service interval, or choose **Choose another date** to open the date picker. Either choice moves that service's fixed due-date grid. Service-completion schedules remain read-only here because their next due date is calculated from the completion date, and so does a due-date service whose schedules use different cadences (for example, a 1-year and a 5-year test on the same service) — editing stays disabled there since one picked date can't mean the same thing for all of them. Review the due-date choices, invoice items, and any custom fields. A **Suggestions for your review** box appears at the top of the summary when there's something to flag. Tap Save & Submit to Office when ready; there is no additional checks screen or required override reason. Tap **Review** beside a suggestion to open the inspection report or supporting records. Photo, billable-item, and work acknowledgment suggestions appear only when at least 95% of 20 or more past visits of the same type included them. Service completions do not produce suggestions: your business may record them through inspection reports or summary submission. An admin can turn these suggestions off under Settings -> Work Management -> Visit checks (the **Job Summary suggestions** switch). Missing-report suggestions include the trade and visit type, such as **Kitchen Suppression - Inspection**, so reports for different trades are easy to distinguish. 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, and any deficiencies you recorded in the Deficiencies section become their own Deficiencies tasks. 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 -> Scheduling, 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) * [Configure Technician App behavior](/administration/settings/require-photo-names-and-swipe-to-pass-fail-assets.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) When Visit checks is active, review missing work before saving or submitting. See [Review visit checks](/customers-and-work/scheduling/review-visit-checks.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/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 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.