Tenders and schedules of works are rarely written as a rhythm. They say two cuts a month April to September, one in October, litter picked every month, hedges twice a year — a count per task per month. Working backwards from that to "every 3rd visit from visit 2, March to October" is arithmetic nobody should have to do, and it is easy to get wrong.
So you can type the counts instead. On Contracts → New contract, at the work step, answer "Do you know how many visits for the year?" with Yes and you get a grid: tasks down the side, months across the top, a number in each box.
Tasks share a day. Six cuts and nine litter picks in a month is nine visits, not fifteen — the busiest task sets how many days the crew is on site and the others ride along. That is what the "visit days" figure under the grid counts. If a task genuinely needs its own trip, tick needs its own day on its row.
The count is the promise. It is what the client is buying, so SwardOps never quietly drops one to make the spacing work. You can set a minimum gap (so two cuts can't land in the same week) and the dates move to respect it. You can also set a maximum gap, but that one only warns: closing it would mean adding a visit the client hasn't paid for, which is your call, not ours.
It prices itself. Each row takes a price per visit, and the total is that price times the visits the term actually buys — shown live as you type, and written onto the contract when you create it. The quote itemises the same way: Grass cutting (13), 13 × £85.
When you award it, the whole term lands on the schedule in one go — not just the next few weeks — because a grid can legitimately have nothing in the next two months and a full programme after that.
Prefer a rhythm? Answer No and the builder works exactly as it always has. The question is only asked because both ways are right for different contracts.