Your Scope 3 Number Went Up Because Your Data Got Better. Here's How to Say So
You spent a year getting real data from your biggest suppliers. You replaced industry averages with their actual figures. Then the new inventory lands on the CFO's desk, and Scope 3 is higher than the number you reported last year.
The awkward question follows: did emissions go up, or did the measurement change? Usually it's the second. A restated baseline after better supplier data isn't a sign the programme failed. It's often the first evidence that it's working. But it only reads that way if you handle the restatement properly.
Why better data moves the number
Most companies start Scope 3 with spend-based estimates: euros spent per sector multiplied by an industry-average emission factor. That's a legitimate starting point, but it can't tell one supplier from another. It even works against you: the MIT Sustainable Supply Chain Lab points out that when companies make more sustainable choices that cost more, spend-based accounting shows their emissions rising , because the price went up.
When supplier-specific or activity-based data replaces those averages, the total shifts. Sometimes it goes up, because the average flattered your suppliers. Sometimes it goes down: in a worked example from Quantis , primary data from key suppliers moved a spend-based 2021 baseline from 500,000 to 420,000 tonnes CO₂e.
Either way, nothing happened in the atmosphere. The GHG Protocol's Scope 3 Standard describes exactly this case: in its third year of reporting, a company "may significantly improve its data quality by collecting more data from suppliers". Its answer is that the company must make sure changes over time reflect real increases or decreases, not changes in method, so that it tracks "like with like".
The rules already expect you to restate
Rebaselining isn't a loophole or an admission. Every major framework already has a mechanism for it, whether you report under it yourself or your largest customers do.
| Framework | What it asks when better data changes the numbers |
|---|---|
| GHG Protocol (Scope 3 Standard, ch. 9) | Recalculate base year emissions if new data sources or methods cause significant differences. Have a written policy with a significance threshold, and apply it to increases and decreases alike . |
| SBTi | Current criteria list "adjustments to data sources or calculation methodologies" as a trigger for target recalculation , with a 5% threshold. The Corporate Net-Zero Standard V2.0 evaluates data-quality improvements at the end of the target cycle, using 5% per scope. Validations under V2.0 open in February 2027 ; V1.3 stays open until 31 January 2028. |
| ESRS (CSRD) | When new information about a previous estimate reflects circumstances that already existed, restate the comparative figure and explain why; if that's impracticable, say so. The revised ESRS (ESRS 1 ¶84–85), mandatory from financial year 2027, keep this rule from the 2023 set . As PwC notes , this differs from financial reporting, which puts revised estimates in the current period. |
| GHG Protocol Scope 3 revision (draft) | Proposed Revision A1: Scope 3 "shall be disaggregated by data type" (supplier-specific, secondary, spend-based), partly to "incentivize companies to collect primary data" (Phase 1 progress update, March 2026 ; still subject to change). |
Large reporters already do this in the open. Dow's 2025 GHG report restates prior-year Scope 3 for selected categories to reflect "more accurate ecoinvent and CDP emission factors", applied consistently back through earlier years. PepsiCo restated its 2024 Scope 3 performance after recalculating its 2022 packaging baseline from updated volume and specification data.
The direction of travel is clear. The draft Scope 3 revision would make the share of spend-based estimates visible in every disclosure. Companies that are still mostly on averages will have that on display. Companies that did the work, and restated because of it, will be able to show it.
What a restatement does to your target
For an absolute reduction target, rebaselining usually leaves the ambition alone and moves the tonnes. In the Quantis example, the 30% target was simply reapplied to the corrected baseline, so the 2030 goal moved from 350,000 to 294,000 tonnes.
That's the point to make to your board: the target didn't get easier or harder in percentage terms; it now points at a number that's closer to reality. And reductions measured against a primary-data baseline are reductions you can actually trace to suppliers and products. Against a spend-based baseline, the only lever that shows is spending less.

The fair objection
Sceptics have a point. Base years can be used to flatter targets. The Corporate Climate Responsibility Monitor 2025 by NewClimate Institute and Carbon Market Watch criticises late, high-emission base years that lower real ambition. It found the emissions disclosures of most of the 20 companies it assessed "largely incomplete and inconsistent", which makes targets against historical base years hard to interpret.
So "it's just better data" can't be a blanket excuse. Two things separate a credible restatement from a convenient one:
- Symmetry. The policy applies whether the restatement raises or lowers the baseline, as the GHG Protocol requires.
- Separation. Method changes and real changes are reported apart. When they're tangled, for example when a supplier's new figure reflects both better measurement and a real efficiency gain, Quantis recommends the conservative route: treat it as a method change unless you can prove otherwise.
How to restate without losing trust
- Write the recalculation policy before you need it. Name the triggers (structural change, method or data improvement, errors) and a threshold. 5% matches SBTi. Get it signed off now, not in the week the new numbers arrive.
- Label the method behind every figure. If you know which lines are supplier-specific, activity-based or spend-based, you can show exactly where the change came from. The draft GHG Protocol revision is heading this way anyway.
- Restate the base year with the same method, or say why you can't. ESRS allows "impracticable", but you have to disclose it.
- Show a bridge, not just two totals. A simple waterfall works: previously reported baseline, method and data changes, restated baseline, then real changes since. It turns "why did it go up?" into a two-minute conversation.
- Report data quality as a result in its own right. The share of Scope 3 on supplier-specific data, year on year, is progress your board can see before the tonnes start falling.
Where Simple. fits
A restatement is only as convincing as your ability to show where each number came from. We've built Simple. so that every line of a supplier invoice, receipt or bill of materials gets its own CO₂e figure. Each line is labelled with the method used (an environmental product declaration where one exists, then activity-based factors, with spend-based only as a fallback) and the emission factor behind it. You can see which part of your footprint moved because the data got better. If you run your base-year invoices through the same method, you get a like-for-like restatement with the trail to back it up. If you want to try it on your own documents, it's free to try: 100 free credits for your first company, no credit card required .
Sources: GHG Protocol Corporate Value Chain (Scope 3) Standard and Scope 3 Standard Revisions Phase 1 Progress Update (March 2026); SBTi Corporate Net-Zero Standard V2.0 and Criteria Assessment Indicators V1.7; ESRS Set 1 (EFRAG), the revised ESRS (Delegated Regulation (EU) 2026/1563) and PwC's guide to the revised ESRS 1; Quantis, Tracking Progress; Dow 2025 GHG Report; PepsiCo climate disclosures; MIT Sustainable Supply Chain Lab; NewClimate Institute and Carbon Market Watch, Corporate Climate Responsibility Monitor 2025.




