Seven Lessons From a Live Subdivision DA in Sydney.

Midway through the DA programme, the environmental consultant called with the sentence nobody wants: asbestos fragments identified in surface soils, across multiple areas, including outside the footprints of any former structures. The finding triggered a Detailed Site Investigation, a four-week reporting cycle, and a remediation scope that had to be priced into the project then and there.

The lesson is sequencing. Environmental and geotechnical investigations are routinely commissioned late because they feel like checklist items for lodgement. They are actually the reports most capable of changing the project, scope, cost and even viability. Commission them first, before the design is locked and while the findings can still shape the layout and budget at the lowest cost.

The geotechnical report classified lots affected by grouped mature trees as Class P, problem sites, and recommended complete removal of the trees and their root systems to achieve a better classification. The arborist and ecologist, assessing the same trees, were working to retain as many as possible. Both positions were professionally correct from inside their own disciplines. Lodged together, unreconciled, they would have handed council a ready-made refusal reason.

The resolution took weeks of managed correspondence: specific written questions to the geotech about reclassification pathways, an overlay exercise proving which trees genuinely conflicted with roads and earthworks, and cut/fill evidence that retention was impossible where it was impossible. No consultant does that reconciliation for you. It is the development manager’s core function, and it has to happen before lodgement, because afterwards it happens through RFIs at council speed.

Following the arborist’s assessment, the subdivision plans needed indicative building envelopes overlaid on every lot, a modest piece of drafting from the civil designer, quoted at a couple of thousand dollars. Trivial money. But the envelopes fed the arborist’s impact assessment, which fed the ecology report, which fed the DA package: the cheapest variation on the project was, for a fortnight, the only thing standing between the team and lodgement.

Two practices keep this from hurting. First, ask "what does this block downstream?" of every variation, and fast-track the ones with dependencies regardless of their dollar value. Second, agree a variation approval protocol with your client at engagement, a defined turnaround for decisions under an agreed threshold, because the variation itself took days; an unmanaged approval loop could have taken weeks.

A subdivision DA is a stack of documents written by different firms over different months: civil plans, survey, geotech, environmental, arborist, ecology, stormwater, the Statement of Environmental Effects on top. Council assesses them as one proposal, and every inconsistency between them becomes a question, and every question becomes weeks.

On this project, the draft biodiversity report was circulated to the civil designer and planner specifically to be checked against the engineering set and the SEE before lodgement, tree retention numbers, envelope positions, earthwork extents, all cross-referenced. The lodgement-readiness test is simple to state and laborious to pass: could a stranger read every document in the package and find no two of them disagreeing? Until the answer is yes, you are not ready.

The electrical authority’s certified network design arrived on its own schedule, months into the programme, and the moment it landed it had to be checked against the civil layout for clashes with driveway positions, lot boundaries and pillar locations, because a certified design that conflicts with your subdivision geometry is a problem someone has to own quickly.

Utility and authority designs behave like long-lead procurement items: applications in early, progress chased in writing at a fixed cadence, and a same-week clash review whenever a certified issue lands. The authorities are not slow out of malice; they simply run programmes you do not control. What you control is how early they start and how fast you respond to what they produce.

Twice during this DA, consultant invoices aged past due while reports sat in production, overdue accounts with the civil designer and the geotechnical firm, each chased politely and each escalated to the client for same-week payment. No consultant works at full speed for a client whose invoices are sixty days old, and on one occasion an invoice misdirected to the wrong entity added its own loop of delay.

The development manager’s job includes treating accounts payable as programme protection: invoices logged on arrival, forwarded with a clear payment ask, chased to confirmation. It is unglamorous, and it is faster than discovering your BDAR is parked behind an unpaid bill.

The single biggest source of silent delay on this project was not council, weather or money. It was response latency: a report awaited from a consultant who was "going to call back", a question parked in someone’s voicemail, an approval sitting in an inbox. One critical environmental update spent a week in phone tag before a single written email, specific question, specific deadline, produced the answer in two days.

The discipline that fixes it costs nothing: every request in writing with a date on it, every open item on a tracked list reviewed weekly, every phone agreement confirmed by email the same day. Out-of-office replies, leave schedules and "I thought you had that" evaporate as excuses when the paper trail is current. Momentum on a DA is not given to you. It is manufactured, one chased email at a time.