Mobilising a new contract without drowning the office

The contract is signed and everyone is pleased. That is the easy part, and it is close to the last easy part for a while. The month after you win a water hygiene contract, mobilisation, is where year one is actually decided. Get it right and the routine work runs itself for twelve months. Get it wrong and you spend those twelve months fighting a mess you made in the first three weeks.

The mistake almost everyone makes is to start doing the work before setting up the work. Engineers get sent to sites to hit the first visit dates while the office builds the records behind them. It feels like momentum. It is the opposite, and the reason it poisons the data from day one is worth spelling out; we'll come back to it. First, the sequence that actually holds.

Survey first, always

Before a single routine visit is booked, walk every site. Build the asset register: the tanks, the calorifiers, the TMVs, the sentinel outlets, the showers, each one recorded as a real thing with a location. This is the foundation the rest stands on. The schedule is built from it, the quote should already have been built from it, and the engineer's paperwork will refer to it on every visit. Skip it and you are booking work against a site you have not actually seen.

The survey also tells you what you have taken on, which the sales conversation never does. The tender said twelve sites and a tidy asset list. The survey finds the calorifier nobody mentioned, the plant room that needs a permit, the run of outlets dead-legged since a refurbishment two years ago. Far better to meet those in week one than in month six with a client asking why they were missed.

Settle one thing during the survey rather than after it: how each asset is labelled. If the calorifiers are CAL-1 and CAL-2 on a plate in the plant room, the register uses those same references, and so does every future reading. Agree the naming while you are standing in front of the assets. The alternative is three people inventing three schemes and someone reconciling them at the end of the year.

Get the records you are inheriting

Ask the outgoing contractor, or the client directly, for what already exists. Two things matter most: the monitoring history and the current risk assessment status. Monitoring records are meant to be kept for at least five years, so there should be a five-year trail, and the state of that trail tells you a great deal. A clean, complete history means you have inherited a well-run system. Missing months, a flushing log full of holes, a risk assessment two years out of date: that is the true condition of what you have taken on, and from the handover date it is yours to remediate and yours to continue.

There is a liability edge to this too. The day you take over, the gaps become yours to explain. Finding them before your first visit is the difference between managing a known inherited problem and discovering an unknown one halfway through an audit.

Settle the logbook, site by site

Every site needs its logbook arrangement fixed before routine work starts. Where does the record live, who writes to it, how does the monthly round get captured and signed off. Done on paper, monthly temperature monitoring is recorded per site and is genuinely labour-intensive, and it is exactly the kind of thing that drifts when the mechanism is left vague. Settle it now, while you are setting up, rather than discovering three months in that two sites have no consistent record and the readings are scattered across three engineers' phones.

Build the schedule from the register

Only now do you book visits. The schedule comes out of the asset register and the frequencies the programme requires: monthly sentinel temperatures, quarterly showerhead cleans, annual inspections, the whole HSG274 cadence that we put on one page. Because the register is real and complete, every recurring visit lands against an asset that genuinely exists, on the clock that asset needs. Build the schedule first and the register second and you get visits booked against sites whose contents you are still guessing at.

The scale is the reason order matters. Forty sites of monthly-and-quarterly work is thousands of dated tasks a year, and a schedule built on a shaky register multiplies every error across all of them. During mobilisation the point is narrow: the schedule has to be generated from the register, not invented alongside it.

Set the reporting rhythm before the client sets it for you

FM clients have firm expectations about evidence, and if you do not propose a reporting rhythm they will impose one, usually less convenient than what you would have offered. Agree it early: what report, in what format, how soon after each visit, to whom. Paper workflows are increasingly refused once onboarding is done, so if the client wants timestamped digital records, build that into your process from the first visit instead of retrofitting it after the first complaint.

Why the order matters

Here is what happens when engineers arrive before the register exists. They do the work, and the paperwork needs to name the assets, so they invent names on the spot. "Calorifier in the basement." "TMV by the kitchen." "The big tank on the roof." Meanwhile the office is building its own register with its own names, or trying to build one from these very notes. The two never quite line up. Now you have readings attached to asset names that do not match the register, and reconciling them is manual, slow and never entirely finished. The data is dirty from day one, and dirty data does not clean itself. Every audit and every renewal, you pay interest on that first fortnight of doing it backwards.

This is the case BlueWave was built around: sites and their assets set up first, each asset a real record with its own history, and the schedule generated from that register rather than assembled by hand. Because the engineer picks from assets that already exist instead of typing names in a plant room, the readings attach to the right asset the first time and there is nothing to reconcile afterwards.

Mobilisation done well is boring, and boring is the target. The rule of thumb that keeps it boring: no engineer visits a site the office has not finished setting up. Book a visit before the asset register for that site is complete and you have started the year owing yourself a debt, and it is a debt you pay back every month until the contract renews.