> 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/customers-and-work/jobs/recurring-service-completions-on-a-job.md).

# Recurring service completions on a job

The Recurring Service Completions card on the job page shows the recurring services that were completed against the property's assets during this job's visits. It is grouped by asset group, so you can see at a glance which set of equipment was serviced.

Within each group, every recurring service appears with its frequency, followed by how many assets were serviced out of the total in that group, shown as something like 3 of 8 Serviced.

When upcoming work is due, the card also shows the next due date for that service and how many assets share that earliest due date. The asset group heading links to the asset group itself if you want to see the full equipment list and details.

This card is a read-only summary of service activity tied to the job; the completions themselves are recorded through the visits and the technician's work, not edited here. For a service on a fixed due-date schedule, the recorded completion can satisfy a scheduled occurrence that differs from the actual work date; the upcoming date still follows the fixed grid. Asset groups appear in this card only when they have at least one service completion attributed to this job, so a property's other equipment will not clutter the view.

If no recurring services were completed on the job, the count at the top of the card reads zero and no groups are listed.

> **Where to find it:** Open a job from Scheduling > Jobs; see the Recurring Service Completions card on the right side of the job page

## Related guides

* [Clock in and clock out records on a job](/customers-and-work/jobs/clock-in-and-clock-out-records-on-a-job.md)
* [Job inventory: reserved vs used parts, transfers, and shortages](/customers-and-work/jobs/job-inventory-reserved-vs-used-parts-transfers-and-shortages.md)
* [Link quotes and invoices to a job](/customers-and-work/jobs/link-quotes-and-invoices-to-a-job.md)
* [The job detail page: what it shows](/customers-and-work/jobs/the-job-detail-page-what-it-shows.md)
* [What is a job, and how does the Jobs list work?](/customers-and-work/jobs/what-is-a-job-and-how-does-the-jobs-list-work.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/customers-and-work/jobs/recurring-service-completions-on-a-job.md?ask=<question>&goal=<user_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.