This Planning Insight reads a specific proposal — a new single dwelling — against the controls that actually apply to the land. For this Insight the customer uploaded their Certificate of Title and Plan of Subdivision and their VicPlan Planning Property Report, so it goes well beyond the free Property Snapshot: it reads the encumbrances registered on the title and the precise extent of each overlay, not just whether a control is “present”. It is not a compliance check of drawn plans — once you have plans, the $399 Detailed Planning Assessment tests them standard-by-standard. Property identifiers have been redacted in this public sample.
What your title reveals — the free snapshot cannot see any of this
- Restrictive covenant (instrument redacted): the title carries a single-dwelling covenant — the land may not be used for more than one dwelling. This is decisive: a dual-occupancy or a second dwelling is not available here regardless of what the zone would otherwise allow, unless the covenant is removed or varied (a separate, often difficult, application under s 60 of the P&E Act / s 84 of the Property Law Act). Your project (one new dwelling) is consistent with it.
- Carriageway & drainage easement (instrument redacted): a 2.5 m easement runs along the rear boundary in favour of the adjoining lot and the water authority. You cannot build over it, and the authority’s consent is needed for works near it — so the rear ~2.5 m strip is effectively sterilised for the building footprint. Factor this into the setback and siting before you design.
- Section 173 Agreement (instrument redacted): an agreement registered on the title requires a bushfire management plan to be implemented and maintained, and restricts further subdivision. It runs with the land and binds you — the council will enforce it as a condition of any new approval.
Overlays — and why the precise extent matters
Heritage Overlay (Clause 43.01) — whole of lot: the controlling planning constraint. It triggers a permit for buildings and works, supported by a Heritage Impact Statement; new work must be sympathetic to the heritage place.
Land Subject to Inundation Overlay (Clause 44.04) — partial: here is where the deeper read pays for itself. The free snapshot only reports “LSIO present”. Reading the VicPlan polygon against the plan of subdivision, the LSIO covers only the rear ~20% of the lot — the low corner behind the building line. The front building envelope, where a new dwelling would sit, is clear of the LSIO. So the inundation control is not the obstacle a blanket reading would suggest; it mainly affects where you cannot put a shed or fill, and floor-level/drainage conditions if you ever build into the rear.
Zone & permit pathway
GRZ1: a single dwelling is a Section 1 use (no permit for the use). The Heritage Overlay independently requires a buildings-and-works permit, so Clause 54 (ResCode) becomes the assessment framework. The mandatory minimum garden area (Clause 32.08-4) applies and is set by your lot size — it cannot be varied, and the rear easement strip still counts toward it (it is open, non-building land). Bushfire: a BAL assessment and AS 3959 construction apply, dovetailing with the s 173 bushfire plan.
Why the deeper analysis matters here
A free snapshot would have missed the title entirely — it would not have told you the covenant rules out a second dwelling, that the rear easement sterilises 2.5 m, or that a s 173 agreement binds you to a bushfire plan. It would also have treated the LSIO as if it blanketed the lot. With the title and VicPlan read together, the real picture is clear: one well-sited dwelling in the front-to-middle of the lot, clear of the easement and the LSIO, designed to satisfy the Heritage Overlay and the bushfire obligations.
Next step
When you have concept plans, the $399 Detailed Planning Assessment runs them against every Clause 54 standard, the Heritage Overlay design expectations, the easement and covenant constraints and the bushfire requirements — and tells you whether the design will hold up at lodgement, or exactly where it needs to change.