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.

MeasureWorking definitionDecision it supports
New / completed / openDistinct requests in the period; state cutoffCapacity and backlog review
Response timeIntake to first substantive acknowledgmentIntake coverage
Resolution timeIntake to confirmed completion; show calendarWorkflow delays
Open agingTime since intake for unresolved requestsEscalation and prioritization
Repeat issuesLinked recurrence within a defined windowProvider or root-cause review
Cost varianceApproved cost versus invoiced amountScope 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.