Short answer: often yes, but Logan runs a genuine switch, not a single yes/no test. Reconfiguring a lot (the Planning Act term Logan's scheme uses for subdividing) defaults to code assessment under the scheme's own architecture, decided against technical benchmarks rather than through public notification. But that default only holds if every lot your split would create meets the minimum size mapped for its zone and precinct. Miss it on even one lot, and under the scheme's own tables the same application becomes impact assessment, which means public notification and a materially harder path.
Under the Logan Planning Scheme 2015, a subdivision needs a development application in almost every practical case; the assessment sequence starts at the State Planning Regulation before the scheme's own tables, and the scheme itself provides no accepted (no-DA) tier for reconfiguring a lot in the residential zones. What changes is which assessment table applies to it and how it is judged. Section 5.3's own default rule sets reconfiguring a lot at code assessment unless the Table of Assessment says otherwise or a State instrument prescribes otherwise, and it is Table 5.6.1, the zone's own Reconfiguring a Lot table, that usually makes or breaks that default on your block.
The minimum lot sizes, by zone and precinct
Logan's Reconfiguring a Lot code (Table 9.4.6.3.2) and the zone table (5.6.1) set the minimum every new lot has to clear, and it differs sharply between the Low density residential (LDR) zone's precincts and the higher-density residential zones:
| Zone / precinct | Minimum lot size | Minimum frontage |
|---|---|---|
| LDR, Small lot | 300 m² | 10 m |
| LDR, Suburban | 400 m² (rear lots 500 m², measured clear of the access handle) | 12.5 m (10 m cul-de-sac, 15 m corner) |
| LDR, Village | 500 m² (rear lots 600 m², measured clear of the access handle) | 15 m |
| LDR, Large suburban | 1,000 m² | 20 m |
| LDR, Small acreage | 2,000 m² | 20 m |
| LDR, Acreage | 4,000 m² | 40 m |
| Low-medium density residential, Townhouse precinct | 500 m² (no rear lots) | 20 m |
| Low-medium density residential, Apartment precinct | 800 m² (no rear lots) | 20 m |
| Medium density residential (both precincts) | 1,200 m² (no rear lots) | 20 m |
Which row applies to your parcel is a mapping question first: the zone and precinct come off Logan's own zone map, not off what the street looks like. A 900 m² block in the LDR Suburban precinct can clear a one-into-two split under either configuration: two standard lots of at least 400 m², each with its own 12.5 m of frontage, or a front lot plus a rear lot of at least 500 m² measured clear of the access handle. The same 900 m² in the Village precinct cannot produce two complying lots (two standard lots need 1,000 m² there, and a rear-lot split needs 1,100 m²), so a two-lot application on that block would run as impact assessment rather than code.
The switch: code assessment, or impact assessment
This is the switch to test first on any Logan block. Table 5.6.1 sets reconfiguring a lot in the LDR zone at code assessment where every resulting lot meets its precinct's minimum (and, in the Suburban and Village precincts specifically, every rear lot clears the higher rear-lot minimum, measured clear of the access handle), or where the reconfiguration is over land with an existing or approved Multiple dwelling. Fall short of that test on any lot, and the same table sends the application to impact assessment instead, with public notification, unless a State instrument prescribes otherwise: for some one-lot-into-two subdivisions the Planning Regulation prescribes code assessment against its own Schedule 12 benchmarks, a layer that sits ahead of the scheme's tables. The Low-medium density residential zone runs the identical switch off its own 500 m² (Townhouse) and 800 m² (Apartment) minimums, and Medium density residential off its single 1,200 m² figure. There is no partial credit: one non-complying lot in a multi-lot split is enough to flip the whole application's category.
Two of Logan's ten local plans, Loganholme and Loganlea, carry their own reconfiguring-a-lot tables with different triggers again (in Loganholme, a proposed lot under 600 m² in the Residential choice precinct or under 1,200 m² in the Residential core precinct, or a site frontage under 40 m, sends the application to impact assessment; an inverted pattern worth reading carefully rather than assumed). Where a local plan states its own table, it overrides the zone table for that footprint, so the mapping has to be checked before the lot-size test is applied.
What the overlays actually do to a subdivision
Flood, bushfire and landslide overlays are commonly assumed to push a subdivision straight to a harder assessment tier. In Logan, none of them change reconfiguring a lot's own category at all. The Flood hazard overlay (Table 5.10.5.1) lists reconfiguring a lot as "no change" in every mapped tier, from the Low flood island through Moderate and High flood risk to the Flood investigation area; the flood code becomes an extra assessment benchmark, not a category change. The dwelling that eventually goes on the new lot is where the tier bites: a dwelling house or dual occupancy (auxiliary unit) stays "no change" in the Low flood island and Moderate flood risk area, but the High flood risk area or Flood investigation area pushes that dwelling's own assessment to code.
Bushfire hazard and landslide hazard/steep slope overlays follow the same shape: reconfiguring a lot stays "no change" in category, but each overlay's own code becomes a real benchmark. On mapped bushfire land, the code's acceptable outcomes look for a Bushfire Attack Level of 29 or lower on each new lot, asset protection zones on slope under 18 degrees and within the lot, and either reticulated water at 10 L/s and 200 kPa or, where that is not available, on-site storage of 5,000 to 20,000 litres depending on lot size. On land mapped for the landslide hazard and steep slope area overlay (12 to 15% grade, depending on how the hazard was identified), the standard route is a site-specific geotechnical report certifying a factor of safety greater than 1.5. None of this changes whether the subdivision itself is code or impact assessed; it changes what the application has to demonstrate to get through.
If the numbers don't work, the two-dwellings pathway often survives
Where a block cannot clear a second freehold lot, a second dwelling is often still open in the LDR zone. Logan's own term for a granny flat is "Dual occupancy (auxiliary unit)," and it is accepted development, no DA at all, in any precinct of the LDR zone, provided it meets the auxiliary unit code's own requirements. A full dual occupancy, two dwellings rather than one plus a secondary unit, is accepted development subject to requirements on a lot of 700 m² or more in the Suburban precinct (525 m² in Small lot, 875 m² in Village); below that threshold it drops to code or impact assessment instead. In the Low-medium density residential zone's Townhouse precinct, a dual occupancy is accepted on a lot of 500 m² or more; its Apartment precinct treats a non-auxiliary dual occupancy as code assessment, not accepted at all. Every dual occupancy needs 2 parking spaces per dwelling, one covered.
"Accepted subject to requirements" is not an unconditional green light, either. The scheme's own words (section 5.3.3(2), read via Logan's rules API):
"Accepted development that does not comply with one or more of the nominated acceptable outcomes in the relevant parts of the applicable code(s) becomes code assessable development, unless otherwise specified."
So a dual occupancy that clears the lot-size threshold but misses one of the code's other requirements, siting, height or parking among them, cascades into a code assessable application, limited to whichever requirement was not met. It does not simply fail; it moves to a different, slower tier.
How to check your own block
- Find your parcel's zone and precinct on Logan's eplan. That tells you which row of Table 5.6.1 and which line of the Reconfiguring a Lot code governs, and whether one of the ten local plans (Loganholme and Loganlea in particular) sits on top of it with its own table.
- Test every lot your split would create against that precinct's minimum area and frontage, and against the higher rear-lot minimum, measured clear of the access handle, where the precinct allows a rear lot at all. One lot short of the minimum sends the whole application to impact assessment under the zone table, subject to the State Regulation's Schedule 12 layer for simple one-into-two splits.
- Check the overlay maps: flood, bushfire and landslide/steep slope. None of them changes a subdivision's own category in Logan, but each loads its own code onto the application, and a dwelling built later on the new lot can face a different, harder category than the subdivision itself did.
This page is general information about the Logan planning scheme, not advice about your property. Overlay effects vary lot by lot, planning schemes amend, and the council's current scheme prevails. Do not rely on this page for a specific property. Get a site-specific report or independent professional advice before acting. We work with town planners, not in place of them: where a pathway depends on design or professional judgement, a town planner or the relevant qualified professional confirms it for your specific proposal.
Want the answer for your block? Our $690 site-specific report reads the zone, the precinct, every overlay mapped on the property and the surviving development pathways for one property, with every figure cited to the scheme. Not ready for that? Start with the free development risk checklist, or read our Logan planning and zoning guide.
Sources: Logan Planning Scheme 2015 (the council's official eplan), including the Reconfiguring a Lot zone table (5.6.1), the Reconfiguring a Lot code (9.4.6) and the overlay codes cited above. Everything on this page comes from the council's own published planning scheme; we explain it in plain English. The scheme text itself is the authority.
Published by LandIntel. How we research: our methodology.
Verified 3 to 7 July 2026 against the Logan Planning Scheme 2015, Version 9.2 (including TLPI No. 1/2024), effective 1 July 2025; schemes amend, and the live scheme prevails.