A monthly operations report that leads to decisions
A practical report structure for lean teams, with defined response and resolution metrics, aging, costs, repeat issues and decisions due.
Start with the decisions and risks, then explain the workload, time, cost and quality behind them. A useful report distinguishes completed work from pending work and keeps metric definitions stable from month to month.
Lead with the operating decision
The first page should explain what needs attention: a persistent provider problem, an upcoming renewal, overdue work or a cost decision. State the owner and decision date. Keep the request register available as supporting detail instead of asking leadership to reconstruct the story from every closed ticket.
JLL's public 2026 global FM report discusses the difficulty of consistently measuring outcomes and fragmented decision rights. That is context from a global organizational survey, not a US small-business benchmark. This template turns the issue into a local discipline: define the decision and the evidence needed to make it.
Agree on definitions before drawing a trend
Measure response from intake to the first substantive acknowledgment, and resolution from intake to confirmed completion. Specify whether you report elapsed time or working time, whose service calendar applies and how waiting periods are handled. Do not quietly exclude inconvenient cases.
A median can describe a typical completed request, but it hides the unfinished queue. Show open aging and the longest waiting items beside completion time. Keep counts visible so readers can recognize when a small sample makes a percentage unstable.
| Measure | Working definition | Decision it supports |
|---|---|---|
| New / completed / open | Distinct requests in the period; state cutoff | Capacity and backlog review |
| Response time | Intake to first substantive acknowledgment | Intake coverage |
| Resolution time | Intake to confirmed completion; show calendar | Workflow delays |
| Open aging | Time since intake for unresolved requests | Escalation and prioritization |
| Repeat issues | Linked recurrence within a defined window | Provider or root-cause review |
| Cost variance | Approved cost versus invoiced amount | Scope and approval control |
Explain costs with comparable categories
Separate recurring service fees, approved additional work, supplies and exceptional events. State whether amounts include tax and delivery and whether they are actual invoices, commitments or estimates. For multi-location comparisons, show the period, site scope and a relevant denominator such as attendance days when that data is dependable.
A higher cost may reflect an office opening or necessary work deferred from a prior month. Add context before describing a site as inefficient. Do not turn a lower invoice total into savings without checking whether service volume or quality changed.
Treat released time as a measured estimate
If you report reduced client involvement, document the baseline method. Use comparable categories and record the client's actual time spent on approvals, clarifications and follow-ups. A hypothetical time allowance can support planning, but label it as an estimate rather than a demonstrated SFI outcome.
Released capacity is not automatically cash saved or revenue earned. Report the operational change first. A separate financial estimate should disclose the internal rate and whether it represents avoidable expense or an opportunity-cost assumption.
Close the report with an action register
For each recommendation, show the problem, evidence, proposed action, expected operational effect, approval required and review date. Distinguish a task the coordinator can perform from a client decision. Carry unresolved actions forward with an updated reason, rather than letting them disappear from the next report.
Illustrative entry: repeated printer callouts justify a comparison of continued repair and replacement. The coordinator prepares service history and quotes; the client decides. The report should not claim that replacement will save a specific amount unless the comparison supports it.
Keep the reporting work proportionate
Capture category, timestamps, owner, cost and completion evidence while the request is handled. Start with a short report and remove measures nobody uses. SFI can discuss reporting appropriate to an agreed workflow and available data; it should not imply dashboards or integrations beyond confirmed capabilities.
Sources and reading limits
The workflow and templates are editorial proposals. External sources provide the context described below; they do not verify SFI results or delivery capabilities.
- IFMA — Bridging Data & Decision-Making in FM ↗
April 7, 2026; public abstract only. Linking operational activities to assets; full downloadable paper not reviewed. Accessed November 4, 2026.
- JLL — Global State of Facilities Management 2026 ↗
October 27, 2026; global organizations across 15 countries. Public HTML read; no paywalled report or US-only inference. Accessed November 4, 2026.
