REGULATION DECODED
The Fast-Track Assumption: Why Confirming Comes Before Designing
CURRENT AS AT 22 SEPTEMBER 2026.
NSW COMPLYING DEVELOPMENT RULES ARE UNDER ACTIVE REFORM.
SEO/AI under the hood (amended per review actions 2 & R4): exact-match H1 restored per audit 2.1 – the personality line survives as the subhead · URL /services/certification/ per the audit keyword map · meta description: “Principal Certifier Appointment, Construction & Occupation Certificates and Complying Development (CDC) from one specialist, ISO 9001-certified team – approval to occupation.” (adopted from Option 1’s written set) · the “Quick Answer” block is deliberately extractable – it’s the sentence we want ChatGPT/Gemini/AI Overviews to quote · FAQPage + Service schema · 800+ words at full build · division-coded breadcrumb.
A pathway, not a preference
It’s easy to talk about complying development as though it’s one of two options on a menu: the fast one or the slow one. It isn’t. As the rules stand today, a CDC is available only where a proposal meets every applicable development standard, with no variations and no exercise of judgement by the certifier. Two things worth adding. Complying development isn’t only set by the Codes SEPP. An LEP can specify it too. And meeting every standard is necessary but not sufficient: separate provisions rule out complying development on certain land regardless of how compliant the proposal is, including environmentally sensitive land, foreshore areas and significantly contaminated land. Heritage conservation areas are also restricted, with narrow exceptions for things like a detached outbuilding or a swimming pool. A Development Application (DA), by contrast, is a merit assessment. The consent authority can weigh it up, ask for changes, and still approve something that doesn’t tick every box on paper.
That difference matters more than it sounds like it should. The standard, default position for any project is the DA pathway. The CDC pathway is the exception, carved out for the narrow slice of development that leaves nothing to merit assess because it already complies with everything that governs it. Nothing about a project’s size, budget or ambition earns it fast-track treatment. Only compliance does.
Why the fast-track exists at all
The CDC pathway exists to remove merit assessment where merit assessment isn’t needed, not to reward projects that want to move quickly. Once you see it that way, the mistake becomes obvious: designing toward CDC, or simply assuming a project will qualify, before anyone has actually checked it against the full rule set.
We see this across every project type and scale. A homeowner adding a second storey assumes complying development applies because a neighbour’s renovation went through that way. A developer designs a townhouse scheme around CDC provisions because the fee and timeframe look better on paper than a DA. In both cases, the assumption is doing work that only a proper check should be doing.
What it costs to get the order wrong
Get this wrong and there’s only one way back: the standard DA pathway, usually after time and money have already gone into a design built around assumptions that don’t hold. Worse, a design drawn to fit CDC provisions often isn’t a design that reads well under a DA’s merit assessment either, so the rework isn’t a simple resubmission. It can mean revisiting decisions that were locked in months earlier.
How we check it, and when
We check pathway eligibility at the concept stage, before a design is finalised, not after. That’s a deliberate sequence: confirm the rules first, then let the pathway shape the design, rather than the other way around. Send us your address and concept and we’ll tell you plainly which pathway you’re actually working with, and why.
Not sure which pathway applies?
Tell us your address and concept and we’ll tell you plainly.