Skip to main content
    QHSEtech
    Best Practice14 min readUpdated

    Scope 3 Emissions in 2026: Data Strategy & Software Playbook

    By Dimitris Mitsios · Dimitris works at Tekmon, which pays for sponsored placements on this site. Disclosure · AI-assisted (how pages are made)

    Scope 3 is where many carbon programs stall. Here is the category-by-category data strategy, the methodology choices, and the software architecture that actually scales.

    Best Practice illustration for the article “Scope 3 Emissions in 2026: Data Strategy & Software Playbook” — The QHSE Standard

    Quick Facts

    • Standard: GHG Protocol Corporate Value Chain (Scope 3) Standard. ESRS E1-6 asks for Scope 3 emissions from each significant category (it becomes E1-8 in the revised ESRS that apply to financial years starting on or after 1 January 2027; the amending regulation of 3 July 2026 was published on 21 September 2026 and enters into force on 10 November 2026), and IFRS S2 (paragraph 29(a)(vi), in the version that includes the amendments issued in December 2025) asks which of the Scope 3 Standard's categories are included.
    • Categories: 15 (8 upstream, 7 downstream). The Scope 3 Standard requires companies to account for all Scope 3 emissions and to disclose and justify any exclusions.
    • Scale compared with operational emissions: in 2023 disclosures to CDP, companies' upstream (supply-chain) Scope 3 emissions were on average 26 times their Scope 1 and 2 emissions.
    • Methodology ladder (more specific to your own value chain at the top): supplier-specific primary data → average data with supplier overrides → activity-based secondary → spend-based. This is the working order used in this guide, built on the Scope 3 Standard's primary and secondary data types; the Standard itself asks for data quality sufficient for your goals, not a fixed ladder.
    • Status of the standard: the GHG Protocol is revising the Scope 3 Standard. Its Phase 1 progress update of 31 March 2026 says the content is draft, is not a GHG Protocol standard and is not yet in public consultation, so the 2011 text cited here is the published standard to work from today.
    • Assurance: the IAASB's ISSA 5000 is a general standard for limited and reasonable assurance on sustainability information, not a Scope 3 rule. It is effective for periods beginning on or after 15 December 2026, with earlier application permitted.

    Editorial stance — The QHSE Standard: We focus on what works in production environments, not theoretical perfection. Spend-based data is a legitimate starting point — it just cannot be the destination.


    1. Why Scope 3 still defeats many programs

    Scope 3 looks like a measurement problem. It is actually four problems stacked on top of each other:

    1. Inventory boundary — what is in, what is out, justified against the GHG Protocol screening criteria.
    2. Data acquisition — extracting category-relevant data from systems that were never designed to produce it (ERP, procurement, logistics, product lifecycle).
    3. Methodology consistency — picking emission factors and methods that survive year-on-year comparability.
    4. Supplier engagement — converting tier-1 (and eventually tier-n) suppliers from spend lines to primary-data partners.

    A well-run Scope 3 program treats these as sequential, not parallel. Trying to fix all four at once is a common way to fail.


    2. The 15 categories — where to start, what to defer

    Cat.NameRelevance heuristicTypical first-year approach
    1Purchased goods & servicesOften materialSpend-based → hybrid by year 2
    2Capital goodsMaterial for capex-heavy sectorsSpend-based
    3Fuel & energy relatedIncludeActivity × DEFRA/IEA factors
    4Upstream transportationMaterial for traders/retailersActivity-based via 3PLs
    5Waste from operationsOften immaterial for office-basedActivity from waste contractors
    6Business travelDepends on travel volumeActivity from TMC + cards
    7Employee commutingOften smallSurvey-based
    8Upstream leased assetsSector-dependentLease register × intensity
    9Downstream transportationManufacturers / distributorsModelled
    10Processing of sold productsIntermediate manufacturersEngineering estimate
    11Use of sold productsCan be the largest for makers of energy-using productsLifecycle modelling
    12End-of-lifeProducersEoL scenario × waste factors
    13Downstream leased assetsReal estate, equipment lessorsSame as Cat. 8
    14FranchisesFranchisors onlyFranchisee survey
    15InvestmentsFinancial institutions (PCAF)Asset class methodologies

    Rule of thumb: get Cat. 1, 3, 4, 6, 11 (where applicable) on a defensible footing first. The relevance column is a screening heuristic, not a licence to skip: the Scope 3 Standard asks you to account for all Scope 3 emissions and to disclose and justify any exclusion.


    3. Data hierarchy — and the discipline to climb it

    Many teams stay on spend-based data because the next step is hard. The migration path looks like this:

    Year 1 — Spend-based baseline. Pull procurement spend by EEIO category, multiply by region-specific emission factor (Exiobase, USEEIO, CEDA). Output: a complete first inventory. Caveat: under a spend-based method, a 10 % spend reduction, for example, reads as a 10 % emissions reduction, which is not credible.

    Year 2 — Hybrid model. Identify the top 50 suppliers by spend. Request primary data — ideally a verified product-level carbon footprint or a corporate footprint with allocation method. Replace spend-based numbers for those suppliers; keep spend-based for the long tail.

    Year 3 — Supplier-specific dominant. Top suppliers locked into annual data exchange via CDP Supply Chain or your EHS/ESG platform. Long tail moves to activity-based proxies (kg of material × material-specific factor) where possible.

    Year 4+ — Product-level data. Integrate EPDs and PCFs at SKU level, the data a credible product carbon label rests on.

    The four data-quality tiers, in the GHG Protocol's terms

    The Scope 3 Standard (chapter 7, table 7.3) splits data into primary data, from specific activities within your value chain, including data provided by suppliers, and secondary data, which is not from specific activities in your value chain, such as industry-average, financial and proxy data. For Category 1, the GHG Protocol's Technical Guidance for Calculating Scope 3 Emissions names four calculation methods, which work as the tiers you climb:

    1. Supplier-specific method: product-level cradle-to-gate inventory data collected from the supplier.
    2. Hybrid method: allocated Scope 1 and 2 data from suppliers, plus emissions calculated from their activity data (materials, fuel, electricity, transport, waste), with secondary data filling the gaps.
    3. Average-data method: mass or other physical units of what you buy, multiplied by secondary emission factors such as industry averages per unit.
    4. Spend-based method: the economic value of what you buy, multiplied by secondary emission factors per unit of spend.

    To rate data within any tier, the Scope 3 Standard (table 7.6) gives five data quality indicators: technological, temporal and geographical representativeness, completeness and reliability. Recording a rating per material category makes year-on-year improvement visible, and if you track performance or set a target, the Standard requires a base-year emissions recalculation policy (chapter 9), which is where you decide when a better data source means restating the past.

    Worked example: when a better data source arrives

    The numbers below are invented for illustration. Suppose a manufacturer spends 1,200,000 a year with one metal-parts supplier and applies a spend-based factor of 0.40 kg CO2e per currency unit, giving 480 tCO2e in Category 1. In year 2 the supplier provides a product-level footprint covering the parts bought, and the same purchases now calculate to 310 tCO2e.

    StepCategory 1 figureWhat to record
    Year 1, spend-based480 tCO2eMethod, factor source and version
    Year 2, supplier-specific310 tCO2eNew method, supplier data date, data quality rating
    Difference170 tCO2eA change of method, not a reduction in activity

    The 170 tCO2e should not be presented as progress against a target. Under your base year recalculation policy you decide whether the change crosses your significance threshold; if it does, restate the base year with the better data, and if you set the threshold at, say, a 10% change in base year emissions, write that down before the data arrives. Showing both numbers side by side, with the reason for the difference, is the entry an assurance provider can follow.


    4. The software architecture that scales

    A Scope 3 process needs traceable data and owned handoffs, whether the records are initially in spreadsheets or specialist software. Use these four layers to identify gaps before purchasing:

    Layer 1 — Source systems

    ERP, procurement, HRIS for commuting/travel, transport and product-lifecycle systems. Identify the data owner and the export or interface for each source. For environmental records such as waste and energy, see environmental data management software.

    Layer 2 — Activity ledger

    A normalised store of activities (kg of steel, km flown, kWh purchased) with metadata: site, supplier, category. Jumping straight from the source systems to a category 1 calculation leaves nowhere to keep the underlying quantities, so build the ledger first.

    Layer 3 — Carbon engine

    A platform that holds emission factors, applies methodologies, supports supplier-primary overrides, and produces audit trails. Compare the carbon accounting workflows, then ask every vendor to replace an estimate with supplier-specific data, retain the old factor and show how the change affects the total. Name the plan and any separately licensed factor library.

    Layer 4 — Disclosure

    Maps engine output to ESRS E1 (E1-6 today, E1-8 in the revised ESRS), IFRS S2 and CDP. Often the same tool as Layer 3 for smaller programmes. Where many contributors and reviewers are involved, test assignment, evidence access, approval and correction in the ESG reporting comparison. Confirm whether disclosure and carbon calculations share records or depend on an interface.

    QHSE and EHS systems can serve as a Layer 1 source of environmental records, such as waste and energy data, that feed the activity ledger. Whether a given product holds those records is a question for its profile and a demo; a QHSE system does not replace a carbon engine.

    Correction, 23 September 2026: an earlier version of this note named a commercial partner of this site as the example QHSE platform and called such platforms "the cheapest way" to ensure data integrity at source. That cost claim had no source, and the name and the claim have been removed.

    Compare ESG software scope and evaluation questions →. Use the data fields above to prepare a supplier request for your chosen reporting boundary.


    5. Supplier engagement that does not collapse at scale

    The single biggest factor in primary-data quality is how you ask. Practices to consider, each tied to the Scope 3 Standard where it states something:

    • Prioritise by expected emissions, not spend alone. The Scope 3 Standard (section 7.1) warns that spend and revenue may not correlate well with emissions, so a low-spend, high-emission supplier can matter more than a large low-emission one. Screen first, then rank.
    • Use standard formats. Ask for data in the templates suppliers already fill in for other customers, such as the CDP supply chain questionnaire, rather than a bespoke form, and pre-fill what you already know.
    • Agree the method before the numbers. For your largest suppliers, settle allocation rules and system boundaries with them before asking for product footprints.
    • Build supplier capacity. Smaller suppliers may need training or tools, not only a data request.
    • Tiered request. Top 20 suppliers get a structured PCF + verification ask. Tier 2 (next 80) get a corporate footprint + allocation method ask. Tail gets a one-page CDP-aligned questionnaire.
    • Reciprocity. Share back the supplier's contribution to your inventory. They can reuse the data in their own ESRS E1 or SBT submission, which may make a repeat request easier to answer.
    • Procurement integration. Tie data submission to procurement scoring; see supplier management software for what the reviewed profiles document.
    • Score the data, not the number. A scoring rule that penalises a high reported figure gives a supplier a reason to withhold data, so consider scoring completeness, method disclosure and timeliness instead of the emissions level.

    6. Methodology choices that auditors actually scrutinise

    Points an assurance provider may probe, drawn from what the Scope 3 Standard requires you to disclose:

    • Boundary justification. Why did you exclude Cat. 8? Document the screening test.
    • Emission factor versioning. Did you switch factor sources mid-year? Disclose it. Did you back-restate? Disclose that too.
    • Allocation method for shared facilities. Mass-based, value-based, physical — pick one and stay consistent.
    • Treatment of biogenic emissions. Reported separately, not netted: the Scope 3 Standard requires biogenic CO2 emissions in the value chain to be kept out of the scopes and reported separately.
    • Renewable energy claims for Cat. 3. Market-based vs location-based, contractual instruments tracked.
    • Double counting between categories. The Scope 3 Standard defines the categories so that there is no double counting between them; check the boundaries your methods draw, for example between Cat. 1 and Cat. 4 (upstream transportation).

    A methodology note in the appendix answers these points in one place and gives a reviewer a single document to test.


    7. Targets — SBTi alignment in 2026

    The glossary entry on the SBTi explains the initiative. Two versions of the SBTi's corporate standard are in play. Under the Corporate Net-Zero Standard V1.3.1 (April 2026), whose submissions the SBTi's transition guide says remain open until 31 January 2028:

    • A near-term Scope 3 target is required if relevant Scope 3 emissions are 40 % or more of total Scope 1, 2 and 3 emissions (criterion C4).
    • Near-term Scope 3 targets must cover at least 67 % of Scope 3 emissions (C6), and long-term targets at least 90 % (C7).

    The Corporate Net-Zero Standard V2.0, published on 11 June 2026 and effective from 1 February 2027, drops the 67 % coverage rule:

    • Near-term targets must cover every Scope 3 category (1 to 14) that is 5 % or more of the company's Scope 3 emissions (C14.1), with limited, listed exclusions (C14.2).
    • Companies choose between overarching emission reduction targets, supplier or customer alignment targets, and category- or activity-specific targets.
    • Scope 3 targets are optional for "Category B" companies (small companies, and medium-sized companies in lower-income countries).

    V2.0 validation opens on 1 February 2027, and from 1 February 2028 V2.0 is mandatory for all new submissions, so a company without validated targets should decide which version to submit under before then. Build your data architecture so that the move from "we measure it" to "we have an SBT-aligned target" is just an analytics layer, not a re-platforming.


    7a. Who has to report, and what to ask a software vendor

    Whether Scope 3 must be reported under the ESRS depends on CSRD scope. Directive (EU) 2026/470, adopted on 24 February 2026, amended the CSRD so that, for EU undertakings, the scope is companies with more than 1,000 employees on average and net turnover above EUR 450 million (check the Directive text and your member state's transposition for your own case). Customer-driven requests can reach further: a supplier below that threshold may still be asked for data by a customer. See the ESRS implementation guide and the double materiality guide for how Scope 3 relates to the materiality assessment.

    Questions to put in writing to each carbon or ESG software vendor, with the same wording for all:

    1. Which of the 15 categories does the product calculate, and with which method (supplier-specific, hybrid, average-data, spend-based) for each?
    2. Which emission factor libraries are included, which are licensed separately, and is the factor version stored against every calculated line?
    3. Can a supplier-specific figure replace an estimate while the earlier figure and the reason for the change stay visible?
    4. Is there a field for the data quality indicators in table 7.6 of the Scope 3 Standard?
    5. Can the activity ledger be exported in full if you leave, and in what format?
    6. How are base year recalculations recorded and who approves them?

    The scope 3 emissions software and carbon accounting software pages list what the researched profiles document, the capability map shows the same records by capability, and the pricing index says whether a current price is on record. The glossary entries for Scope 3 emissions and Scopes 1, 2 and 3 define the terms, and the carbon footprint calculator is a small way to test the arithmetic on your own figures. None of this is legal advice.


    8. A 90-day acceleration plan

    DayActionOutput
    0–15Materiality screening across 15 categoriesRanked list, justification log
    15–30Spend-based baseline for material categoriesInventory v1
    30–45Top-supplier list + data request packageEngagement plan
    45–60Pilot with 5 suppliersMethodology notes, learnings
    60–75Carbon engine selection / proof of valueVendor scorecard, decision memo
    75–90ESRS E1 Scope 3 disclosure draftReviewable narrative + quantitative file

    9. Bottom line

    Scope 3 is not a measurement project — it is a data-supply-chain project. A company preparing for assured reporting has the best chance of a defensible Scope 3 figure if it builds the four layers above, climbs the methodology ladder supplier by supplier, and treats its QHSE/EHS records as source data beneath the carbon engine.

    Choosing a carbon engine? Take the Get Matched quiz for a shortlist based on your industry, size and priorities, then ask each carbon engine to demonstrate integration with your EHS stack.

    Frequently asked questions

    Is spend-based Scope 3 data acceptable?

    The Scope 3 Standard allows secondary data where the inventory is sufficient for your goals and asks you to document data quality. Spend-based figures are secondary data, so they can be a starting inventory, but they cannot show the effect of a supplier's own actions.

    Do I have to report all 15 categories?

    The Scope 3 Standard asks companies to account for all Scope 3 emissions and to disclose and justify any exclusion. Which categories a company must disclose under the ESRS or IFRS S2 depends on its materiality assessment and the standard that applies to it.

    Which SBTi version should I use now?

    The SBTi's transition guide says V1.3.1 submissions remain open until 31 January 2028 and V2.0 validation opens on 1 February 2027. Check the SBTi site for your own situation.

    Sources

    Corrected 23 September 2026: claims about named vendors that no source we could check supported were removed or reworded to match each product's researched profile.

    Corrected 23 September 2026: statistics without a primary source were sourced, labelled as examples or removed, and the standards and regulations cited now link to their official texts. The SBTi thresholds were attributed to the wrong version of the standard and the ISSA 5000 date was wrong; both now match the source documents.

    Revised 4 October 2026: the SBTi V1.3.1 submission window was corrected from "until the end of 2027" to 31 January 2028 (SBTi transition guide), the revised-ESRS dates and the status of the Scope 3 Standard revision were added, unsupported generalisations were reworded, and a worked example, vendor questions and an FAQ were added.

    Updated 24 September 2026: merged the sourced sections of Scope 3 Data Collection: Spend-Based to Supplier Actuals.

    Scope 3GHG ProtocolCarbon AccountingESRS E1Supply ChainESG

    Dimitris Mitsios

    Founder of The QHSE Standard; product marketing at Tekmon

    Dimitris Mitsios is the founder of The QHSE Standard and works in product marketing at Tekmon. His professional focus includes software positioning, digital workflows and user adoption.

    Dimitris works at Tekmon, which pays for sponsored placements on this site.

    Researched and drafted with AI assistance and published under the author's editorial responsibility (how pages are made). Found an error? Send a correction with a source.

    Related software

    Browse all platforms →

    Ordered by how closely our sources document this process, not by quality. Sponsored placements are labelled. How lists are ordered

    Not sure which fits? Take the three-question quiz
    Back to all articles