Work that comes back, booked before you forget it
Annual furnace service. Quarterly filter change. The twice-a-year gutter clean. Set it up once and RadiusOS makes the job a couple of weeks before each one is due, so it lands on your list instead of in your memory.
Why this is worth the two minutes
Repeat maintenance is the steadiest money a trade makes and the easiest to lose. Nobody forgets a job a customer just called about; what gets forgotten is the one that was due eleven months after the last visit, on a week you were busy.
The fix is not a reminder. A reminder tells you to do something and then it is gone. This puts a real job on your job list, with the address and the unit already on it, at a point where you still have time to call and book it.
Setting one up
Open the address and use Set up recurring work in the Recurring work section. It needs three things and defaults the rest.
What it is
"Annual furnace service", "Quarterly filter change". This becomes the title of every job it makes, so write it the way you'd want to read it on a job list.
How often, and when the next one is due
Monthly, quarterly, twice a year, or once a year. The due date is the only thing RadiusOS can't work out for you. A date in the past is fine - the job appears on the next overnight run.
Which unit, if it's about one
Tying it to a specific furnace or heater is what gives that unit a service record you can show a customer four years later. Leave it blank if the work is about the whole place.
The lead time is set to 14 days and that's usually right. Long enough to phone the customer and find a slot, short enough that your job list isn't full of next quarter.
What happens then
Every night RadiusOS looks at what's coming due. When one is inside its lead time, it makes the job: same title, same address, same unit, sitting in your job list as a new lead. The job says where it came from, so you know it wasn't booked by a person.
Then the next due date moves on by itself. You don't touch the agreement again unless something changes.
The job is a lead, not a booking. Nobody has spoken to the customer yet - that's your call to make, which is the whole reason it appears two weeks early.
If it can't make the job
Free keeps five jobs open at a time. If you're at five when one comes due, RadiusOS doesn't make the job and doesn't move the date on either. The agreement shows "Waiting" with the reason, and the job gets made the moment you finish something and free a slot.
The point of that is what doesn't happen: the visit is never quietly skipped. A schedule that silently drops an occurrence is worse than no schedule, because you'd have no way to know.
Pausing and stopping
Pause is the normal way to stop one: the customer didn't renew, the building is empty for the winter. No new jobs get made, everything it already made stays exactly where it is, and Resume picks it back up.
Delete is underneath the pause box, for the one you set up twice by mistake. Jobs it already made keep their own records; they just stop saying where they came from.
Asking your assistant instead
If you've connected RadiusOS to Claude, ChatGPT or Cursor, "what maintenance is coming up?" answers from the same list. It tells you if anything is waiting on a job slot too, rather than reading back a schedule that isn't actually running.
Plans
Recurring work is on every plan, including Free. What limits Free is the same five-open-jobs ceiling as everywhere else, and the agreement tells you when it's hit rather than skipping. Paid plans have no ceiling, so agreements just run.