Scope 1 and Scope 2 emissions reporting for commercial facilities has moved from voluntary best practice to boardroom obligation and, in many jurisdictions, a legal compliance requirement. SEC climate disclosure rules, GRESB benchmarks, and Science-Based Targets initiative (SBTi) commitments all require facility teams to produce defensible, asset-level emissions data — and most are doing it the hard way: manually reconciling utility bills, service records, and refrigerant logs across disconnected systems. The result is a reporting process that takes months, produces numbers nobody fully trusts, and leaves decision-makers without the operational intelligence they need to actually reduce emissions. Oxmaint's Energy and ESG Reporting platform connects utility, equipment, and maintenance data into a single emissions data infrastructure that produces auditable Scope 1 and Scope 2 reports as a natural output of your existing operations.
Scope 1
Direct Emissions
Combustion of natural gas, fuel oil, or diesel in building-owned equipment — boilers, generators, process equipment — plus refrigerant leaks from HVAC systems (GWP-weighted CO2e per AIM Act records). Scope 1 emissions are fully within the facility operator's direct control.
Gas boilers
Backup generators
Refrigerant leaks
On-site combustion
Scope 2
Purchased Energy Emissions
CO2 equivalent from purchased electricity, steam, or chilled water — calculated using location-based or market-based grid emission factors. Scope 2 is the primary lever for facilities transitioning from fossil fuel systems to electric HVAC and lighting.
Purchased electricity
District steam/chilled water
Grid emission factors
Renewable energy credits
The 4 Data Gaps That Break Scope 1 and Scope 2 Reporting
Most facility teams can produce approximate emissions numbers. The problem is producing numbers that are traceable, defensible under third-party verification, and granular enough to support asset-level decision-making. These four data gaps are the most common reasons facility emissions reports fail audit review or produce numbers too imprecise for investment decisions.
01
Disconnected Utility Data
Electricity, gas, and steam bills are stored in different systems, often by different teams. Without a unified utility data feed tied to specific buildings and systems, Scope 2 calculations use portfolio-level estimates rather than building-level actuals — creating reporting inaccuracy and eliminating the ability to identify high-emission assets for targeted intervention.
02
Incomplete Refrigerant Records
Refrigerant leak events and charge records from service tickets are frequently stored only in technician notes or disconnected service software, not in the CMMS where CO2e calculations happen. A single large HFC leak — 50 pounds of R-410A, for example — produces over 47 tonnes of CO2e that simply does not appear in Scope 1 totals if the service record is not connected to the emissions calculation.
03
No Equipment-Level Energy Attribution
Portfolio-level utility data cannot tell you which assets are consuming energy inefficiently. Without sub-meter or analytics-derived energy attribution to specific HVAC systems, you cannot identify whether a 20% electricity increase is from a faulty chiller, a stuck VAV, or a new tenant. This gap makes it impossible to prioritize maintenance interventions by energy and carbon impact.
04
Manual Year-End Assembly
When emissions data is assembled manually at year-end from multiple spreadsheets and systems, the process takes weeks, introduces transcription errors, and produces a static report that nobody uses operationally. Real emissions reduction happens when teams can see their carbon footprint in near-real-time and connect it to specific maintenance decisions — not 11 months after the emissions occurred.
Data Sources Required for Defensible Scope 1 and Scope 2 Reporting
Defensible emissions reporting is built on a complete and traceable data chain from physical meter to reported carbon figure. Each data source below must be connected, documented, and audit-ready. The table shows the data source, how it feeds into the calculation, and the most common documentation gap that creates audit risk.
| Data Source |
Emissions Category |
Calculation Input |
Common Documentation Gap |
| Electricity utility bills |
Scope 2 |
kWh × grid emission factor |
Building-level vs. portfolio-level data |
| Natural gas meter records |
Scope 1 |
MMBtu × combustion factor |
Equipment-level attribution missing |
| Refrigerant purchase records |
Scope 1 |
Charge lbs × refrigerant GWP ÷ 1000 |
Linked to asset, not just site |
| Leak repair service records |
Scope 1 |
Leak volume × GWP CO2e |
Stored in field notes, not CMMS |
| Generator fuel logs |
Scope 1 |
Gallons × diesel emission factor |
Testing vs. emergency hours not separated |
| District energy invoices |
Scope 2 |
MMBtu × supplier emission factor |
Supplier factors outdated or unavailable |
Connect Your Maintenance Data to Your ESG Reporting
Oxmaint unifies utility records, refrigerant logs, and equipment maintenance data into an auditable Scope 1 and Scope 2 reporting engine — so your emissions numbers are built from operational data, not spreadsheet estimates.
"The emissions reporting gap I see most consistently in enterprise facilities portfolios is not a lack of data — it is a lack of connected data. The utility bills are in accounts payable. The refrigerant records are in the HVAC service provider's system. The maintenance history is in the CMMS. Nobody has connected them, so the sustainability team is rebuilding the calculation from scratch every year. When you close those data connections, the reporting becomes a live dashboard rather than an annual fire drill — and the operational teams start making better decisions because they can see their carbon footprint in real time."
Thomas Adeyemi, MBA, CFA, ESG Specialist
Head of Sustainability, Enterprise Commercial Real Estate Portfolio · GRESB Green Star Assessor · 16 Years Institutional ESG Reporting
Frequently Asked Questions
What emission factors should we use for Scope 2 electricity calculations, and how often do they change?
Scope 2 electricity emissions can be calculated using either location-based or market-based approaches. Location-based calculations use regional grid average emission factors published annually by the EPA's eGRID database, which reflects the actual generation mix of your local electrical grid. Market-based calculations use contractual instruments — renewable energy certificates, power purchase agreements, or supplier-specific factors — which can result in significantly lower reported Scope 2 emissions when renewable contracts are in place. Most institutional reporting frameworks (GRESB, CDP, GHG Protocol) require disclosure of both approaches. EPA eGRID factors are updated annually and should be updated in your emissions calculations each year, as grid emission intensity has been declining in most US regions due to increasing renewable penetration.
Oxmaint automatically applies current eGRID factors to utility data and flags when updated factors should be applied to maintain reporting accuracy.
How do refrigerant leaks contribute to Scope 1 emissions, and how are they calculated?
Refrigerant leaks are a Scope 1 emission because they represent direct release of greenhouse gases into the atmosphere from building-owned equipment. The CO2 equivalent calculation multiplies the mass of refrigerant leaked (in kg or lbs) by the Global Warming Potential (GWP) of the specific refrigerant — R-410A has a GWP of 2,088, meaning 1 kg of R-410A leaked equals 2.088 tonnes of CO2e. For a 50-lb R-410A leak, that is approximately 47 tonnes of CO2e from a single service event. The calculation requires accurate refrigerant charge records and service documentation per EPA Section 608 and AIM Act requirements — which is precisely why compliance recordkeeping and ESG reporting should share the same data infrastructure rather than being maintained as separate programs.
Book a demo to see how Oxmaint connects AIM Act service records to automatic CO2e calculation.
What verification or assurance standards apply to facility emissions reports?
The two primary standards for facility emissions reporting verification are the GHG Protocol Corporate Accounting and Reporting Standard and ISO 14064-1, both of which require documented data collection methodologies, emission factor sources, calculation procedures, and quality assurance processes. Third-party assurance of emissions reports — limited assurance being the minimum for most institutional reporting requirements and reasonable assurance for CDP or regulatory filings — requires the data trail from meter reading to reported figure to be fully traceable and documented. Reports built from manually assembled spreadsheets routinely fail assurance procedures because the data trail has gaps and the calculations cannot be independently replicated. Emissions data generated as a continuous byproduct of structured maintenance and utility tracking systems is inherently more assurance-ready than data assembled retrospectively for reporting purposes.
Stop Spending Months on Emissions Reports. Start Building Them in Real Time.
