Project-Level Carbon Reporting for Australian Civil...

The site supervisor on a major road duplication has 47 concrete delivery dockets, 18 fuel receipts from the bowser truck, three months of plant hire fuel returns, and a folder of subcontractor diesel declarations sitting on his ute dashboard. The sustainability advisor in head office needs all of it. The ISCA verifier will want to see it again in March. The client (TfNSW or MRPV) wants a monthly carbon estimate. The NGER team wants it rolled into corporate by August. The CFO needs it in the AASB S2 disclosure.

That's one project. The contractor has eleven of them running.

This is what project-level carbon reporting actually looks like on Australian civil jobs. Not the diagram in the IS rating manual. The real thing.

The data sources on a civil project

Every civil project generates emissions data from roughly nine recurring sources. We've watched the same pattern on roadworks, tunnel jobs, rail packages and water infrastructure.

Fuel dockets from on-site refuellers. A 20,000-litre fuel truck visits the site two or three times a week. Each fill of a haul truck, dozer or excavator generates a docket with litres, plant ID, sometimes an odometer reading. Most are paper. Some are emailed PDFs from the fuel supplier (Ampol, BP, Viva). A small number come through telematics if the plant has it.

AdBlue deliveries and consumption. Often forgotten. AdBlue itself isn't a Scope 1 fuel, but its consumption ratio (typically 3-5% of diesel) is a useful data-quality cross-check against diesel records. We've seen reported diesel volumes that imply zero AdBlue use, which is physically impossible on modern Tier 4 plant.

Concrete delivery dockets with strength grades. Every load arrives with a docket showing m³, strength (N20, N32, N40, N50), supplementary cementitious material (SCM) blend, and supplier batch plant. The strength matters because the embodied carbon of N50 is materially higher than N32 (more cement, less fly ash or slag). For ISCA Mat-1 credits, you need the actual blend, not a generic concrete factor.

Asphalt tonnages. Delivery dockets from Boral, Fulton Hogan, Downer or Hanson with tonnes, mix type (AC14, AC20, SMA, OGA), warm-mix vs hot-mix, recycled content percentage. Warm-mix asphalt and high-RAP content materially change the EPD value.

Plant hire fuel logs. Wet hire plant (operator included) comes with fuel use. Dry hire usually doesn't unless you specify it in the contract. This is one of the most common data gaps on a job. If you didn't write the fuel reporting clause into the hire agreement, you're chasing the data after the fact.

Electricity from temporary site connections. The site office, workshop, batching plant, dewatering pumps and tower cranes draw from a temporary builders' supply. Sometimes there's a meter. Sometimes there isn't. On a 24-month job in Victoria at 0.78 kg CO2-e/kWh, this is not a rounding error.

Off-site fabrication EPDs. Precast segments, steel reinforcement, structural steelwork, signage gantries. The fabricator may have an EPD. They may not. EPD Australasia is the place to check first before falling back to generic factors.

Subcontractor diesel returns. Earthworks subbies, line marking crews, demolition contractors. Some give you litres. Some give you spend. Some give you a flat "we used our normal fleet" and expect you to estimate.

Waste haulage and disposal. Tonnes to landfill vs recycling, haul distance. Often arrives via the waste contractor's monthly invoice with mixed line items.

Nine sources. Multiply by ten or twelve concurrent projects. This is why the 10,000 fuel receipts a quarter problem is real, not rhetorical.

How this maps to ISCA IS rating credits

The Infrastructure Sustainability Council (ISCA) IS rating tool is the dominant sustainability rating for Australian infrastructure projects. Most major civil packages on Cross River Rail, Snowy 2.0, Inland Rail, Western Sydney Airport, Sydney Metro West, Suburban Rail Loop Victoria and North East Link are rated under either IS Design v2.1, IS As Built v2.1 or IS Operations v2.0.

The credits that consume the data above are concentrated in three places:

Ene-1 Energy and Carbon Monitoring & Reduction. Requires a project carbon footprint covering Scope 1 (diesel, gas, refrigerants on site), Scope 2 (purchased electricity) and material Scope 3 categories. The credit rewards a documented baseline, demonstrated reduction initiatives, and verified actuals against the baseline. The verifier will ask for source documents, not summary spreadsheets, to substantiate the kilolitres of diesel and kWh of electricity claimed.

Mat-1 Materials Footprint. Requires quantified embodied carbon for the project's significant materials (concrete, steel, asphalt, aggregates, pavement). EPDs preferred. Generic factors accepted with justification. This is where the strength grade on the concrete docket actually matters, and where most spend-based carbon tools fall over completely.

Mat-2 Sustainable Procurement. Rewards verified sustainable procurement processes. Less about emissions numbers, more about supplier engagement and EPD coverage of supply.

There are other credits that touch carbon (Cli-1 Climate Change Risk, Eco-2 Land, Was-1 Waste) but Ene-1 and Mat-1 are the heavy lifters for emissions data flow.

The MRPV and TfNSW workflows

Major Road Projects Victoria (MRPV) requires carbon reporting on its program of works under the MRPV Sustainability Strategy. The expectation on Tier 1 contractors is monthly or quarterly carbon updates, with annual reconciliation against a project baseline. The reporting templates lean heavily on the IS rating framework.

TfNSW operates the Carbon Estimate and Reporting Tool (CERT) for its capital program. CERT requires upfront design-phase carbon estimates and ongoing actuals reporting through delivery. The categories largely mirror IS Ene-1 and Mat-1, with TfNSW-specific factor sets in some cases.

We don't directly integrate with either CERT or the ISCA submission portal. Both are bespoke client systems. What practitioners actually do is maintain a clean project carbon ledger inside their own system, then export the figures into whatever template the client wants this month. The CERT spreadsheet changes. The ISCA evidence pack stays the same.

The verifier conversation three months later

This is where most project carbon programs come unstuck.

The ISCA verifier visits in March for a project that submitted its annual evidence pack in December. The verifier picks ten line items from the carbon spreadsheet, more or less at random, and asks for the source document for each one. Concrete delivery on 14 August, 8.5 m³ of N40, where is the docket? Diesel volume in September of 142,000 litres, show me the refueller dockets that sum to that.

If those documents live in a site supervisor's email inbox, a contracts admin's network drive, the head office sustainability folder and a finance system, you have a problem. Not necessarily a credit-losing problem, but a problem that consumes 40-60 hours of someone's week to resolve.

A project carbon system that's worth using has to do three things on day one of the job:

Capture the source document, not just the number
Link the number back to the source document with a permanent reference
Lock the period once it's reported, so re-runs don't accidentally change historical figures

Carbonly's source document tracking was built specifically for this verifier conversation. Every emission line item has a "view source" link back to the original PDF or scanned docket. Period locking sits behind a six-role RBAC so the project engineer can't accidentally re-process August after it's been signed off.

How project data feeds corporate NGER and AASB S2

This is the second place practitioners get burned. The project sustainability advisor reports to the ISCA verifier in one set of numbers. The corporate NGER team reports to the Clean Energy Regulator in another. The CFO discloses to investors under AASB S2 in a third. If those three numbers aren't traceable to the same underlying activity data, you have a dual-framework reporting problem.

The aggregation pattern that works:

Project layer: each project (named after the job, e.g. "M1 Pacific Motorway Upgrade Stage 4") holds its own activity data and emission factors
JV layer: where the project is a joint venture, allocation is applied (operational control, financial control, or equity share depending on which arrangement governs)
Head contractor layer: roll-up of all projects under operational control feeds the head contractor's NGER inventory
Corporate disclosure layer: same roll-up, plus office and corporate fleet emissions, feeds the AASB S2 disclosure with assurance

The head contractor 50-site reporting workflow walks through this aggregation in more detail. Carbonly's JV consolidation handles the operational/financial/equity share toggle so the same project data set produces the correct number for each parent's books.

AR5 vs AR6 on the same project

Here's a technical wrinkle that catches a lot of project teams.

NGER currently uses AR5 GWP values (CH4 = 28, N2O = 265). AASB S2 requires AR6 GWP values (CH4 = 27.9 for non-fossil, 29.8 for fossil; N2O = 273). For a project where the dominant Scope 1 source is diesel, the AR5/AR6 difference is small enough to almost ignore. CO2 from diesel combustion dominates the CO2-e and the methane and N2O components are tiny.

But for a tunnel job with significant refrigerant losses on chillers, or a project with biogenic methane emissions from organic-laden spoil, the same project's emissions inventory can vary by single-digit percentages depending on which GWP set is applied. The ISCA verifier wants the AR5 number to align with NGER. The CFO wants the AR6 number for AASB S2.

The AASB issued AASB S2025-1 in December 2025 providing jurisdictional relief so that NGER reporters can use AR5 GWPs in their AASB S2 disclosure for the NGER-covered portions of their inventory. That removes some of the friction, but only for the parts of the corporate inventory that overlap NGER. Project-only data outside the NGER boundary still needs AR6 for AASB S2 purposes.

Carbonly stores activity data raw (litres, m³, tonnes, kWh) and applies the GWP set at report-generation time. The same project ledger produces an NGER-compliant report under AR5 and an AASB S2 disclosure under AR6 from one data set. We're not aware of any other Australian product that does this cleanly. We'd be happy to be wrong about that.

What we actually built for civil contractors

We'll be honest about what's in the product and what isn't.

Built and working. Project-specific email ingestion (every project gets a unique email address, so the site supervisor or fuel supplier can forward dockets directly into the project's emission ledger). OneDrive and SharePoint folder-per-project sync. Document AI extraction across PDF, Word, PowerPoint, Excel, CSV, RTF, image and scanned formats. Five-tier material matching against the NGA library, EPD Australasia preferencing, and custom factor libraries. JV consolidation under operational, financial or equity share. Period locking. Seven-year audit trail. Supplier portal where subcontractors log in with a separate role to submit their diesel returns directly. Six-role RBAC. Anomaly detection that flags the diesel volume that doesn't match the AdBlue purchase. Source document linking on every emission record. AR5 and AR6 GWP toggle at report time. Carbonly Co-Pilot natural language assistant so the sustainability advisor can ask "what was August diesel on the Western package" and get a number with the source dockets attached.

Connecting your AI assistant directly to the project's live emission ledger. Practitioners on civil jobs are already using ChatGPT, Claude and agentic workflows for routine work. We've built a way to plug those assistants directly into the project's emission data so an AI agent can answer "show me all concrete deliveries to chainage 4500-5500 above 30 m³" without anyone running an export first. Same audit trail, same RBAC.

What we don't have. Direct push integration with the ISCA IS rating tool. Direct integration with TfNSW CERT. Built-in PCAF financed emissions engine. NABERS, CBAM or ESRS modules. If you need any of those, we'll be upfront about it.

Where the quantity-based extraction differentiator actually matters

Most carbon software defaults to spend-based emissions for materials and subcontractor data because it can't read the physical quantity off a supplier invoice. Spend-based for civil materials produces nonsense numbers. The same dollar of concrete buys very different volumes depending on the strength grade. The same dollar of fuel buys different litres depending on whether it's a bulk delivery or a forecourt fill.

Carbonly's AI document engine reads the actual m³, tonnes and litres off the docket. That's the entire point. ISCA Mat-1 credits require quantity-based footprinting for significant materials. CERT requires quantity-based reporting on the design carbon estimate. You can't get there with spend.

If you're working alongside a sustainability consultant on the IS rating submission (most contractors do), the consultant is going to be much faster when the underlying data is already in quantities with source documents attached. Our experience is that consultants who've used Carbonly on one job tend to ask for it on the next. They're buyers, not competitors. They want the data hygiene problem solved so they can focus on the strategy and credit narrative work.

Where this still gets hard

We're not pretending project carbon reporting is a solved problem. A few things remain genuinely difficult.

Dry-hire plant fuel data is messy unless the hire contract requires it. The cleanest fix is in procurement, not in the carbon system. Subcontractor data quality varies enormously, and the supplier portal helps but it doesn't force a subcontractor to keep good records. And the boundary question between "project Scope 1" and "head contractor Scope 1" gets blurry when the same fleet asset moves between projects mid-month.

We're still working out the cleanest way to handle mid-project boundary shifts on long-running JV packages, particularly where the equity share changes after a partner buy-out. The accounting works. The audit narrative is the hard part.

What to do next week

Pick one project. Get the next quarter of fuel dockets, concrete dockets and subcontractor returns flowing into a single ledger with source documents attached. Lock the period when you report it. Then run the same numbers through both an AR5 and AR6 lens so you can see what the gap will be when the corporate AASB S2 disclosure lands.

That's the test. If the system can survive a verifier picking ten random line items from a quarter of activity, it'll survive the rest of the job.

Project-Level Carbon Reporting for Australian Civil Contractors: From Fuel Docket to ISCA Submission