This checklist is written for small to mid-scale residential projects—infill, subdivisions, terraces, and renovations—operating under Hamilton and Waikato conditions. Use it as a live document, not a one-off read.
1) Macro & policy check (before land is unconditional)
- District Plan zoning and overlays reviewed (density, height, hazards)
- Infrastructure growth areas and timing understood
- Likely Development Contributions identified and timed
- Market demand and exit strategy tested (sale vs rental)
Hamilton note: zoning may allow yield, but services and stormwater often decide feasibility.
2) Site due diligence (before concept design)
- LIM reviewed (flooding, hazards, services)
- Title checked (covenants, easements, consent notices)
- Access and servicing feasibility confirmed
- Neighbour sensitivities identified early
3) Feasibility & concept design
- Yield tested against planning and infrastructure limits
- Stormwater strategy considered at layout stage
- Geotechnical risk identified (especially clay soils)
- Indicative DCs, build cost, finance and contingencies modelled
- Two options tested: compliant vs higher-yield (risk-priced)
4) Consultant team & roles
- Planner aligned to consent pathway
- Surveyor engaged early (especially for subdivision)
- Architect/designer briefed on compliance priorities
- Civil + geotech coordination established
- Legal and accounting advice aligned to structure and tax
5) Consents & approvals
- Resource consent pathway confirmed
- Written approvals sought where beneficial
- Building consent drawings coordinated and complete
- RBW responsibilities clearly allocated to LBPs
- Engineering approval conditions scoped and programmed
6) Pre-construction readiness
- Scope frozen before signing contracts
- Provisional sums minimised and stress-tested
- Programme aligned to inspection sequence
- Stormwater, services and foundation details resolved
- Cost and time contingencies locked in
7) Construction phase control
- Inspection schedule managed proactively
- Variations tracked and approved in writing
- RBW Records of Work collected progressively
- Compliance documentation filed during the build
- Programme buffers protected where possible
8) CCC & handover preparation
- Final inspections booked early
- All documentation compiled (RoWs, certificates, approvals)
- Outstanding fees/levies cleared
- Practical completion items resolved
- Handover pack prepared (warranties, manuals, maintenance)
9) Settlement & post-settlement risk
- CCC issued and on file
- Buyer queries anticipated and answered clearly
- Defects reporting process defined
- Maintenance period managed professionally
- Communication logged and consistent
10) Review & repeat
- Lessons learned documented
- Cost and time variances analysed
- Consultant and contractor performance reviewed
- Templates updated for the next project
Why this checklist works in Hamilton
Hamilton projects sit at the intersection of:
- intensification policy,
- constrained infrastructure, and
- increasingly risk-aware buyers and insurers.
Projects that follow a joined-up process tend to:
- consent faster,
- cost less to fix later, and
- sell or rent with fewer surprises.
Use this checklist as a live tool
The most successful developers:
- revisit this list at every stage gate,
- treat compliance as value protection, not friction,
- and design for delivery—not just approval.