Maintenance Reporting Across Multiple Sites: What Head Office Actually Needs to See

What is multi-site maintenance reporting?

Multi-site maintenance reporting is the process of pulling maintenance data from every location into one consistent view, so head office and regional managers can compare sites and see where risk or cost is building. It typically draws on work orders, preventive maintenance schedules, asset histories, statutory inspection records, stock levels and cost data.

Comparison is what separates it from single-site reporting. A site manager needs to know what is late today, while head office needs to know which sites are drifting and whether a problem at one location could appear at others running the same equipment.

That only works when every site records work against shared definitions. If those aren't agreed yet, start there. Our guide to standardising maintenance across sites covers what to fix centrally and what to leave with local teams.

‍

What does head office actually need to see?

Head office needs reporting that answers a short list of business questions:

• Are we compliant at every site, and where are we exposed right now?
• Is critical equipment available when operations need it?
• Is maintenance spend going where we expect, and how much of it is reactive?
• Which sites are slipping, and what is behind it?
• Which assets are reaching the point where replacement makes more sense than repair?

Anything that doesn't help answer one of these belongs in a site or regional view. Job lists and individual work orders add pages to a board pack without changing any decision.

Many maintenance teams struggle to give leadership this kind of clarity. In the 2026 edition of UpKeep's State of Maintenance Report, 62.2% of the 214 maintenance and reliability professionals surveyed rated their measurement capability as fair or worse, and only 21.8% said they could demonstrate return on investment clearly or very clearly. Half of respondents managed six or more locations. The sample is mostly North American, so treat the figures as indicative for UK operations.

‍

What should a multi-site maintenance report include?

A useful report covers five areas: statutory compliance, availability of critical assets, the balance of planned and reactive work, cost, and spares. Each area needs a headline figure plus the named exceptions behind it.

Statutory compliance and open defects

This section usually carries the most legal risk, so it should come first. A single compliance percentage isn't enough on its own. An estate running at 98% can still have a lift truck in daily use with an expired thorough examination, and that is the item a director needs to see.

Report the following by site:

• Overdue statutory inspections, with how many days each is overdue
• Inspections due in the next 30 days that aren't yet booked
• Open defects from thorough examination reports, with their remedy deadlines
• Equipment taken out of use while it waits for repair

Defect tracking matters because the examination report sets the deadline. According to HSE guidance on thorough examinations, a report must record the date the next examination is due and any defect that is or could become a danger to people. Where a defect doesn't require the equipment to stop immediately, it must be remedied, or the equipment taken out of use, within the period stated on the report. Serious defects are also reported to the enforcing authority. A defect logged at one site and then forgotten is exactly the exposure head office can't see without this section.

For the record keeping that sits behind these figures, see our guide to audit-ready maintenance records.

Availability and downtime on critical assets

Downtime should be reported by asset criticality. An hour lost on a sortation line or the only reach truck in a cold store matters far more than a day lost on a spare pallet truck, and blending the two hides the difference.

Useful measures include:

• Downtime hours on critical assets, by site and asset type
• Repeat failures, such as any asset with three or more breakdowns in the period
• The ten assets across the estate with the most downtime
• Mean time to repair for critical asset types

The estate-wide top ten is often the most useful list in the report. When the same machine model appears from four different sites, the cause is less likely to be local, and the fix can be made once in the shared preventive maintenance (PM) task list.

Planned versus reactive work

These measures show whether maintenance is getting ahead of failures:

• PM completion rate and schedule compliance by site
• Overdue PMs on critical assets specifically
• Planned versus reactive ratio, measured in labour hours
• Backlog size and the age of the oldest open work

Read these together. A site with high PM completion and a rising reactive ratio is doing its PMs, but they may not be preventing the failures that matter, which usually means the task content needs reviewing. Measure the ratio in hours where you can, because counting jobs makes a five-minute reset look the same as a two-day gearbox replacement.

Maintenance cost

Total spend per site says little on its own, because sites differ in size and equipment age. More useful measures are:

• Cost per asset, grouped by asset type
• Contractor spend as a share of the total
• Reactive work as a share of total maintenance cost
• Spend against budget, with any variance explained in a sentence

Spares and stock

Stock is where multi-site operations can lose money without noticing, because each store looks reasonable in isolation. Fluke's UK spare parts research, published in September 2026, found that 83% of UK respondents had experienced maintenance delays because parts were unavailable or on long lead times. On average, 22% of their spare parts inventory was already obsolete.

At estate level, that points to four measures:

• Stock value by store, with slow-moving and obsolete lines flagged
• Critical spares below their minimum level
• Jobs delayed waiting for parts, by site
• Parts that were out of stock at one site while another site held them

‍

Who needs which view?

The same data should feed every level of the organisation, with the detail and frequency changing as it moves up. Treat the split below as a starting point. The right content and cadence for each level will depend on how your business is structured and governed.

Site view (daily and weekly)

Open and overdue work, PMs due this week, jobs waiting on parts and anything flagged as a safety risk.

Regional view (weekly)

A side-by-side comparison of sites on PM completion and the planned versus reactive ratio, plus exceptions such as overdue statutory inspections and repeat failures. Regional managers need to spot a site slipping before it shows in the monthly figures.

Head office view (monthly)

Estate-wide trends across the five areas above, the top downtime assets, cost against budget and a named list of compliance exceptions.

Board view (quarterly)

A page or two at most. Compliance status with any open exceptions, availability of critical assets against target, the cost trend, and the sites or assets that need an investment decision.

Each level should be able to drill into the one below it, so a question from the board can be answered without a fresh spreadsheet request to the site.

‍

How do you make site figures comparable?

Four habits make the biggest difference.

Use the same definitions everywhere

Terms like "planned" and "critical" need to mean the same thing at every site, and so do failure codes and mandatory completion fields. If one depot counts a breakdown from the moment it is reported and another from when an engineer arrives, their downtime figures can't be compared.

Normalise before you compare

Compare cost per asset or per asset type, and downtime as a share of scheduled operating hours where you record them. A site with twice the fleet will always spend more in absolute terms.

Compare each site against its own trend

A league table can pit a new distribution centre against a 20-year-old plant. A site's movement over six or 12 months is usually a fairer signal than its rank, and it gives sites less reason to manage their figures.

Report data completeness next to performance

This step is easy to overlook. The best-looking site is sometimes the one recording the least. If engineers at one location close jobs without a failure code or labour time, that site's repair time and labour cost figures will be understated. Show the percentage of completed work orders with every mandatory field filled in, by site, alongside the performance figures.

‍

Common mistakes in multi-site maintenance reporting

• Averages that hide outliers. A 94% PM completion rate across ten sites can include one site running at 70%.
• Percentages without counts. 95% inspection compliance means something different at a site with 20 lifting assets than at one with 400.
• Too many KPIs. A pack with 30 measures is hard to act on. Six to eight that every site understands will usually do more.
• Manual consolidation. If someone spends the first week of each month merging site spreadsheets, the report is out of date before anyone reads it, and every manual step is another chance for definitions to drift.

‍

Where reporting software fits

Report quality is decided when the job is closed. If reports run from the records engineers update on the job, the consolidation step disappears and head office sees the same numbers as the site.

Service Geeni's CMMS records work against individual assets at each site, so the same figures can be viewed by site, by region or across the estate. Automated scheduled reports can be sent to each level, and for the questions a monthly pack doesn't anticipate, the AI Operations Agent lets managers ask questions in plain English, with answers limited to the data each user is permitted to see.

If you're unsure whether your current system can support reporting at this level, our comparison of multi-site and single-site CMMS covers what changes as an estate grows. 

‍

Frequently asked questions

What KPIs should a multi-site maintenance report include?

A workable core set is overdue statutory inspections, open defects, PM completion, planned versus reactive ratio, downtime on critical assets, backlog age, cost per asset and data completeness. The exact list matters less than applying the same definitions at every site.

How often should head office review maintenance performance?

Monthly for operational trends and compliance exceptions, with a shorter quarterly summary for the board. Overdue statutory inspections and dangerous defects shouldn't wait for either. They need to reach the responsible manager as soon as they arise.

Should sites be ranked against each other?

Ranking can help when sites are similar in size and equipment age, and it can mislead when they aren't. Comparing each site against its own trend, using normalised figures, tends to give a fairer picture and invites less defensive behaviour.

What is the difference between a maintenance report and a maintenance dashboard?

A dashboard is a live view for managing day-to-day work. A maintenance report is a fixed snapshot of a set period, usually with commentary, used for decisions and as a record of performance. Most multi-site operations need both, built from the same data.

‍

Bringing it together

Good multi-site maintenance reporting is short at the top and detailed underneath. Head office should see compliance exceptions by name, availability of the assets that matter, cost in context and the direction each site is moving in, with every figure traceable to the work orders behind it.