The wall planner falls over somewhere around forty sites

A wall planner is a beautiful thing at ten sites. You see the whole month at a glance, the colours mean something, and when a job moves you move a magnet. It keeps working right up until it doesn't, and the point where it stops is not gradual. Somewhere around forty sites the arithmetic of recurring compliance work overwhelms any surface a single pair of eyes can scan. The failure is quiet. You don't notice the schedule has stopped coping until an audit or a breach makes it obvious, by which time the gap is months old.

Here is the arithmetic, because it is the whole argument. Take forty sites on a standard HSG274 Part 2 regime: monthly sentinel temperatures, a quarterly showerhead clean, a quarterly rotating set of representative outlets, annual inspections of tanks, calorifiers and TMVs. Count only the dated jobs that have to land on an engineer's calendar and you are already past nine hundred a year. Add weekly flushing of little-used outlets, where that duty is yours rather than the site's, and it is another two thousand-odd on top. Each monthly visit is itself six or more readings once the engineer is standing at the outlet. The wall planner shows you none of that detail. It shows you a month, and a month is not where compliance work lives.

Where the sheet actually breaks

The spreadsheet lasts longer than the wall planner and hides its failures better, which is worse. Teams describe the same slow slide every time. The workbook grows a second tab, then a fifth, then a colour code only the person who built it can read. That person takes leave in August, the monthly round slips to six weeks because no one else can tell which cells are due, and nobody is certain which copy is even current once two people have edited two versions. Planned maintenance gets missed, quietly, every week.

The reason is structural, not a matter of discipline. Static, manual scheduling works on paper and falls over in real field operations, because a spreadsheet is a snapshot and compliance work is a moving system. Every recurrence is attached to a different asset on a different clock. A snapshot cannot track that without a person redrawing it by hand, and the redrawing is the job that slips first when the week gets busy.

Why you can't see the break coming

The cruel part is the timing. A schedule that is quietly failing looks identical to one that is working, right up to the moment someone asks it a hard question. The visits that did happen are all present and correct. The engineer's readings are fine. What is missing is the visit that never got booked, and a missing thing is exactly what a glance cannot catch. You scan the planner, everything you can see is done, and the outlet whose quarterly clean fell off the list eight months ago is not on the planner to be seen. The break announces itself on someone else's schedule: an assessor's audit, a client's compliance review, an outbreak investigation. By then you are explaining a gap, not preventing one.

One missed task is not one missed task

Lose track of a single planned job and you have not lost a single job. You have risked an unhappy customer, a breach of contract, or a genuinely dangerous situation, and with legionella the third of those is not hypothetical. The monthly temperature round that slid to six weeks is now a gap in the record, and monitoring records have to be kept for at least five years. A gap in a five-year record is precisely what an assessor reads as a finding. The wall planner never warned you, because a planner has no memory of what should have happened and didn't.

What a real schedule has to know

The thing a planner or a sheet can't do is hold the state of the work. A schedule that survives forty sites has to carry, at minimum, four things:

• Recurrence per task, per asset. Not "this site is monthly" but "this calorifier is annual, these four sentinel outlets are monthly, those showerheads are quarterly." The unit is the asset, not the site.
• Who is free to do it. A due date is worthless if the only engineer who covers that postcode is booked solid that week. Availability is part of the schedule, or the schedule is a wish list.
• What is overdue, surfaced by itself. This is the one no spreadsheet manages. Overdue work has to raise its own hand. If a human has to notice the gap, the auditor notices it first.
• The history, reachable from the same place. Five years of monitoring, attached to the asset it belongs to, so producing March 2024's reading for one outlet takes seconds rather than an afternoon in a folder.

When the spreadsheet is genuinely fine

Below a certain size none of this applies, and moving to software too early is its own waste. One or two engineers, a dozen sites, a single person who holds the whole schedule in their head with a sheet backing up their memory: that setup is cheaper and quicker than any system, and switching would slow it down. Don't let anyone shame you out of it.

The tell is not a site count. It is when the sheet starts needing its own administrator: when someone spends Friday afternoons maintaining the schedule instead of doing the work, when a second person has to ask which version is current, when a slipped visit turns up by accident rather than flagged on purpose. That is the point the spreadsheet stops paying for itself, and it tends to arrive alongside the contract that pushes you past the size where one head holds it all.

This is the problem BlueWave's scheduler was built around. Each recurring task is booked against the actual asset on the site, this calorifier, these sentinel outlets, those TMVs, so the recurrence lives on the asset rather than in a colour a colleague has to interpret. Visits generate on their own clock and land against an available engineer, and a round that slips shows up as overdue work on a screen instead of a surprise in an audit three years later. The five-year record accumulates as the work happens, and the invoice can follow the completed visit instead of waiting for month-end.

Whatever you run your schedule on, the test is the same. Ask it what is overdue right now, this minute. If the answer starts with opening the sheet, the sheet already doesn't know, and neither do you. The full task-by-task cadence sits on one page if you want to see how many moving parts you are really asking a wall planner to hold. Scheduling is one of eight leaks we map across a water hygiene operation; the wall planner feeds most of the other seven.