The month-end scramble to find missed sites
Your water treatment business runs contracts for offices, schools, care settings, hotels and industrial units. Most include monthly monitoring: sentinel outlet temperatures, calorifier readings, cold water storage checks, maybe some quarterly or six-monthly tasks on top. Each contract says what is done and how often.
In practice, the schedule is a wall planner, a shared spreadsheet or the operations manager's head. Engineers are given a list each week. Near the end of the month someone goes through the spreadsheet row by row and realises a care home in the north of the patch was never booked, a school was visited but the quarterly shower head clean was forgotten, and two sites are showing as done because an engineer marked them in the wrong column.
Then comes the phone call from a facilities manager asking why their logbook has a gap for August. Nobody can answer quickly, because the answer is spread across a diary, an email chain and a PDF report that may or may not have been sent.
Why a spreadsheet cannot keep up with contract scope
The obvious explanation is that the team is busy. The real cause is structural. A contract is not one visit a month, it is a bundle of tasks with different frequencies: monthly temperatures, quarterly descaling, six-monthly tank inspections, annual TMV servicing. A spreadsheet row per site cannot hold that without becoming a grid nobody trusts.
- Task frequencies sit in the contract document, not in the schedule.
- The diary shows a booking, but not which tasks the booking covers.
- Completion is marked by hand, separately from the engineer's report.
- Contract changes (a new building added, a wing closed) never reach the schedule.
- Nobody sees overdue work until someone thinks to look.
So the schedule drifts from the contract a little every month, and the drift only shows when a client or auditor asks.
The quiet cost of missed monitoring
A missed visit is not just a lost invoice line. It leaves a gap in the client's records, which is exactly what they pay you to prevent. It damages trust at renewal time, and it can mean an awkward conversation about whether the monthly fee was earned.
It also costs office time. Reconstructing what happened at a site means reading reports, checking the diary and asking engineers from memory. Catch-up visits get squeezed into already full routes, which pushes other sites late, and the problem rolls into the next month.
A schedule that is built from the contract
What we build treats the contract scope as the source of truth and generates the work from it.
- Each site is set up with its contract tasks and frequencies: monthly, quarterly, six-monthly, annual, or a set number of visits per year.
- The system generates due tasks for each period automatically, grouped by site so one visit can cover several tasks.
- The planner books visits against those due tasks, either by hand or from a suggested plan grouped by area.
- Engineers see the task list for each site on a phone or tablet and record results against each task.
- When the report is submitted, the tasks are marked complete, with the date and engineer, and the evidence is attached.
- Anything due but not booked, or booked but not completed, sits on an exceptions list for the operations manager.
| Status | What it means | Who acts |
|---|---|---|
| Due | Task falls in this period, not yet booked | Planner |
| Booked | Visit in the diary covering the task | Engineer |
| Completed | Results recorded and report submitted | Nobody, unless review is needed |
| Overdue | Period ended without completion | Operations manager |
| No access | Engineer attended but could not complete | Planner, to rebook |
If you already use a job management system for bookings, we connect to it through its API where one exists, so the planner keeps using the diary they know and the contract logic sits alongside it.
What the operations manager sees on a Monday
Instead of scanning a spreadsheet, the manager opens one screen showing every site with work due this month and its status. Filters show overdue tasks, sites with no booking yet and sites where the engineer recorded no access.
When a client asks about a gap, the answer is a click away: what was due, when it was booked, who went, what they recorded, and the report that was sent. When a contract changes, updating the task list changes future months automatically.
Engineers also benefit. Their visit shows the full task list for the site, including the quarterly or annual job they might otherwise not know was due.
Signs this is your business
- Your schedule is a spreadsheet with one row per site and a column per month.
- You find missed visits at month end, or when a client asks.
- Quarterly and annual tasks get forgotten because they are not on the monthly list.
- Engineers mark visits complete separately from submitting their report.
- Contract changes take weeks to reach the schedule, if they reach it at all.
If two or more of these sound familiar, tell us how your contracts and diary work today and we will describe what we would build.