> 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/administration/how-recurring-service-automation-works-the-full-cycle/visit-types-which-services-an-inspection-report-can-complete-and-reset.md). # Visit types: which services a visit or inspection report can complete A visit type is a named kind of visit - for example a Fire Extinguisher Inspection - usually tied to an equipment type. Visit types are managed in Settings -> Scheduling -> Visit Types. They matter for automation because they control which recurring services a Pass/Fail answer on an inspection report can complete. On the Service Visit Types page in Settings you map each service to its visit type(s): a service can be mapped to specific visit types, or to All visit types (a wildcard that always applies). Each service also has an optional **Create *****service name***** completions on Job Summary submission** switch. Every recurring service schedule is set with a visit type, and the visit you schedule for the approved work carries that visit type. When an inspection report is submitted, a Pass/Fail (compliance) answer records a service completion only for services that match its visit type through that mapping (or, when the report has no linked visit, the All-visit-types services for its equipment type). By default, that report-based behavior is unchanged. If **Create *****service name***** completions on Job Summary submission** is turned on for a service, submitting the Job Summary for a matching visit records that service as complete for each applicable asset at the property—even when the visit has no inspection report. If the matching asset group has no assets, Essential instead advances the recurring schedule from the visit date because there is no asset on which to record a completion. Both paths clear Awaiting Service Completion and advance the next due date by the recurring frequency. A populated group with no applicable assets is left unchanged. Clocking out alone does not trigger this automation; if no Job Summary is submitted, the service does not advance. A service a tech instead marks Done on the report is not gated this way - it always completes its service when marked Done. That service completion is what resets the recurring-service cycle: it becomes the new last service date, clears Awaiting Service Completion, and sets the next due date to the last service date plus the frequency. If a Pass/Fail report isn't clearing Awaiting Service Completion, check that the service is mapped to that visit type. If a visit without a report should clear it, check the mapping, that service's **Create *****service name***** completions on Job Summary submission** switch, and whether the Job Summary was submitted. > **Where to find it:** Settings -> Service Visit Types maps each service to its visit type(s) and controls whether submitting a matching visit's Job Summary can complete it without a report ## Related guides * [How recurring service automation works (the full cycle)](/administration/how-recurring-service-automation-works-the-full-cycle.md) * [What "Awaiting Service Completion" means and how it clears](/administration/how-recurring-service-automation-works-the-full-cycle/what-awaiting-service-completion-means-and-how-it-clears.md) * [What a service completion is and how it's recorded](/administration/how-recurring-service-automation-works-the-full-cycle/what-a-service-completion-is-and-how-its-recorded.md) * [Add, edit, or disable visit types](/administration/settings/add-edit-or-disable-visit-types.md) * [Custom Task automation: an internal task instead of customer outreach](/administration/how-recurring-service-automation-works-the-full-cycle/custom-task-automation-an-internal-task-instead-of-customer-outreach.md) * [How automated outreach batches are built and who they go to](/administration/how-recurring-service-automation-works-the-full-cycle/how-automated-outreach-batches-are-built-and-who-they-go-to.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/administration/how-recurring-service-automation-works-the-full-cycle/visit-types-which-services-an-inspection-report-can-complete-and-reset.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.