Seven principles now anchor your compliance program

If you read one chapter of the Template for Compliance Programs, make it Chapter 2. The compliance principles have always been the philosophical core of the Template — but they've now been rebuilt and given a much clearer job: every compliance program should be consistent with them, and any deviation from the Template must be justified against them.

Here's the full set, in plain language:

1. Balance risk against cost. Testing and monitoring regimes should weigh the cost of compliance activities against the risk of non-compliance and its impact on power system security.

2. Continuous plant monitoring is preferred where practicable — but not mandatory. If you don't monitor continuously, you must document why and put alternative regimes in place that give reasonable assurance. (New. This one deserves its own post — it's next in the series.)

3. Testing frequency should be proportional to the risk of non-compliance. More drift, more risk, more testing.

4. Programs must provide reasonable assurance of ongoing compliance. Active use and implementation, reviewed and updated periodically.

5. The impact of plant changes on compliance must be assessed. (New as a standalone principle.) Hardware mods, equipment swaps, software and firmware updates — each needs a prompt assessment of its compliance impact, including whether models and data held by AEMO and the NSP need updating.

6. Programs must align with good electricity industry practice. The Template sets objectives and outcomes; you exercise diligence in the detailed methods.

7. Variations from the Template must be consistent with the compliance principles. (New.) Deviating is allowed — but the deviation must be documented, with reasons, having regard to these principles.

The 2019 Template had ten principles. The 2026 Template has seven, and four of them use "must". That isn't just consolidation. The 2019 principles read as design rationale — the Panel explaining why the Template is shaped the way it is. The 2026 principles read as obligations, addressed to you.

Three of the seven are new, and they're the ones to sit with. Principle 2 makes continuous monitoring the stated preference — monitor, or explain why not. Principle 5 formally recognises something power systems engineers have known for years: in an inverter-dominated fleet, a firmware update can change plant behaviour as materially as a hardware replacement. Principle 7 closes the loop on flexibility — the Template has never been an exhaustive checklist, but now every departure from it needs documented reasoning anchored back to the principles.

Together, those three convert things that were previously matters of engineering judgement — whether to monitor continuously, how to treat a firmware update, how far you can vary from the Template — into things you have to be able to evidence.

And three 2019 principles have no direct successor. Old #7 (event analysis in lieu of a performance test) and old #8 (a range of methods where direct testing isn't possible) have been absorbed into the tables and the event definitions — the substance survives, it just lives somewhere more useful. Old #9 is the one worth noticing: the statement that a Generator is accountable only for its own plant, and for settings approved by AEMO or the TNSP, now appears as a note inside the Table A.13 methods rather than as a governing principle of the framework. It still applies. It just isn't a principle any more.

Why does this matter for your GCP update? Because the AER's technical compliance audits assess whether your program is consistent with the Template, follows good electricity industry practice, is current with Template amendments, and provides reasonable assurance of ongoing compliance. The principles are now the clearest articulation of what "consistent" means. A program drafted once and shelved will struggle against Principle 4. A program with no plant-change process will struggle against Principle 5. A program full of undocumented workarounds will struggle against Principle 7.

Our approach when we review a GCP is to test it against each principle in turn — a fast, honest diagnostic of whether a program describes compliance or delivers it. The update window is the right time to run that test on yours.

Want a second pair of eyes across your program against the seven principles? Let's discuss.

Q: Which compliance principles are new in the 2026 Template?

A: Three. Principle 2 states that continuous plant monitoring is preferred where practicable but not mandatory — where it isn't implemented, the reasons must be documented and alternatives providing reasonable assurance put in place. Principle 5 requires prompt assessment of the compliance impact of plant changes, including software and firmware updates. Principle 7 requires that any variation from the Template is consistent with the compliance principles and documented with reasons.

Q: How many compliance principles are in the 2026 Template?

A: Seven, down from ten in the 2019 Template. Four of the seven use "must". Three 2019 principles have no direct successor — the substance of two now sits inside the compliance tables and event definitions, and the third appears as a note within the Table A.13 methods.

Q: Can a compliance program deviate from the Template?

A: Yes — the Template is not an exhaustive checklist. However, deviations must be consistent with the compliance principles and the reasons must be documented, per Principle 7.

Q: What does the AER check in a technical compliance audit?

A: Whether the program is consistent with the Template, follows good electricity industry practice, is current with Template amendments, and provides reasonable assurance of ongoing compliance.