Auckland Council resource consents for residential subdivision routinely require a CPEng peer review of the engineering design before S224c is issued. For developments managed through HAL Projects (or similar development managers), the peer review requirement is embedded in the consent conditions, meaning your engineer's design will be reviewed by an independent Chartered Professional Engineer before titles can be issued. Understanding what that review covers, and how to design for it, avoids expensive revision cycles.
What Is a CPEng Peer Review?
A CPEng peer review is an independent technical review of an engineering design carried out by a Chartered Professional Engineer who was not involved in the original design. The reviewer assesses whether the design methodology is sound, whether the calculations are correct, whether the design complies with the applicable standards, and whether the design documentation is complete and internally consistent.
In the context of Auckland subdivision consents, the peer review is typically a condition of the resource consent itself. The wording varies, but a typical condition reads: "Prior to the issue of a section 224(c) certificate, the applicant shall provide a peer review of the engineering design by an independent Chartered Professional Engineer confirming that the design complies with Auckland Council's engineering standards."
This is not optional. Until the peer review is completed and any issues are resolved, S224c cannot be issued and titles cannot be released.
What the Peer Reviewer Checks
A thorough CPEng peer review of a subdivision engineering design covers the following areas.
Stormwater design. The reviewer checks the hydrological methodology (TP108 compliance in Auckland), the design storm selection, the pre-development and post-development runoff calculations, the detention sizing, and the stormwater conveyance network. Common review findings include incorrect curve numbers for the site's soil type, use of the wrong TP108 rainfall zone, and detention systems that have not been tested across the full range of storm durations.
Flood hazard assessment. If the site is within or adjacent to a flood hazard overlay, the reviewer assesses the flood modelling methodology, the model inputs (terrain data, boundary conditions, roughness values), and the resulting flood extents and levels. For 2D HEC-RAS models, the reviewer will check the mesh resolution, the terrain processing, and whether the boundary conditions are appropriate for the catchment. At Glendale Road in Henderson, the 2D flood model was subject to CPEng peer review as a consent condition, and the review confirmed that the site-specific modelling had correctly identified overland flow paths that the regional mapping had missed.
Water supply design. The reviewer checks the hydraulic model, the pipe sizing, the pressure at the most disadvantaged lot, and the firefighting supply compliance with SNZ PAS 4509:2008. A common finding is that the design achieves minimum pressure only when the full ring main is completed, which is problematic for staged subdivisions.
Wastewater design. The reviewer checks pipe grades, pipe sizing, manhole spacing, and the downstream capacity assessment. Where on-site wastewater systems are proposed, the reviewer assesses whether the soil conditions support the proposed disposal method.
Roading and earthworks. The reviewer checks pavement design, geometric design (sight distances, intersection layout), and earthworks volumes. For sites with geotechnical constraints, the reviewer assesses whether the geotechnical recommendations have been correctly incorporated into the engineering design.
Documentation and Producer Statements. The reviewer confirms that the design documentation is complete, internally consistent, and accompanied by the appropriate Producer Statements (PS1 for design). A design that is technically correct but poorly documented will still generate review comments.
How HAL Projects Manages the Review Process
HAL Projects is a development management firm that coordinates the engineering and planning processes for residential subdivisions in the Auckland and Waikato regions. For projects managed by HAL Projects, the CPEng peer review is typically coordinated through HAL's own quality assurance process, with the peer reviewer selected from HAL's panel of approved reviewers.
The practical effect for the design engineer is that the peer review is not a final check at the end of the project. It is an iterative process. The peer reviewer issues a report identifying any concerns or non-compliances, and the design engineer must respond to each item with either a design amendment or a technical justification for the existing approach. This response-and-resolution cycle can add weeks or months to the project programme if the original design has significant issues.
For SAE's work through HAL Projects, including the Glendale Road project and developments at Clematis Avenue in Hamilton, we structure our design documentation to anticipate the peer review process. This means documenting all design assumptions explicitly, providing full calculation sets (not just summary results), and referencing the specific clauses of the applicable standards that each design element complies with.
How to Design for Peer Review
The most effective way to manage the peer review process is to design as if the peer reviewer is reading over your shoulder. In practice, this means the following.
Document every assumption. State the vertical datum, the soil type, the curve number, the design storm, the pre-development land cover, the time of concentration, and the design standard for every element. A peer reviewer who has to infer your assumptions will generate queries. A peer reviewer who can see your assumptions stated clearly will either agree with them or raise a specific technical objection that you can respond to directly.
Provide full calculation sets. Do not submit only the summary output from your design software. Provide the input parameters, the model configuration, and enough intermediate results for the reviewer to trace the logic from input to output. For stormwater detention sizing, this means providing the full set of hydrographs for each storm duration tested, not just the critical duration result.
Reference the standards explicitly. When your design complies with a specific clause of the Auckland Council Code of Practice, or a specific section of TP108, cite it. When your design deviates from the standard (for a documented engineering reason), state the deviation and the justification. The peer reviewer is checking compliance; make it easy for them to confirm.
Address known sensitivities upfront. If you know a particular aspect of the design is marginal or requires engineering judgement (for example, a curve number selection for a mixed soil type, or a time of concentration estimate for an unusually shaped catchment), address it in the design report rather than waiting for the reviewer to raise it. A proactive explanation is far more efficient than a reactive response.
What Happens When the Review Finds Issues
Peer review findings range from minor documentation clarifications to fundamental design errors that require redesign. Minor findings (missing drawing references, unclear notation, minor calculation corrections) are resolved quickly. Major findings (incorrect flood levels, undersized detention, non-compliant water supply pressure) require design amendments, revised drawings, and potentially revised consent conditions.
The cost of a major review finding is not just the engineering fee to revise the design. It includes the delay to the S224c programme, the developer's carrying costs during that delay, and the potential need to re-engage the council for approval of the amended design. For a 20-lot subdivision, a three-month delay caused by a peer review redesign cycle can cost the developer tens of thousands of dollars in finance charges alone.
This is why designing for peer review from the outset is not a matter of professional pride. It is a direct cost-saving measure for the developer.
CPEng peer review is a consent condition on most Auckland subdivisions, and for projects managed through HAL Projects it is embedded in the quality assurance process. Design for it from the start: document every assumption, provide full calculations, cite the applicable standards, and address known sensitivities upfront. A clean peer review saves weeks of programme time and avoids costly redesign cycles.