From planning permit to Statement of Compliance: the Victorian subdivision delivery arc

The Victorian sequence is broadly stable across councils and growth areas, even though every project experiences it as chaos. A permit issues under the Planning and Environment Act with conditions attached. The plan of subdivision is certified. Engineering design proceeds from functional layout to detailed design, collecting approvals from council and the servicing authorities. Works are tendered and constructed under council and authority oversight. Assets are inspected, accepted and handed over. Referral authorities consent, the council issues the Statement of Compliance under the Subdivision Act, and the plan is lodged for registration — at which point lots exist as titles and settlements can occur.

On the programme, “detailed design” looks like one bar. In reality it is several interleaved approval tracks: council engineering approval for roads and drainage within its remit, the drainage authority for trunk and overland flow in growth areas, and the water corporation’s acceptance process for sewer and reticulated water. Each track has its own submission standard, review clock and resubmission etiquette — and they reference each other, so a change forced by one reviewer can reopen another’s completed review.

The scheduling consequence is under-appreciated: the critical path through design is rarely the drafting time. It is the number of review cycles multiplied by the review period. A design team that gets through on submission two beats a faster-drafting team that needs submission four, every time. Which is why the functional layout stage matters more than its modest drawings suggest — it is the cheap place to surface the disagreement that would otherwise appear as a detailed design rejection, three months further in.

The permit condition register should be read against this network from day one. Conditions gating commencement decide which approvals must land before a contractor mobilises; conditions gating the Statement of Compliance decide which acceptances must be engineered into construction rather than left for close-out. Sorting the register by gate is the fastest reality check a delivery programme can get.

The site works of a subdivision are conventional civil construction — earthworks, sewer, water, drainage, roads — run under hold-point supervision. What distinguishes subdivision delivery is that the physical works are only half the deliverable. The other half is the acceptance trail: inspections passed, drainage CCTV reviewed and rectified, supervision fees paid, maintenance security lodged, and as-constructed information delivered in the form each authority’s asset system requires.

Practical completion is therefore a paperwork event as much as a site event, and the paper half is where weeks quietly go. A CCTV run that finds a bellied pipe starts a rectify-and-reshoot loop with its own scheduling. As-constructed data that arrives as marked-up PDFs gets bounced by an assets team that needs structured data. None of this appears on a construction programme as a line item — it appears afterwards, as slippage.

By the time a Statement of Compliance application is being prepared, its outcome is already determined. The council can issue it when the permit’s relevant conditions are satisfied and every referral authority has consented — and each authority’s consent has its own preconditions: works accepted, fees settled, easements and reserves shown correctly on the plan. If those threads were tracked from permit issue, SoC preparation is an assembly job measured in days. If they were not, it is an investigation measured in months, conducted at the exact moment the finance costs of delay are highest.

Staged subdivisions raise the stakes: compliance runs per stage, conditions and authority requirements apply across stages, and the register has to answer “what does Stage 3 still owe” without double-counting what Stage 2 already discharged. This is squarely a data-structure problem, and spreadsheets are the wrong data structure for it.

Titling follows registration at the titles office, and the development is not finished even then — the defects liability period, final completion and the return of maintenance securities run beyond it. But commercially, the Statement of Compliance is the finish line that matters: it is the gate between money spent and money settled.

The practical lesson of the arc is not that it is complicated — everyone in the industry knows it is — but that its complexity is relational. Conditions gate phases. Designs await authorities. Acceptances feed consents. The delivery state of a subdivision is a graph, and the industry manages it with tools that cannot represent edges: PDFs, folders, spreadsheets, inboxes.