For the sprinkler system owner

One sprinkler system on the board, six zones off the valve box at the side of the house. The fall blowout / winterize each year on October 15, on a calendar line. The spring start-up each year on April 15, on its own line. The backflow preventer test each year on June 1, the line the water district's certificate hangs on. The controller battery swap each April 1. The rain sensor check each May 1. And the head/nozzle check one line per zone: Zone 1, the front lawn rotors, through Zone 6, the drip on the garden beds. That is the whole list, and it lives on one due board.

You know the last blowout. Front Range Irrigation came on October 14, 2025, hooked the compressor to the valve box, blew each zone clear until the heads spat air, and the invoice said $95. Say that once to Muse in the chat you already have open and the row is written, shop and cost on it. Each year on October 15 puts the next blowout at October 15, 2026, and the board counts the leftover days on the calendar: 10 days left as of October 5. Book the truck for that week and the lines go into winter dry.

You know the other dates too. The start-up went April 14, 2026, and one year puts the next on April 15, 2027, with 192 days left as of October 5: valve on, zones run one at a time, heads re-aimed, nozzles watched for misting. The backflow preventer was tested May 28, 2026 for $45, and the tester filed the certificate with the water district; each year on June 1 puts the next test at June 1, 2027, with 239 days left, the certificate on its own line next to the cost.

Before the first freeze, ask Muse what's due on the sprinkler system. The blowout comes back with October 15 and the 10 days. The start-up comes back with April 15, 2027 and the 192 days. The backflow test comes back with June 1, 2027 and the 239 days. The zone checks come back six rows, one per zone. The board subtracts on the calendar and names what is left, and no row sits in the due path. You asked in the chat you already have open. There is no day-to-day owner app to click.

The calendar lines keep their dates. The blowout is each year on October 15, because the blowout counts before the first hard freeze, and the board does not slide the date because October got busy. And a season missed stays missed: if October 15 comes and goes without the blowout, the line stays due past New Year's instead of quietly resetting, still on the board in January, late since October 15, until you log it. When the truck finally comes in April and you log that blowout, the visit counts once: it pays the missed season, and the next blowout still comes due the coming October 15, not a year later. These are the cadences you told Muse, not spec-sheet promises.

The zone checks ride one line per zone. Zone 1, the front lawn rotors. Zone 2, the back lawn rotors. Zone 3, the spray heads on the side yard. Zone 4, the sprays on the shrub beds. Zone 5, the drip line in the vegetable garden. Zone 6, the drip on the garden beds. Each is due May 10, one walk of the yard with the controller running a zone at a time: watch each head, clean the clogged nozzles, open the valve box and look for a weeping seal. Say which zones you checked and one ask writes all six rows. The small rows live there too: the two AAs behind the controller door each April 1, and the rain sensor each May 1, cottonwood fluff brushed off, sensor tripped, zones standing down while it rains.

The system gets the walk-the-yard habit too. When you close the controller, tell Muse what the walk surfaced, in the same breath as the date: a Zone 3 head leaking at the seal, a nozzle on Zone 1 misting, the drip filter on Zone 6 clogged again. Muse keeps each one as a note on that line, so the repair history rides with the system instead of on a spiral notepad in the garage drawer. Fold the notes into the zone check. The board keeps the lines, and the habit keeps them honest between them.

The board can call ChatGPT too. Subscribe once and ChatGPT hears before the freeze: the blowout line lands on the due board and a signed webhook names the job, so you are not carrying the October date around in your head. An agent that speaks MCP can hear the same board. You did not have to ask first.

Every row you log stays in the service log: blowouts with shop and cost, start-ups, backflow tests with the certificate date, battery swaps, zone checks. So the day the house sells, say it once: sold. Muse archives the sprinkler system and the due board drops it that day, and the history stays: years of blowout dates, what each cost, who came out, the backflow certificates by year. Hand that history to the buyer. If the deal falls through, one ask puts the system back on the board.

One line, said plainly: Maintenance Due is a personal due board and service log for your sprinkler system. It is not a backflow-certificate filing tool, a cross-connection-control program, or a licensed irrigation contractor; it files nothing with the water district and clears nothing with anybody. The tester files the certificate; the district's rules are yours to follow. The board counts the calendar days you tell it and keeps the notes you give it.

The house log on /home-maintenance-checklist shows how calendar rows look. Copy the prompt on /for-your-agent and paste it into Muse. Free.