Work that comes round every year

More, then Schedules. Enter a job that repeats, say how often, and the work order creates itself when it is due and lands in the list with everything else. Nobody has to remember, which is the entire point.

What belongs here

The jobs that get skipped because they are nobody's emergency. Gutters twice a year, not once, because the second clean feels unnecessary until it is not. The backflow certification your county wants. The irrigation shutdown before the first freeze, written as its own job rather than folded into a vague autumn task. Anything a departing board member currently carries in their head.

When it appears

The job is created on its due date and behaves like any other work order from then on: assign it, add a cost, close it. The dashboard surfaces scheduled work that is past its date, so a missed one shows up rather than sitting quietly.

Never stack duplicates

If a job is still open when the next one is due, you get one job, not two. A schedule that quietly built a pile of identical open jobs would be worse than no schedule.

Changing or stopping one

Open the schedule and edit it, and the change applies to jobs not yet created. Removing a schedule leaves the jobs it already made alone, so your history stays intact.