Task schedules
Every task group and task template carries a schedule. The schedule does not decide when someone visits - that is the estate’s service schedule - it decides which of those visits the task appears on.
The modes
Section titled “The modes”Under How should it repeat? you pick one of these cards, plus Same as its group on a template that belongs to a group. By readings or dates is offered on tasks only, not on task groups. Below the cards, only the settings for the one you picked are shown, with a line saying in plain words when the task will come up.
| Card | Meaning |
|---|---|
| Every visit | The task is on every visit the estate’s schedule produces. This is the default, except on an asset that tracks readings. |
| Certain months | The task is only on visits that fall in the months you tick. |
| Every few weeks or months | The task is due on a cadence of its own, and lands on the first visit on or after each due date. |
| By readings or dates | The task comes up once time has passed or an asset’s reading has grown by an amount since it was last done, such as every 5,000 mi or 6 months, or ahead of a date such as the warranty end. A new task on an asset that tracks attributes starts on this card. |
Certain months
Section titled “Certain months”Tick the months the work applies to. A task set to Nov, Dec, Jan appears on every visit in those months and on none of the others - which is what makes a “Seasonal - Winter” group work on an estate that is visited weekly all year.
Every few weeks or months
Section titled “Every few weeks or months”This card reads as one sentence: Repeat every 3 months counted from when it was last done, Starting a date.
- The number and weeks or months set the cadence.
- counted from is when it was last done or a fixed start date.
- Starting is the first date the task can be due. It is required, and with a fixed start date it is also the origin the grid is measured from.
when it was last done counts the interval from the day the task was last completed or skipped, so a task that slips stays that far behind. a fixed start date keeps due dates on the same grid regardless of when the work actually happened.
Either way the task fires once per due date: it appears on the first visit that covers that date, not on every visit after it.
By readings or dates
Section titled “By readings or dates”Each condition under Repeat when reads as a sentence: Time passes 6 months, a number reading goes up by an amount (Odometer goes up by 5,000 mi), or a date is a length of time away (Warranty end is 30 days away). The date is a date reading or the asset’s Warranty end. Select Add another for more, up to five. With two or more, Whichever comes first brings the task up as soon as one is met, and Only when all are met waits for every one.
A reading’s amount must be above zero. Time is counted in whole days, weeks or months, from 1 up to 3,650 of them; a date may be 0 (the day itself). The dialog says which condition to fix before you can go on.
Conditions count from the last time the task was completed or skipped on that asset, using the readings saved at that moment. On a visit that spans several days, a completed task counts from the day it was checked off, and a skipped one from the visit’s first day. A task that has never been done comes up on the next visit, unless it was created with When was it last done? set to I know. A date condition is different: it waits for its day, and once the task is done it stays quiet until the date moves later. The day the conditions are met, the task appears on the Tasks page, assigned to the task’s default assignees or the estate concierge, and on the next visit as open work. Readings are only known as of today, so it is not shown on later visits in the preview.
Readings come from the asset the task lands on: an asset task uses that asset’s readings, and a library template uses the readings of the class under Which assets get it?.
Active dates and conditions
Section titled “Active dates and conditions”These settings apply to every card. When you add a task they are on the last step; select Change beside Active to set the dates.
| Setting | Effect |
|---|---|
| Starts | The task does not appear on visits before this date. On Every few weeks or months this is the Starting date next to the cadence. |
| Ends | The task stops appearing after this date. Leave it blank and the task recurs indefinitely. |
| Only when the estate has a | Library tasks and groups only. Pick an asset class and the task only applies to estates that actually have an active asset of that class. |
That last one is worth a moment: it is the difference between “pool opening” being planned for an estate with a pool and being silently skipped on one without. It is not the same as Which assets get it?, which decides how many tasks a template creates once it does apply.
Examples
Section titled “Examples”Assume an estate visited every week.
| Schedule setting | When the task appears |
|---|---|
| Every visit | Every week. |
| Certain months: Dec, Jan, Feb | Every week during December, January and February; never otherwise. |
| Every 1 month counted from a fixed start date, starting 1 March | On the first visit on or after 1 March, 1 April, 1 May, and so on. |
| Every 3 months counted from when it was last done, starting 1 March | First on the first visit on or after 1 March. If it is completed on 12 March, next due 12 June; if that one is completed on 30 June, next due 30 September. |
| Every 2 weeks, ends 30 June | Every other week, then nothing from 1 July. |
| Every visit, only when the estate has a Pool | Every week, but only on estates that have an active Pool asset. |
| By readings or dates: Odometer goes up by 5,000 mi or Time passes 6 months, whichever comes first | On the first visit after the car has done 5,000 mi since its last oil change, or 6 months have passed, whichever comes first. |
Carryover
Section titled “Carryover”A task that is still open when its visit is closed out does not vanish. It carries onto the next visit, and the preview shows it under Possible carryover until the earlier visit is actually closed. Work that has carried so far that it no longer suits the season it landed in is separated out under Needs attention, on both the preview and the estate’s Tasks tab, so someone decides about it rather than letting it drift forward forever.

