How to check development applications near a property

Use the official tracker first, then the council register the state page itself says you still need. Write the gap the host publishes.

Planning is a state and territory matter in Australia, administered largely by councils. The names differ: development application in New South Wales, Queensland and the ACT; planning permit in Victoria and Tasmania; development approval in South Australia and Western Australia; development permit in the Northern Territory. The schemes, portals and assessment paths differ too. Always use the scheme and portal for the council and state where the property sits.

For every application that could touch the lot, write description, dwelling count or floor area if stated, status, lodgement and decision dates, and the distance and direction from this parcel. Open the decision notice for approvals. Conditions and staging tell you what is actually permitted.

State-assessed, ministerial, DAP and major projects often sit on a different list from the council tracker. If you only search one list you will miss the largest buildings.

Lodged or on exhibition: a proposal that may be approved, refused, amended or withdrawn. Approved: permitted, usually with conditions and a lapse date, not necessarily commenced. Under construction: disruption now. Completed: already in the street. The same description means different things at each stage. See this lot’s history for the same anatomy on one parcel.

Pick the distance after you know the project type. Adjoining and opposite: overshadowing, privacy, outlook, construction noise, party-wall or fence works. The same street or the next intersection: traffic, parking, character. A wider suburb or corridor: competing supply of comparable dwellings, retail, a new school or a station precinct.

A two-lot subdivision next door is a different search from a 200-dwelling build-to-rent four blocks away. Using one metre figure for both hides one of those effects. Districts’ nearby pipeline uses a product radius and also stores 200 m, 400 m, 800 m and 2 km counts where the register is loaded. That is a software default, documented on how to use the nearby pipeline. It is not a planning rule and not a reason to ignore a project that sits just outside the default.

• Searching only this street name and missing the parallel street behind the rear fence.
• Treating Victoria or a Queensland council as if a statewide register existed.
• Using DAMS or a court list as the local DA pipeline.
• Counting each stage of a staged approval as a separate project.
• Reading an empty Districts pipeline as “nothing planned” when the register was never loaded for that council.

It does not tell you the project will be built, when, or in that form. It does not model overshadowing. It does not include most infrastructure projects, which live on agency pages. See catalyst claims. Coverage limits above are content: a five-year ACT window, a 2014 WA DAP start, a 31 July 2020 SA cutoff are gaps, not clean bills.

Where an adapter exists, Districts queries applications within its product radius of the official parcel, groups applications on the same site into one project, and shows status, distance and a source link. Grouping is a Districts-derived indicator. An empty result after a completed query means no applications in the loaded extract within that radius. A missing register is unknown. The development activity methodology states the rules.

1. Re-run the jurisdiction workflow in the table on the day you act.
2. Open the decision notice and the plans for anything adjoining.
3. Check the second list (minister, DAP, SARA, major projects) for large buildings.
4. Ask council planning staff for commencement if the file is approved and silent.