Infrastructure Sustainability Council: a builder's take

The Fifth Estate has run a video interview with Toby Kent on big ambitions for the Infrastructure Sustainability Council, and if you build houses, decks or shop fitouts you probably scrolled straight past it. Fair enough. Infrastructure means tunnels, rail and water treatment, not a slab on a corner block in Craigieburn.

Read it anyway. Not for the tunnels, but for what comes downhill. The reporting that starts life on a rating scheme for a multi-billion dollar rail package has a habit of turning up, three or four contracts later, in a subbie's scope of works. By the time it reaches you it has stopped being a sustainability ambition and become a clause you have to price.

What the Infrastructure Sustainability Council actually does

The Infrastructure Sustainability Council is the industry body behind the IS rating scheme, the sustainability rating used across Australian and New Zealand infrastructure from planning through design, construction and operations. Think of it as a Green Star equivalent for civil work. Governments and asset owners write a target rating into the head contract, the head contractor has to evidence it, and evidence means data: what materials went in, where they came from, what happened to the waste, who was employed.

That is the mechanism worth understanding. A rating scheme does not regulate you. It changes what your client has to prove, and your client can only prove it with paperwork you supply.

The paperwork flows downhill, and it lands in your scope

If you have done any work on a government-funded job in the last few years you have already seen the early version of this. It usually shows up as some mix of:

Material declarations. Environmental Product Declarations, recycled content percentages, or a supplier letter confirming source. Concrete, steel and aggregate get asked about first.
Waste dockets by stream. Not one skip invoice for the job. Timber, concrete, plasterboard and general, weighed and separated, with the tip receipts to match.
Plant and fuel records. Hours run, litres burned, sometimes machine by machine.
Local and social procurement spend. Victoria's Social Procurement Framework and Local Jobs First policy are the obvious example, but every state has a version. It means naming your suppliers and their spend, and reporting apprentice or trainee hours.
A monthly return. Usually a spreadsheet in the head contractor's format, due on their date, not yours.

None of that is difficult. All of it takes time, and it is time that is invisible at quoting stage, because it does not look like work. It looks like admin you will do on a Sunday.

Price the reporting, do not donate it

Here is the builder-eye take. The scheme is not the problem. Unpriced compliance is the problem, and it is the same failure as unpriced variations: you agree to something small in a pre-start meeting and discover in month four that it costs you a day a month.

Do the sum properly before you sign. If a monthly return takes two hours, chasing supplier declarations takes another two, and separating and documenting waste adds an hour a week, you are looking at roughly ten hours a month. At any realistic charge-out rate that is real money over a six-month job, and it is money you have already given away if it is not in the price. Put it in as a line item, ex GST, described plainly as project reporting and compliance. Clients on rated jobs expect to see it. It is the ones who hide it in an overhead percentage who wear it.

The same goes for pricing the physical side. Four bins instead of one costs more in hire and in space on a tight site. Recycled content specifications can narrow your supplier list and lift your rate. Get those numbers from your suppliers at quoting time, not after you have won it. If your estimating is still living in a spreadsheet that gets copied job to job, this is the point where it starts costing you, and it is worth reading up on what good construction estimating software actually does with allowances like these.

Set the records up now, because they are the same records that protect you

The genuinely useful part: the habits this asks for are habits you should already have.

Photograph the docket at the bin, not at the end of the month. File supplier declarations against the job the day they arrive. Log crew hours against tasks as they happen. Keep site diaries with dates. That is the exact evidence trail that wins a delay claim, settles a defect argument, and survives an audit. Sustainability reporting is just the first client to ask for it out loud.

You already do this for the things the National Construction Code requires. Frame certificates against AS 1684 for residential timber framing, energy ratings under the NCC's Section J and NatHERS provisions for new homes, waterproofing sign-offs. The ABCB publishes the current NCC free online, and the discipline of keeping code evidence per job is the same discipline. Check the relevant state or territory site for the exact adoption dates and variations that apply where you build, because they differ.

If your job records still live across a ute glovebox, a phone camera roll and three group chats, this is the change that will finally break that. Getting them into one place per job is what construction project management software is for, and it is a much cheaper fix than losing a tender because you could not produce a year of waste data.

None of this is about caring more or less about sustainability. It is about noticing early that a policy conversation in Sydney becomes a reporting clause in your contract, and pricing it before you sign rather than after.

Built Simple is free to start, and the app is a free download on iOS and Android with all 45 calculators on board. Worth a look if you want your dockets, photos and job records in one spot before the next tender asks for them.