> ## Documentation Index
> Fetch the complete documentation index at: https://help.sweeply.dk/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand recurrence and task cadence

> Use the base order cycle, cycle start week, and task multipliers to model recurring work.

The subscription creates base order occurrences. Each task then decides whether it participates in every occurrence, a repeated multiple of the cycle, or only on request.

## Base order cycle

The **Order cycle** is the number of weeks between base visits. The **Cycle start week** anchors that sequence.

Example: a four-week cycle anchored in week 10 produces base occurrences in weeks 10, 14, 18, and so on.

## Task frequency

| Task setting       | Result on a four-week base cycle |
| ------------------ | -------------------------------- |
| Every cycle        | Every 4 weeks                    |
| Every second cycle | Every 8 weeks                    |
| Every third cycle  | Every 12 weeks                   |
| On request         | No automatic generated task      |

Each task can have its own first week while remaining aligned to the base cycle. This lets related services rotate without creating several subscriptions.

## Example: rotating interior work

A customer receives exterior cleaning every four weeks and interior cleaning every second visit:

* Base order cycle: 4 weeks
* Exterior task: every cycle
* Interior task: every second cycle
* Cycle start week: the first agreed exterior visit
* Interior first week: the first visit that should include interior work

## Planning requirements are separate

Cadence determines **which target week** needs a visit. Days, time windows, and preferred members determine **where the route planner may place it inside that week**.

<Warning>
  Changing the cycle or anchor week can realign multiple future orders. Review the update confirmation before saving an active subscription.
</Warning>