Consents
Engineering approvals
This stage manages civil, stormwater, wastewater, vehicle crossing, road corridor, and subdivision engineering approvals where required. This page shows what a beginner residential developer in Auckland should check, who to ask, what evidence to save, and where to verify before committing money or instructions.
How to execute this stage
Micro-stage control plan
Work through each applicable step in order. A hold point means pause the dependent decision or work until the stated evidence and authorised review are complete.
01Approval pathwayLevel 2 · Consents
TaskCheckHold pointEvidenceRecordNext actionSimple explanation
Approval pathway
Technical context
Test this point against Engineering plans, the current feasibility version and written input from Civil engineer. Separate verified facts, professional opinion and assumptions.
Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on engineering scope.
Prerequisites
- Engineering plans is current and its source/date are recorded.
- The project objective, feasibility version and decision deadline are clear.
- Civil engineer has a focused brief where professional confirmation is required.
Checks
- Does Engineering plans directly support the conclusion?
- Which information is verified, assumed, missing, superseded or contradictory?
- Has the feasibility, programme, risk register and decision register been updated?
Evidence to save
- Engineering plans
- Written Civil engineer response or a recorded reason it is not required
- Dated feasibility/risk/decision update
Hold point
Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.
Stop or escalate when
- The source is missing, old, inconsistent or outside the reviewer's scope.
- The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
- A deadline is approaching and the responsible professional has not confirmed the position.
Documents and records
- Engineering plans
- Consent tracker
- Council meeting notes
- Current feasibility, risk register and decision register
- Cost effect
- Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before engineering scope.
- Programme effect
- Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.
Next action
design standards
Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.
Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.
02design standardsLevel 2 · Consents
TaskCheckHold pointEvidenceRecordNext actionSimple explanation
design standards
Technical context
Test this point against Approval applications, the current feasibility version and written input from Surveyor. Separate verified facts, professional opinion and assumptions.
Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on construction sequence.
Prerequisites
- Approval applications is current and its source/date are recorded.
- The project objective, feasibility version and decision deadline are clear.
- Surveyor has a focused brief where professional confirmation is required.
Checks
- Does Approval applications directly support the conclusion?
- Which information is verified, assumed, missing, superseded or contradictory?
- Has the feasibility, programme, risk register and decision register been updated?
Evidence to save
- Approval applications
- Written Surveyor response or a recorded reason it is not required
- Dated feasibility/risk/decision update
Hold point
Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.
Stop or escalate when
- The source is missing, old, inconsistent or outside the reviewer's scope.
- The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
- A deadline is approaching and the responsible professional has not confirmed the position.
Documents and records
- Approval applications
- Consent tracker
- Council meeting notes
- Current feasibility, risk register and decision register
- Cost effect
- Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before construction sequence.
- Programme effect
- Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.
Next action
conditions
Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.
Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.
03conditionsLevel 2 · Consents
TaskCheckHold pointEvidenceRecordNext actionSimple explanation
conditions
Technical context
Test this point against Watercare approvals, the current feasibility version and written input from Auckland Council. Separate verified facts, professional opinion and assumptions.
Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on who manages approvals.
Prerequisites
- Watercare approvals is current and its source/date are recorded.
- The project objective, feasibility version and decision deadline are clear.
- Auckland Council has a focused brief where professional confirmation is required.
Checks
- Does Watercare approvals directly support the conclusion?
- Which information is verified, assumed, missing, superseded or contradictory?
- Has the feasibility, programme, risk register and decision register been updated?
Evidence to save
- Watercare approvals
- Written Auckland Council response or a recorded reason it is not required
- Dated feasibility/risk/decision update
Hold point
Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.
Stop or escalate when
- The source is missing, old, inconsistent or outside the reviewer's scope.
- The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
- A deadline is approaching and the responsible professional has not confirmed the position.
Documents and records
- Watercare approvals
- Consent tracker
- Council meeting notes
- Current feasibility, risk register and decision register
- Cost effect
- Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before who manages approvals.
- Programme effect
- Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.
Next action
inspection points
Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.
Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.
04inspection pointsLevel 2 · Consents
TaskCheckHold pointEvidenceRecordNext actionSimple explanation
inspection points
Technical context
Test this point against AT corridor/access approvals, the current feasibility version and written input from Watercare. Separate verified facts, professional opinion and assumptions.
Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on what must be completed before title/ccc/settlement.
Prerequisites
- AT corridor/access approvals is current and its source/date are recorded.
- The project objective, feasibility version and decision deadline are clear.
- Watercare has a focused brief where professional confirmation is required.
Checks
- Does AT corridor/access approvals directly support the conclusion?
- Which information is verified, assumed, missing, superseded or contradictory?
- Has the feasibility, programme, risk register and decision register been updated?
Evidence to save
- AT corridor/access approvals
- Written Watercare response or a recorded reason it is not required
- Dated feasibility/risk/decision update
Hold point
Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.
Stop or escalate when
- The source is missing, old, inconsistent or outside the reviewer's scope.
- The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
- A deadline is approaching and the responsible professional has not confirmed the position.
Documents and records
- AT corridor/access approvals
- Consent tracker
- Council meeting notes
- Current feasibility, risk register and decision register
- Cost effect
- Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before what must be completed before title/ccc/settlement.
- Programme effect
- Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.
Next action
as-built needs
Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.
Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.
05as-built needsLevel 2 · Consents
TaskCheckHold pointEvidenceRecordNext actionSimple explanation
as-built needs
Technical context
Test this point against As-built requirements, the current feasibility version and written input from Auckland Transport. Separate verified facts, professional opinion and assumptions.
Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on engineering scope.
Prerequisites
- As-built requirements is current and its source/date are recorded.
- The project objective, feasibility version and decision deadline are clear.
- Auckland Transport has a focused brief where professional confirmation is required.
Checks
- Does As-built requirements directly support the conclusion?
- Which information is verified, assumed, missing, superseded or contradictory?
- Has the feasibility, programme, risk register and decision register been updated?
Evidence to save
- As-built requirements
- Written Auckland Transport response or a recorded reason it is not required
- Dated feasibility/risk/decision update
Hold point
Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.
Stop or escalate when
- The source is missing, old, inconsistent or outside the reviewer's scope.
- The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
- A deadline is approaching and the responsible professional has not confirmed the position.
Documents and records
- As-built requirements
- Consent tracker
- Council meeting notes
- Current feasibility, risk register and decision register
- Cost effect
- Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before engineering scope.
- Programme effect
- Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.
Next action
bonding/fees where relevant
Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.
Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.
06bonding/fees where relevantLevel 2 · Consents
TaskCheckHold pointEvidenceRecordNext actionSimple explanation
bonding/fees where relevant
Technical context
Test this point against Inspection notes, the current feasibility version and written input from Contractor. Separate verified facts, professional opinion and assumptions.
Why it matters: This check can change yield, consent pathway, acquisition terms, funding, cost, programme or exit strategy. It must be resolved before the developer relies on construction sequence.
Prerequisites
- Inspection notes is current and its source/date are recorded.
- The project objective, feasibility version and decision deadline are clear.
- Contractor has a focused brief where professional confirmation is required.
Checks
- Does Inspection notes directly support the conclusion?
- Which information is verified, assumed, missing, superseded or contradictory?
- Has the feasibility, programme, risk register and decision register been updated?
Evidence to save
- Inspection notes
- Written Contractor response or a recorded reason it is not required
- Dated feasibility/risk/decision update
Hold point
Do not waive a condition, instruct design/work, commit funding, lodge, purchase, settle or represent the conclusion as confirmed until the authorised decision-maker has the required evidence and advice.
Stop or escalate when
- The source is missing, old, inconsistent or outside the reviewer's scope.
- The check changes yield, approval pathway, funding, legal rights, tax, safety or a material cost/programme assumption.
- A deadline is approaching and the responsible professional has not confirmed the position.
Documents and records
- Inspection notes
- Consent tracker
- Council meeting notes
- Current feasibility, risk register and decision register
- Cost effect
- Record changes to land value, consultant/council cost, construction/civil cost, finance, holding cost, contingency and exit value before construction sequence.
- Programme effect
- Record the decision deadline, dependencies, information lead time and effect on acquisition, consent, procurement, construction, sales or settlement milestones.
Next action
Make and record the stage decision: Construction sequence. Then open the next applicable development stage.
Applicability: Confirm whether this check applies to the actual site, ownership, strategy, consent pathway, infrastructure and delivery model; record a reason when not applicable.
Use current site-specific documents and appropriately appointed professional advice. BuildPath does not make the development decision for you.
Developer go / no-go control
Decision gates before the next commitment
A gate records whether evidence supports a commercial decision. It does not replace advice or predict an authority, lender, purchaser or market outcome.
Before building consent lodgement
Decision: Lodge coordinated documents, resolve gaps, or defer
Minimum evidence
- • Architectural, structural, civil, services and specifications are coordinated
- • Design producer statements/calculations and approval dependencies are identified
- • Consent deliverables reflect the intended procurement and construction scope
Update before deciding
- • Developed-design quantities and trade scope
- • Authority, testing and observation requirements
- • Long-lead procurement and consent response allowance
Stop / escalate when
- • Unresolved interface changes could invalidate another discipline
- • Required approval/ownership information is absent
- • Budget or programme has not been updated for the developed design
What this stage means
- Engineering approvals is the part of the project where the developer turns an idea into a checked decision, not a guess.
- The stage should connect market demand, planning rules, legal constraints, design, cost, funding, time, risk, and exit strategy.
- For Auckland residential development, the answer is site-specific. The same idea can be low risk on one site and unworkable on the next because of zoning, overlays, title interests, services, slope, flooding, neighbours, or finance.
Why this stage matters
- Early mistakes become expensive because land, design, consultants, holding costs, consent fees, and finance costs continue even when the project is paused.
- The developer needs written evidence for lenders, consultants, lawyers, valuers, builders, purchasers, and future dispute protection.
- This stage usually needs verification from Watercare builders and developers, Auckland Transport corridor access, Auckland Council resource consent, Relevant professional advice before the developer treats the conclusion as reliable.
Step-by-step guide
- 1Define the decision needed at the end of this stage and the date it is needed by.
- 2Gather the stage documents: Engineering plans, Approval applications, Watercare approvals, AT corridor/access approvals, and the remaining stage records.
- 3Read the documents once for understanding, then again to list unknowns, risks, contradictions, missing evidence, and professional questions.
- 4Ask the responsible professionals to confirm the critical points: Civil engineer, Surveyor, Auckland Council, Watercare.
- 5Update the feasibility, programme, risk register, and decision register with source references and dates.
- 6Decide whether to proceed, pause, redesign, renegotiate, add conditions, seek more advice, or abandon the option.
- 7Save the evidence in a dated folder and write a short stage closeout note explaining what was decided and why.
What the developer must do
- Write down the development objective for engineering approvals in one clear paragraph: build-to-sell, build-to-rent, retain one dwelling, subdivide, renovate, or staged development.
- Open the current feasibility, programme, decision register, risk register, and due diligence folder before making new commitments.
- Collect the documents needed for this stage: Engineering plans, Approval applications, Watercare approvals, AT corridor/access approvals, As-built requirements, Inspection notes.
- Send focused questions to the right people: Civil engineer, Surveyor, Auckland Council, Watercare, Auckland Transport, Contractor, Developer.
- Record assumptions separately from verified facts so the feasibility does not look more certain than it really is.
- Update cost, time, consent, finance, and sales assumptions immediately after receiving new information.
- Escalate anything that changes yield, sale price, cost, timing, consent pathway, title, funding, or settlement risk.
Verification
Source / where to check
Use current official information and the controlled documents for the actual project.
Use Watercare and civil engineering advice to verify water and wastewater connection requirements, network capacity, approvals, fees, and construction standards.
Check corridor access, traffic management, vehicle crossing, road occupation, and public road/footpath requirements where the site works affect the transport corridor.
Check council guidance, application requirements, RFI process, consent conditions, approved plans, engineering approvals, and monitoring requirements for site-specific development approvals.
Planner, surveyor, architect, engineer, quantity surveyor, lawyer, accountant, lender, valuer, real estate agent, and other project specialists must confirm site-specific decisions.
Project-specific consented documents and professional advice override generic guidance.
Common mistakes
- Treating an agent comment, generic online rule, or old document as verified site-specific advice.
- Forgetting to update the feasibility after design, consent, finance, or market information changes.
- Not allowing enough contingency, professional fees, council fees, finance costs, holding costs, and time risk.
- Failing to keep written records of who confirmed what and when.
- Using engineering approvals to push ahead even when the red flags show the project should pause.
Common risks
- Yield reduces after proper planning, engineering, title, or infrastructure review.
- Costs increase after QS, builder, civil, geotechnical, demolition, asbestos, or consent information is received.
- Programme moves out because consultant inputs, council RFIs, neighbour issues, finance, title, or construction sequencing take longer than assumed.
- Funding or sales assumptions change before the project reaches settlement.
- The developer relies on unverified information and loses negotiating power or misses a due diligence deadline.
Common costs
- Professional fees for planner, architect/designer, surveyor, engineer, QS, lawyer, accountant, valuer, and lender reports.
- Council fees, consent fees, development contribution estimates, engineering approvals, infrastructure checks, and inspection/monitoring costs where relevant.
- Design revisions, reports, investigations, demolition/asbestos work, service location, geotechnical testing, and valuation updates.
- Holding costs such as interest, rates, insurance, utilities, temporary maintenance, and security.
- Contingency for unverified conditions until the relevant professional confirms them.
Quotes and fee proposals to obtain
- Obtain written fee proposals or quotations from the relevant stage professionals: Civil engineer, Surveyor, Auckland Council, Watercare, Auckland Transport, Contractor, Developer.
- Issue the same current documents and a clear scope to each party so prices, exclusions, assumptions, deliverables, lead times, and programme can be compared.
- Identify council, authority, investigation, testing, design, construction, monitoring, and close-out charges that may sit outside a consultant or contractor quote.
- Record every provisional sum, estimate, exclusion, expiry date, dependency, and unverified allowance in the Quote Register and feasibility.
- Do not approve an appointment or purchase order until scope ownership, evidence required, payment terms, variation process, insurance or competency checks, and completion deliverables are understood.
Common delays
- Waiting for property file, LIM, title instruments, survey information, consultant reports, or council responses.
- Design changes caused by planning controls, infrastructure constraints, engineering findings, budget pressure, or market feedback.
- Lender, valuer, lawyer, or purchaser conditions not being satisfied on time.
- Council RFI responses needing more consultant work than expected.
- Construction or subdivision closeout documents not matching settlement or sales deadlines.
Common consultant questions
- For Engineering approvals, what are the three highest risks that could change cost, time, yield, or approval pathway?
- Which parts of your advice are confirmed, which are assumptions, and which require another professional to confirm?
- What documents did you rely on, and are any documents missing, outdated, superseded, or inconsistent?
- What decision does the developer need to make now, and what should wait until more information is available?
- What wording should go into the decision register, consultant meeting minutes, or lender/client update?
Red flags
- A professional says the issue is outside their scope and no one else has been asked to confirm it.
- The feasibility only works if optimistic sale prices, low construction costs, fast consent, low interest, and no delays all happen together.
- A title, planning, flooding, geotechnical, access, service, or covenant issue may prevent the intended yield.
- A seller, agent, builder, or consultant pressures the developer to waive due diligence before core checks are complete.
- The project file has no written evidence for a major decision.
When to stop and get professional advice
- Stop and get professional advice when title, easements, covenants, unit title, cross lease, or subdivision matters affect the proposal.
- Stop and get professional advice when zoning, overlays, activity status, notification, infrastructure capacity, flooding, geotechnical, contamination, or heritage could affect yield.
- Stop and get professional advice when GST, income tax, entity structure, lending, guarantees, or sale contract terms affect the decision.
- Stop and get professional advice when the developer is about to sign, waive a condition, lodge consent, start work, approve a variation, accept practical completion, or settle.
Decisions that must be made
- Engineering scope
- Construction sequence
- Who manages approvals
- What must be completed before title/CCC/settlement
Evidence to save
- Dated source documents and consultant advice.
- Feasibility version showing the assumptions used at the time of decision.
- Risk register and decision register entries.
- Meeting notes, emails, marked-up plans, calculations, photos, and council/lender/consultant responses.
- Clear note of who approved the next step and any conditions attached to that approval.
Beginner-friendly example
The civil engineer confirms that a public network connection needs separate approval and inspection, so it is added to the programme.
Use this in my project
Turn engineering approvals into controlled action
Open the relevant workspace register, create the project-specific record, link the controlling documents and preserve evidence. The guide does not automatically approve or verify the action.