s92 Risk Scan
Predict likely s92 further-information requests before lodging your consent application.
A section 92 (s92) request under the Resource Management Act 1991 is a council demand for further information to process a resource consent application. Receiving an s92 stops the consent clock and typically delays a project by 20–40 working days.
The s92 Risk Scan analyses your proposed application context against a database of 25 known s92 triggers and flags the highest-risk areas before you lodge.
Using the s92 Risk Scan
- 1Select the s92 Risk Scan tab in the Consent Planner.
- 2Enter the property address and proposed development type (e.g., 3-lot subdivision, 6-unit residential development).
- 3Optionally, list any known overlay conditions (these are pre-populated if you have already run the Pre-Application Package).
- 4Click Scan for Risks.
- 5Review the flagged triggers. Each trigger includes: the s92 category, the most likely council question, and the required supporting evidence.

Trigger Categories
| Category | Risk Level | Common Triggers |
|---|---|---|
| Infrastructure Capacity | High | Water pressure confirmation, wastewater capacity letter from Watercare or City Care |
| Traffic & Access | High | ITA (Integrated Traffic Assessment) required above threshold trip generation |
| Contamination | High | HAIL-listed site without PSI report, unexplained fill material |
| Noise & Amenity | Medium | Proposed residential adjoining business zone without acoustic assessment |
| Heritage & Character | Medium | Overlay-listed site without heritage impact assessment |
| Geotechnical | Medium | Steep sites, coastal proximity, or ECan liquefaction zone without geotech report |
| Ecology | Medium | SEA proximity without ecological impact assessment |
| Stormwater | Low-Medium | Pre-1990 development without stormwater management plan |
Pre-empting s92
The most effective way to avoid an s92 is to include all required technical assessments upfront. Use the Risk Scan results as a checklist for your application package. Each flagged risk includes the specific RMA provision and typical council wording to help you brief your technical specialists.
Found an error? Open an issue on GitHub