Generic job software thinks in jobs. Water hygiene thinks in outlets

Most field service software is built around a job. It gets accepted, the engineer drives to site, marks themselves on-site, does the work, marks it complete. That pipeline is the standard shape of the tools, and for plenty of trades it's exactly right. Water hygiene isn't one of them. A monthly monitoring visit isn't a job that opens and shuts. It's forty temperature readings against forty registered outlets, each with its own history, and the record has to still make sense in five years.

The mismatch sits in the data model, not the feature list. A generic system stores a job with a status and some notes hung off it. Compliance work is assets times readings times recurrence times evidence: this tap, checked this month, at this temperature, sitting between the reading before it and the reading after. Close the job and you've binned the only thing that mattered.

A monitoring visit is not one job

Walk a single visit. An engineer arrives at a care home with forty sentinel and rotating outlets on the schedule: hot at the taps nearest and furthest from the calorifier, cold at the nearest and furthest from the storage tank, the calorifier flow and return, and a rotating set of other outlets so every one gets covered across the year. That's the baseline HSG274 regime, repeated month after month, and the monthly sentinel round has to land without gaps. Each reading belongs to a specific fitting. Each means nothing alone and everything in sequence.

A job-shaped tool records all that as one visit with forty numbers in a notes field or a bolted-on form. That's fine until an auditor asks for the temperature history of one particular shower across two years. Now you're opening forty-line visit records one at a time, hunting the row that mentions that shower. The data exists. It's just stored against the wrong thing: the visit, not the outlet.

Bolting asset structure onto a job tool

The bigger platforms know this, so they add asset registers. The trouble is that an asset module grafted onto a job-first system tends to stay awkward, because it was never the spine. One reviewer running a large estate said it straight: the asset management is clunky, every asset has to be added by hand, and across 600-plus sites it becomes impractical. That's the tax for making the register an afterthought instead of the foundation. Clunky asset admin is also how you lose the engineers, who quietly stop trusting a tool that fights them.

There's a second tax too. Generic CAFM and job systems often need add-ons or a separate platform to run per-outlet temperature monitoring properly. The core product does jobs; the compliance workflow is sold beside it. Two systems, two sources of truth, and the join between them is a spreadsheet somebody keeps by hand.

Compliance data is asset-shaped

The thing being monitored has a structure the job model can't see. A TMV isn't a line item. It has a make, a model, a location, a pipe run, a service history and its own standing in the risk assessment. A calorifier has flow and return temperatures that trend over years. A little-used outlet has a flushing record that either holds or has gaps. Showers, taps, TMVs, tanks: the register is the real object, and the visit is just the day you touched it.

Recurrence lives on the asset as well, and a single site rarely keeps one rhythm. The little-used outlets need weekly flushing. The sentinels want monthly temperatures. Showerheads come round quarterly, and tanks, calorifiers and TMVs annually. That's four different clocks, running on four different sets of fittings under one roof, every one tracked to the individual asset. Flatten the lot into "a visit" and you lose what makes a programme a programme: which asset is due, and when. The schedule isn't a property of the calendar. It's a property of the register.

Get the register right and the rest falls out of it. The monitoring schedule is a property of the asset. The five-year history is a property of the asset. The form the engineer fills in down in the plant room is generated from the assets on that site. Get the register wrong and you spend the whole contract reconciling.

Where a generic tool is genuinely fine

Worth being straight here, because the opposite case is oversold. If your work is reactive plumbing, a leak, a dead pump, a call-out with a start and an end, a generic field service tool fits well and usually costs less. The job model matches the job: something breaks, you fix it, you close it, and nobody audits the temperature of a tap you never went near. Plenty of water treatment firms run a mix, and for the reactive half the generic tool is fine.

The mismatch starts the moment your deliverable stops being a closed job and becomes a compliance record that has to survive an audit years later. That's where asset-shaped beats job-shaped, and no number of add-ons closes the gap.

Three questions for any vendor

Skip the feature list. Ask the vendor to show you three things on their own system, live:

• Show me one outlet's five-year history on a single screen. Not the visits it appeared in. The outlet, with every reading against it, in order.
• Show me how a new asset joins the schedule. A TMV gets fitted on a site today; how many clicks until it's on the right cadence and showing up on the next visit?
• Show me what the auditor gets. Pick a random site and produce the evidence an assessor would ask for, without someone assembling it by hand afterwards.

If any of those turns into "well, you'd export that and...", the register is an afterthought.

This is the shape BlueWave is built on. The asset and site register is the spine rather than a bolt-on: every tap, TMV, tank and calorifier is a record carrying its own history, the monitoring schedule hangs off the asset, and the form an engineer fills in on site is generated from the assets actually there. Put the three questions above to us as readily as to anyone else. The whole product is an answer to them.

Whatever you're weighing up, the test is the outlet, not the demo. Pick one shower on one site and ask to see its life: when it was fitted, every reading, every flush, every gap. If that story is easy to tell, the software thinks in outlets. If telling it is a reporting project, the software thinks in jobs, and your compliance records are just along for the ride.