> 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/what-a-service-completion-is-and-how-its-recorded.md). # What a service completion is and how it's recorded A service completion records that recurring service work was performed. It clears **Awaiting Service Completion** and recalculates the next due date. With **Service Completion driven**, the latest completion plus the schedule frequency determines the next due date. With **Due Date driven**, the completion satisfies a particular due occurrence and future dates stay on that grid. Month rounding and postponement can also change the displayed result. Scheduling a covering visit clears the due-date override when it arms Awaiting Service Completion. For a fixed schedule, a report keeps two dates when needed: the actual date the work was performed and the due occurrence it satisfied. Essential advances past elapsed grid points and uses the first scheduled occurrence after the actual work date as the next due date. A later one-time due-date override can delay the displayed date, but an earlier override does not pull the fixed grid forward. Completing the service clears that override. The usual path is to publish the inspection report from its visit. Reports published directly from the mobile Reports tab record no service completions. A Pass/Fail (compliance) answer normally logs it for services mapped to the report's visit type (set under Service Visit Types in Settings), so if a Pass/Fail report doesn't clear "Awaiting Service Completion", check that mapping. A service a technician marks Done on the report is not gated this way and normally completes when marked Done. A date explicitly chosen for the service on this report can preserve or create its completion even when the answer itself is not mapped to the visit type. For services that do not require a report, you can turn on **Create *****service name***** completions on Job Summary submission** under Settings -> Service Visit Types. Before the first submission, the technician reviews selected services under **Next Due Dates**. Essential creates one completion per applicable asset unless that visit or report already supplied the authoritative date. In completion-based mode it uses the visit date. In fixed-schedule mode it satisfies the current raw grid occurrence while retaining the visit time as the actual work time; the technician can tap an enabled service card to choose a different next grid date. A populated group with no applicable assets is left unchanged. Clocking out alone does not trigger this option. An empty asset group has no asset completion. Its schedule can advance from the visit date, except when a report already owns its date or a later stored date must be preserved. Awaiting Service Completion is still cleared for the matched schedule. You can also set the date by hand. Open the asset (**Edit Asset**) and set its " Last Date" field, or edit the recurring service. Completion-based schedules show **Last Service or Installation Date**; fixed schedules show **Last Due Date** — enter the grid occurrence that was most recently due, and the next due date lands one frequency after it. A service question answered **N/A** goes the other way: when the report is published from its visit, it deletes that asset's completion history for the service. Other applicable assets, the schedule's fallback date, or a due-date override can still keep the service due. See [Require a service completion date, and mark a service N/A](/field-operations/inspection-reports/require-a-service-completion-date-and-mark-a-service-not-applicable.md). Once a service completion exists—or the recurring schedule advances directly for an empty group—the schedule resumes. The next cycle starts from either the new last service date or the satisfied fixed-grid occurrence, according to the schedule's setting. A completion is not the only way to resume: you can clear Awaiting Service Completion directly without recording work, and removing scheduled coverage may offer choices to keep the schedule paused or restart its automation. > **Where to find it:** Recorded by an inspection report, an opted-in matching visit's Job Summary submission, or by editing the Last Date on the asset or recurring service ## 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) * [Visit types: which services an inspection report can complete and reset](/administration/how-recurring-service-automation-works-the-full-cycle/visit-types-which-services-an-inspection-report-can-complete-and-reset.md) * [Custom fields: your business's extra fields on records](/administration/basics/custom-fields-your-businesss-extra-fields-on-records.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) --- # 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/administration/how-recurring-service-automation-works-the-full-cycle/what-a-service-completion-is-and-how-its-recorded.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.