Industry solutions · Facilities & Asset Management

Facilities and Asset Management Reporting for Portfolios and Service Levels

Service level performance, reactive versus planned work, asset condition, and cost per square metre across a portfolio — in one weekly operating view.

  • SLA performance measured per contract, not averaged
  • Reactive versus planned tracked as a trend by site
  • Lifecycle and condition data tied to the spend decision
Book the Reporting Friction Audit →See the sprint

Weekly pack

Portfolio weekly pack

Fake data
SLA performance96%Contract Manager
Reactive work34%Facilities Manager
Open work orders218Helpdesk
Cost per m²$41Finance
Condition audits due12Asset Manager

Reporting areas

What facilities and asset teams report on first

Each one starts as a single trusted number with a named owner, then earns its place in the weekly review.

Service level performance

Response and rectification against the SLA for each contract, with breaches attributed to access, parts, or resourcing rather than reported as a single percentage.

Reactive versus planned work

The ratio tracked over time by site and asset class, because the trend is what indicates whether the maintenance strategy is working.

Asset condition and lifecycle

Condition ratings, remaining life, and replacement forecast tied to the capital plan, so renewal spend is argued from data rather than from age.

Cost per site and per square metre

Total cost of occupancy normalised across a portfolio, which is what makes sites comparable when they differ in size and use.

Contractor performance

Response times, first-time completion, rework, and cost by contractor, on the same pack used for internal performance.

Compliance and statutory routines

Essential services, fire, electrical, and other statutory routines tracked to due date with evidence linked for audit.

Systems we pull from

Built from the systems already managing the portfolio

We build on what you already own. No new platform to buy, and each system stays the record of truth for its own work.

Send us your report pack →
CAFM and facilities management platforms
Helpdesk and work request systems
Asset registers and condition audit data
Contractor invoices and purchase orders
Building management and metering data
Statutory compliance and certification records

FAQ support

Frequently asked questions

Clear answers on timeline, investment, and delivery scope.

Our SLA reporting comes from the contractor. Can we produce our own?

Yes, and having an independent view is usually the reason this gets built. Contractor-supplied SLA reporting is calculated by the party being measured, often with exclusion rules that are not visible to you. Building the same measure from your own helpdesk and work order data gives a comparable number, and where the two differ the difference is itself informative.

We manage sites across different states with different systems. Does that work?

Yes, and portfolio-level comparability is the main benefit. The work is in normalising the data — different work order categories, different priority definitions, different cost coding. That mapping is built once during the sprint, after which adding a site is configuration rather than a rebuild.

Can condition data drive the capital forecast?

It can, and that is the strongest use of this reporting. Condition rating plus remaining life plus replacement cost produces a renewal forecast that can be defended in a budget submission. The constraint is condition audit coverage — where audits are patchy, the forecast is shown with that gap visible rather than hidden behind an average.

Does this replace our CAFM system?

No. Work orders are still raised, dispatched, and closed in the CAFM system. The reporting reads from it, along with the finance and compliance data the CAFM system does not hold, which is precisely why a separate reporting layer is needed.

How do you handle cost per square metre across mixed-use sites?

By normalising carefully and being explicit about it. Cost per square metre is only comparable within a use class, so the reporting groups by use type and shows the basis on the page. A single portfolio-wide figure across warehouses and offices is a number that invites the wrong conclusion.

How long before the first portfolio view is live?

One to two weeks for a single view such as SLA performance or reactive-versus-planned. Three to six weeks for the full pack. Multi-site normalisation is the usual driver of the longer end of that range.

Related sectors

Agriculture & AgribusinessYield by block, input cost per hectare, machinery utilisation, and livestock or crop performance in one seasonal operating view built from the records you already keep.Food & Beverage ProcessingLine throughput, product yield and giveaway, quality holds, and batch traceability in one weekly operating view built from the plant data you already capture.Aged Care & DisabilityRoster coverage, service delivery against plan, staff compliance, and incident close-out in one weekly operating view — built from the systems you already use to run care.

Where to go next

Maintenance and reliability reportingBacklog, PM compliance, and failure history in detail.Dashboard / Reporting SprintThe audit-first delivery model.Compliance and training reportingStatutory routines and audit evidence reporting.Local government fitCouncil asset and service reporting.

Send the current portfolio report.

The Reporting Friction Audit starts from the facilities pack you produce today and returns a friction map plus a 30-day fix path before any dashboard is scoped.

Book the Reporting Friction Audit →