Every grounds contract needs two schedules: the year planner (what happens in which month) and the week board (who's where on Tuesday). Most templates you'll download only do the first. Here's a working version of both.
The UK grounds year, month by month
January–February — machinery servicing window: mower blades, LOLER/PUWER inspections, winter repairs. Tree work while dormant. Gritting on triggers. Plan the season's contracts and pricing.
March — first cuts as growth starts (regional: south typically mid-March, north later). Beds: mulch and edge. Spring fertiliser/moss treatments begin. Line marking: pre-season initial marks for summer sports get planned.
April–May — mowing steps up to full frequency (fortnightly domestic, weekly fine turf). Summer sports changeover: cricket squares in play, athletics tracks and summer layouts marked. Hedge trimming checks for nesting birds first — active nests are legally protected.
June–July — peak cutting. Watering programmes for new planting. Weed control rounds. School grounds: the summer-holiday works window gets booked NOW (renovations, big jobs while sites are empty).
August — school renovation window: pitch repairs, scarifying, seeding before autumn term. Hedges (post-nesting main trim). Plan winter services sales.
September — autumn renovations: aeration, scarification, overseeding, autumn feed. Winter sports changeover — football/rugby pitches initial-marked. Sell gritting contracts.
October — final regular cuts as growth slows. Leaf clearance begins in earnest. Machinery: post-season service list starts.
November–December — leaf clearance peak, then winter pruning, gritting season live, hedge reduction work, machinery deep maintenance. Quiet-season projects: fencing, landscaping builds.
From year planner to week board
The year planner sets frequencies per season; the week board is where it becomes real. The mechanics that matter:
- Anchor each round to a repeat pattern (weekly, fortnightly, every N weeks) with a season window — so mowing generates visits March–October and stops itself in winter.
- Tasks within a round can have their own seasons — the same fortnightly school round carries mowing all season but line marking only in term-appropriate windows.
- Weather moves things — the board must make it a 10-second job to slide Tuesday's rained-off round to Thursday without retyping anything.
- Catch-ups must be visible — a skipped element (too wet to mark lines) should reappear on the next visit automatically, not live in someone's head.
You can run this on a wall planner and a spreadsheet. The failure mode is that the two drift apart — the wall says fortnightly, reality says "when we got there". Purpose-built scheduling ties the year pattern to the live board so the season generates the visits and the visits record what actually happened; that's the core of SwardOps, where a round set to "fortnightly, March–October" builds its own season and the crew's phones tick it off visit by visit.