Insights Archive - My Subdivision https://hjh.wqb.mybluehost.me/website_b6fced6f/insights/ Mon, 13 Oct 2025 06:31:03 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 https://i0.wp.com/mysubdivision.co.nz/wp-content/uploads/2025/10/cropped-Subdivision-website-16.webp?fit=32%2C32&ssl=1 Insights Archive - My Subdivision https://hjh.wqb.mybluehost.me/website_b6fced6f/insights/ 32 32 249251559 Reading a LIM Like a Developer https://mysubdivision.co.nz/insights/insights-reading-a-lim-like-a-developer/ Wed, 01 Oct 2025 05:03:15 +0000 https://hjh.wqb.mybluehost.me/website_b6fced6f/?post_type=insights&p=456 Built for Auckland subdivisions and small multi-unit projects Key takeaways What to scan first in a LIM to avoid weeks of rework. Which items trigger specialist inputs (and in what order). A simple decision tree for “go / conditional / no-go”. A LIM can feel dense, but you don’t need to read every line. The […]

The post Reading a LIM Like a Developer appeared first on My Subdivision.

]]>

Reading a LIM Like a Developer

Built for Auckland subdivisions and small multi-unit projects

Key takeaways

  • What to scan first in a LIM to avoid weeks of rework.

  • Which items trigger specialist inputs (and in what order).

  • A simple decision tree for “go / conditional / no-go”.

A LIM can feel dense, but you don’t need to read every line. The developer’s approach is to triage risk quickly, then commission targeted checks. Here’s how to scan a LIM for feasibility, servicing, and consent pathway—without getting lost.

Start with the headline constraints

  • Zoning & overlays: Note the zone and any overlays (heritage/SEAs, flood/inundation). These drive design options and reports.
  • Site history & consents: Past consents can reveal known issues (e.g., fill, retaining, historic flooding).
  • Hazards: Flood levels, overland flow paths (OLFP), coastal/inundation risk—flag for three-waters strategy.

Services & access can you connect and comply?

  • Stormwater & wastewater: Check if public networks are available and where; depth/grade feasibility will affect costs and programme.
  • Water supply/pressure & fire-fighting: Note any pressure/flow limitations and hydrant coverage.
  • Vehicle access: Crossings, gradients, sightlines, and road classification—access non-compliance is a common cause of redesigns.

Geotech & ground conditions

  • Slope/retaining/fill: Steep or filled sites raise geotechnical complexity.
  • Soakage potential: Soil type/borings (if available) hint at whether soakage is viable or if detention/retention will dominate.

Trees, ecology, heritage

  • Protected trees/SEAs/heritage: These change footprints, access, and servicing routes.

Translate findings into a consent pathway

  • Non-notified vs risk of notification: Are effects internalised, or will affected-party approvals be needed?
  • Evidence list: AEE + civil/hydraulic + geotech + arborist/ecology + transport diagrams, as required.
  • Sequence: Desktop → options testing → drawings & reports → (optional) pre-app → lodgement.

Decision tree

  • Go: Zone fits, services feasible, no major hazards → proceed to concept and servicing strategy.
  • Conditional go: Known risks (e.g., OLFP, steep access) → commission focused reports; design to mitigate.
  • No-go (for now): Major capacity/heritage/overlay hurdles with poor economics → pause or re-scope.

Need a second pair of eyes?

Book a 15-min Feasibility Call
Feasibility Checklist (Auckland)

The post Reading a LIM Like a Developer appeared first on My Subdivision.

]]> 456