> 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/setting-up-a-recurring-service-in-depth-frequency-automation-rounding-and-the-asset-filter.md).

# Setting up a recurring service in depth: frequency, automation, rounding, and the asset filter

Adding a recurring service to an asset group opens a dialog with a handful of settings that together decide when the service comes due and which assets it covers. Service Type picks which service this schedule performs.

Occurs Every sets the frequency as a number plus a unit (Day, Week, Month, Quarter, or Year), so 6 Months or 1 Year. **Recurring Mode** then chooses how that frequency advances (hover the label in the dialog for a quick reminder):

* **Service Completion driven** is the standard behavior. Each completion becomes the starting point for the next due date.
* **Due Date driven** keeps the service on its due-date grid. Finishing work early or late satisfies one scheduled occurrence without permanently shifting every future occurrence.

Your business can set a default Recurring Mode for new recurring services, and can hide this selector entirely so every new schedule uses the default — both from the **Recurring Mode** card on the Recurring Service Templates settings page. Hiding the selector doesn't change existing schedules; they keep the mode they were saved with.

Can Trigger Automation? decides whether this schedule feeds your automated outreach: Yes lets it drive automation, No marks the timing as flexible so it tracks a due date but will not kick off automated outreach on its own.

The date field follows the selected mode. **Last Service or Installation Date** is shown when the schedule advances from completed work, and the frequency is added to that date. **Last Due Date** is shown for a fixed schedule and anchors its grid: enter the occurrence that was most recently due, and the next due date lands one frequency after it. Round Due Date can snap that due date to the beginning or the end of the month, or leave it exact, which keeps due dates tidy on monthly or quarterly cadences.

In fixed-schedule mode, moving the one-time due-date override earlier than the grid does not pull the service forward; a later override can delay the displayed due date. Postponement is applied after that calculation. When work is completed, Essential advances past elapsed grid points and uses the first scheduled occurrence after the work date as the next due date.

The Asset Filter controls scope. With no filter, the service applies to every asset in the group. Add Filter lets you build a condition on asset type and attributes so the schedule applies only to matching assets, and the dialog shows a live count of how many assets currently match.

If a group has assets but none match the filter, the service shows **Never Due (no matching Assets)** until a matching asset exists. Editing an existing service saves only what you changed.

> **Where to find it:** The Recurring Services card on an asset group; click Add (or Edit on an existing service) to open the Add Recurring Service dialog.

## Related guides

* [How recurring service automation works (the full cycle)](/administration/how-recurring-service-automation-works-the-full-cycle.md)
* [Recurring service templates and template groups](/field-operations/assets/recurring-service-templates-and-template-groups.md)
* [Set up recurring services on an asset group](/field-operations/assets/set-up-recurring-services-on-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)
* [Manually trigger or delay an asset group's automation](/field-operations/assets/manually-trigger-or-delay-an-asset-groups-automation.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/setting-up-a-recurring-service-in-depth-frequency-automation-rounding-and-the-asset-filter.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.