It’s October. Your JSE auditor calls. They want to trace your Scope 2 emissions back to the mill’s meter data. Your CFO pulls the number from an ESG spreadsheet. The auditor asks, “Where does this come from?” Who entered it? What’s the source document?
Mining companies face at least eight ESG frameworks in 2026: ISSB, GRI, TCFD, JSE, SASB, DMRE, carbon tax reporting, and EU CSRD alignment. ISSB wants Scope 2 by location. GRI wants water by source. TCFD wants climate risk by scenario. Same underlying data, eight different cuts, and auditors need to trace the numbers back to the source. Most mining companies we work with still use spreadsheets, and the chain breaks at three points.
The Three-Gap Framework
Spreadsheet-based ESG reporting fails in three specific, testable ways. The data has no traceable lineage. It’s not validated against operational reality. And derived metrics are aggregated using methods that are flat-out mathematically wrong. We’ve started calling these the Lineage Gap, the Validation Gap, and the Aggregation Gap.
The Lineage Gap
You have a number. Where did it come from?
A water withdrawal figure flows from the mine site to a regional manager, gets adjusted, gets summed with other regional numbers, and lands in the disclosure. Four months later, an auditor requests the original plant-level data, including timestamps and approval stamps. You’re hunting through email attachments and hoping someone kept the right version.
How to close it: Capture ESG metrics at source. Scope 2 emissions are calculated from monthly utility bills, but within a site, power consumption is measured continuously at the substation. Energy intensity per tonne should be derived from production records and real-time power data, not from an operator’s monthly estimate entered into a spreadsheet. Once that data feeds into a system of record, lineage takes care of itself.
The Validation Gap
A site reports zero water withdrawal for the month. That same site processed 10,000 tonnes at normal production intensity. Those two facts can’t both be true, but nobody catches it until the auditor reconciles ESG numbers against production records four months later.
What catches this: Cross-referencing ESG inputs against operational data in real time. The system knows what the site produced (from the production database), what resources it consumed (from meters and utility feeds), and what it reported (from ESG submissions). When a submission violates the operational baseline, a validation rule fires, and the site manager receives an alert that day. Not four months later when the auditor finds it, but while there’s still time to correct the record or investigate the equipment fault behind the anomaly.
The Aggregation Gap
Say you want to report energy intensity per tonne across your operation. Five sites, different production volumes. You average their per-tonne ratios directly.
That’s wrong. The table shows why:
| Site | Production (t) | Energy (kWh) | Intensity (kWh/t) |
|---|---|---|---|
| Site A | 5,000 | 25,000 | 5.00 |
| Site B | 12,000 | 48,000 | 4.00 |
| Site C | 3,000 | 18,000 | 6.00 |
| Site D | 8,000 | 40,000 | 5.00 |
| Site E | 20,000 | 80,000 | 4.00 |
| Total | 48,000 | 211,000 |
Wrong method (average of per-site ratios):
(5.00 + 4.00 + 6.00 + 5.00 + 4.00) ÷ 5 = 4.80 kWh/t
Correct method (total energy ÷ total production):
211,000 ÷ 48,000 = 4.40 kWh/t
The naive average gives Site C (3,000 tonnes, high intensity) the same weight as Site E (20,000 tonnes, lower intensity). That’s a 9.2% error, overstating energy use by 19,400 kWh across the operation. Any auditor reconciling your reported energy intensity against actual utility bills will find it.
The right approach: Aggregate by framework-specific rules, not by whatever’s easiest in a spreadsheet. GRI asks for water intensity per unit of product. TCFD needs Scope 3 emissions allocated by geography. The aggregation engine applies the correct calculation for each framework automatically: total divided by total, weighted by production volume, allocated by the rules the standard prescribes.
This is the problem we built Capstone to solve. It captures ESG metrics from production systems, validates them against operational data, and aggregates by framework-specific rules. The audit trail runs from the meter to the disclosure.
See how this works in practice: African Rainbow Minerals consolidated 1,153 ESG data points across 8 operations using this approach, and Anglo American cut sustainability data validation from 2 months to 2 weeks across 160+ operations.
Why Standalone ESG Tools Fall Short in Mining
The market offers ESG disclosure tools (Salesforce Sustainability Cloud, Workiva, IBM Environmental Intelligence, among others). They’re good at intake forms, compliance templates, and multi-framework report generation. But they aren’t designed to ingest production data. Some offer ERP connectors, but their data model starts from disclosure forms, not from plant-floor measurements.
That’s a problem for mining, because mining ESG metrics are calculated, not entered. Energy intensity per tonne requires throughput. Water recycling percentage requires water balance data. Emissions per unit of ore moved requires production records. These tools handle the disclosure layer well. They don’t touch the calculation layer.
In practice, most mining operations split ESG data across three systems: production databases (throughput and plant performance), financial systems (cost allocations), and ESG spreadsheets (the disclosure numbers). The links between them are manual: copy-paste, email, quarterly reconciliation meetings. Every handoff is a chance for a transcription error, a version mismatch, or a stale number. The auditor traces a number back to a spreadsheet column, not to a meter. It doesn’t matter whether the compilation is done in-house or by an external ESG consultant. The data gaps are the same.
The 2026 Regulatory Landscape
ISSB is the global baseline. Mandatory for listed companies in many jurisdictions by 2026-2027, it uses financial materiality: how sustainability issues affect enterprise value, cash flows, and cost of capital. It’s investor-focused, not impact-focused (that’s GRI’s domain).
GRI is the oldest disclosure standard and is still widely required. It’s more granular than ISSB, and many auditors still expect GRI data even when ISSB is the formal requirement. For a deeper look at what the new GRI 14 mining sector standard means for your data architecture, see GRI 14 Mining Sector: Why It’s a Data Architecture Problem.
TCFD disbanded in 2023. Its recommendations are now folded into ISSB standards, but regulators in the UK, Singapore, and Australia still reference TCFD-aligned disclosure requirements. If you’re reporting under ISSB, you’re covering TCFD.
For South African operations, there are two separate requirements. JSE mandates climate-related financial disclosure for listed companies (historically TCFD-aligned, now folding into ISSB) plus local environmental and social metrics. DMRE is the mining regulator, separate from the JSE, that requires mine-specific water, air, energy, and biodiversity metrics on its own timeline.
SASB is industry-specific. Mining SASB metrics differ from energy SASB metrics. The standards are now maintained under the IFRS Foundation alongside ISSB. There’s no formal reporting requirement in most jurisdictions, but investors increasingly expect it.
Then there are carbon tax frameworks: the EU ETS, South Africa’s carbon tax, and Australia’s various schemes. Each calculates scope 2 and 3 emissions differently. Each requires its own audit trail.
EU CSRD is the one catching people off guard. Under the Omnibus I directive (adopted February 2026), non-EU companies now need €450M+ in EU net turnover (over two consecutive years) and an EU subsidiary or branch generating €200M+ to fall in scope. The thresholds were raised from the original €150M, but if you’re a large mining group with European operations, you’re likely still caught. It uses double materiality (financial plus impact) and requires sector-specific European standards (ESRS).
Every one of these frameworks calculates the same emissions differently: different boundary rules, allocation methods, verification trails. An ESG system for mining needs to produce compliant outputs for all of them from a single data source.
FAQ
Q: Can we use Power BI or Tableau to build the single source of truth?
A: Some teams do build calculation layers in DAX or Power Query, and BI tools visualise ESG data well. The gap is governance. Power BI doesn’t natively support version control for metric definitions, maintain immutable audit trails, or enforce approval workflows for regulated data. If your auditor needs to see who changed a calculation and when, BI tools won’t give you that out of the box. We’ve covered this trade-off in detail in Power BI and Capstone: Why You Need Both.
Q: Does the platform need to replace our production database?
A: No. It sits between your production systems and your disclosure outputs. It needs read access to your ERP and plant systems, and it stores the calculated ESG metrics with full lineage. Nothing gets replaced.
Q: How long does it take to set up?
A: Lineage is fast: about 30 days to define data sources and calculate core metrics. Validation rules take another 30 days because you’re deciding what “normal” looks like at each site. Aggregation logic and multi-framework reporting are framework-specific, so expect 4-6 weeks to validate each framework’s output.
Q: Can we keep using spreadsheets for regional data entry?
A: Technically yes, but you’re reintroducing the lineage gap. Better to use web forms or API feeds that push data directly into the system of record, with versioning and approval workflows baked in.
The Next Step
We’re seeing the shift across our client base: auditors are moving from “did you report everything?” to “can you prove these numbers?” They’re asking for source documentation, testing calculation logic, and reconciling ESG numbers against production records.
If your audit is within 6 months and you can’t trace your ESG numbers back to their sources, start now. The three-gap framework gives you a quick diagnostic. Ask your team three questions: Can we trace any number back to the source in under 15 minutes? Do we have automated checks that flag contradictions between ESG and production data? Are we aggregating derived metrics by framework-specific rules, or by hand?
If the answer to any of those is no, you’re exposed. The cost of closing these gaps is a platform investment and a few months of configuration. The cost of not closing them is a restatement, regulatory attention on your next filing, and months of remediation, pulling your team away from running the operation.
Talk to us about closing the three gaps before your next audit.
NxGN Solutions builds Capstone, an operational intelligence platform for manufacturing and mining. Capstone ingests production, environmental, and financial data to calculate and audit ESG metrics by framework, with full lineage and continuous validation. Learn more at nxgnsolutions.com.