A variation pathway for Complying Development Certificates (CDCs) is finally on the table, with the NSW Government’s Explanation of Intended Effect now on exhibition until 24 June.
At its core, this reform acknowledges the binary nature of the CDC system. A development either complies or it doesn’t. And when it doesn’t, even by the smallest margin, the only pathway is a full Development Application (DA), with all the time, cost and complexity that entails.
The proposed variation pathway is initially limited to the Housing Codes (not the Group Home, Industrial, Business or other Codes) and is limited to key standards such as height, setbacks, floor area, parking, and tree retention.
This is a pragmatic and necessary shift. In practice, minor technical breaches frequently have no perceptible impact but still trigger a DA. In many cases, the merit of a particular variation is abundantly clear and councils have no issue with it, yet the system still forces a full DA pathway.
This is the inefficiency the reform seeks to address.
So far, so good.
However, are we in danger of overengineering flexibility?
The Explanation of Intended Effect runs to around 40 pages, detailing how variations could be applied across different standards, with layered criteria and parameters for each. This is before the framework has even been expanded beyond the initial set of Codes and standards.
This creates a tension at the heart of the reform. If Councils are capable of determining the merit of a variation through a full DA process, why does this discretion need to be so prescribed in the variation process? More importantly, does this level of detail risk recreating the very problem the reform is trying to solve?
There is a real possibility that, rather than streamlining the process, we complicate it further.
In trying to manage every scenario, we may be undermining the objective of simplicity.
A more principles-based model would arguably better align with the intent of the reform.
For example, a variation pathway could be structured around a small number of clear, defensible thresholds:
Under such a framework, the role of council is straightforward: determine whether the variation is acceptable in context. If it is, the project proceeds efficiently. If not, the fallback remains a DA. Council retains discretion and their decision is not appealable until DA stage.
Importantly, this doesn’t dilute planning oversight. It simply right-sizes the process to the scale of the issue.
The success of this reform won’t be measured by how comprehensively it defines every edge case. It will be measured by whether it meaningfully reduces friction in the system, without compromising outcomes.
The question isn’t whether we need flexibility. That’s already been answered.
The real question is whether we can deliver it in a way that is genuinely simple, usable, and trusted by industry, Councils and the community.
At the moment, the intent is strong, but the execution needs work.
If you’re interested in understating how this pathway could impact your typical project type, reach out to Ian Cady or your existing Ratio contact.
