Infrastructure Sustainability Council Ratings: How Carbon Data Drives the Score

If you're tendering for a major Australian infrastructure project (rail, road, water, energy, ports, airports) above roughly $100m in 2026, the client almost certainly requires a target IS rating. State governments mandate it. Federal infrastructure agencies mandate it. The Infrastructure Sustainability Council's IS rating scheme is the de facto sustainability scoring standard for infrastructure across Australia and New Zealand.

The energy and carbon category typically accounts for 10 to 15% of the total IS score, depending on the rating tool version and the specific project. That makes carbon the second-highest weighted category after stakeholder engagement in most projects. Getting the carbon evidence right is the difference between a "Commended" rating (which most clients will accept) and an "Excellent" or "Leading" rating (which earns the bonus points written into many head contractor agreements).

For head contractors on major projects working through IS ratings, the carbon evidence pack is the part that's hardest to assemble. The data has to flow continuously across project phases that are run by different teams using different systems.

The four IS rating tools and where carbon sits

The IS rating scheme has four tools, applied at different project stages:

Tool	Stage	Carbon Focus
IS Planning	Pre-design	Strategic emissions assessment
IS Design	Detailed design	Designed-in carbon reduction
IS As-Built	Construction completion	Verified construction emissions
IS Operations	In-service	Operational emissions performance

The IS v2.1 Design and As-Built rating is the most commonly applied tool. The energy and carbon credit (Ene-1 to Ene-3, depending on version) is where most points are won and lost.

The credit structure typically rewards:

• Modelled emissions reduction vs reference design: Quantified reduction in design-stage emissions modelling
• Embodied carbon measurement and reduction: Material-by-material carbon accounting
• Operational energy performance: Predicted operational emissions performance
• Renewable energy integration: Onsite or contracted renewable supply

Each sub-credit has documentation requirements. The verifier (typically an ISC-accredited assessor) wants to see the methodology, the inputs, the calculations, and the assumptions.

The data flow that breaks projects

Here's the pattern we see on infrastructure projects of $200m to $2bn scale:

The planning team commissions an emissions assessment from a sustainability consultant, who delivers a model in a custom Excel workbook. The model goes into the planning IS submission and then sits on a shared drive.

The design team picks up the project and runs detailed design. The design-stage emissions model is rebuilt from scratch by a different consultant, often with different assumptions and different boundaries. The IS Design rating submission uses the new model. The reconciliation between planning and design assumptions is patchy.

The construction team starts on site. Diesel consumption, concrete pours, steel deliveries, electricity use, and waste flows all generate real-world emissions data. Most of this data lives in supplier invoices, fuel dockets, and material delivery dockets. The construction emissions data does not flow into the design-stage model. It sits in a separate spreadsheet maintained by the site's environmental team.

The IS As-Built submission requires verified construction emissions to be compared against the design-stage modelled emissions. At this point someone realises the categories don't match, the boundaries are different, and the data has to be retrospectively reconciled. This typically takes months and burns budget.

The operations phase, when applicable, starts with no emissions baseline tied to design intent. The operational team runs its own meter-based monitoring. The connection back to the IS Operations rating is essentially a fresh start.

This isn't a hypothetical pattern. It's what happens by default unless someone designs the data flow up front.

What an IS-ready emissions ledger looks like

The pattern that works on major projects:

1. Single project emissions ledger from planning onwards. Same data structure across phases. Different teams contribute different inputs but everything lands in one place.
2. Material library mapping to project bill of quantities. Concrete grades, reinforcing steel grades, asphalt, pipe materials, structural steel - each tied to an emission factor with EPD evidence where available. We've covered embodied carbon measurement in detail.
3. Construction-phase data ingestion via supplier invoices. Fuel cards, electricity bills, concrete delivery dockets, material take-offs all flow through the document engine continuously. Not assembled at the end of the project.
4. Phase-by-phase verification against the reference design. The IS rating submission compares each phase's actual emissions to the modelled emissions, with reasons for any divergence.
5. Operations handover including the emissions baseline. The operations team inherits the data lineage rather than starting fresh.

This is the same data discipline we describe for head contractors managing 50 sites. For infrastructure megaprojects the scale is different (one project, many phases) but the underlying problem is the same: continuous emissions accounting through a complex delivery structure.

The Scope 3 wrinkle on infrastructure projects

IS rating submissions typically include Scope 1 (construction equipment, site fleet, fuel combustion), Scope 2 (purchased electricity for site offices and temporary construction power), and parts of Scope 3 (especially Category 1 purchased goods, primarily concrete and steel; and Category 2 capital goods, where applicable).

The Scope 3 boundary on infrastructure is where most projects get fuzzy. The IS Materials credit (typically Mat-1 to Mat-3) requires embodied carbon accounting for major materials, which is essentially Scope 3 Category 1 in GHG Protocol terms. The boundary is usually drawn at the cradle-to-gate point: emissions from raw material extraction through to delivery at the project site, but not the construction process itself (which sits in Scope 1 of the head contractor).

This boundary works for IS rating purposes but doesn't match the head contractor's AASB S2 group disclosure. The head contractor's group Scope 3 Category 1 includes more than just project-specific materials. The IS rating submission has to extract the project-specific subset from the group total without double-counting.

Where the points actually come from

On IS-rated projects, the largest single source of awarded points in the Energy and Carbon category tends to be:

• Modelled embodied carbon reduction below a reference benchmark. Achieved through cement substitution (fly ash, slag), low-carbon concrete mixes, and material take-off optimisation.
• Construction-phase fuel reduction. Achieved through equipment scheduling, idle reduction, and use of biodiesel or HVO blends.
• Operational energy performance modelling. Predicted operational emissions vs a reference design.
• Renewable energy supply during construction. Behind-the-meter solar at site offices, plus PPA-backed grid supply.

Each requires different evidence. Modelled embodied carbon reduction needs Environmental Product Declarations from material suppliers. Construction fuel reduction needs fuel data with timestamps. Operational modelling needs performance simulation outputs. Renewable supply needs LGC surrender records or PPA contracts.

The verifier checks each evidence trail. Missing evidence means lost points.

The relationship between IS, NABERS, and Green Star

For projects that include buildings (rail stations, water treatment plants, road maintenance facilities), the IS rating overlaps with Green Star Buildings v1.1 and potentially NABERS Energy. Different rating tools for different scopes:

• IS: Whole-of-asset infrastructure (linear and non-linear)
• Green Star Buildings: Building components within an infrastructure project
• NABERS Energy: Operational energy performance of building components

A rail station building inside a rail project might earn Green Star credits for the building, NABERS Energy stars once operational, and IS credits for the project as a whole. The carbon data feeding all three should be consistent. In practice it often isn't, because the three rating processes are run by different consultants using different tools.

The pattern that works: feed all three from the same project-level emissions ledger, with the data tagged at the asset level so the building portion can be sliced out for Green Star and NABERS without recalculating from scratch.

What changes if your project is funded by a green bond

Many recent Australian infrastructure projects have been financed through green or sustainability-linked bonds, often issued under the Climate Bonds Standard. Green bond proceeds have to be allocated to eligible green projects and reported on annually with quantified environmental impact.

The reporting requirement on a green bond-funded infrastructure project is essentially the same as an IS rating submission, with one key difference: the bondholders typically want quantified avoided emissions versus a counterfactual scenario. This is a forward-looking number rather than a measured one, and the methodology has to be defensible.

The data discipline that supports IS rating evidence also supports green bond impact reporting, provided the project's emissions baseline and the counterfactual scenario are properly documented at financial close.

Practical sequence for a head contractor on an IS project

If you're a head contractor about to mobilise on an IS-rated project:

1. Get the IS rating tool in front of the sustainability lead and the project director early. The credit requirements drive the data plan.
2. Define the emissions ledger structure before site setup. Same structure for the next 3 to 5 years.
3. Set up the supplier data flows. Fuel cards, concrete suppliers, steel suppliers, electricity retailers all feeding the ledger continuously.
4. Tag every input with phase, scope, and credit alignment. Some inputs serve multiple credits.
5. Run quarterly internal reviews against the design-stage model. Find divergences early.
6. Pre-engage the IS verifier. Walk them through the data flow before the As-Built submission so there are no surprises.

The pattern is similar to 50-site emissions reporting workflows in head contractor environments, just more concentrated on an IS megaproject. One project, more data per project, longer time horizon.

The bottom line

IS ratings reward sustained data discipline, not heroic year-end reporting efforts. The projects that achieve "Excellent" or "Leading" ratings tend to have continuous emissions accounting flowing through every phase. The projects that come in at "Commended" tend to have spent the budget on consultants reconciling data that should have been reconciled along the way.

If you're a head contractor working on an IS-rated infrastructure project and your emissions data is currently a mix of consultant deliverables, site spreadsheets, and SAP exports that never line up, email hello@carbonly.ai or join the waitlist. The system that produces a clean As-Built submission is the same system that produces clean NGER and AASB S2 disclosures, all from one source of truth.