Short answer: often yes, but a duplex (dual occupancy) in Redland's Low density residential zone has to clear three separate conditions before it reaches the accepted subject to requirements track, and the three conditions do not all fail the same way. Under Redland City Plan 2018, Version 14, Table 5.4.1 (the LDR use table) sets the test on its own: the lot sits outside the LDR1, LDR2 and LDR4 precincts, the building stays at or under 8.5 m, and the site carries no more than one dwelling for every 400 m² of its area. Clear all three and the pathway is accepted development, assessed against the benchmarks the use table points to in the LDR zone code (Table 6.2.1.3.1), covered below. Miss the height or the density condition and the use table is explicit: it becomes Code assessment, a full application. Sit inside LDR1, LDR2 or LDR4, and the answer is not a fallback to Code assessment at all; it is a different situation entirely, covered further down.
The density condition, worked in real numbers
The density condition reads as a ratio, one dwelling per 400 m² of site area, and it is worth doing the arithmetic rather than treating it as an abstract test. A dual occupancy is two dwellings. Two dwellings at no more than one per 400 m² means the site needs at least 800 m² (2 multiplied by 400 m²) before the density condition is even satisfied. Below that, the density condition fails on its own terms, regardless of height or precinct.
That worked 800 m² floor is easy to confuse with the 800 m² the zone code itself states once the use-table gate is already cleared: Performance Outcome 2 (PO2) of the LDR zone code looks for dual occupancies on lots of 800 m² or more, unless the design comes in a form consistent with the low density, open and low-rise character of the locality. The two numbers land in the same place, but they are not the same requirement. One is the worked consequence of the use table's density condition (Table 5.4.1's 1 dwelling per 400 m²); miss it and the application is code assessable outright, no argument available. The other is the performance outcome itself (Table 6.2.1.3.1, PO2), whose acceptable outcomes are AO2.1 (the same 1 dwelling per 400 m² density) and AO2.2 (a 20 m frontage), and whose character limb is the argument open to a design on a smaller site. Reading them as one 800 m² rule risks treating an arguable performance outcome as a hard gate, or a hard gate as something negotiable.
Two different fallbacks, not one
Table 5.4.1 resolves a dual occupancy proposal that does not meet all three accepted-development conditions in two genuinely different ways, and conflating them is the trap on this question.
| What the proposal misses | What Table 5.4.1 does |
|---|---|
| Height over 8.5 m, or density over 1 dwelling per 400 m² | Named, typed fallback: Code assessment (a full development application against the zone code's benchmarks) |
| Site sits in LDR1, LDR2 or LDR4 | No fallback in the use table at all; dual occupancy is not a use the table provides for in these precincts |
A height or density miss lands on a known, named pathway: Code assessment is a real application, but it is a defined one, decided against the zone code's benchmarks. A site in LDR1 (large lot), LDR2 (park residential) or LDR4 (Kinross Road) does not land on that pathway or any other typed one, and the use table's own Code assessment row says so in its trigger, which applies "If not in precincts LDR1, LDR2 or LDR4 and not accepted subject to requirements" (Table 5.4.1): the code fallback excludes those three precincts by name. In these precincts, the use table simply does not provide for a dual occupancy; dwelling houses are the residential use it recognises there. Nothing in our records resolves what category, if any, an application for two dwellings would take on land in one of those precincts, and treating it as automatically code assessable "by default" would be reading a fallback into the table that is not written there. That is a site-specific question for Redland's mapping and, in practice, a town planner, not something this page can settle in general.
The zone code's own requirements, once the gate is cleared
Clearing the three use-table conditions does not finish the assessment; the accepted pathway is subject to the requirements of the LDR zone code (Table 6.2.1.3.1). Under PO2, described above, the acceptable outcomes are AO2.1 (no more than 1 dwelling per 400 m² of site area) and AO2.2 (a minimum 20 m frontage); under PO3, which covers design and siting, AO3.1 calls for compliance with the QDC MP1.3 design and siting provisions. An acceptable-outcome miss is not an automatic refusal. The general mechanic for accepted subject to requirements development in Redland works like this: missing an acceptable outcome makes the proposal code assessable, but only against the single corresponding performance outcome, not the whole code (the scheme's Part 5 editor's note, which applies unless the table specifies otherwise). Worked through honestly: an 850 m² site with 18 m of frontage clears the use-table gate (two dwellings on 850 m² is one dwelling per 425 m², inside the density condition), misses AO2.2's 20 m frontage, and per the editor's note becomes code assessable against PO2 alone; PO2's area limb (800 m² or more) is one the site already satisfies, which leaves the character limb as the live question for the design. MP1.3 is the exception that "unless the table specifies otherwise" points at, because the use table's own editor's note under the dual occupancy rows specifies a different route (Table 5.4.1, verified 15 July 2026):
"Dual occupancies that do not comply with any relevant acceptable outcomes of the Queensland Development Code MP1.3 will require a concurrence agency referral to Council under Schedule 9 of the Regulation."
So an MP1.3 acceptable-outcome miss routes to a concurrence agency referral to council under Schedule 9 of the Planning Regulation, not to the generic single-performance-outcome narrowing. Whether a particular design clears its acceptable outcomes, wins its performance-outcome argument or trips that referral is a question for the plans in front of a town planner, not a figure this page can pre-decide.
What the flood overlay does, and does not, change here
Redland's Flood and Storm Tide Hazard Overlay carries a note that matters specifically for accepted-development pathways like this one. Its own words, verbatim, from the Part 5 overlay table:
"This overlay code is not applicable to development that is accepted subject to requirements."
That note means a dual occupancy that reaches the accepted subject to requirements track under Table 5.4.1 does not get pulled into the flood overlay code at all, an outcome unlike a neighbouring council where an accepted pathway can still be pulled down by a flood tier. Separately, and worth checking on its own terms rather than assumed, this overlay's one category-changing trigger, the "drainage constrained" mapping, is scoped in the table's own text to material change of use or building work for a dwelling house or a community residence on the Southern Moreton Bay Islands. A dual occupancy is neither of those two uses, so even setting the accepted-development exclusion aside, that specific trigger's own wording does not reach it. The landslide hazard overlay carries the same no-change pattern for any use, including a dual occupancy. Flood and landslide are the two Redland overlays our records have read in category terms so far; the rest of the overlay suite has not had that treatment, so any other layer the council's mapping shows on a specific parcel gets read before it is treated as neutral, not after.
Selling one and keeping one: what the titling step actually does
A dual occupancy earns its place on this list because, unlike a granny flat, both dwellings can eventually be sold separately. The mechanics: reconfiguring a lot (subdivision) creates new freehold land parcels under a standard format plan, splitting the underlying land itself. A dual occupancy does not touch the underlying land at all; the site stays one lot throughout the development approval. Once the building is approved and built, each dwelling can be registered as its own lot on a building format plan layered over that single freehold title, which is what allows one to be sold and one to be kept (or both sold) without ever subdividing the land. That building-format step is its own process afterwards, run by a solicitor and a planner, not an automatic consequence of the development approval. It is also the reason a dual occupancy and a granny flat (secondary dwelling) in the Redlands answer different questions even though both add a second dwelling: a secondary dwelling stays on the one title with the house and is not separately saleable, while a dual occupancy is built specifically to be titled apart. Where a block cannot meet the density arithmetic or sits in an excluded precinct, it is also worth checking whether a straight freehold split clears the numbers instead; that comparison, including the accessway net-area trap that catches otherwise-compliant Redland lots, is covered in our companion piece on subdividing land in the Redlands.
How to check your own block
- Confirm your parcel's precinct on Redland's planning scheme mapping: LDR standard, or one of LDR1, LDR2 and LDR4. That alone decides whether the use table's accepted pathway is available at all.
- If your precinct is not LDR1, LDR2 or LDR4, run the density arithmetic against your site area (divide by 400 and check the result reaches at least 2 for a dual occupancy) alongside the 8.5 m height limit, then check the zone code's frontage and site-area outcomes and the QDC MP1.3 design and siting provisions against your design.
- Pull up the overlay mapping for the parcel and read every layer it shows, flood, storm tide and landslide included; then have a town planner confirm whether the design meets every acceptable outcome, needs a performance-outcome argument or trips the MP1.3 referral, and how the eventual building format titling step should be structured for your circumstances.
This page is general information about the Redland City 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, read our Redlands planning and zoning guide, or compare against our companion pieces on subdividing land in the Redlands and building a granny flat in the Redlands.
Sources: Redland City Plan 2018 (the council's official planning scheme, redland.qld.gov.au), Table 5.4.1 (LDR use table), Table 6.2.1.3.1 (LDR zone code, PO1 to AO3.1) and the Part 5 overlay tables 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 July 2026 to 15 July 2026 against Redland City Plan 2018, Version 14; schemes amend, and the live scheme prevails.