A record-reading method for public NSW development-application data. It does not infer approval likelihood, construction or feasibility.
Direct answer
A NSW development-application map can show nearby lodgements and determinations, but each marker is an application record, not proof of approval, construction, feasibility or future supply. Filter by place, date, development type and status, then open the source record and keep its application identifier and currency with every observation.
A map marker becomes evidence only when its cohort and source record travel with it
Define the study area, preserve the active filters, open the application record and keep the interpretation limit beside the result.
- Define the cohort
Set the site or study area, distance rule, period and question before counting markers.
- Preserve the filters
Record the place, date, development type, status and map extent that shaped the visible result.
- Open the source record
Retain application identifiers, council, description, dates, status, source URL and checked date.
- Bound the interpretation
Treat the record as application evidence, not proof of approval, construction, feasibility or future supply.
Start with the decision the map needs to support
Define the site or study area and the question. A due-diligence check may look for nearby proposals that warrant review. A research task may compare lodging or determination patterns across councils. Those tasks need different radii, periods and denominators.
Do not begin by counting every visible marker. The map extent and active filters can change the apparent pattern.
Use the official tracker and source record
The NSW Planning Portal Application Tracker allows searches by fields including project, council, address, date, development type and status. It also directs users to council-managed trackers where the expected information is not found.
For each retained result, record:
- the application and Planning Portal identifiers;
- address or mapped location;
- council and application type;
- lodgement, determination and status dates where available;
- the displayed development description; and
- the source URL and checked date.
Status labels are not interchangeable
Lodged, under assessment, determined, approved, refused and withdrawn describe different stages or outcomes. Keep the source label rather than collapsing records into "active" or "development" without a defined rule.
An approval still does not prove that work started or finished. Construction and occupancy require separate evidence.
Coverage changes across time and systems
The NSW Online DA Data API record states that the public feed covers applications lodged through the Planning Portal since January 2019. It also notes that records may be missing before councils were mandated to use the Portal from 1 July 2021.
Council systems, amended applications and historical records can add further gaps. State the period and coverage caveat beside any count or trend.
Nearby applications need a defined distance rule
Record whether "nearby" means a fixed radius, adjoining parcels, a street, suburb, local government area or another boundary. Distances calculated from a point are different from parcel-to-parcel proximity.
A nearby application may be relevant context. It does not establish the same planning controls, impacts or likely outcome for the subject site.
A map-reading checklist
Development-application map-reading checklist
A Plynth-authored checklist for retaining the cohort, record identity and interpretation limit behind a mapped DA observation.
| Check | Why it matters |
|---|---|
| Study area | Defines which records can enter the result |
| Filters | Makes the visible cohort reproducible |
| Application identity | Prevents duplicate or amended records being merged blindly |
| Status and dates | Separates pipeline stages and time periods |
| Source coverage | Exposes council and historical gaps |
| Interpretation limit | Stops the map becoming an approval or supply forecast |
Plynth product boundary
Plynth's public proposition includes NSW development-activity analysis. This guide explains the official tracker and its public-data limits; it does not claim that Plynth exposes every official field or council record. It also makes no completeness, real-time, national-coverage or approval-prediction claim.
Official sources
Start with the NSW Planning Portal Application Tracker and its Online DA Data API record. For broader method selection, see planning data analysis use cases.