Why a base year matters
A base year is the fixed point against which every future emissions figure gets compared. Without one, a company can report a lower Scope 3 number this year than last year and have no way of knowing whether that drop reflects real decarbonisation, a change in how the number was calculated, or simply a divested business unit that no longer shows up in the inventory. The base year is what turns a series of annual snapshots into a trend line that means something.
This matters more for Scope 3 than for Scope 1 or 2 because Scope 3 inventories are built from a mix of data sources across categories — Purchased Goods & Services, Business Travel, Use of Sold Products, and so on — and those sources change quality and coverage far more often than a company's own fuel or electricity records do. A base year that isn't actively maintained will drift out of comparability within a couple of reporting cycles.
Setting the base year
GHG Protocol guidance treats the base year choice as a practical decision, not a symbolic one. The year selected should be one for which reasonably complete and verifiable data exists across the categories a company has determined are relevant to its Scope 3 footprint. For companies just starting Scope 3 measurement, this often means the base year is whatever year they first assembled a reasonably complete inventory — not necessarily the earliest year for which any data exists.
Because Scope 3 data quality varies so much by category — spend-based estimates sit at the weak end of the hierarchy, supplier-specific primary data at the strong end — companies should document, at the time they set the base year, exactly which data quality tier was used for each category. That documentation is what makes recalculation decisions defensible later.
The recalculation triggers
GHG Protocol base year guidance centers on a small number of triggers that justify going back and restating the base year figure. Recalculating isn't optional housekeeping — it's what keeps the comparison honest.
Structural changes. Mergers, acquisitions, and divestitures change what's inside the organizational boundary. If a company acquires a supplier it previously bought materials from, some emissions that were once Category 1 (Purchased Goods & Services) may now sit inside Scope 1 or 2. If a business unit is sold off, its historical emissions need to come out of the base year too, so that the trend line reflects the company's current structure rather than a structure that no longer exists.
Methodology and data quality changes. This is the trigger most Scope 3 practitioners run into constantly. Moving a category from spend-based estimation to supplier-specific primary data — the intended direction of travel under the data quality hierarchy — will almost always change the reported figure, sometimes substantially, even though nothing about actual emissions has changed. The same applies to switching emission factor databases, changing allocation methods, or expanding category boundaries to cover activities that were previously excluded as immaterial. GHG Protocol treats these as legitimate recalculation triggers precisely because the resulting change is a measurement artifact, not a performance change, and needs to be separated from the base year to keep the comparison clean.
Error corrections. Errors surface — a double-counted supplier, a unit conversion mistake, a misclassified category. GHG Protocol leaves it to each company to define its own significance threshold for what counts as an error large enough to warrant recalculation, rather than prescribing a fixed percentage. What the standard does require is that the threshold be defined in advance and applied consistently, not decided case by case once a convenient or inconvenient number turns up.
Write the recalculation policy down before you need it
The practical failure mode isn't missing a trigger — it's not having a documented policy for handling one when it appears. A recalculation policy set in advance should specify: which triggers apply, the significance threshold for errors, whether recalculation applies to the base year only or to all intervening years, and who signs off on a restatement. Companies that wait until an acquisition or a data quality upgrade forces the question tend to make ad hoc calls that are hard to defend to auditors or to the market later, and that inconsistency is exactly what erodes trust in a reported trend.
Why this is no longer just good practice
Regulatory disclosure regimes are increasingly built on the assumption that a company's emissions trend is real and traceable. Under frameworks like the EU's CSRD/ESRS E1 or California's SB 253, which phases in third-party assurance requirements for Scope 3 disclosures, an assurance provider will ask not just what the current-year number is but why it moved relative to the base year — and whether that movement was structural, methodological, or an error correction. A vague or undocumented answer is the kind of gap that surfaces in assurance findings. Treating base year management as a live discipline, with a written recalculation policy maintained alongside the inventory itself, is what keeps a Scope 3 trend line credible enough to survive that scrutiny.
For companies building or overhauling a Scope 3 inventory, base year policy is worth settling at the same time as category boundaries and data quality tiers — not retrofitted once the first restatement question comes up.