PONOPT FIELD NOTES · Энергия и освещение

Contractor Emissions and Scope 3: What Can a City Actually Measure?

How a city can actually measure contractor and Scope 3 emissions: two accounting lenses, spend-based versus supplier data, municipal case evidence, and practical limits.

A city can measure contractor emissions mainly as Scope 3 of its own procurement: purchased goods and services, capital works, waste and upstream transport. Start with a spend-based estimate to rank contracts, then move the largest contractors onto activity or supplier-specific data. In the community-wide GPC inventory these emissions appear only partly, under narrower transboundary definitions.

Key takeaways

  • Contractor emissions show up most fully in the municipal organization's own Scope 3 inventory (purchased goods and services, capital goods, waste, upstream freight), not in the community-wide GPC footprint, where they are narrower and partly reported as territorial Scope 1.
  • Spend-based (EEIO) screening is a legitimate year-one method for prioritization, but it carries high uncertainty; material contractors should move to activity or supplier-specific data.
  • Municipal case studies in Zeist and Nijmegen find that more than 95% of procurement climate impact is indirect Scope 3, driven mainly by civil engineering works, waste processing and social services.
  • Supplier-specific data is obtainable through contract terms and environmental product declarations; the City of London reported 40 suppliers covering nearly 50% of spend on purchased goods and services.
  • Procurement rules such as the UK's PPN 06/21 show how authorities can require carbon reduction plans from large suppliers, though jurisdiction, scope and thresholds differ.
  • Guard against double counting between territorial Scope 1 and procurement Scope 3, and document methodology, base years and data-quality tiers so results stay comparable over time.

Two accounting lenses, two different answers

Before counting contractor emissions, choose the frame. In a community inventory built to the Global Protocol for Community-Scale Greenhouse Gas Inventories (GPC), a contractor burning fuel on a site inside the city boundary contributes to the city's territorial Scope 1, not to its Scope 3. Scope 3 there is narrower and transboundary: waste exported across the boundary, and, at the expanded BASIC+ level, transboundary journeys.

The picture changes when the municipality treats itself as an organization under the GHG Protocol Corporate Value Chain (Scope 3) Standard. Everything the city buys from contractors — construction, cleaning, waste haulage, machinery and services — then falls into the indirect emissions of procurement. This organizational lens is where contractor emissions become genuinely measurable and manageable.

Keeping the two frames separate prevents the most common error: transferring numbers from one inventory into the other, which causes double counting and misleading conclusions about progress.

  • GPC describes a territory and its residents; its Scope 3 covers transboundary flows.
  • Organizational Scope 3 describes the city as a buyer: goods, services, capital works, waste, business travel and commuting.
  • A contractor's fuel burned inside the boundary is usually territorial Scope 1, not procurement Scope 3.

Which contractor emissions land where

In practice, most of a city's contractor emissions sit in a few corporate Scope 3 categories: purchased goods and services (category 1), capital goods and construction (category 2), fuel- and energy-related activities (category 3), upstream transportation (category 4), waste generated in operations (category 5), and business travel or commuting.

The heaviest contracts are usually roads and civil engineering, building operations, waste collection and treatment, transport services and social care. CE Delft's work for Zeist found that waste processing, civil engineering and the social domain drive the largest share of procurement climate impact, while civil works dominate resource depletion because of the materials in roads, sewers and street furniture.

A practical first step is to map every contract line to a Scope 3 category. The map instantly shows which contractors are visible in the system and which fall out of it, such as small subcontractors or hired machinery.

  • Category 1 — goods and services, from office supplies to consultancy.
  • Category 2 — capital works and materials such as concrete, steel and asphalt.
  • Categories 4 and 5 — inbound freight and waste leaving the boundary.
  • Business travel and staff commuting are separate, usually smaller, line items.

Methods: from spend to supplier data

There are three tiers of accuracy. The spend-based method multiplies a contract value by an average sector intensity drawn from environmentally extended input-output tables such as Exiobase or national databases. It is cheap, covers the whole portfolio and works well for a first-year screening, but it carries large uncertainty and cannot tell what a specific contractor actually does.

The activity-based method uses physical units: tonnes of concrete, kilometres driven, litres of fuel, tonnes of waste by disposal route. It is more accurate and lets you compare contractors, but it requires data the city must request in advance through the contract.

The third tier is supplier-specific data: primary reports from the contractor, environmental product declarations (EPDs) for construction materials, or the contractor's own Scope 1 and 2 figures. The City of London is moving exactly this way, from spend-based calculations to contract-specific carbon data: in one year 40 suppliers provided contract-specific data covering nearly half of spend on purchased goods and services.

The GHG Protocol methodology allows a hybrid approach, combining primary data where available with average factors to fill gaps. The essential rule is never to add supplier-specific data on top of the spend-based estimate for the same volume, because that counts the same emissions twice.

  • Year one — spend-based estimate across the whole portfolio for ranking.
  • For construction materials, ask for EPDs and physical quantities, not invoiced money.
  • For waste, collect tonnes by disposal route: landfill, incineration, recycling.
  • For machinery and vehicles, collect fuel type, volume or hours run.

What cities actually find

European studies converge on the same picture: most of a municipality's procurement climate impact is indirect and occurs beyond its borders. For Zeist the annual impact of procurement was estimated at roughly 37 kilotonnes of CO2-equivalent, with more than 95% indirect Scope 3 emissions arising during production and processing of materials and services. Nijmegen reached similar conclusions and recommended focusing on extending the service life of infrastructure and using recycled and biobased materials.

The City of London example shows how to shift from average factors to contract-level data and to embed requirements in procurement policy and contract management. The UK goes further at national level: Procurement Policy Note 06/21 requires suppliers bidding for major central government contracts to publish a Carbon Reduction Plan and commit to Net Zero, or risk exclusion from the process.

These are national rules in specific jurisdictions, not a universal standard. A city must reconcile any requirement with its own public-procurement law and avoid copying foreign thresholds blindly. This is general information, not legal advice for any particular jurisdiction.

  • Zeist: roughly 37 kt CO2-eq per year, with over 95% in procurement Scope 3.
  • Largest sources — civil engineering works, waste processing and the social domain.
  • City of London: 40 suppliers provided contract data, about 50% of goods and services spend.
  • UK PPN 06/21: carbon reduction plans required from major government suppliers.

Honest limits: risks and constraints

The honest answer to what a city can really count is a set of categories with differing accuracy, not one precise number. Spend-based estimates against sector averages can deviate substantially for an individual contract, especially when a contractor has already cut emissions or, conversely, uses carbon-intensive materials.

The main technical risk is double counting. A contractor's fuel burned on a site inside the city boundary can enter both the territorial Scope 1 and the procurement Scope 3 unless the accounting boundary is agreed in advance. A second risk is data from small and medium contractors, who often have no reporting system, forcing the city back onto average factors and clearly labelled estimates.

A third risk is mixing methodologies and base years. Switching from spend-based to supplier-specific data changes the numbers by itself, with no change in real emissions. Cities should therefore document the methodology version, emission-factor sources, base year and data quality, and review materiality each year as spend and grid factors shift.

  • Set the accounting boundary so a contractor's fuel is not counted twice.
  • Tag every value: primary data or an estimate from averages.
  • Do not compare years directly across a methodology change without recalculating.
  • Small contractors are the biggest data gap; decide explicitly where average estimates are acceptable.

A pragmatic measurement ladder

The workable approach is not to cover everything at once but to build a ladder of accuracy. In year one the city runs a spend-based estimate across the portfolio, ranks contracts and picks the material categories. Then, for the top few dozen contractors by emissions or spend, it inserts data and EPD requirements directly into tender documents and contracts.

This staged path delivers priorities in the first cycle and gradually raises the share of primary data without rebuilding the whole system. The key is to place data requirements at the tender stage, not after the contract is signed, when leverage is already limited.

Contractor Scope 3 tiering matrix and procurement data request

A reusable template for procurement teams: how to split contracts into accuracy tiers, when to advance a contractor to the next tier, and what data to request in the contract.

  1. Tier 0: map every contract to a Scope 3 category — goods and services, capital works, waste, freight, travel.
  2. Tier 1: run a spend-based (EEIO) estimate across the portfolio; use it for ranking, not as a precise figure.
  3. Trigger: advance to Tier 2 contractors in the top 20–40 by contract value or estimated emissions.
  4. Tier 2 (construction): require EPDs for concrete, steel and asphalt, plus physical material quantities.
  5. Tier 2 (waste): collect tonnes by disposal route — landfill, incineration, recycling — not the invoice sum.
  6. Tier 2 (transport and plant): record fuel type and volume or distance and hours, not cost.
  7. Tier 3: ask the contractor to submit its own Scope 1 and 2 emissions for the reporting year.
  8. Embed requirements in tender documents and the contract, not after signature.
  9. Keep spend-based and primary figures separate in the report to avoid double counting.
  10. Tag each number with method, base year and quality: measured versus estimated.
  11. Revisit materiality annually as spend and emission factors change.

Questions people ask

What is the difference between contractor emissions in a city's organizational and community-wide inventories?

In a community inventory built to the GPC, a contractor's fuel burned inside the boundary counts toward the city's territorial Scope 1, while Scope 3 covers transboundary flows such as exported waste. When the city treats itself as an organization under the GHG Protocol Corporate Value Chain Standard, everything it buys from contractors — works, services, waste and freight — becomes indirect Scope 3 of procurement. These are different frames with different meanings, and figures should not be transferred between them without risking double counting.

Is a spend-based estimate good enough for a first Scope 3 measurement of procurement?

Yes, for year one it is an accepted method: contract spend is multiplied by an average sector intensity from environmentally extended input-output databases. It covers the whole portfolio cheaply and is suitable for ranking contractors by materiality. Accuracy is low because the factors are averages and do not reflect a specific supplier, so spend-based results are best used as a filter, with material contracts moved to activity or supplier data. Changing method alters the numbers on its own, which matters when comparing across years.

How can a city obtain primary emissions data from contractors?

The simplest route is to embed the requirement in the tender and contract: the contractor supplies material and fuel volumes, environmental product declarations for concrete, steel and asphalt, or its own Scope 1 and 2 emissions for the year. The City of London used this path to collect contract-specific data from 40 suppliers covering nearly half of goods and services spend. For small contractors without a reporting system, average factors remain acceptable, but the values should be labelled as estimates rather than measurements.

What share of municipal procurement emissions is typically Scope 3?

CE Delft estimates that more than 95% of municipal procurement climate impact is indirect Scope 3 occurring beyond municipal borders during production and delivery of materials and services. For the municipality of Zeist the total impact of annual procurement was about 37 kilotonnes of CO2-equivalent. The largest sources are civil engineering works, waste processing and the social domain; the city's own direct emissions within the procurement portfolio are generally small.

Why can contractor emissions be double counted, and how can a city avoid it?

Double counting occurs when a contractor's fuel burned on a site inside the boundary is recorded both as the city's territorial Scope 1 and as the Scope 3 of its procurement. The city should set the accounting boundary in advance: when a contractor operates within the territory, its direct fuel belongs to territorial Scope 1 and is not duplicated in procurement Scope 3. Similarly, supplier-specific data must not be summed with a spend-based estimate for the same volume; choose one method per volume and document the decision.

Can a city require contractors to publish carbon reduction plans?

Yes, within the procurement law of its own jurisdiction. One example is the UK's Procurement Policy Note 06/21, under which suppliers bidding for major central government contracts must publish a Carbon Reduction Plan and commit to Net Zero or risk exclusion at selection. The rule applies to central bodies and specific contract-value thresholds. A city must verify its local public-procurement rules and authority rather than copying another country's thresholds. This is general information, not legal advice.

Sources and further reading

Sources were checked when this page was generated. Confirm changing dates, rules and prices with the original publisher.

  1. GHG Protocol for Cities (Global Protocol for Community-Scale Greenhouse Gas Inventories)World Resources Institute / GHG Protocol
  2. Corporate Value Chain (Scope 3) StandardGreenhouse Gas Protocol
  3. Procurement Impact Analysis – Municipality of ZeistCE Delft
  4. Indirect CO₂ Emissions in the Municipality of Nijmegen – Scope 3 Emissions from Municipal Procurement and ResidentsCE Delft
  5. Responsible Procurement Impact ReportCity of London Corporation
  6. Procurement Policy Note 06/21: Taking account of Carbon Reduction Plans in the procurement of major government contractsUK Government (Cabinet Office)