Most Scope 3 inventories are built on a fiction of convenience: money spent, multiplied by an industry-average factor. The method — spend-based estimation, usually via environmentally extended input-output (EEIO) models — cannot see that one contractor runs new equipment and another runs old, that one job landfilled everything and another recycled half. It prices the invoice, not the work. For recurring vendors with contracts and billing systems, companies are slowly replacing those proxies with primary data: actual fuel, hours, materials and waste from the supplier’s own operations. For reactive specialty trades — the restoration crew dispatched at 2 a.m., the emergency mechanical repair, the one-off strip-out — almost nobody collects anything. The work is procured under duress, invoiced in lump sums, and either omitted from the inventory or buried inside a spend factor. This guide is about closing that specific gap: what to capture, whose boundary it belongs in, and how to make a field crew’s paperwork into auditable carbon data.
Why the proxies are on their way out
Scope 3 is the bulk of most footprints — CDP puts the average at roughly 75% of a company’s total emissions, with sector figures ranging from about 70% to over 90% — so the quality of Scope 3 data is the quality of the inventory. Three forces are pushing from estimates toward activity data:
- California’s SB 253 requires Scope 1, 2 and 3 reporting for companies doing business in the state above $1 billion in revenue, with Scope 3 phasing in from 2027 (the full regime is in our SB 253 / SB 261 compliance playbook). The categories where specialty-trade emissions concentrate are Category 1 (purchased goods and services) and Category 5 (waste generated in operations).
- The EU’s CSRD / ESRS E1 requires value-chain disclosure under double materiality. Estimates are permitted where primary data cannot be obtained with reasonable effort — but assurance expectations ratchet, and a number you cannot trace to an activity is a number an assurer will eventually challenge.
- The GHG Protocol’s Scope 3 Standard is being revised for the first time since 2011. Its Phase 1 progress update (March 2026) proposes exactly the direction this guide assumes: companies would disclose what share of their Scope 3 data is primary, activity-based or spend-based, account for at least 95% of reportable Scope 3 emissions, and use granular supplier data rather than allocating a diversified supplier’s company-wide footprint. A consultation draft of the consolidated standard is expected in 2027. These are proposals, not law — but nobody builds a data system against the direction the standard-setter just announced.
The reactive-trade blind spot
Recurring vendors and emergency trades fail data collection for opposite reasons. Recurring services — janitorial, landscaping, scheduled maintenance — run through RFPs and multi-year agreements; the survey goes out once a year and someone answers it. Reactive trades are dispatched first and paperworked later, if at all:
| Attribute | Recurring vendor services | Reactive specialty trades |
|---|---|---|
| Procurement channel | Scheduled RFP; multi-year master agreement | Emergency dispatch; duress procurement |
| Data infrastructure | ESG surveys, centralized billing | Paper work orders, decentralized local crews |
| Shape of the work | Predictable routines, often area-based | Job-specific: deconstruction, drying, rebuilding |
| Primary carbon drivers | Commute fleets, standardized chemicals | Equipment run-time, vehicle transport, structural waste |
| Current accounting | Spend proxies or allocation formulas | Omitted, or hidden in lump-sum invoices |
Three root causes compound. Duress procurement: when the pipe has burst, nobody onboards the vendor into an ESG portal before dispatch. Tiered subcontracting: the prime contractor’s invoice covers spot labor, sub-trades and rental equipment whose fuel and hours the prime never sees. Schema mismatch: standard vendor surveys ask for company-level Scope 1 and 2 totals, which a twelve-person restoration firm cannot translate into the carbon content of your specific job. The fix is not a better survey. It is a job-level field set the crew can actually complete.
Whose emissions are they? The occupier–owner boundary
Emergency work inside a leased space belongs in the occupier’s Scope 3 — and getting this boundary wrong creates both double counting and gaps.
| Reporting entity | Frameworks | Scopes that apply | What falls inside |
|---|---|---|---|
| Corporate occupier (tenant) | GHG Protocol, SB 253, CSRD | Scope 3 Category 1 (services) & Category 5 (waste) | Specialty-trade labor, emergency restoration, suite repairs, job-site fuel, demolished materials |
| Property owner / asset manager | GRESB, ENERGY STAR, NYC LL97, DC BEPS | Scope 1 & 2 (base building); Scope 3 Category 13 (downstream leased assets) | Central plant, common areas, structural capital projects, shared utilities |
The allocation follows control: the occupier contracts the service, defines the scope, approves the invoice and controls access to the space. One nuance worth capturing in the data model: where drying equipment and air scrubbers plug into tenant-metered power, that electricity is the occupier’s Scope 2 — the service is Category 1, the kilowatt-hours may already sit in the tenant’s own utility data. A field set that records both the equipment hours and the power source keeps the two from being counted twice or not at all.
A 12-field job-level intake schema
What follows is a field set this guide proposes — lift it, rename it, adapt the units to your region. It is deliberately small: twelve fields a dispatcher or crew lead can complete from the work order, the fuel log and the waste ticket. Every field maps to a GHG Protocol category so the payload drops into an inventory without translation.
| # | Field | Format | Maps to |
|---|---|---|---|
| 1 | Work order ID | Alphanumeric ID | Administrative matching |
| 2 | Facility / location ID | Asset ID or GIS ref | Facility allocation boundary |
| 3 | Equipment runtime hours | Hours, by equipment power rating (kW) | Cat 1 (service); occupier Scope 2 where tenant-metered |
| 4 | Primary fuel source | Grid / diesel / propane | Category 1 (direct fuel) |
| 5 | Vehicle transport mileage | Miles or km | Category 1 (transport) |
| 6 | Chemical consumables volume | Gallons or litres | Category 1 (purchased goods) |
| 7 | Debris / waste volume | Tons or cubic yards | Category 5 (waste in operations) |
| 8 | Waste stream classification | C&D / hazardous / landfill-bound | Category 5 |
| 9 | Disposal facility type | Recycling / incineration / landfill | Category 5 |
| 10 | Demolished material mass | Weight or area | Category 5 (embodied carbon loss) |
| 11 | Replacement material mass | Weight/area + % recycled content | Category 1 (embodied carbon of replacements) |
| 12 | Data quality flag | Primary (measured) / secondary (estimated) | Assurance & revision-readiness |
Field 12 is the one that future-proofs the rest. The GHG Protocol revision proposals would have companies disclose the share of primary versus estimated data. A payload that already flags which numbers were measured and which were estimated converts that disclosure from a research project into a filter.
Making it contractual: the MSA data rider
Voluntary data requests lose to emergency conditions every time; a payment condition does not. The mechanism that works is a rider in the master services agreement tying the field data to invoice approval. Model language, to be adapted by your own counsel:
Contractor agrees that submission of operational activity data — conforming to the job-level intake schema in Exhibit [X] — is a condition of final work-order approval and invoice disbursement. For all emergency, mechanical and specialty trade services, Contractor shall submit complete field logs detailing (a) equipment operating hours and fuel sources, (b) total transport mileage, (c) mass and classification of demolished debris, and (d) certified waste disposal pathways. Failure to provide complete metrics within fifteen (15) business days of job completion shall withhold invoice payment until data verification is resolved.
Fifteen days is negotiable; the structure is not. Data as a deliverable, with a deadline, attached to the money.
The rollout, in three phases
Phase 1 — pre-qualification. Register specialty-trade vendors in the CMMS alongside recurring vendors. Collect the baseline once: fleet composition, equipment wattage profiles, waste-hauling partners and their disposal facilities. Execute the MSA rider at renewal — or immediately, by amendment, for your highest-volume emergency vendors.
Phase 2 — dispatch and execution. Work orders issue pre-populated with the twelve fields, so the schema arrives with the job instead of chasing it. Crews log equipment deploy times, generator fuel draw and vehicle trips on the same mobile form they already use for job notes. If the form adds more than a few minutes to closeout, it will be abandoned by the third emergency — design for the 2 a.m. version of your vendor, not the office version.
Phase 3 — reconciliation and invoicing. The completed payload travels with the itemized invoice. Run one validation that catches most fabrication and most error: logged equipment runtime against billed labor hours — the two should move together. Then export validated payloads to the accounting platform, mapped to emission factors (regional grid factors such as eGRID for electricity; established waste coefficients such as EPA WARM for disposal pathways), and the Category 1 and 5 lines stop being estimates.
Finally, benchmark the transition honestly. Run one reporting cycle with both methods live: the old EEIO spend factor and the new primary data, side by side, for the same jobs. The gap between them — per job type, per vendor — is your evidence for what the proxies were hiding, and it is the exhibit that justifies the programme’s cost in the next budget round. Our compliance frameworks map shows where this data feeds once collected — CSRD, ISSB and California all draw on the same activity records.
Frequently asked questions
Which Scope 3 categories cover emergency restoration and specialty-trade work?
Primarily two: Category 1 (purchased goods and services) for the service itself, its fuel, transport and materials; and Category 5 (waste generated in operations) for demolished material and its disposal pathway. Electricity drawn from the occupier’s own metered supply sits in the occupier’s Scope 2 — record the power source so it is counted once.
Can we keep using spend-based estimates?
For now, in most regimes, yes — ESRS permits estimates where primary data cannot be obtained with reasonable effort, and the current GHG Protocol standard accepts spend-based methods. The direction is against them: the Protocol’s revision proposals would require disclosing how much of the inventory is spend-based and would restrict company-wide supplier allocations. Spend-based is a bridge, and bridges have a far bank.
Who reports the emissions — the tenant or the landlord?
Both, in different scopes, without double counting if the boundary follows control. The occupier reports the contracted work in Scope 3 Categories 1 and 5; the owner reports base-building energy in Scope 1 and 2 and the leased asset in Category 13. Building-performance regimes like NYC LL97 and DC BEPS assess the asset, which is the owner’s filing problem — powered by data both parties have reason to keep straight.
Is the 12-field schema an official standard?
No. It is a field set proposed by this guide, designed so every field maps to an existing GHG Protocol category. The standards — GHG Protocol, ESRS, CARB’s SB 253 rules — specify what must be reported; the job-level capture mechanism is each company’s own design problem, and this is a workable one.
When does Scope 3 reporting start under California’s SB 253?
Scope 3 phases in from 2027 for in-scope companies, on the schedule CARB sets; Scope 1 and 2 come first (2026 cycle). The operational implication: the data systems for Scope 3 need to exist before the first Scope 3 year opens, which is why vendor intake belongs in contracts being renewed now.
Sources: GHG Protocol Corporate Value Chain (Scope 3) Standard (2011) and Scope 3 Standard revision Phase 1 Progress Update (March 31, 2026), incl. Data Quality Indicator and 95% coverage proposals; CDP supply-chain reporting (Scope 3 averaging ~75% of total emissions); MIT Center for Transportation and Logistics, State of Supply Chain Sustainability 2024; California SB 253 and CARB’s implementing regulation (see the compliance playbook linked above); ESRS E1 value-chain provisions. Framework positions are as published at the time of writing; the GHG Protocol items marked as proposals are draft revision content, not final standard text.