Scope 1, 2, and 3 Carbon Accounting Without the Spreadsheet
Most carbon inventories still get built the same way. A consultant arrives once a year, requests twelve months of utility bills and fuel receipts, drops the numbers into a workbook, applies emission factors by hand, and hands back a PDF. The result is a snapshot that was already months old the day it shipped. When a buyer or a regulator asks how a figure was derived, the trail leads back to a tab in a spreadsheet that only one person understood.
That model is breaking down. Disclosure expectations are tightening, procurement teams are asking suppliers for verified numbers, and boards want to see carbon the way they see revenue: current, sourced, and ready to defend. EnergyOS produces carbon accounting directly from the energy data you already collect, so the number is a byproduct of operations rather than a once-a-year project.
The takeaway: when your carbon inventory is derived automatically from metered consumption and a registered set of emission sources, it stays current, it stays site-level, and every figure traces back to the standard and the measurement behind it.
The three scopes, plainly
The GHG Protocol organizes corporate emissions into three scopes. The distinction matters because disclosure frameworks, and the people reading your disclosures, expect you to report them separately.
Scope 1 covers direct emissions from sources your organization owns or controls. In most portfolios that means combustion: natural gas in boilers and furnaces, diesel in backup generators, propane, fuel oil. If you light it on site, it is Scope 1.
Scope 2 covers indirect emissions from purchased energy, mostly the electricity you buy from the grid. You do not burn anything yourself, but generating that power produced emissions upstream, and those belong to you.
Scope 3 covers everything else in your value chain: purchased goods and services, business travel, upstream and downstream transportation, use of sold products, waste. It is usually the largest share of a company's footprint and the hardest to measure, because most of the data lives outside your walls.
The two scopes you can measure with real precision are the two tied directly to energy. That is where EnergyOS starts.
Scope 2, two ways at once
The GHG Protocol asks companies to report Scope 2 using a dual approach, and EnergyOS produces both numbers from the same consumption data.
The location-based figure reflects the average emissions intensity of the grid your sites actually draw from. EnergyOS maps each site to its EPA eGRID subregion using the site's state and location, then applies that subregion's emission factor to the site's measured electricity consumption. This is the honest picture of the physical grid serving you, and it is the number many frameworks treat as the baseline.
The market-based figure reflects the energy you have contractually chosen. If you hold Energy Attribute Certificates, RECs, SRECs, AECs, or power purchase agreements, those instruments live in a certificate inventory inside the platform and get allocated to specific sites and periods. EnergyOS applies them following the GHG Protocol's market-based method, so your procurement decisions show up in the reported number rather than sitting in a separate contract file nobody links to the inventory.
Reporting both side by side is not optional under the standard, and it tells a fuller story. Location-based shows your exposure to the grid as it is. Market-based shows what you have done to change your supply. Buyers and regulators want to see the pair.
Scope 1 from meters, entries, and EPA factors
Direct combustion is where hand-built inventories tend to double-count, and where EnergyOS is deliberate about the source list.
Emissions come from a registry of combustion sources that you define. Each source has one clear place in the accounting. That structure exists for a specific reason: in a building with both a main gas meter and submeters on individual pieces of equipment, naively summing everything would count the same fuel twice. The registry lets you register the source of record and keep overlapping submeters from inflating the total. It is the kind of judgment a careful consultant makes on a good day and forgets on a busy one. Here it is built into how sources are declared.
For each source, EnergyOS applies EPA fuel emission factors. Carbon dioxide is calculated in kilograms per unit of fuel. Methane and nitrous oxide are converted to carbon dioxide equivalent using AR5 global warming potentials, so the three combustion gases roll up into a single CO2e figure that matches what disclosure frameworks ask for.
Fuel data comes in two ways. Where a live meter exists, consumption flows straight through. Where it does not, for a source like a delivered propane tank or a generator with no telemetry, you enter the fuel manually. Either way the source is registered and the factor is applied consistently every period.
Scope 3, honestly
Scope 3 is broader than energy, and any vendor who tells you a metering platform closes it out is overselling. EnergyOS lays the groundwork, but value-chain categories such as purchased goods, business travel, and product use require data sources beyond your meters: supplier records, spend data, travel systems, logistics. We treat this as partly current capability and partly roadmap, and we would rather say so than imply a number is complete when it is not. The honest position is that Scope 1 and Scope 2 are where the platform gives you defensible precision today, and Scope 3 is a structured build-out that depends on bringing in those additional sources.
Why continuous and site-level changes the argument
The data feeding all of this is the same pipeline that runs your metering: submeters, and utility imports through Green Button, Bayou, and ENERGY STAR. Consumption lands in the platform continuously, so carbon is computed as an ongoing series of per-site snapshots rather than a single annual reconstruction.
Three things follow from that.
You get carbon per site, not just a corporate roll-up, which is what you need when one facility is a hotspot or when a specific building has to report on its own.
You get carbon that stays current, so a mid-year board question or a customer questionnaire does not trigger a fresh data-gathering scramble.
You get carbon that is auditable, because every figure traces back to a measured consumption value, a named emission source, and a published factor from eGRID or EPA. When someone asks how you got a number, the answer is a data lineage, not a memory of what a spreadsheet did last spring.
For disclosure, that lineage is the whole point. Templates and scheduled exports turn the same underlying data into the reports your frameworks and buyers expect, on a cadence you set. The number you disclose and the number you operate on are the same number.
See it on your own data
If your carbon accounting still lives in a workbook that resurfaces once a year, the gap between what you can defend and what you are asked to defend is only going to widen. EnergyOS closes it by deriving the inventory from the energy data you are already measuring.
Book a platform walkthrough and we will show you Scope 1, 2, and market-based versus location-based Scope 2 built from live consumption. Call 215-645-7141.





