The Monthly Maintenance Report Your Boss Actually Reads

The last week of every month has a familiar shape in most facility teams. Someone opens the logbook, exports a spreadsheet, scrolls back through a WhatsApp group, and digs out the three service reports a vendor emailed as PDFs. Two or three days later an eighteen page report exists. It gets printed, tabled at the management meeting, and flipped through in under a minute.

Then someone asks a question that is not answered anywhere in those eighteen pages. Why has the chiller cost so much this year. The answer needs numbers nobody assembled, because the report was built to show what the team did, not what the building is costing. The following month, the same eighteen pages get produced again.

The gap is not effort. Facility teams put real work into these reports. The gap is that the report answers the question the team wants to answer, and management is asking a different one.

Why Most Maintenance Reports Go Unread

Once you look at a stack of monthly reports side by side, the same handful of problems keep appearing. They are worth naming plainly.

• They report activity, not consequence. A line saying 142 work orders were completed has no denominator, no comparison, and no money attached to it. Nobody can make a decision from it.
• They are written defensively. The report is produced by the person whose performance it describes, so it naturally presents a month in which nothing went badly wrong. A report where nothing ever goes wrong is a report nobody needs to open.
• There is no baseline. A number without last month beside it, or the target, or the same month last year, is not information. It is just a figure.
• They arrive too late. A report on July delivered on 20 August is a history lesson. The decisions it might have informed were made in the second week.
• They look identical whether the month was good or bad. If the shape of the report does not change when the building has a terrible month, the report is not measuring the building.
• There is no ask. Nothing is requested, nothing needs approving, nothing is owed. So the report goes into a folder and the meeting moves on.

That last one is the real mechanism. People read documents that require something of them. A report that asks for nothing gets treated as something to acknowledge rather than something to act on.

The Five Questions Behind Every Review Meeting

Strip away the format and senior management is asking five things in every monthly review. A report that answers these five directly will be read. A report that answers something else will not, no matter how thorough it is.

• Am I going to be surprised? The split between planned and unplanned work, and whether that split is drifting in the wrong direction.
• What is this costing, and is it moving? Cost by asset and by area, and which handful of assets are absorbing most of it.
• Are we exposed? Statutory certificates approaching expiry, preventive maintenance that is overdue, and safety items still open.
• Is the team keeping up or falling behind? How big the backlog is and, more importantly, how old it is.
• What do you need from me? Decisions, approvals, and budget, each with a number and a date attached.

Those five questions are the report. Not twelve charts, not a section for every module in the system. Five sections, in that order, because that is the order the questions arrive in a meeting.

The One Page That Carries the Report

The practical version of this is one page. Everything else becomes an appendix for whoever wants the detail, and most months nobody will. The page has four bands and a footer.

• A strip of four numbers across the top. Each one sits beside last month and beside the target. Three figures per metric, so the direction is visible without anyone doing arithmetic.
• What went wrong this month. Three items at most, each with what it cost and where it now stands. If more than three things went wrong, the other ones were not significant enough to make the page.
• What is expiring or overdue. Certificates and preventive maintenance, with dates. This is the section that protects the organisation, and it is the one most often buried on page eleven.
• The five assets costing the most. Flag any asset that also appeared last month. A repeat entry tells you something a single month never can.
• Decisions needed. One to three items, each with a ringgit figure and a date by which the decision is needed.

The repeat offender flag is worth dwelling on. A pump that shows up in the top five costs for two consecutive months is no longer a maintenance issue, it is a capital decision waiting to be made. Nothing in a standard monthly report surfaces that, because the standard report has no memory of the previous one.

The Numbers That Survive the Cut

Deciding what to include is easier once the five questions are fixed, because each metric either serves one of them or it does not. These earn their place:

• Planned versus unplanned ratio. The single best indicator of whether a maintenance operation is in control. Most teams aim for roughly 80 planned to 20 unplanned, and the trend matters more than the number in any given month.
• Preventive maintenance completed on time. Not completed. On time. Most reports quietly count a PM finished three weeks late as a completion, which is exactly how a compliance problem stays invisible until an audit.
• Backlog size and backlog age. How many jobs are open, and how many have been open longer than 30 days, trended across six months. Age is the number that predicts trouble.
• Repeat failures. Assets with two or more corrective jobs in the last 90 days. This is the shortlist for replacement discussions.
• Cost per asset against replacement cost. The single most persuasive number a facility manager can put in front of finance, because it turns a maintenance complaint into a comparison between two figures.
• Certificates expiring within 90 days. Short, factual, and the section that makes the report worth keeping on file.
• Downtime hours on critical assets only. Tracking downtime across every asset produces a number that means nothing. Restricting it to the assets that actually stop the building makes it readable.

These do not:

• Total work orders raised. No denominator, and easily inflated by splitting one job into three.
• Average closure time across all priorities. An emergency and a leaking tap averaged together describe neither.
• Complaint counts with no category. A count without a cause cannot be acted on.
• Any chart with twelve categories. Nobody reads past the fourth.
• Mean time between failures on an asset that failed twice. The formula runs, but two data points do not support a conclusion.

Every Metric You Report Becomes a Target

There is a consequence to publishing numbers that deserves saying out loud. Any metric that appears in a monthly report will, over time, be optimised by the people it measures. This is not dishonesty, it is a predictable response to being measured.

Report closure rate and jobs start getting closed before the work is verified. Report work order volume and one job quietly becomes three. Report average response time and the easy tickets get picked up first while the difficult ones sit. None of this is malicious, and all of it is avoidable if the metric is paired with something that cannot be gamed in the same direction. Closure rate sits next to reopened jobs. Volume sits next to cost. On time PM completion sits next to overdue count.

How to Put Bad News in Writing

The most valuable habit in monthly reporting is the least comfortable one. Naming a problem in writing, early, before it becomes expensive.

Consider a single sentence. The bearing on AHU 3 has failed twice since May, replacement is RM8,000, and if it fails during a tenant event the hall is unusable for a day. Written in June, that sentence is a budget request with a clear risk attached, and the decision belongs to management. Written in September, after the failure, the identical sentence reads as an excuse.

This is what the decisions section on the front page is really for. It moves a known risk from the facility team's shoulders onto the organisation's decision record. Teams that report problems early tend to be trusted with larger budgets, because their reports have a track record of being accurate before the fact rather than explanatory after it.

The Ten Minute Rule

A good format is not enough on its own. There is a practical constraint that quietly destroys most reporting improvements. If a number takes more than ten minutes to produce, it will not survive past the third month. The format degrades, the hard numbers get dropped, and the report drifts back to the eighteen easy pages.

Some of these numbers are genuinely hard to produce from a logbook and a spreadsheet. Cost per asset requires every work order and every part issued to be linked to a specific piece of equipment. Repeat failure counts require corrective jobs to be attributable to an asset rather than a location. Backlog ageing requires an accurate open date on every job. If that structure was never built into how work is recorded, the numbers cannot be assembled at month end at any price. This is the connectivity problem that sits underneath most reporting failures, and it is worth solving before redesigning the report itself.

Where the underlying records are already structured, most of this page stops being a monthly exercise. In Cerev CMMS, planned versus unplanned, PM completion, backlog ageing, cost by asset and certificate expiry are all derived from the work as it is recorded, and the monthly pack can be scheduled rather than compiled. The point is not the automation itself. It is that a report which assembles itself is a report that still looks the same in month twelve.

Start With the Five Questions

The temptation in reporting is always to add. Another chart, another breakdown, another section to demonstrate thoroughness. The harder discipline is to decide what management is actually asking and answer only that.

Five questions, one page, and a short list of decisions with dates against them. Everything else moves to the appendix, where it remains available to anyone who wants it and stops competing for attention with the things that matter. A report built this way takes less time to produce than the eighteen pages it replaces, and it has a considerably better chance of being read.