Auckland planning and consent
Residential Resource Consent Guide
Resource consent controls are specific to the site, proposal, current Auckland Unitary Plan provisions, related approvals, and the issued decision. This guide explains the management workflow; it does not determine whether consent is required or what the outcome will be.
Site-specific rulesConditions registerRFI controlImplementation evidenceLast reviewed 11 August 2026
Step-by-step process
- 1Define the development strategy, proposed activity, site address, legal description, expected yield, access, earthworks, services, subdivision, and construction approach.
- 2Obtain the current Record of Title and instruments, LIM, property file, GeoMaps information, topographical/site survey, and all known existing consent records.
- 3Ask an Auckland-experienced planner for a written site-specific review of zone, precinct, overlays, standards, infringements, activity status, assessment criteria, information requirements, and notification risk.
- 4Coordinate the concept with the architect/designer, surveyor, civil/geotechnical/traffic specialists, arborist, landscape designer, and other consultants identified by the planner.
- 5Update the feasibility and programme for consultant reports, council deposits/fees, design changes, infrastructure works, monitoring, consent conditions, legal advice, holding costs, and uncertainty.
- 6Confirm the application strategy and document list. Run a pre-lodgement coordination review so plans, assessments, reports, title information, and specialist recommendations agree.
- 7Lodge through the current Auckland Council process and maintain a dated application, document, fee, and correspondence register.
- 8When an RFI arrives, assign every question to an owner, record dependencies, coordinate one consistent response set, and update drawings/reports rather than replying with unsupported statements.
- 9When a decision is issued, read every condition and approved plan. Build a conditions register organised by pre-commencement, during works, monitoring, prior to occupation/use, subdivision/title, and ongoing obligations.
- 10Before construction, satisfy all pre-commencement conditions and related engineering/traffic/erosion/sediment approvals. Keep written acceptance where council or a specialist must confirm it.
- 11During delivery, collect the inspections, monitoring reports, approvals, photos, as-builts, notices, and certificates required by the consent and related approvals.
- 12Before occupation, settlement, title, or project close-out, confirm every relevant condition has evidence, an owner, a status, and council/consultant acceptance where required.
Key people
- Developer / development manager
- Planner
- Architect or architectural designer
- Licensed cadastral surveyor
- Civil and geotechnical engineers
- Traffic engineer where needed
- Landscape designer / arborist where needed
- Lawyer for title and legal instruments
- Quantity surveyor for cost impact
- Auckland Council processing and monitoring officers
Decisions to record
- Proceed, redesign, seek pre-application input, lodge, pause, or abandon
- Application scope and activity status assumption
- Who owns each report and RFI
- Cost/programme impact of each condition
- Whether a change needs planner/council review
- Condition close-out evidence and acceptance
Property and proposal
- Record of Title and instruments
- LIM and property file
- Current survey/site information
- Existing and proposed site plans
- Development brief and yield study
- Photographs and surrounding context
Planning assessment
- Zone, precinct and overlay review
- Relevant objectives, policies and rules
- Development control assessment
- Identified infringements
- Activity status analysis
- Assessment of environmental effects
- Notification assessment where relevant
Specialist inputs
- Architectural design
- Civil and stormwater/wastewater information
- Geotechnical and earthworks information
- Traffic/access information
- Landscape/arborist information
- Flood/overland flow information
- Acoustic, contamination, heritage, ecological or other reports where advised
Implementation and close-out
- Issued consent decision and conditions
- Approved plans and reports
- Conditions register
- Engineering approvals
- Construction/traffic/erosion plans where required
- Monitoring records
- As-built information
- Council correspondence and final condition evidence
Consent conditions
Turn the decision into a controlled conditions register
| Condition | Trigger | Required action | Owner | Due | Evidence | Cost impact | Programme impact | Status | Council / consultant confirmation |
|---|---|---|---|---|---|---|---|---|---|
| Pre-commencement | Before any relevant site work | List every plan, approval, notice, meeting, certification, or payment required before starting. | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry |
| During construction | At stated stage or continuously | Brief the site team, programme hold points, collect monitoring and evidence, and escalate deviations. | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry |
| Prior to occupation / use | Before occupation, use, handover, or settlement milestone | Complete physical work and provide the specified reports, certifications, as-builts, or confirmations. | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry |
| Subdivision / title | Before survey approval, section 223/224 process, or title action where relevant | Coordinate survey, engineering, legal, servicing, easement, and condition evidence with the responsible specialists. | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry |
| Ongoing | Continues after completion | Place the obligation in the handover and property-management record with a named owner. | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry | Project entry |
Red flags — pause and get advice
- The intended yield only works if an unverified planning interpretation is accepted.
- The title, easement, covenant, consent notice, access, flood path, service corridor, or protected feature conflicts with the concept.
- Architectural, civil, survey, traffic, landscape, or planning documents show different layouts, levels, boundaries, or dwelling numbers.
- A significant infringement, notification risk, infrastructure constraint, or specialist report is missing from the feasibility allowance.
- A consent condition requires work, monitoring, approval, bond, easement, legal instrument, or specialist sign-off that has not been priced or programmed.
- Construction is about to start before pre-commencement conditions or related approvals have written confirmation.
- A change is proposed that may no longer match the approved resource consent plans or assessment.
Evidence to save
- Dated AUP/GeoMaps screenshots and planner advice used for the decision.
- All lodged, superseded, approved, and revised plans/reports with a clear document register.
- Council invoices, receipts, correspondence, RFIs, responses, meeting notes, and decision documents.
- Condition register with owners, due dates, cost/programme effects, and links to evidence.
- Pre-start approvals, monitoring reports, site photos, survey/as-built records, specialist sign-offs, and council acceptance.
- Decision-register note whenever the concept, consent pathway, yield, cost, programme, or condition strategy changes.
Related free tools
Source / Where to check
Use the current Auckland Unitary Plan text and maps for the specific zone, precinct, overlay, standards, activity status, assessment criteria, and information requirements. Check Auckland Council’s current resource consent application and process guidance, the complete issued consent and approved plans, and written advice from the project planner and relevant specialists.
Insufficient data to verify — check the Auckland Unitary Plan for the specific site zone, precinct, overlay, and activity status.