A round keeps the same frequency for its life, so you don't change a round's rhythm halfway through the year — you give the site more than one round, each with its own season, and let the dates hand over between them.
On a contract. In the builder, under the site's regular visit, there's + Different rate for part of the year. Add one per change of rhythm. A typical grass contract:
- Fortnightly — 1 Mar to 31 Mar
- Weekly — 1 Apr to 30 Jun
- Fortnightly — 1 Jul to 31 Oct
They all sit on the one contract, so the client still gets one contract and one invoice — only you know it's three rounds behind the scenes. The quote's visit count adds them up, so the price reflects the real number of cuts.
On a round you already have. Same idea without the builder: set the season on the existing round, then add the others from the site (New round) and tick the box to link it to the contract. They'll show on the contract and be costed against it.
The rules worth knowing:
- Don't let the seasons overlap. 31 Mar then 1 Apr is right; if two rounds both cover the 31st you'll get two visits that day and it'll be counted twice in the price. The builder warns you and names which two clash.
- A round with no season set counts as all year, so it clashes with everything — give every round its own window once you have more than one.
- Seasons are day and month only. The year is ignored, so you set it once and it repeats every year. A window can cross new year (1 Nov to 28 Feb) perfectly well.
- Set each round's start date to the day you want its first visit. The season hides visits outside it rather than restarting the rhythm, so if your last weekly cut is 29 June and the fortnightly round starts on 1 July you'll get one two days later. Start it the 13th and the handover is a clean fortnight.
- Tasks on "every Nth visit" are counted against the main round. A hedge cut set to every 4th visit comes round monthly on a weekly round and every two months on a fortnightly one. If a task needs its own rhythm regardless of season, give it its own line with its own dates instead — the builder flags this when it applies.