> 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/assets/set-up-recurring-services-on-an-asset-group.md). # Set up recurring services on an asset group Recurring services are the scheduled, repeating work for a piece of equipment, for example an annual inspection, and you set them up per asset group. On the asset group page, the Recurring Services card identifies each schedule by its service name and reads "No recurring services" when there are none; use Add to create one and choose how often it repeats. The Automation Setup card controls what goes out for that schedule (an email, a text, or a custom task), and Next Automation shows the next time it will run. These schedules generate recurring service requests or internal tasks for this equipment; approved work is then scheduled as a visit from the resulting task. > **Where to find it:** On the asset group page, the Recurring Services card (right side), the Add link ## Related guides * [Set or change an asset group's automation (Automation Setup)](/field-operations/assets/set-or-change-an-asset-groups-automation-automation-setup.md) * [Setting up a recurring service in depth: frequency, automation, rounding, and the asset filter](/field-operations/assets/setting-up-a-recurring-service-in-depth-frequency-automation-rounding-and-the-asset-filter.md) * [Add or bulk-add assets to an asset group](/field-operations/assets/add-or-bulk-add-assets-to-an-asset-group.md) * [Asset groups and assets: terminology and screen labels](/field-operations/assets/assets-vs-asset-groups-vs-asset-items-the-terminology.md) * [Deleting an asset group (and what it removes)](/field-operations/assets/deleting-an-asset-group-and-what-it-removes.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/assets/set-up-recurring-services-on-an-asset-group.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.