Planning maintenance across a multi-building estate

Maintenance planning for a single building is largely a scheduling problem. Add a second, third and tenth building, spread across different postcodes and possibly different management structures, and it becomes something else — a question of consistency, visibility and who's actually accountable for what, on top of the original scheduling problem, which doesn't go away.

Consistency is the thing that quietly erodes first

A single site with one engineer or one small team tends to run consistently because there's only one interpretation of "how we do things here." Spread the same work across several buildings and several people, and consistency becomes something that has to be actively maintained rather than something that happens naturally — one site's PPM schedule stays disciplined, another quietly slides, and without a way to see both side by side, the drift goes unnoticed until something fails.

One asset register, not several disconnected ones

It's common for a growing estate to end up with a different record per building — a spreadsheet here, a folder of paper records there, whatever the site's own team happened to set up before central oversight existed. A single, consistent asset register structure across every building is what makes estate-wide reporting possible at all; without it, any question about the whole estate has to be answered by manually combining several inconsistent sources, which tends not to happen reliably or often.

Who owns what, across sites

Ownership gets genuinely ambiguous at scale in a way it rarely does on a single site. Is a specific PPM task owned by the site's on-site team, a mobile engineer covering several buildings, or a central contractor? Estate-wide planning needs that answered explicitly for every asset category, because "someone will handle it" is a reasonable assumption for one building and a real gap once there are ten, each with a slightly different answer.

• –A shared asset and task structure across every building, not a different format per site
• –Clear ownership for each maintenance category — on-site team, mobile engineer, or external contractor
• –A way to compare sites against each other, so a slipping site is visible before it becomes a serious problem
• –Local flexibility for genuinely site-specific factors, without losing estate-wide consistency on the basics

Reporting upward without losing the detail

Whoever's accountable for the whole estate — an operations director, a board, a client — generally wants a summary, not a building-by-building breakdown of every task. But that summary is only trustworthy if it's built from the same underlying detail at every site, which is really the same requirement behind estate-wide compliance reporting more broadly: the roll-up is only as good as the consistency underneath it.

Team structure matters here too — how a facilities function is organised across sites shapes how easily any of this can actually be delivered, which is worth reading alongside our notes on structuring a multi-site facilities team.

Where consistency actually goes

Estates rarely diverge by decision. They diverge because one site inherited a good site manager who built sensible local practice, another was acquired with its own contractors and conventions, and a third has been running on a spreadsheet since before the current system existed. Each is defensible locally. Together they mean the same asset type is inspected at three different frequencies, recorded in three formats, and impossible to report on estate-wide without manual reconciliation.

The question worth answering early is which things genuinely must be identical across sites — usually the asset taxonomy, the criticality scale and the statutory calendar — and which can safely stay local, such as who holds keys or how a job is dispatched. Standardising everything fails on contact with real buildings; standardising nothing leaves you unable to answer a simple question about the estate.

Common mistakes

• –Allowing each site its own asset naming, which makes estate-wide reporting impossible
• –Different inspection frequencies for identical assets with no recorded rationale
• –Rolling out a standard without asking why a site does it differently
• –Reporting an estate-wide figure assembled from incompatible local data
• –No named owner for compliance at a site, so it defaults to whoever is nearest
• –Assuming an acquired site's previous arrangements were compliant without checking