The Coverage Problem: When 75% of Your Building Data Is Missing

EDRA's B2 component measures something deceptively simple: what proportion of total building consumption is actually represented in your dataset? If a building has 5 meters but only 2 are submitting data, coverage is 40%. Below 75%, performance scoring is blocked entirely. The building might be the most energy-efficient asset in your portfolio — but without sufficient data coverage, it cannot be scored.

Most portfolios discover this problem only after submission rejection. The assumption is that "we have data for all our buildings" — which is technically true. They have some data for all buildings. But GRESB and ENERGY STAR require representative data: consumption figures that account for the whole building, not just the landlord-controlled areas or the meters that happen to report consistently. Tenant-metered spaces, common areas with separate utility accounts, and sub-metered floors all contribute to the coverage calculation.

The gap between "having data" and "having coverage" is where most submissions fail. A 22-asset mixed-use portfolio might report energy data for every asset — but when you examine the metering boundaries, nine of those assets are only capturing 40-60% of actual consumption. The retail tenants have their own utility accounts. The parking garage runs on a separate meter. The rooftop equipment is billed to a different entity. None of this shows up in the portfolio-level view until someone maps the metering boundary against the physical boundary.

The fix is operational, not technological. It starts with metering boundary audits: walking each asset's physical footprint against its data footprint. Where do the meters end and the gaps begin? From there, tenant data collection agreements, sub-meter installation, and utility account consolidation close the coverage gap. These are 4-8 week projects, not 12-month transformations — but they have to be identified first.

EDRA's B2 score makes coverage visible before it becomes a submission blocker. Every asset gets a coverage percentage. Every gap gets a reason code. The portfolio manager sees exactly which assets are at risk and what specific data is missing — not after rejection, but before the submission cycle even begins.