Move from allocation to measurement: what to meter, where, and how to justify it
Master meter
Whole building
Submeters
Tenant suites or systems
System meters
HVAC, lighting, EV charging, etc.
Tenant meters
Tenant-controlled, sometimes inaccessible
Beginner rule: Metering only creates value if the data is actually ingested, QA'd, and used.
| Option | What it measures | Value | Feasibility | Cost | Data access | Recommended? | Notes | |---|---|---|---|---|---|---|---| | Add tenant submeters | suite usage | high | medium | $$ | high | | | | Add system meters | HVAC/lighting | medium-high | medium | $$ | high | | | | Metering platform | automated exports | high | medium | $$ | high | | | | Do nothing + allocate | estimated | low | high | $ | medium | | |
Metering Data Plan Building: Metering changes: Data source (platform/export): Ingestion cadence (monthly/weekly): Data fields required: Evidence storage: QA checklist: Owner: Use cases: - reporting - tenant engagement - anomaly detection - cost recovery / billing support
Metering Pilot Plan Building: Goal (what problem are we solving?): Meters to install: Install timeline: Data ingestion owner: Success metrics: - % measured coverage increase - reduction in proxy/allocation usage - data availability latency
v1.0 (2026-01): Latest release