Most multifamily energy programs start with a technology decision: which sensors, which platform, which dashboard. That’s backwards. The programs that actually work start with a governance decision: who gets to see what data, who consents to sharing it, and who benefits when it’s used well. Technology is the easy part. Trust is the part that determines whether any of it gets adopted.
The friction shows up early. A property manager wants whole-building energy data to benchmark performance, but that data lives across dozens or hundreds of individually metered units, records the manager often doesn’t control and residents have little reason to hand over without knowing why. Ask for that data before explaining the benefit, and participation drops. Deploy sensors before residents understand what’s being measured, and a program is managing a trust problem instead of an energy problem.
This isn’t a hypothetical edge case. It’s the standard failure pattern across affordable and market-rate multifamily programs alike: strong technical design, weak adoption, because the sequencing ran technology first and governance second. It shows up again at the ownership layer, too. Owners who don’t directly pay the utility bill have little financial reason to invest in efficiency, and tenants who don’t control the building have little ability to act on the data even when they want to. A program that doesn’t address who benefits, explicitly, walks straight into that gap.
Three principles flip the sequence back around
- Consent before collection. Residents should understand what’s being measured, why, and what happens to it, before a single sensor goes in. Retrofitting consent after deployment reads as an apology, not an invitation.
- Minimization over maximization. Collect what a program actually needs to answer its question, not everything a platform is capable of capturing. A narrower ask is also an easier yes, and it’s easier to explain in one sentence at a resident meeting.
- Visible benefit-sharing. If a program identifies savings, residents and owners both need to see, concretely, where that value goes. Data governance that only serves the party doing the measuring doesn’t hold up over a multi-year program, no matter how sound the engineering behind it is.
None of this replaces good technical work. Accurate whole-building data, real benchmarking, and anomaly detection are still what make a program worth running, and as more cities move toward mandatory energy reporting for larger buildings, the technical bar is only going up. But the order matters. Programs that lead with governance and earn trust first tend to get the participation rates that make the technology worth deploying. Programs that lead with the technology and treat governance as a compliance afterthought tend to stall exactly where the first ones didn’t: the point where they need residents, owners, and utilities to actually say yes.
That’s the sequencing built into C-MEIP: privacy-first governance, clear roles, and defined consent before any data collection begins. Not because it’s the safer thing to say in a proposal, but because it’s the only sequencing that scales past a single pilot building.