Scope 2 emissions reporting — the indirect greenhouse gas emissions from purchased electricity — has moved from a voluntary disclosure exercise to a practical operational requirement for a growing share of commercial and industrial organizations. Frameworks like the GHG Protocol's Scope 2 Guidance, CDP disclosure requirements, and the SEC's climate disclosure rules have all raised the data quality bar significantly in recent years.
Most sustainability teams we encounter are working with annual electricity totals pulled from monthly utility bills, converted to emissions using an eGrid regional average emission factor. That approach satisfies the minimum requirements for many disclosure frameworks, but it increasingly does not satisfy auditors, supply-chain customers requiring supplier-level disclosure, or internal sustainability targets that are getting more specific each year.
Granular energy data — hourly or sub-hourly interval data, broken down by system and building zone — changes what is possible in Scope 2 reporting. This article is about how to structure that data collection and what you can do with it.
Location-Based vs. Market-Based Scope 2 Accounting
Before discussing data granularity, it is worth being precise about which Scope 2 accounting method is being served. The GHG Protocol's Scope 2 Guidance defines two methods:
Location-based accounting uses grid average emission factors for the region where the electricity is consumed. This is the simpler method and requires only total consumption data and a regional EF (the EPA's eGrid database for U.S. facilities). Monthly billing data is sufficient.
Market-based accounting uses contractual instruments — renewable energy certificates (RECs), power purchase agreement specifics, or supplier emission rates — to calculate emissions. This method requires more sophisticated data management and is where granularity starts to matter.
If you are pursuing a 24/7 carbon-free energy matching strategy — where your electricity consumption is matched to carbon-free generation on an hourly basis rather than an annual total — you need hourly consumption data at minimum. Annual matching can be done with annual totals. Hourly matching requires hourly data. Google's CFE (Carbon-Free Energy) score methodology, for example, explicitly requires hourly matching, not annual.
Most organizations reporting Scope 2 today use location-based accounting. But the trajectory of disclosure requirements is clearly toward more granular market-based accounting, and organizations that build the data infrastructure now will be ahead when that shift accelerates.
What Granular Data Actually Enables
Beyond the 24/7 matching question, hourly or 15-minute interval data unlocks several reporting and analysis capabilities that monthly billing totals cannot support:
Emissions intensity by operating mode. With interval data, you can calculate emission factors separately for occupied hours (typically higher-emission on-peak grid periods) vs. unoccupied hours (often lower-emission off-peak grid periods). This allows you to report accurately on the emissions impact of specific operating decisions, not just total consumption.
System-level and zone-level attribution. If your building has sub-metering at the system level — separate meters or submeter channels for HVAC, lighting, process loads, and data center infrastructure — you can break down Scope 2 emissions by system type. This matters for internal accountability: the facilities team may be responsible for HVAC emissions, while IT is accountable for data center load, even if it all appears on a single utility bill.
Before-and-after change attribution. When you retrofit lighting, commission a new chiller, or deploy energy optimization software, interval data lets you measure the emissions reduction attributable to that specific change. Monthly billing data makes attribution nearly impossible because too many variables change simultaneously. Interval data, combined with degree-day normalization, makes attribution defensible.
Science-based target tracking. Organizations with SBTi (Science Based Targets initiative) commitments need to show a measured reduction trajectory against a base year. Monthly billing data is sufficient for the commitment level, but operational decision-making benefits from interval granularity to understand whether you are on track within the year.
The Data Infrastructure Gap Most Buildings Have
Most commercial and industrial buildings have a utility meter with AMI (Advanced Metering Infrastructure) capability — they just do not know it or have not activated the data access. In most U.S. utility territories, commercial and industrial accounts can request interval data download through the utility portal or via Green Button Connect (a standardized API for energy data sharing). The data is usually available, just not pulled automatically.
Sub-metering is a different story. Whole-building consumption from the utility meter is increasingly accessible. System-level sub-metering — separate channels for HVAC, lighting, process loads — is much less common unless it was specified at construction or added during a retrofit. Many buildings have a BMS with circuit-level monitoring on their main electrical panels, but the data is not being exported anywhere useful for reporting purposes.
This is the infrastructure gap that matters most for granular Scope 2 reporting. Getting 15-minute whole-building data from the utility AMI is a starting point. Getting system-level breakdown requires either: (a) sub-metering hardware at the distribution board level, or (b) disaggregation algorithms that infer system-level consumption from whole-building interval data plus equipment runtime telemetry from the BMS.
Option (b) is less precise than direct sub-metering but can be achieved without hardware installation if you already have BMS telemetry. The disaggregation accuracy depends on how detailed your BMS telemetry is, but for HVAC — typically 40–60% of commercial building energy use — it can be reasonably precise if you have zone-level temperature and equipment state data.
Structuring Your Monitoring for Reporting Readiness
If you are building or upgrading your energy monitoring infrastructure with reporting requirements in mind, here is the hierarchy we recommend thinking through:
Tier 1: Whole-building 15-minute interval data. This is the baseline. Activate Green Button or request AMI data export from your utility. If your utility does not offer this for your account class, request interval data directly from your account representative. Most C&I accounts can get this regardless of tariff structure.
Tier 2: System-level attribution. Even without sub-metering hardware, BMS telemetry combined with equipment nameplate data can produce reasonable HVAC attribution. Document the methodology clearly if you use this approach in disclosures — auditors and third-party verifiers will ask.
Tier 3: Time-of-use emission factors. Replace annual eGrid average factors with time-varying marginal emission factors for your region. NREL's Cambium database provides hourly marginal operating emission rates (MOERs) by EPA region, which give a more accurate picture of when your consumption is more or less carbon-intensive. This is particularly relevant if you are shifting load through demand response or predictive scheduling — you want to show that you are shifting toward lower-emission periods, not just reducing total consumption.
Tier 4: Hourly market-based accounting. This requires RECs or PPAs with hourly matching capability, plus hourly consumption data to match against. Most organizations are not here yet, but it is the direction the largest disclosure frameworks are pointing.
Where Optimization Software and Reporting Intersect
There is an underappreciated connection between energy optimization and sustainability reporting: optimization systems generate the interval-resolution telemetry that reporting systems need.
When Voltpathio connects to a building's BMS, it collects 15-minute interval data on energy consumption, HVAC runtime, zone temperatures, and equipment states. That same data feed is exactly what a sustainability reporting workflow needs for Tier 1 and Tier 2 reporting. The optimization system is not just reducing consumption — it is generating the audit trail that proves the reduction.
We are not saying that every energy optimization platform automatically solves the reporting data problem — the data needs to be exported, formatted, and integrated with whatever reporting tool your sustainability team uses. But the telemetry infrastructure is shared. Organizations that instrument their buildings for optimization are simultaneously instrumenting them for reporting, which makes the incremental cost of the reporting capability much lower.
The reverse is also true: organizations that invest in sub-metering purely for reporting purposes often find they have more than enough telemetry to support optimization as well. The data was collected; it just needs to be acted on.
A Note on Data Retention and Auditability
Scope 2 disclosures are increasingly subject to third-party assurance — limited or reasonable assurance reviews that look at data lineage, methodology consistency, and supporting documentation. For energy data, this means you need to retain raw interval data, the methodology used to calculate emissions from that data, and documentation of any normalizations or adjustments applied.
Monthly billing data retained as PDF utility bills does not satisfy this requirement well. An interval data export stored in a structured format (CSV or database) with documented timestamps, meter IDs, and emission factor version numbers does. This is not complicated to set up, but it requires intentional data management practices that are separate from the energy management workflow itself.
Build the retention requirement into your monitoring infrastructure from the start. Retroactively reconstructing base-year data from utility bills and PDFs is painful, and the effort grows with each year of gap.