The Scope 3 Reckoning: Why Mining's Next Reporting Standard Runs Through the FMS

By the OpenAutonomy.com  Editorial Team

The GHG Protocol's Phase 1 Progress Update points emissions reporting toward primary, traceable, auditable data. For mining, that data chain runs straight through the fleet management system. The teams who think this is a sustainability problem are about to discover that payload accuracy, material tagging, and fuel telemetry quality are now boardroom concerns.

On 31 March 2026, the Greenhouse Gas Protocol published its Scope 3 Standard Revisions Phase 1 Progress Update. It is not a final standard. A full draft for public consultation is expected mid-2026, with a final standard targeted for late 2027. The direction of travel, however, is now clear, and the implications for mining operators are larger than most operations teams have yet recognized.

The headline number in the progress update is the proposed 95% completeness threshold: companies reporting in conformance with the revised standard would have to account for and report at least 95% of required Scope 3 emissions, with the remaining 5% quantified, justified, and disclosed rather than waved away in a narrative. The deeper change, and the one that should reshape how mines think about their own data, is the proposed disaggregation of reported emissions by data type, distinguishing primary or activity-based data from secondary, spend-based, or proxy data, and requiring the breakdown to be reported in absolute tonnes of CO₂-equivalent rather than as percentages.

The combined direction is unambiguous. The standard is being rewritten to make the difference between primary and proxy data visible, comparable, and auditable. Primary data, the kind that comes from real measurements of real activity rather than industry averages applied to spend, is becoming the basis on which Scope 3 inventories are judged.

For mining, the operational consequence of that shift sits much closer to the operator's seat than most boardrooms currently appreciate.

Where mining's Scope 3 data actually comes from

Most of the emissions that matter in a mining operation, including the ones that show up in customer Scope 3 inventories, are tied to physical activity at the truck, the loader, and the auxiliary fleet. Diesel burned per tonne hauled. Material moved by grade and destination. Idle time versus productive time. Equipment-hour attribution. Loads dispatched and completed.

The integration layer where almost all of that comes together is the fleet management system. The FMS is the layer that knows what was loaded, where it came from, where it went, and which truck did the work. The maintenance system knows what was burned and what failed. The operational data lake, where one exists, is downstream of both.

Which means that the audit trail for primary, traceable Scope 3 data in mining starts at the FMS. If the FMS payload data is wrong, every emissions-per-tonne calculation downstream of it is wrong. If material classification is bench-level rather than actual, the allocation of emissions to product is approximate at best. If fuel data arrives as event-based snapshots rather than continuous flow, allocating burn to specific loads is reconstruction, not measurement.

Most mines have lived with these data quality limitations for years because the data never previously had to stand up to an auditor.

What the new direction actually demands

If the proposed disaggregation rule lands, every Scope 3 category will need to be reported with a clear breakdown of how much of the number came from each tier of data quality. A mining customer reporting Scope 3 Category 1 emissions on a copper concentrate purchase will be expected to show how much of that figure was derived from supplier-specific primary data versus industry averages.

The implication moves upstream quickly. The supplier-specific number is only as good as the supplier's own data chain. For a mining operator, that chain runs:

Truck telemetry → FMS payload and material tagging → maintenance and fuel data → emissions calculation → reported figure.

Three properties of that chain matter under the proposed standard. It has to be traceable, meaning every reported tonne of CO₂-equivalent can be linked back to specific operational activity. It has to be measurable rather than estimated, with primary data preferred at every step. And it has to be auditable, meaning a third party can follow the chain end to end and verify it.

Most mining FMS deployments were not designed against these properties. They were designed for production reporting and dispatch optimization, with emissions reporting bolted on later. The data flows that work for "tonnes per hour by shift" do not necessarily survive an external audit of "tonnes of CO₂-equivalent per tonne of product, traceable to source".

What breaks first

Four FMS data quality issues become operational liabilities under the proposed direction.

Payload accuracy. Calibration drift, allocation rules at the loading face, and the difference between rated and actual payload all introduce systematic errors that do not matter much for production reporting but compound when they become the denominator of an emissions intensity figure.

Material classification. Many sites tag material at the bench level using mine plan attribution rather than at the truck level using actual loaded grade. The error is small at the bench but large at the product line, and it is exactly the kind of error a tier-disaggregated standard makes visible.

Fuel telemetry. Where fuel data arrives via fuelling events rather than continuous flow telemetry from the engine, allocation to specific loads or routes is interpolated. That works for an internal report. It does not pass the traceability test cleanly.

Equipment-hour attribution. Hours-on, hours-loaded, idle hours, and standby hours are often recorded inconsistently across OEMs and across FMS configurations. Emissions intensity per productive hour is meaningfully different from emissions intensity per powered hour, and a defensible inventory has to know which it is calculating.

Each of these is fixable, but none of them cheaply, quickly, or by the sustainability team alone.

Why this is now a procurement question

Mines that have already bought their next-decade FMS architecture, and the data layer around it, may have already constrained their options. Mines that have not yet made those decisions still can.

The question that needs to be asked of FMS, AHS, and onboard systems vendors, in current and future RFPs, is not just "can you produce an emissions report" but "what is the data lineage of the figures in that report, and can it survive an external audit at a tier-disaggregated level". The answer determines whether the sustainability team has primary data to report or whether the boardroom is going to have an uncomfortable conversation with its assurance provider.

The follow-on question is about ownership. If the underlying telemetry sits inside an OEM-controlled cloud, can the operator export it on demand, in raw form, with documentation of how it was sampled and processed. If the answer is no, or the answer involves a fee per export, the mine does not have the audit trail it needs. It has the OEM's interpretation of its audit trail.

This is not an argument against OEM-hosted data. Plenty of OEM platforms already deliver documented, exportable, audit-grade telemetry, and a well-specified contract can guarantee the access an auditor needs. The point is narrower: the operator has to know the data lineage and hold the right to export it, regardless of who hosts it. Architecture is a choice; traceability is a requirement.

The propagation effect

In September 2025, GHG Protocol and ISO announced a formal partnership to co-develop harmonized standards. The revised Scope 3 Standard is widely expected to form the basis of an ISO standard. Thirty-seven jurisdictions are at various stages of adopting or referencing the ISSB sustainability disclosure standards, which themselves point to GHG Protocol as their methodological foundation. SBTi-validated targets explicitly require GHG Protocol methodology.

What that means in practice is that this revision does not stay inside one body of guidance. It propagates through SBTi commitments, through regulatory regimes that build on GHG Protocol methodology, from California's SB 253 to the European CSRD, through procurement requirements at customers like the major automakers and battery manufacturers, and through the reporting expectations of major financial institutions. A mine that supplies copper concentrate to a battery maker with SBTi-validated Scope 3 commitments will be asked, eventually, to deliver primary, tier-disaggregated data on the emissions associated with that concentrate.

The standard does not become final until 2027 at the earliest. The data chain that supports it has to be built before then.

The plumbing question

This is, in the end, a plumbing problem rather than a policy problem. The policy question is being settled by the GHG Protocol Technical Working Groups, the Independent Standards Board, and the public consultation that follows. The plumbing question is the one that will be answered by every individual operator over the next two to three years, in decisions about FMS architecture, data ownership, telemetry granularity, and integration with maintenance and emissions reporting systems.

Plumbing decisions are usually invisible until they fail. The proposed Scope 3 direction is going to make them visible, in audit findings, in supplier ratings, and in the questions investors ask. The mines that build for traceability now will be reporting from primary data when their customers and regulators ask for it. The mines that do not will be explaining their methodology.