Updated: Jul 23, 2026 • 3 min read

Build a multi-site facilities performance scorecard

A site scorecard is useful when it creates a fair comparison and explains why performance differs across buildings.

Why this workflow breaks

Regional leaders receive incompatible spreadsheets from sites and cannot separate demand mix from controllable operating performance.

Manual reporting usually fails in three places:

The goal is not to remove the operations director, account director, regional facilities manager, or contract manager from the decision. It is to prepare consistent evidence and a reviewable first draft before the deadline.

Data to connect

Start with read-only access to work orders, planned maintenance, inspection results, spend records, occupancy or footfall context, satisfaction data, and site targets.

Document the reporting period, source of truth, owner, and refresh schedule for each input. If two systems disagree, the Agent should flag the conflict and show both values instead of silently selecting one.

Metrics and signals

Use thresholds that correspond to an action. A red status without a defined response becomes noise. Review thresholds after the first three runs and record any definition change.

What the Agent should produce

The expected output is a monthly scorecard with normalized metrics, trend, red-amber-green status, drivers, and actions for every site.

A strong output contains:

Example Agent instruction

"Create the monthly facilities scorecard using approved site targets and metric definitions. Compare each site with its own trend and relevant peer group. Explain material movements, show demand context, and avoid ranking sites on metrics that are not comparable."

Add your own thresholds, recipients, approval rules, and output format. Keep the first version internal until the owner confirms that the calculations and narrative match the existing process.

Implementation workflow

  1. Connect the approved sources through Connectors or provide a controlled export.
  2. Write down metric definitions and materiality thresholds.
  3. Run one historical period and compare the result with the manually approved report.
  4. Correct mapping, ownership, and narrative issues before scheduling.
  5. Deliver recurring internal drafts in a Document.
  6. Require approval before any external message or high-stakes recommendation.
  7. Use Logs to review sources, timing, outputs, and failures.

Review checklist

Before approving an output, confirm:

How to measure success

Measure preparation hours saved, on-time delivery, exception lead time, false-positive rate, and the percentage of outputs approved without major correction. The workflow is successful when the owner begins the review with evidence and decisions, not with data collection.

Next step

Test this workflow on one reporting period with read-only data. Keep the current manual process running until the output reconciles, then schedule the Agent and review thresholds after the first three runs. Book a demo to map the workflow to your stack.