Reporting to a Facilities Manager: The Numbers They Ask For

A facilities manager asks for 6 numbers and is testing 2 things with all of them: whether you are reliable, and whether their budget is under control. A vendor who reports before being asked is answering a question their manager asked them, which is why it changes the relationship.

The short version

Reporting feels like an administrative tax and it is closer to account defense. The facilities manager holding your contract has to justify it upward, and the material they use is whatever you gave them.

Two things follow. A vendor with no reporting is a vendor who is only as good as their last complaint, because there is nothing else in the file. And a vendor who reports monthly, in the same format, with the awkward numbers included, is very hard to replace on price alone.

The reason the awkward numbers matter: a report that only contains good news gets read once. A report that flags a site trending badly, before anyone else notices, is the one that makes you the person they call about problems rather than the vendor they manage.

The 6 numbers, and what each is really testing

Number	What they do with it
Response time against the agreed window	Their own SLA compliance upward. The first thing checked
First-time fix rate	Predicts disruption at their sites, which is what their operators complain about
Spend by site	Budget control, and finding the sites that are outliers
Spend by asset	Capital planning. This is the repair-or-replace conversation
Repeat visits on the same equipment	Tests whether the underlying fault was actually fixed
Planned versus reactive split	Whether the maintenance program is working or is decoration

The fourth is the one most vendors cannot produce and the one that carries the most weight. A facilities manager who can walk into a budget meeting with "these eleven units consumed 40 percent of the maintenance spend and here is their age" has an argument for capital. Handing them that is worth more than a discount.

Spend by asset requires a decision you made years earlier

Every other number can be reconstructed from jobs. This one cannot.

Spend by asset needs each job attached to a specific piece of equipment, and each part consumption attached to that job with a real cost. Where jobs are attached to an address rather than to equipment, the report does not exist and cannot be built retrospectively without reading years of work orders.

What it requires in practice:

• Equipment identified by manufacturer, model and serial, so the same piece of equipment is the same record across visits and across technicians
• Every job against the equipment, not the site, including the visits where nothing was replaced
• Parts cost from the purchase order rather than an assumed markup, or the spend figure is an estimate wearing a decimal point

Roopairs keeps equipment records with manufacturer, model and serial alongside purchase orders attached to work orders, which is what makes spend-by-asset a report rather than a project.

The honest sequencing point: if you do not have this today, start now on the accounts that matter. Twelve months of asset-level history is a report. Three months is a start. Nothing is what most vendors bring to a renewal.

What a monthly report should look like

One page, the same shape every month, sent without being chased.

1. The headline numbers, this month against last and against the year, on response, first-time fix and spend
2. Exceptions, meaning every missed window with the reason. Naming your own misses is what makes the rest credible
3. Sites to watch, with the two or three trending badly and why
4. Assets to watch, meaning units where the repair spend is approaching the replacement case
5. What you recommend, in two or three lines, and what you need from them

The consistency is the point. A report that changes format every month cannot be compared, and comparison is the only thing they want to do with it. Same rows, same order, same day of the month.

Length is a trap in the other direction too. A twenty-page pack does not get read, and the numbers that mattered are somewhere on page eleven.

Recommendations are where reporting earns money

The numbers are the entry fee. The recommendation is the part that produces work.

A facilities manager is not looking for data, they are looking for decisions they can take upward. "Fryer at site 14 has had four repairs in eight months totaling more than half a replacement, and it is nine years old" is a capital request they can make with your name on it.

Three recommendation types that land:

• Replace this unit, with the repair history and the arithmetic behind it
• Change the maintenance interval here, because reactive calls at this site cluster around something preventable
• This is a usage or training issue, not an equipment issue, evidenced by the fault pattern

The third is the one that builds the most trust, because it is the one where you decline work you could have kept billing for. A vendor who says "this keeps failing because of how it is being cleaned" has told a facilities manager something no other vendor did.

Reporting to a chain versus reporting to an owner

Same records, different report, and sending the wrong one wastes both.

A facilities manager over forty sites wants aggregates, exceptions and outliers. They will not read a per-job narrative and they need to compare across sites and across months.

An independent owner wants the opposite: what is wrong with my two ovens, what will it cost, and what should I do about it. Aggregates mean nothing across two pieces of equipment.

What is shared is the underlying record. If every job carries its equipment, its parts and its real cost, both reports come out of the same data. If it does not, neither report exists and you are writing both by hand.

The cadence question

Monthly for the numbers, quarterly for the conversation, and never only at renewal.

Monthly reporting is a document. Quarterly is a meeting where the recommendations get discussed and next quarter's work gets agreed. The two do different jobs and skipping the second is why so much reporting produces nothing.

The failure mode worth naming: a vendor who reports for the first time three weeks before renewal has advertised that the reporting is a sales exercise. Reporting is only credible when it predates the moment you need it.

Start with your largest account, one page, the six numbers you can actually produce, and note the ones you cannot. The gaps in the first report are your list of what to fix in the records.

Roopairs runs a product tour where you can see equipment records, job history and job costing, which is where these numbers come from.

What a kitchen operator says

“I love that my service vendors use Roopairs because I get everything in real time. All of my invoices, status of jobs whether they're open or closed, where I'm at on parts and pieces coming in. I don't have to call him up and ask him what everything's going on, it goes directly to my inbox.” — a kitchen operator whose service company runs Roopairs

Also worth reading

• 5 Numbers a Service Owner Should See Weekly
• Equipment Downtime Reporting Customers Will Read
• Should I use OEM or non OEM commercial kitchen parts

Frequently asked questions

What reports do facilities managers want from a service vendor?

Response time against the agreed window, first-time fix rate, spend by site, spend by asset, repeat visits on the same equipment, and the planned versus reactive split. All six test two things: whether you are reliable and whether their budget is under control.

Which number matters most?

Spend by asset, because it is the one they can take into a capital budget meeting and the one most vendors cannot produce. It requires jobs attached to specific equipment and parts costed from purchase orders, which is a records decision made long before the report is requested.

Should we report our own missed SLAs?

Yes, with the reason. Naming your own exceptions is what makes the favorable numbers credible, and a facilities manager who finds a miss you did not report will discount everything else in the document.

How often should we report?

Monthly for the numbers and quarterly for the conversation where recommendations get discussed. Reporting that begins three weeks before renewal reads as a sales exercise, because it is one.

What makes a report worth reading?

Consistency and recommendations. Same rows, same order, same day of the month, so the numbers can be compared. Then two or three lines on what you recommend, because a facilities manager is looking for decisions they can take upward rather than for data.

Do independent customers need the same report?

No. Aggregates and outliers mean nothing across two pieces of equipment. An owner wants what is wrong with their equipment, what it will cost and what to do. Both reports come from the same records if jobs carry equipment and real parts cost.