Somewhere in your business there’s a slide with 10 June 2027 on it.
It might be in a board pack. It might be a milestone in a project plan, or the line that justified a budget submission back in August. Whoever built it did the sensible thing and lifted the date from a law firm update, a vendor webinar or a conference slide, because that’s where everyone got it.
That date isn’t in the Rules.
We went and read the instrument this week, which is a dull sentence with an interesting result. The Enhanced CIRMP Rules don’t contain a deadline. They don’t contain a single calendar date of any kind. What they contain is a clock, and for a good number of operators the clock didn’t start when you think it did.
What the instrument actually says
The Security of Critical Infrastructure Legislation Amendment (Enhanced Critical Infrastructure Risk Management Program) Rules 2026 is a short amending instrument. [1] It changes the principal CIRMP Rules and then, like most amending instruments, it’s spent. The Federal Register marks it “no longer in force”, which sounds alarming and isn’t. The amendments live in the principal Rules and they apply.
Its commencement provision, section 2, is one line in a table. The whole of the instrument commences “the day after this instrument is registered”. [1] No date. The explanatory statement records registration on 9 June 2026, so commencement is 10 June 2026. [2]
Then section 4A(6) does the work everyone has turned into a deadline. It doesn’t set dates either. It sets two grace periods during which specified provisions don’t apply. [1]
For section 6A and subsections 8A(2) and 9A(2), the period runs to “the end of the last day of the period of 12 months after the commencement of this instrument”.
For sections 8A other than 8A(2), 8B, 8C, 9A other than 9A(2), 10A and 11A, it’s twenty four months.
The instrument doesn’t give you a deadline. It gives you a stopwatch and tells you when to start it.
So 10 June 2027 is commencement plus twelve months. It’s arithmetic, not law. As shorthand it’s close enough for most purposes, and we’ll keep using it ourselves. But it breaks in two ways, and the second one is the one worth your time.
Break one: you don’t have one deadline, you have two
Read the two limbs again and notice they cover different provisions.
One set of obligations falls due twelve months after commencement. A different set falls due twenty four months after. They aren’t a staged rollout of the same thing. They’re different requirements on different clocks.
The explanatory statement says why the longer one is longer. The twenty four month period is “intended to provide adequate time” for responsible entities to have critical workers assessed under the new suitability provisions. [2] That’s a people process, and people processes take longer than documents, so the drafters gave it a year more.
If your plan has a single milestone in it, you’ve merged two scopes into one date. That’s survivable if the merged date is the earlier one, because you’ll be early on half of it. It’s expensive if it’s the later one, because you’ll be a year late on the other half and you’ll find out from a regulator.
Break two, and this is the one: the clock starts when the asset does
Here’s the limb almost nobody quotes.
For an asset that becomes a critical infrastructure asset on or after commencement, both periods run from the day the asset became one. [1] Not from 10 June 2026. From the day it was captured.
So the date depends on the asset, not on the entity, and not on the industry.
Think about what that means at a few real desks.
You’re at a generator that acquired a portfolio in March this year. Those assets came into your CIRMP scope on acquisition, not in June 2026. They have their own twelve and twenty four month clocks, and both run later than the ones on your existing fleet.
You’re at a water utility that commissioned new treatment capacity and crossed a threshold partway through the year. Same answer. That asset is on its own clock.
You’re at a business that found out in October that something you’d never thought of as critical infrastructure had been brought into scope. Your clock started in October.
None of those people are on 10 June 2027 for those assets. They’re all on a later date, and it’s a different later date each time.
A date that belongs to an asset can’t live in a board pack. It has to live next to the asset.
And there’s a carve-out at the other end that’s worth knowing about. Section 12 of the new Part 3 says the amendments don’t apply to an asset that was declared under section 51 of the Act before commencement, where that declaration is still in force. The explanatory statement adds that such an asset would need a new declaration to be caught by the enhanced obligations. [1][2]
That’s a small category. If you’re in it, it’s a very important small category.
Why we didn’t put a single date in the last one
Two weeks ago we wrote about what the updated CIRMP guidance asks for that the 2023 version didn’t. That post doesn’t contain one date, one framework name or one security profile. That was deliberate, and the reason was simple: we’d already had live copy go out carrying a date we couldn’t stand behind, so we stopped using dates until we’d read the instrument.
We’ve now read it. This is the result, and it’s less comfortable than the version we were avoiding. The honest position isn’t that the date was slightly wrong. It’s that there is no date, and the thing we were all quoting was somebody’s arithmetic passed along until it hardened.
Our own 2027 outlook page has been corrected this week on the back of it.
This is a register problem wearing a calendar’s clothes
Step back from CIRMP for a second, because the shape of this is familiar.
If you hold one captured asset, you have two dates and you can keep them in your head. If you hold nine, acquired and commissioned over four years, you have eighteen dates, and no two of them are the same. There is exactly one place a date like that can live and stay true, and it’s in a field next to the asset it belongs to.
We’ve made this argument before from the other direction. Your CPS 230 vendor register almost certainly stops one step too soon, because it records who the provider is and what they do, and not the two things that decide what happens when they fail. Same failure here. The asset register records what the asset is. It usually doesn’t record when it became captured, which is now the thing that determines what you owe and when.
That field costs nothing to add and it can’t be reconstructed later under pressure. Acquisition dates get fuzzy. Commissioning dates get argued about. “When did this become a critical infrastructure asset” is an easy question in the month it happens and a horrible one three years on with a regulator in the room.
Where BayRisk lands on this
Here’s our position, plainly.
Nothing above makes your obligation bigger. It makes it more specific, and specific is harder to fake than big.
A programme run off a calendar date treats compliance as an event. Everyone converges on a milestone, the evidence gets assembled in the weeks before it, and the date passes. A programme run off an asset register treats it as a property of the estate. Each asset carries its own status, its own dates and its own evidence, and the answer to “where are we” is available on any given day rather than in the fortnight before someone asks.
That second thing is harder to start and much easier to live with, and it’s the same argument we made about the guidance a fortnight ago. The regulator has stopped asking whether your programme is up to date and started asking whether it’s effective. Effectiveness is a property of an estate, not a document.
And it’s worth saying what this isn’t. It isn’t a reason to panic about a date you’ve missed, because for most existing assets the common reading of the twelve month period lands on 10 June 2027 and you’re fine. It’s a reason to check whether the dates you’re working to actually belong to the assets you hold. For a single-asset operator that’s a five minute job. For anyone who has bought, built or been captured since the middle of last year, it’s an afternoon, and it’s an afternoon that’s much cheaper now than it will be later.
If you want to work through which of your assets are on which clock, that’s a short conversation: hello@bayrisk.com.au.
References
- Security of Critical Infrastructure Legislation Amendment (Enhanced Critical Infrastructure Risk Management Program) Rules 2026 (LIN 26/075), F2026L00701, as made. Section 2 for commencement, section 4A(6) for the twelve and twenty four month grace periods and the limb running from the day an asset becomes a critical infrastructure asset, and section 12 of the new Part 3 for the section 51 declaration carve-out. Federal Register of Legislation. https://www.legislation.gov.au/F2026L00701/asmade
- Explanatory Statement to the Security of Critical Infrastructure Legislation Amendment (Enhanced Critical Infrastructure Risk Management Program) Rules 2026, F2026L00701. For the registration date of 9 June 2026, the stated purpose of the twenty four month period in relation to critical worker suitability assessments, and the position on assets declared under section 51 before commencement. Federal Register of Legislation. https://www.legislation.gov.au/F2026L00701/asmade
- Security of Critical Infrastructure Act 2018 (Cth), subsection 30AB(3), under which the grace period provision operates.
- Security of Critical Infrastructure (Critical Infrastructure Risk Management Program) Rules (LIN 23/006), the principal instrument amended by F2026L00701, in which the amended obligations sit.