What a Regional Manager Should Report and How Often

Most regional reports fail for one reason: they report activity, not condition. Forty pages of what the team did last month, no clear answer to the only question that matters — are the buildings getting better or worse?

Regional manager reporting is a cadence problem before it is a data problem. Get the rhythm right — weekly flash, monthly one-pager, quarterly owner pack — and the content follows; get it wrong and good data arrives too late to change a decision.

Key takeaways

• Report condition and exceptions, not activity. A page of what the team did is not a report.
• Three cadences cover almost every need: weekly flash, monthly regional report, quarterly owner pack.
• Every number needs a definition, an owner and a threshold; a number without a threshold is trivia.
• Report coverage alongside score. A 4.2 average from six of eleven scheduled inspections is not a 4.2.
• Bad news belongs at the top of the report, with a trend, an owner and a date, not in an appendix.
• One dataset, three views: the site reads its own areas, the region reads comparisons, the owner reads trend and risk.

What is the core of regional manager reporting?

Five categories are enough: condition, service performance, vendor performance, compliance and risk, and the asks. Anything that does not fit one of those is either detail for a site meeting or a distraction.

The fifth category is the one most reports omit, and it is why regional reports feel like homework. If the report never asks for anything, nobody has to read it.

How often should each report go out?

Weekly for exceptions, monthly for performance, quarterly for trend and risk, annually for condition and capital. The cadence should match how fast a decision can change something, not how fast a spreadsheet can refresh.

Anything more frequent than weekly becomes noise that people mute. Anything less frequent than quarterly for trend leaves the owner making decisions on anecdotes.

What belongs in a monthly regional report?

One page, six blocks, same order every month: headline score and coverage, the trend, the five worst open items, service performance, vendor performance, and the asks. A reader who opens it on a phone during a commute should get the whole picture before the second screen.

The six blocks, in order:

1. Headline. Average condition score for the region, the coverage rate behind it, and one sentence on whether the month was better, worse or flat.
2. Trend. The same two or three measures over six months. A single month is a mood; six points is a direction.
3. Worst open items. Five entries at most, each with building, item, age and due date. If there are more than five, the list is a backlog problem and should be reported as such.
4. Service. Requests opened, closed, and the aged tail — anything open more than 30 days, with a name against it.
5. Vendor. Scorecard result per building, and any formal notice issued. Keep it factual; the argument belongs in the review meeting.
6. The asks. Two or three, each with a decision required and a date it is needed by.

Keep the appendix for the detail that supports the page: building-by-building scores, deficiency counts, and the inspection dates that prove coverage.

What should stay out of the report?

Leave out activity counts that cannot change a decision — kilometres driven, meetings held, calls answered — and leave out any number the region cannot act on. Reporting is a filtering job, and a report with thirty measures filters nothing.

Four common fillers to cut:

• Photo galleries with no caption, item or score. Two dated photos per building, chosen to show change, do more than forty.
• Percentages of percentages. "98% of issues actioned" means little without the base count and the definition of actioned.
• Cross-region league tables without adjustment for building age, type and occupancy. Comparable comes before compared.

If a number has been in the report for a year and nothing has ever been done differently because of it, retire it. Replacing three such measures with one useful one is a net gain in attention.

How do you write for three audiences from one dataset?

Write three views from the same underlying record: the site view, the regional view and the owner view. The temptation is to write three reports from three spreadsheets, which is how portfolios end up with numbers that cannot be reconciled.

• Site view. Its own areas, item by item, with photos and open deficiencies. Detailed because the site can act on detail.
• Regional view. Buildings compared with each other and with their own history, plus exceptions and coverage. Aggregated because the region acts on patterns.
• Owner view. Trend, risk, capital implications and the asks. Summarised because the owner acts on money and exposure.

One rule protects all three: the numbers must come from the same inspection records, not from someone's summary of them.

The owner-facing structure is covered further in condition reporting to owners, and the metric selection that feeds the regional view in inspection metrics for managers.

What makes a number credible in a report?

Four things: a written definition, a coverage rate, a named inspector and a calibration history. Without those, a score is an opinion with a decimal point.

• Definition. "Average cleanliness score" needs the scale, the areas included and the weighting, written once and never quietly changed.
• Coverage. Report inspections completed against inspections scheduled. A 92% coverage with a published gap is more credible than a 100% claim nobody believes.
• Sampling. If the score comes from a sample, say the sample size. Six areas out of forty is a spot check, not a condition assessment.
• Calibration. Note when managers last scored the same areas blind and agreed. A portfolio with three uncalibrated managers has three scales.

When a number moves sharply, the first question is whether the building changed or the measurement did — a new inspector, a revised item list, a different scale. Reports that ignore that distinction cause a lot of unnecessary work.

How should bad news appear in a report?

At the top, with a trend, an owner and a date. Bad news that arrives late reads as concealment, and the cost of that perception dwarfs the problem itself.

A useful shape for a failing item: what it is, when it was found, how long it has been open, what it now needs, who owns it and when the next update comes. That format survives a budget meeting because it removes the two things that make owners nervous — vagueness about the cause, and vagueness about the next step.

Do the opposite for good news. A rising score with falling coverage is not good news, and reporting it as such is how a regional manager loses credibility the following quarter.

What should a quarterly owner pack contain?

Trend, risk, spend and asks — in that order, in six to ten pages. The owner is not reading for condition detail; they are reading for whether the asset is being looked after and what it will cost.

A workable contents page: portfolio condition trend with coverage, building-by-building summary with a one-line narrative each, capital and deferred items with cost ranges, the risk register's top five, vendor performance, and the decisions requested.

Vendor performance in the pack should tie back to the contract, not to impressions; the structure for that is in vendor reporting to owners, and the dashboard layer that produces the numbers is covered in operations dashboards and metrics.

How do you cut the reporting workload?

Automate the arithmetic, not the judgement. If two people spend three days a month assembling a report from spreadsheets, the portfolio is paying for a formatting exercise that could be spent on the five worst items.

Three changes cut most of the effort:

• Fixed template, fixed fields. Same order every month, populated from one source. Anything that has to be typed fresh each month will be typed inconsistently.
• Exception-based reporting. The monthly report highlights exceptions and aggregates; the full detail lives in the record. Reports that reproduce everything teach readers to skim.
• A single owner for the number set. One person maintains definitions and the calculation. Distributed ownership of a metric is how two reports end up disagreeing about the same building.

Frequently asked questions

How long should a monthly regional report be?

One page plus an appendix. If it needs more than one page, the extra is either detail that belongs in the record or a sign that too many buildings are failing and the report should say that in one sentence instead.

Should the report use averages or building-level scores?

Both, in that order. The average answers whether the region is holding; the building-level distribution answers where to go next week. An average alone hides the building that is collapsing.

What if the inspection coverage is poor that month?

Report it plainly and attribute it — vacancies, a vendor transition, storm damage. Coverage is part of the result, not a footnote, and a region that reports its own gaps is more credible than one that reports a perfect score from thin sampling.

Do owners want to see photos?

Yes, but two or three, dated, with the item and score attached. A gallery of pretty lobbies teaches nothing; one photo of a failing roof detail beside one of the repair shows the owner exactly what the money bought.

Is a dashboard a replacement for the monthly report?

No. A dashboard answers the question you thought to ask; a report tells you the three things you would have missed.

Reporting that survives a bad quarter

Every portfolio has a quarter where the numbers fall: a roof fails, a vendor underperforms, a manager leaves mid-inspection cycle. The report that survives is the one whose format did not change, whose definitions stayed stable, and which said the bad news first.

That credibility is built long before the bad quarter, in the routine that produces the numbers: property management operations sets the standard, the recurring inspection produces the record, and the report is only the last step. IFMA's research and benchmarking programme is a fair reference when an owner asks how the portfolio compares externally — meaningful only once internal definitions have been stable for a few quarters.

NeatScore keeps that last step short: area-specific checklists on APPA 1–5 scoring, a photo per item, offline inspections that sync, deficiency tracking and a dated branded report you can hand to an owner without rewriting it. Try it free for 14 days, or see pricing.