Why methodology determines whether emissions data can be trusted
Two logistics companies, similar fleets, similar routes. One reports 8 kg CO₂e per tonne-kilometre. The other reports 14 kg CO₂e per tonne-kilometre. Both claim to follow international standards.
Which number should a sustainability manager use in their CSRD report? The honest answer is: it depends entirely on what freight emissions methodology the operator actually used. Without knowing that, you cannot rely on either figure with confidence, because the gap between them reflects methodology, not performance. This is precisely where the standardisation problem becomes a reporting problem.
The inconsistency problem across logistics actors
Freight emissions figures vary between operators not because reality differs, but because calculation approaches differ. The sources of inconsistency are structural:
Emission factor selection: different databases, different vintages, different scopes. A road transport emission factor from 2018 differs from a 2024 factor that accounts for fleet electrification and updated fuel specifications.
Allocation logic: when a vehicle carries multiple customers' goods, who carries which share of the emissions? The answer depends on whether the operator uses mass, volume, or TEU (Twenty-foot Equivalent Unit) count as the basis, and each approach produces a different result for the same shipment.
System boundary: does the calculation include Tank-to-Wheel (TTW, direct combustion only), or Well-to-Wheel (WTW, including fuel production and distribution)? The choice affects the number by 15%–25% for conventional diesel.
Transport chain definition: a shipment from Hamburg to Milan may involve a pre-carriage truck leg, a main rail leg, and a final road delivery. Does the calculation cover each leg separately? Does it include hub operations?
Without a shared methodology, every operator can produce a number that is technically defensible but not comparable with anyone else's number. As a result, operators cannot aggregate, audit, or use the data externally, regardless of how carefully they calculated it.
How ISO 14083 standardises freight emissions methodology
ISO 14083 addresses each of those four inconsistency sources directly. The standard covers all transport modes (road, rail, sea, inland waterways, and air) and specifies:
- Required inputs: fuel consumption or energy use, distance, payload, vehicle or vessel type, and transport mode
- Emission factors: which emission factors are acceptable and from which sources, distinguishing between default values and primary data
- Allocation rules: how to allocate emissions across goods in a shared transport operation (mass-based, volume-based, TEU-based)
- System boundary: whether calculations cover TTW or WTW emissions, declared explicitly
- Transport chain completeness: pre-carriage, main carriage, and last-mile segments, each necessary for a complete calculation
How GLEC makes ISO 14083 operational
The GLEC Framework addresses the inconsistency problem directly through its data quality tier system, formally the Data Quality Indicator (DQI), a four-level classification that identifies how reliable each input to a calculation is, and that operators must declare in every output record.
- Tier 1: Actual measurements: fuel receipts, GPS distance, weigh-bridge data
- Tier 2: Carrier-specific averages based on their own fleet data
- Tier 3: Mode-specific defaults from a regional dataset
- Tier 4: Global average defaults; rough industry estimate
Tier 4, labelled "Unsatisfactory" in the DQI system, applies global averages that are not differentiated by transport mode or region. Consequently, Tier 4 data is not acceptable for ISO 14083-compliant reporting. It is only suitable for rough pre-booking estimates where no other data is available. The minimum reportable tier is Tier 3.
However, this is where a significant source of incomparability emerges within compliant reporting. Two carriers operating the same route, one using Tier 1 primary data from actual fuel receipts and the other using Tier 3 regional defaults, will produce figures that diverge meaningfully. A regional default applies an average across many operators; the actual fuel consumption of a specific fleet on a specific route will differ, sometimes by a substantial margin. Moreover, under CSRD reasonable assurance review, a Tier 3 figure requires the carrier to justify why primary data was unavailable. Specifically, a Tier 1 figure is self-evidencing; a Tier 3 figure is not.
What "methodology-first" means in daily logistics practice
Methodology is not a compliance document; it is an operational discipline. Applying it correctly means selecting the right emission factor for each shipment, applying the correct allocation rule across every multi-modal leg, and declaring the boundary scope for each calculation. The standard therefore operates at the shipment level, not just at the report level.
However, two companies can both cite ISO 14083 and produce figures that are not comparable, if one applies the standard correctly and the other applies it selectively or partially. That's why the citation is not the proof. The application is. In practice, "ISO 14083-based" tells you nothing about whether the operator applied the calculation correctly, it tells you only which rules they intended to follow.
For this reason, CO2Path follows this logic precisely. ISO 14083 and the GLEC Framework form the calculation foundation, applied consistently across every shipment, with the methodology version and emission factor source recorded in every output. The result is a complete audit trail connecting the reported figure to the underlying inputs, so any external reviewer can verify not just the number, but how CO2Path produced it.
In practice, correct application breaks down in predictable ways: distance estimates that skip ISO 14083's mode-specific correction factors, outdated emission factor databases applied uniformly across a fleet, and allocation logic that doesn't match the standard's mass-based rules. A forthcoming post will examine each of these failure patterns in detail.
CO2Path is built on ISO 14083. Explore how it works → Request a demo
Frequently asked questions
Figures vary because different operators use different methodologies — different emission factor databases, different allocation logic, different system boundaries. Two carriers on the same lane can produce emissions figures that differ by 40% or more, not because reality differs but because the calculation approaches differ. ISO 14083 provides a common framework to eliminate this structural inconsistency.
ISO 14083 standardises the emission boundary (Well-to-Wheel), allocation method (mass-based across co-loaded shipments), system boundary (all transport legs from consignor to consignee), and emission factor structure (by vehicle type and energy carrier). These choices eliminate the most common sources of incomparable figures between operators.
ISO 14083 sets the rules; the GLEC Framework provides the data and implementation guidance to apply them. GLEC v3 is fully harmonised with ISO 14083:2023 and provides default emission factors, transport mode datasets, and a data quality tier system so operators can calculate to the standard without building their own factor libraries.
CSRD assurance reviewers do not just check whether the final figure is plausible — they work backwards: methodology documentation is requested first, before the number is examined. If the methodology is undocumented, proprietary, or inconsistent between reporting periods, the assurance team raises a finding at that step — the number never gets evaluated on its merits. This means a company with a precisely calculated figure but no audit trail is in a worse position than one with a rougher estimate and complete methodology documentation.
WTW covers the full carbon cost of a fuel — from extraction, refining, and distribution (Well-to-Tank) through to combustion in the vehicle engine (TTW). ISO 14083 requires WTW for all calculations. A WTW figure is typically 15–25% higher than tailpipe-only figures.