128 councils, zero APIs: why NSW planning compliance is so hard
The NSW Planning Portal gives you zoning and LEP standards for any address in the state. But the controls that drive most compliance decisions — DCP setbacks, parking rates, landscaping requirements, precinct-specific rules — are published by 128 individual councils in formats ranging from 400-page PDFs to unstandardised web pages. There are no APIs. There is no common schema. And every council updates on its own schedule.
NSW planning data — what is digital vs what is not
LEP (Local Environmental Plan)
Source: NSW Planning Portal — Format: Standardised (Standard Instrument)
Zoning, lot sizes, height limits, FSR
SEPP (State Environmental Planning Policies)
Source: NSW Planning Portal — Format: Standardised (state-level)
Housing Code, exempt/complying, transport corridors
DCP (Development Control Plan)
Source: 128 individual councils — Format: No standard — varies by council
Setbacks, landscaping, parking, design, precinct controls
Section 7.11/7.12 contributions
Source: Individual councils — Format: PDF schedules, some with calculators
Infrastructure contributions, rates, thresholds
Council-specific overlays
Source: Council GIS (where available) — Format: ArcGIS, MapInfo, or none
Heritage, flood, DCP precinct maps, character areas
The two layers with APIs (LEP and SEPP) cover zoning and state-level rules. The three layers without APIs (DCP, contributions, overlays) contain the site-specific controls that drive most compliance decisions.
What the Planning Portal does well
Credit where it is due. The NSW Planning Portal is one of the better state-level planning systems in Australia. It provides:
- Zoning data for every lot in the state, with permitted and prohibited uses derived from the Standard Instrument LEP
- LEP development standards — maximum building height, floor space ratio, minimum lot size — as mapped spatial layers
- SEPP provisions including the Housing Code, exempt and complying development criteria, and transport corridor overlays
- Heritage and environmental overlays — state and local heritage listings, acid sulfate soils, some biodiversity layers
- Section 10.7 data for planning certificates, referenced by conveyancers across the state
The Portal's spatial API (layerintersect) allows programmatic queries against these layers. For LEP-level compliance questions — “what zone is this lot in?” or “what is the maximum height?” — the data is comprehensive, current, and machine-readable. This is genuinely good infrastructure.
What it does not cover
The gap is the Development Control Plan. Every council in NSW has a DCP (some have multiple), and the DCP is where most of the site-specific development controls live. The Planning Portal does not include DCP data. There is no state-level API, no common schema, and no requirement for councils to publish DCPs in any particular format.
NSW Planning Portal — what it covers vs what it does not
Available via Planning Portal
Not available — must check each council
The practical consequence: a planner checking compliance for a residential development needs the Planning Portal for zoning and LEP standards, then must separately find, download, and manually read the relevant council's DCP to determine setbacks, parking, landscaping, and design requirements. If the site falls within a DCP precinct, they need to identify the correct precinct — often from a PDF map — and find the precinct-specific controls, which may override the general DCP provisions.
For professionals who work across multiple councils, this is a daily frustration. For property buyers trying to understand what they can build, it is often an impenetrable barrier. PlotDetect's DCP browser and compliance assessment are built specifically to bridge this gap.
How councils publish DCPs
There is no standard format for a DCP. Each council chooses how to structure, publish, and update its development controls. The result is a landscape that resists automation at every turn.
How councils publish DCPs — five different approaches
Monolithic PDF
Single 400-page document, no internal hyperlinking
Examples: Common in regional councils
Sectioned PDFs
Separate PDFs per section (residential, commercial, precinct)
Examples: Inner West, Canterbury-Bankstown
Web-based with PDF maps
HTML provisions with linked PDF precinct maps
Examples: City of Sydney, North Sydney
Interactive GIS + PDF
Council GIS links spatial precincts to DCP provisions
Examples: Northern Beaches, Wollongong
Multiple concurrent DCPs
Pre-merger councils each retain separate DCPs
Examples: Inner West (3 former DCPs), Cumberland (2)
The merger problem compounds this. When NSW councils were amalgamated in 2016, many merged councils retained their pre-merger DCPs. Inner West Council, for example, operates under three former DCPs (Ashfield, Leichhardt, Marrickville) with different structures, numbering systems, and precinct definitions. A single property lookup requires knowing which former council area the address falls in before you can identify the correct DCP.
Updates add another dimension. Councils amend DCPs periodically, but there is no central notification system. A setback rule that was correct six months ago may have been amended without any programmatic way to detect the change.
The cost of manual compliance checking
Manual DCP compliance checking is slow, expensive, and error-prone. The costs are borne across the entire development pipeline:
Time
A planner checking DCP compliance for a medium-density residential project typically spends 4-8 hours on the DCP alone — finding the document, identifying the correct precinct, cross-referencing general and precinct-specific controls, and documenting the applicable standards. Across hundreds of DAs per council per year, this adds up to thousands of professional hours spent reading PDFs.
Errors
Manual processes produce inconsistent results. Two planners reading the same DCP for the same site may identify different applicable controls — especially where precinct boundaries are ambiguous or where general provisions interact with precinct-specific overrides. These errors surface as assessment delays, requests for additional information, or incorrect compliance advice.
Inconsistency across councils
A developer working across three councils must learn three different DCP structures, three different precinct systems, and three different sets of terminology for equivalent controls. Side setbacks might be called “side boundary setbacks,” “side setbacks,” “lateral setbacks,” or “building separation” depending on the council. There is no common vocabulary.
Progress so far
The situation is not entirely static. Two developments are moving in the right direction:
ePlanning spatial layers
The NSW ePlanning program has published ArcGIS MapServer endpoints for various planning spatial layers, including some development control overlays. These are publicly accessible without authentication. Coverage is growing, but the data is primarily spatial (boundaries, zones) rather than the textual development controls within those boundaries.
Council GIS portals
Some councils have invested in interactive GIS portals that link spatial precincts to DCP provisions. Northern Beaches and Wollongong offer relatively good spatial interfaces. But these are council-by-council investments with no common standard, and many councils — particularly in regional NSW — have no GIS portal at all.
The gap between what is digitally available and what is needed for automated compliance remains large. LEP and SEPP data is well served. DCP data — the layer that contains the controls most relevant to actual building design — remains overwhelmingly analogue.
What digital planning could look like
A fully digital planning system would mean a planner, developer, or property buyer could enter an address and receive every applicable development control — LEP, SEPP, and DCP — in a structured, machine-readable format. The controls would be spatially linked to the correct precinct, current as of the latest amendment, and consistent in terminology across councils.
This is not a technology problem. The technology to extract, structure, and serve this data exists today. The barriers are institutional: 128 councils with independent publishing practices, no mandate for digital-first DCP publication, and no common data standard for development controls.
Until the institutional barriers are resolved, the gap between state-level digital planning infrastructure and local-level development controls will persist. Bridging that gap — making DCP controls as accessible as LEP zoning data — is one of the most consequential challenges in NSW planning technology.
See what applies to your address
PlotDetect brings LEP, SEPP, and DCP controls together for NSW addresses. Browse DCP provisions by council, or run a compliance check for a specific site.