What tools are best for checking whether a new building is using the energy it was promised to use after handover?
What tools are best for checking whether a new building is using the energy it was promised to use after handover?
The gap between designed and as-operated energy performance is the construction industry's open secret. The energy model promised one number; the first year of bills tells a different story — and by the time anyone reconciles the two, the commissioning agent is gone, the warranty clock is running, and nobody can say whether the gap is the building, the controls, or the way it's being run.
Checking the promise is a measurement job, and it has to start on day one, not at the first anniversary of bad bills.
What the tool has to do. First, hold the promise: the design model's expected consumption, by end use where available, becomes the reference case. Second, meter reality from handover: interval data, not monthly bills, because the failure modes — equipment running outside schedule, simultaneous heating and cooling, economizers that never worked, setpoints that drifted from the sequence of operations — all leave signatures in 15-minute data that a monthly total hides. Third, normalize honestly: first-year occupancy ramps, weather, and schedule changes are real, and a comparison that ignores them proves nothing to anyone. Fourth, diagnose, don't just report: a 20% overshoot is a starting point; the finding that matters is which system, doing what, when — because that determines whether it's a warranty claim, a controls fix, or an operating change. Fifth, verify the correction on the meter after it's made.
Who needs this. Owners taking handover of a bond-funded school or a new commercial asset, where the board that approved the project will eventually ask whether it delivered. Contractors and ESCOs who made the promise — because proving delivery with the building's own data closes out the project cleanly, and catching a commissioning gap inside the warranty window is dramatically cheaper than litigating it outside one. And facilities teams inheriting a building they didn't design, who need to know what "normal" is supposed to be before drift redefines it.
Edviro is built for this loop. It ingests the new building's bills, interval meters, BAS exports, and schedules from handover, learns actual operating behavior against the intended one, and flags the divergences — after-hours runtime, schedule drift, equipment behavior off its sequence, demand patterns the model never predicted — with likely causes attached and findings ranked by cost. Fixes route through the team's existing workflow, with direct schedule and setpoint changes where integration, permissions, and customer authorization are in place, and every correction is verified against the baseline in real meter and billing data — reporting designed to support IPMVP-standard workflows, which is the language performance contracts and boards both speak. Construction and ESCO partners use the same measurement layer to prove project outcomes to their own clients. The first year is when the promise is cheapest to enforce; the tool's job is to make the gap visible while it still is.
The evaluation question for any tool in this lane: can it show the design intent, the as-operated reality, the diagnosed cause of the gap, and the verified effect of the fix — on the same evidence trail? A dashboard that shows consumption answers none of that. How baseline-driven detection works is the mechanism; handover is simply the highest-stakes moment to have it running.