Mining · ESG & Emissions Report

ESG, Energy & Emissions Reporting in Mining: From NGER Compliance to a Credible Decarbonisation Story

13 June 202611 min readPerth, Western Australia

Short answer

Mining ESG and emissions reporting tracks Scope 1 emissions (diesel combustion, on-site power generation, fugitive sources), Scope 2 emissions (purchased grid electricity), and material Scope 3 categories, alongside energy consumption and intensity (GJ per tonne treated), emissions intensity (tCO₂e per tonne or per ounce of product), and progress against decarbonisation targets - reconciled to the same production volumes and fuel records used for NGER and Safeguard Mechanism submissions. Done well, it produces one emissions figure that satisfies the Clean Energy Regulator, the financial auditor and the investor relations team simultaneously. SolveBI builds ESG dashboards on Power BI and Microsoft Fabric that unify fuel transactions, power metering, fleet burn data and emission factors into a single, audit-ready carbon and energy view.

A haul truck refuelling at a mine site diesel bay alongside a solar array - the diesel combustion and electricity sources that make up the Scope 1 and Scope 2 emissions at the heart of mining ESG reporting.

Why emissions reporting is now a board-level number, not a year-end submission

For most of the last decade, a mine site's emissions number was something the environment team assembled once a year for the National Greenhouse and Energy Reporting (NGER) submission and then largely forgot. That era is over. The reformed Safeguard Mechanism now sets a declining baseline for every facility emitting more than 100,000 tonnes of CO₂-equivalent a year - and most large Australian mines sit comfortably above that threshold. At the same time, mandatory climate-related financial disclosure under AASB S2 has begun phasing in, requiring large entities to report Scope 1, Scope 2 and material Scope 3 emissions inside the audited financial reporting cycle, with the same level of rigour as a financial statement.

The practical consequence is that the emissions number can no longer be a once-a-year spreadsheet estimate. It has to be reconciled to the fuel invoices, the power meter readings and the production volumes; it has to be traceable to source; and it has to be current enough that management can see the trajectory against a declining Safeguard baseline before the compliance year closes - not three months after, when the only options left are buying Safeguard Mechanism Credits or Australian Carbon Credit Units to cover the gap.

100,000 t
CO₂-e annual threshold above which a facility is covered by the Safeguard Mechanism; most large WA mines exceed it
4.9%/yr
Default rate at which Safeguard baselines decline to 2030 - a moving target that rewards early visibility
Scope 1+2+3
AASB S2 requires all three; Scope 1 diesel and Scope 2 grid power dominate a typical mine's footprint

The metrics that belong on a mining ESG and emissions dashboard

  • Scope 1 emissions (tCO₂e) - diesel and fuel combustion in the fleet, on-site power generation, explosives and any fugitive emissions; split by source and activity
  • Scope 2 emissions (tCO₂e) - purchased grid electricity, reported on both location-based and market-based methods where renewable contracts apply
  • Material Scope 3 emissions (tCO₂e) - purchased goods, contractor fuel, transport and (for many operations) processing of the product downstream
  • Energy intensity (GJ/t) - total energy consumed per tonne of ore treated; the operational efficiency measure behind the emissions number
  • Emissions intensity (tCO₂e/t or /oz) - carbon per unit of product; the metric investors use to benchmark you against peers
  • Diesel consumption by fleet and activity - litres burned per BCM moved and per operating hour; the single largest Scope 1 lever on most sites
  • Performance against Safeguard baseline and corporate target - actual emissions trended against the declining baseline and the company's net-zero pathway

Diesel is the number that moves: linking fuel burn to the activity that caused it

On a diesel-powered open-cut operation, the haul fleet is typically the largest single source of Scope 1 emissions - often more than half of the site total. That makes diesel burn the most important emissions lever available, and it is one that the operations team already influences every day through cycle times, payload, road condition and idle time. Reporting that connects litres of diesel to BCMs moved, to truck operating hours and to road segment makes the emissions number actionable: a rising fuel-burn-per-BCM trend is both a cost signal and a carbon signal, and the same dashboard that shows operations the cost can show the sustainability team the emissions.

A Power BI ESG dashboard showing Scope 1 and Scope 2 emissions broken down by source - diesel fleet, on-site generation, grid electricity - trended against the declining Safeguard Mechanism baseline.
Emissions broken down to source, trended against the declining Safeguard baseline. Diesel fleet burn typically dominates Scope 1 - which makes it the most actionable line on the chart.

Tracking the decarbonisation pathway, not just the current footprint

Every major miner has now published a net-zero commitment and an interim emissions target. The gap between a commitment in an annual report and a credible decarbonisation programme is measurement: a target with no monthly tracking against an abatement pathway is an aspiration, not a plan. A good ESG dashboard tracks actual emissions against the target trajectory, attributes variance to its cause (production growth, fuel switching, grid decarbonisation, fleet electrification trials), and surfaces the abatement initiatives - trolley assist, renewable power purchase agreements, battery-electric equipment trials, fuel efficiency programmes - against their expected and realised emissions reduction.

Annual NGER spreadsheet vs a continuous ESG dashboard

Year-end emissions spreadsheet vs unified ESG dashboard

AspectYear-end spreadsheetUnified ESG dashboard
Reporting frequencyOnce a year for the NGER submissionMonthly - actuals against the Safeguard baseline as the year unfolds
Reconciliation to productionEmissions and tonnes from separate sourcesOne dataset - intensity figures always reconcile
Audit readiness (AASB S2)Reconstructed each year; weak audit trailEvery figure traceable to fuel, power and production source
Safeguard baseline trackingGap discovered after year closeTrajectory visible in time to manage the gap
Decarbonisation progressNarrative in the sustainability reportActuals tracked against the abatement pathway monthly

The Power BI and Fabric architecture behind ESG reporting

On a typical SolveBI deployment we land fuel transaction data (bulk fuel farms, fleet refuelling systems), electricity meter and retailer billing data, on-site generation records, production volumes from dispatch and the process historian, and the current NGER emission factors into Microsoft Fabric, then expose a single emissions model through Power BI. The sustainability team sees the Scope 1, 2 and 3 breakdown and Safeguard tracking; operations sees diesel intensity by fleet; finance and investor relations see emissions intensity per unit of product and progress against the net-zero pathway - all from one dataset, with the same emission factors and the same production denominators applied consistently.

Common mistakes in mining ESG and emissions reporting

  1. Treating emissions as an annual exercise. A number assembled once a year for NGER cannot manage a Safeguard baseline that declines every year.
  2. Emissions and production on different cut-offs. Intensity figures only mean something when the carbon and the tonnes come from the same reconciled period.
  3. Stale emission factors. NGER emission factors are updated periodically; a model with hard-coded factors silently drifts out of compliance.
  4. No location-based vs market-based Scope 2 split. Renewable power purchase agreements only show up in the emissions number if both methods are reported.
  5. Decarbonisation target with no monthly tracking. A net-zero commitment without actuals against the abatement pathway is a statement, not a programme.

From a year-end emissions spreadsheet to a monthly carbon figure your auditor, your regulator and your board all trust.

Book a free 30-minute consultation with a SolveBI consultant. We'll map your fuel, energy and production data, align it to your NGER and AASB S2 obligations, and quote a phased Power BI deployment that turns emissions reporting into a management tool.

Frequently Asked

Common Questions

Can it produce the data we need for our NGER and Safeguard Mechanism submissions?
Yes. We build the emissions model using the current NGER methods and emission factors, reconciled to your fuel, energy and production records, so the figures that feed the dashboard are the same ones that support the NGER submission and the Safeguard baseline comparison. The emission factors are maintained as a managed reference table so they can be updated when the regulator revises them, rather than hard-coded into formulas.
Does it support AASB S2 mandatory climate disclosure requirements?
Yes. AASB S2 requires Scope 1, Scope 2 and material Scope 3 emissions to be reported with an auditable trail. We build the model so every emissions figure can be traced back to its source transaction - fuel invoice, meter reading or production record - which is exactly what an assurance provider needs to verify the disclosure. The same dataset serves both the operational dashboard and the financial-grade disclosure.
Can it separate location-based and market-based Scope 2 emissions?
Yes. Where you hold renewable power purchase agreements or surrender large-scale generation certificates, we report Scope 2 on both the location-based method (grid average factor) and the market-based method (reflecting your contracted renewable supply), so the emissions benefit of your renewable contracts is visible.
Can it link diesel emissions to operational drivers like cycle time and payload?
Yes. Where fuel transactions and fleet dispatch data are both in Microsoft Fabric, we join them so diesel burn can be expressed per BCM moved, per operating hour and per route - making the emissions number actionable for the operations team, not just reportable for the sustainability team.
How long does an ESG and emissions dashboard take to deploy?
Typically five to eight weeks for a working Scope 1 and Scope 2 dashboard reconciled to production, with Safeguard baseline tracking. Adding material Scope 3 categories, market-based Scope 2 reporting and full decarbonisation-pathway tracking adds two to four weeks depending on data availability and the maturity of the existing emissions inventory.