11.4 Ongoing Commissioning Reporting & Stakeholder Communication
Key Takeaways
- Providing ongoing commissioning reports is a Domain 7 task worth 2 of that domain's 8 questions, because OCx programs are cancelled when their value cannot be demonstrated rather than when they stop working.
- Mature programs issue three distinct products: a weekly or continuous operational fault report for technicians, a quarterly periodic OCx report for facility management, and an annual executive performance summary for the owner and finance leadership.
- Faults must be quantified in money and comfort consequence rather than in counts, because a fault list without monetized or complaint-linked impact gives no basis for prioritization.
- Reporting drift honestly is more credible and more useful than reporting only good news, since performance degradation is the expected condition the ongoing commissioning program exists to catch.
- Every savings claim must trace to a stated baseline and method, and when occupancy or building use materially changes the baseline is re-established rather than quietly stretched.
11.4 Ongoing Commissioning Reporting & Stakeholder Communication
Quick Summary: Provide ongoing commissioning report(s) is a named Domain 7 task worth 2 of the domain's 8 questions — a quarter of the ongoing commissioning material. The reason is blunt: ongoing commissioning programs are cancelled at budget time, not because they stop working, but because nobody could demonstrate that they were working. The OCx report is the instrument that keeps the program funded. It has a different audience, a different cadence, and a different burden of proof than the final commissioning report on a construction project.
1. Three Reports, Three Audiences
A single document cannot serve everyone. Mature OCx programs issue three distinct products:
| Report | Audience | Cadence | Answers |
|---|---|---|---|
| Operational fault report | Facility operations staff | Weekly or continuous | What is broken right now, where, how bad, and what to do about it |
| Periodic OCx report | Facility management and engineering | Quarterly | What did we find, what did we fix, what did it save, what is still open |
| Executive performance summary | Owner, finance, sustainability leadership | Annual, or aligned to the budget cycle | Is the program returning more than it costs, and what should be funded next |
The most common failure is sending the operational fault report upward. A 400-row fault list is actionable for a technician and meaningless to a chief financial officer, who concludes either that the building is broken or that the report is noise. Neither conclusion funds next year's program.
2. The Periodic OCx Report
This is the workhorse. It covers the review period and follows a stable structure so period-to-period comparison is possible.
| Section | Content |
|---|---|
| Period summary | Dates covered, systems monitored, data completeness percentage |
| Performance against KPIs | Each tracked KPI with current value, target, prior period, and trend direction |
| Energy and cost performance | Weather-normalized consumption against the baseline, with savings or drift quantified |
| IEQ performance | Thermal comfort and ventilation compliance metrics against the CFR |
| Faults detected | Count by system and by severity, with the diagnostic conclusion |
| Faults resolved | What was corrected, by whom, and the verified effect |
| Faults outstanding | With age, owner, and estimated cost of continued operation |
| Measures implemented this period | Description, date, and verification status |
| Persistence check | Whether previously implemented measures are still operating as designed |
| Recommendations | Prioritized, with estimated cost, benefit, and required decision |
| CFR review status | Whether facility requirements changed and whether a CFR revision is needed |
Quantify Faults in Money and Comfort, Not Counts
"Forty-seven faults detected" tells a facility manager nothing about priority. The same information stated as consequence drives action:
- "Economizer damper failure on AHU-6 is adding an estimated $940 per month in mechanical cooling; parts and labor to repair are approximately $1,800."
- "Simultaneous heating and cooling on the third floor east zones is wasting an estimated 61,000 kBtu per month and correlates with 14 of the 22 comfort complaints logged this quarter."
This is why the fault triage and waste quantification methods matter: they convert a diagnostic output into a decision the owner can actually make. A fault list without monetized or comfort-linked consequence is a list nobody prioritizes.
Report Drift Honestly
An OCx report that only reports good news is not credible and, worse, is not useful. Drift is the expected condition — that is why the program exists. A report showing that three of eleven measures degraded, that the cause was identified, and that two were restored is far stronger evidence of a functioning program than a report claiming everything held perfectly.
3. The Executive Summary and the Funding Argument
The annual executive product answers one question: did this program return more than it cost? It should fit on one or two pages.
| Element | Example framing |
|---|---|
| Verified savings this year | Weather-normalized energy cost avoided, against the documented baseline |
| Program cost | Provider fees, analytics platform subscription, internal labor |
| Net return | Savings minus cost, stated as a ratio and in dollars |
| Non-energy benefits | Complaints resolved, emergency service calls avoided, equipment runtime reduced, compliance obligations met |
| Risk avoided | Faults caught before failure, with the avoided consequence |
| Recommended next investments | Ranked, with cost and expected return |
Non-energy benefits are frequently the stronger argument. A 30% reduction in hot and cold complaint tickets is visible to leadership in a way that a kilowatt-hour reduction is not, and avoided emergency service calls have an obvious cost.
Anchoring Claims to a Defensible Baseline
Every savings claim in an OCx report must trace to a stated baseline and a stated method — the weather-normalized regression model, its period, and its statistical fit. Claims that cannot survive a finance department's question about methodology damage the program's credibility more than a smaller, well-supported number would. When the baseline is no longer valid — because occupancy, hours, or building use materially changed — the report says so and the baseline is re-established rather than quietly stretched.
4. Making Reports Drive Action
A report that is issued and not discussed changes nothing. Two mechanisms convert reporting into behavior:
- The quarterly review meeting. The periodic report is the agenda. Attendees are the provider, facility management, operations, and an owner representative. Each outstanding fault gets a named owner and a date. The meeting minutes become the action record.
- Closed-loop integration with the maintenance system. Faults that require physical correction become work orders with the diagnostic evidence attached, and the work order's closure is verified against trend data rather than against the technician's completion note.
Exam pattern: a scenario describes an ongoing commissioning program at risk of cancellation despite technically sound analytics. The correct answer improves the reporting and communication — audience-appropriate products, consequence-based quantification, verified savings against a defensible baseline, and a review forum that assigns ownership — rather than adding more fault rules or more sensors.
A facility director forwards the ongoing commissioning platform's weekly fault report, containing 412 open fault instances, to the chief financial officer as evidence that the analytics program is working. What is the likely outcome and the better approach?
Which statement in a quarterly ongoing commissioning report is most likely to drive corrective action?
An ongoing commissioning provider's weather-normalized baseline model was established three years ago. Since then the building converted two floors from open office to a data-processing center operating continuously. How should this affect the current period's savings reporting?
You've completed this section
Continue exploring other exams