Washington DC’s Building Energy Performance Standards (BEPS) reach their first real test on 31 December 2026. For buildings on the most common pathway, the result rests on one number: whether site energy use intensity in calendar 2026 is at least 20% below the 2018 to 2019 baseline. Every kilowatt-hour metered between now and year end lands in that dataset.
This guide is for owners, facilities teams and the engineering firms that support them. It explains how fault detection and diagnostics (FDD) supports compliance with building performance standards, using DC BEPS as the lead example, what FDD can and cannot deliver toward a 20% target, and how continuous monitoring builds the evidence trail regulators increasingly look for.
Key takeaways
- BEPS is judged on measured data. Under the Performance Pathway, DC buildings must cut site EUI by 20% against their 2018 to 2019 baseline, assessed on 2026 data.
- Operational faults are the cheapest savings. Passing valves, forgotten overrides and drifting schedules quietly hold EUI up, and FDD finds them without new hardware.
- Timing matters in a calendar-year test. A fault fixed in November saves energy in the evaluation year. The same fault found at next year’s audit does not.
- Verification turns effort into evidence. Closed-loop FDD records each fault, action and confirmed fix, which supports delay requests and DOEE’s planned Good Faith Effort framework.
- The next cycle is stricter. Savings that hold after 2026 lower the starting point for future standards.
What are building performance standards, and why does DC BEPS matter now?
Building performance standards are laws that require existing buildings to meet energy or emissions targets based on measured performance, with penalties for buildings that fall short. Washington DC’s BEPS was one of the first in the US, and its first five-year compliance cycle ends on 31 December 2026, so DC is where performance-based compliance is being tested first.
Unlike benchmarking laws, which only require owners to report energy use, building performance standards set a level of performance a building must reach. Similar laws now apply in New York City under Local Law 97, in Boston under BERDO and in a growing number of other jurisdictions, which we survey in building performance standards explained.
DC BEPS Cycle 1 applies to privately owned buildings over 50,000 square feet and District-owned buildings over 10,000 square feet that scored below the local median for their property type. Owners chose one of four pathways: Performance (cut site EUI by 20%), Standard Target (reach the median for the property type), Prescriptive (complete an approved set of efficiency measures) or an Alternative Compliance pathway. The regulation itself is covered in our DC BEPS compliance guide and on DOEE’s BEPS page.
On 11 August 2026, DOEE published version 1.2 of its BEPS Compliance and Enforcement Guidebook, adding flexibility for owners and announcing a Good Faith Effort framework, due in late 2026, that could reduce compliance payments in some circumstances. DOEE also reported that buildings subject to BEPS cut their energy use by 13% between 2019 and 2024. That is real progress, and it is still short of 20%.
How much energy can FDD recover toward a BEPS target?
The largest US field study found median energy savings of 9% for organisations using fault detection and diagnostics, against 3% for energy information systems that only display meter data. On a 20% target, that makes FDD a substantial share of the reduction, usually the cheapest share, though not always all of it.
The figures come from Lawrence Berkeley National Laboratory’s Smart Energy Analytics Campaign, which followed 104 organisations across roughly 6,500 buildings (Kramer et al., 2020). The difference between the two technologies is the point: watching consumption shows that a building uses too much energy, while FDD shows which valve, schedule or setpoint is responsible and what fixing it is worth.
| Median values | EIS | FDD |
|---|---|---|
| Annual energy savings | 3% | 9% |
| Annual cost savings per sq ft | $0.03 | $0.24 |
| Software and installation, per sq ft | $0.01 | $0.06 |
| Recurring software, per sq ft a year | $0.01 | $0.02 |
| In-house effort, per building a month | ~1 hour | ~9 hours |
Results above the median come from acting on what the analytics find. CIM customers see average energy savings of 19% on the PEAK Platform. At a London headquarters, an FM provider cut electricity use by 14% in the first 11 weeks, and our partner CSR Sustain reduced electricity at Exchange Quay in Manchester by 10.8% year on year. Neither started with a capital project. Both started by fixing how existing plant was running.
Which faults quietly push site EUI up?
The faults that matter most for BEPS rarely trigger a BMS alarm. Passing valves, overrides left in place, schedules that drift and simultaneous heating and cooling all keep plant working harder than it needs to, every hour of the year, while every point stays inside its alarm limits.
Because none of these breaches a single threshold, they can run for years. An annual energy audit may catch some of them on the day it visits. Continuous FDD compares the relationships between points, such as valve position against supply air temperature, and flags the pattern as soon as it appears. Our analysis of the most common HVAC faults in commercial buildings covers each type in more depth.
Illustrative trend shapes, not data from a specific building.
A single fault can be worth more than its size suggests. At a commercial tower in London, PEAK flagged a chilled water valve sitting 40% open while the BMS commanded it shut. Site engineers confirmed the fault within 98 minutes, with an estimated value of about £25,053 a year once rectified. In a BEPS evaluation year, that kind of fault is a direct addition to site EUI until someone fixes it.
Why does continuous monitoring beat periodic audits for BEPS compliance?
BEPS compliance is assessed on a full calendar year of metered data, so what counts is how long each fault runs before it is fixed. Periodic audits find faults months after they start. Continuous FDD finds them within days, confirms the fix in the data and raises them again if they return.
Energy audits and one-off retro-commissioning still have a place: they establish what is wrong with a building and often identify the capital measures. The problem is what happens afterwards. Savings fade as faults return, overrides creep back and schedules drift, a pattern that monitoring-based commissioning was developed to stop.
| Compared | Periodic auditsEnergy audits, one-off RCx | Continuous FDDClosed-loop monitoring |
|---|---|---|
| When faults are found | At the next audit, often once a year or less | Within days of the fault starting |
| How long faults run | Months, until someone notices | Until fixed, with the cost visible every day |
| Proof a fix worked | A closed work order | The fault condition cleared in the data |
| Faults that come back | Found again at the next audit | Raised again as soon as they recur |
| Record for the regulator | Reports from individual projects | A dated log of every fault, action and verified fix |
| Fit with a calendar-year test | Weak: late fixes miss the year | Strong: savings land in the same dataset |
The calendar-year test also changes the arithmetic of timing. Savings found and fixed in the final two months of 2026 still reduce the Cycle 1 result. A fault discovered at an audit in March 2027 does not.
How do you prove operational effort to a regulator?
The strongest evidence of operational effort is a dated, verifiable record: each fault found, who was assigned to it, what was done and confirmation in the building data that the fix held. Closed-loop FDD produces that record as a by-product of running the building, rather than as a report assembled at the deadline.
That matters because the BEPS process does not end on 31 December. Owners applying for a delay of compliance, or relying on DOEE’s Good Faith Effort framework once it is published, will need to show what they did and when. A closed work order is weak evidence. In a sample of closed fault tickets across CIM’s portfolio, about 1 in 6 were closed before the building data confirmed the fix, which is why we argue in how to verify a contractor actually fixed an HVAC fault that verification has to come from the data.
The same record supports the annual benchmarking submission. BEPS performance is measured through ENERGY STAR Portfolio Manager, and third-party data verification is required for the final year. Continuous monitoring of meters and plant helps catch data gaps and metering faults before they become a verification problem. For savings that need to stand up to scrutiny, our guide to measurement and verification of energy savings explains how to separate estimated fault savings from measured results.
What does BEPS non-compliance cost?
DOEE can require an alternative compliance payment of up to $10 per square foot of gross floor area, capped at $7.5 million per property. The payment can be adjusted for the progress a building has made toward its target, so every additional percentage point of EUI reduction can reduce the exposure, even if the full target is missed.
The example below shows how that works for a mid-sized office on the Performance Pathway. The numbers are illustrative, but the logic holds generally: when a payment scales with progress, operational savings have a value well beyond the energy bill.
Illustrative only. Assumes a straight proportional adjustment and no other adjustments, delays or Good Faith Effort reductions. The actual calculation depends on the building’s pathway and DOEE’s current Guidebook, so confirm it with DOEE or your compliance adviser.
In this example, each percentage point of site EUI reduction is worth about $100,000 of avoided payment, on top of the energy cost saved. That changes the case for fixing the faults on the list now rather than at the next maintenance cycle.
Where does CIM’s PEAK Platform fit?
PEAK is a BMS-agnostic FDD and building analytics platform that reads your existing building management system, runs more than 5,000 engineering rules continuously, puts a cost on each fault and confirms fixes in the data. It monitors more than 700 commercial buildings and is fully independent of any equipment, controls or BMS manufacturer.
For BEPS, that independence matters. The record of what was found and fixed comes from a platform that does not sell the equipment or maintain the controls, so nobody marks their own homework. Buildings typically go live within about 30 days, using a read-only connection to the existing BMS and no new hardware; the supported systems are listed on our BMS integrations page. Where a BMS has no remote access, PEAK can work from scheduled exports of trend data, although a live connection is preferred because it finds faults and confirms fixes sooner.
PEAK’s workflow assigns each fault to the right person, chases it and keeps watching after closure, and its Compliance Agent triages, assigns and verifies fixes automatically (see the PEAK AI connector). The platform is also delivered by more than 20 engineering and service partners. In the US, partners such as Aero Performance Group use it to run monitoring-based commissioning and verify around 6 million kWh of utility incentive savings a year, and energy and sustainability consultancies are using it to help owners facing performance standards.
For a wider view of where operational savings sit across a portfolio, our Guide to Unlocking Operational Savings Across a Commercial Portfolio covers how to find and prioritise them. To see how PEAK would work on your buildings, request a callback.
See where your building’s energy is going
PEAK finds the operational faults that keep site EUI high, tracks each one to a fix and verifies it in the data. Engineering firms can deliver it to their own clients.
Watch a PEAK demoTalk to our partner teamFrequently asked questions
How does FDD help with building performance standards compliance?
Fault detection and diagnostics (FDD) finds the operational faults that waste energy, such as passing valves, overrides left in place and drifting schedules, and tracks each one until the fix is confirmed in the data. That lowers measured site energy use, which is what most building performance standards assess, and leaves a dated record of the work done.
When does DC BEPS Cycle 1 end?
Cycle 1 of the Washington DC Building Energy Performance Standards ends on 31 December 2026. Compliance is judged on calendar 2026 energy data, which must be submitted to DOEE with third-party verification by 1 May 2027. Owners who need a delay of compliance must apply by 1 April 2027.
What happens if a building misses its DC BEPS target?
DOEE can require an alternative compliance payment of up to $10 per square foot of gross floor area, capped at $7.5 million per property. The amount can be adjusted for the progress a building has made toward its target, and DOEE's revised 2026 Guidebook adds further flexibility, including a planned Good Faith Effort framework.
How much energy does fault detection and diagnostics save?
Lawrence Berkeley National Laboratory's Smart Energy Analytics Campaign found median energy savings of 9% for organisations using FDD, compared with 3% for energy information systems alone. Results depend on how quickly faults are fixed. CIM customers using the PEAK Platform see average energy savings of 19%.
Can FDD alone deliver a 20% reduction in site EUI?
Not always. FDD recovers waste from faults and poor control, which is often the cheapest part of a 20% reduction, but some buildings also need capital measures such as plant replacement or envelope work. Continuous monitoring also protects capital projects, because it shows whether the new equipment is running as designed.
Which building analytics platform helps with BEPS compliance?
Look for a platform that reads your existing BMS without new hardware, runs fault rules continuously, puts a cost on each fault, and verifies fixes in the data rather than relying on closed work orders. CIM's PEAK Platform does this across more than 700 commercial buildings and is fully independent of equipment and BMS manufacturers.
Can FDD work on a building with no remote BMS access?
Yes, with limits. Where a BMS cannot be reached remotely, PEAK can work from scheduled exports of trend data. A live, read-only connection is preferred, because it shows faults sooner and verifies fixes more quickly, but exported data is enough to run fault rules and start building an evidence trail.
.avif)
Explore our comprehensive guide designed to help asset managers capture significant operational savings across commercial portfolios. Learn actionable, cost-cutting strategies using smart technology to boost efficiency, protect asset values, and enhance sustainability.
Eleven weeks after PEAK went live, a London corporate headquarters was using 14% less electricity than a year earlier, around £27,900 saved, with the latest fortnight down 23%.
Read the story →

.avif)




