Reporting to Owners, Boards and Franchisors

The maintenance function is funded by people who do not see the equipment. What they see is a cost line and, occasionally, a failure that reached them.

What they actually need to know

Are we exposed? Compliance position, critical equipment at end of life, single points of failure.

Is the spend under control and going somewhere? Trend, not absolute number.

What is coming? Replacement backlog and its cost.

Did anything go wrong, and why? The significant failures and what was done.

Four questions. A report that answers them in one page is more useful than a dashboard.

The annual report worth writing

Compliance position. Sites current on each regulated item, and any gaps with dates for correction. This section should be short and green, and when it is not, it is the most important thing in the document.

Spend, with the split. Scheduled, reactive, regulated, capital. With last year alongside.

The trend that matters: emergency share of work orders, year on year. A falling emergency share with flat or falling total cost is the story.

Significant failures. What failed, what it cost including consequential loss, what was done about the cause. Three or four, not a list.

Replacement backlog. Assets at end of life, cost to replace, exposure if deferred. This is the section that eventually gets capital allocated, and it works by being repeated annually rather than by being dramatic once.

What we are asking for, and what happens if we do not get it.

What to leave out

Work order counts. Meaningless without context and they invite the wrong question.

Activity summaries. Nobody above the maintenance function needs to know how many filters were changed.

Technical detail. The refrigerant type does not belong in a board paper.

Every metric you track. Reporting eight measures internally and four upward is correct.

Making the invisible visible

The central difficulty is that a working programme produces nothing to see.

Report the baseline comparison. "Refrigeration emergency call-outs down from thirty-one to nine since the programme started" requires having measured the before, which is why the baseline matters.

Report avoided cost with the arithmetic shown, and label it as an estimate. Overstating it destroys credibility; omitting it leaves the programme looking like pure expense.

Report the near-misses. "Three walk-in compressors identified as failing during scheduled inspection and replaced during closures rather than during service" is concrete and it describes exactly what the programme is for.

For franchisors

Different problem. The franchisor sets standards and does not see the work.

What can reasonably be required: evidence of the regulated items — hood cleaning, suppression inspection, grease service — as a brand standard with documentation.

What can be offered: a national service agreement franchisees may opt into, which improves their rates and creates aggregate visibility.

What cannot be assumed: any view of franchisee work orders, unless the agreement provides for it.

Report aggregate compliance, not individual franchisee spend. The former is the franchisor's legitimate interest; the latter usually is not.

For a private owner or a small group

The audience is one or two people who also know the sites.

Shorter, more concrete, and more about specific equipment. "The walk-in at the second site is on borrowed time; replacement is a known figure; if it fails during summer it will cost several times that."

Bring the decision, not the analysis. Owners want to decide, not to review a methodology.

The frequency

Monthly to operations — one page, exceptions only.

Quarterly to finance — spend against budget, backlog.

Annually to ownership — the full picture.

Immediately, for anything material — a compliance failure, a significant loss, a systemic problem. A programme that reports bad news only in the quarterly cycle is a programme that will be discovered rather than trusted.

Reporting a failure that reached them

When something goes wrong visibly, the report that follows determines whether the programme gains or loses credibility.

Within twenty-four hours, one page.

What happened, factually, with times.

What it cost, including product and lost trade, estimated and labelled as such.

Why it happened. The actual cause, not the component that failed.

Whether it was preventable, honestly. Sometimes the answer is no, and saying so when it is true makes it credible when the answer is yes.

What has been done and what will be done.

Whether it can recur elsewhere, and what is being checked across the estate. This is the question leadership will ask and answering it first is the difference between a competent report and a defensive one.

No blame, no hedging, no adjectives. A factual account of a failure, delivered promptly, builds more confidence in the function than a quarter of good numbers.