Nms-Rma-Priority-Information-Collection-Final

National Monitoring System for the RMA Priority Information Collection

2014/2015 Financial Year – with Supplementary Guidance October 2014

Improving our resource management system: A discussion document1

This report may be cited as:

Ministry for the Environment 2014. National Monitoring System for RMA Priority Information Collection2014/2014 financial year– with Supplementary GuidanceOctober 2014

Update published in October 2014 by the
Ministry for the Environment
ManatūMōTeTaiao
PO Box 10362, Wellington 6143, New Zealand

Publication number: ME 1161

This document is available on websites of the Ministry for the Environment

Contents

Introduction

Technical instructions

Questions/support

Appendix 1 – Tabulated information

Section 1.1 – Policy statement and plan reviews

Section 1.2 – Preparation of policy statements and plans, changes and variations

Section 1.3 – Efficiency and effectiveness monitoring

Section 1.4 – Iwi/hapū planning documents

Section 1.5 – Resource consents

Appendix 2 – Annual summary information

Section 2.1 – Iwi involvement

Section 2.2 – Resource consents

Section 2.3 – Customer satisfaction

Section 2.4 – Notices of requirement (territorial authorities only)

Section 2.5 – Complaints, monitoring and enforcement resourcing

Section 2.6 – Other monitoring

Section 2.7 – Complaints and monitoring

Section 2.8 – Enforcement

NMS Priority Information Collection 2014/2015 Financial Year – with Supplementary Guidance October2014 1

Introduction

The Ministry for the Environment has been working with councils to develop a National Monitoring System(NMS) to improve monitoring of Resource Management Act 1991 (RMA) functions and processes. We are progressing with a staged implementation of the NMS, starting with collection of a priority information set for the 2014/15 financial year. The priority information set replaces the RMA Survey of Local Authorities and represents a step change towards the NMS.

The NMS will align monitoring arrangements locally and nationally, and improve the range, frequency and quality of RMA implementation information the Ministry and local authorities collect. Capturing more detailed information across key RMA processes will provide a more comprehensive and continuous evidence base to support more detailed analysis and understanding of RMA policy and implementation.

A priority information set is required to be reported by each local authority for the period 1July 2014 to 30 June 2015 (the 2014/15 financial year). The priority information set is required to be reported to the Ministry by 31 July 2015. The information should be reported electronically to .

While the priority information set closely reflects the information previously captured by the RMA Survey of Local Authorities, it requires a different response. A key change is the requirement to report information for each individual plan-making process and each resource consent, rather than a summary. The collection of other information remains in a similar format to the RMA Survey while work is done during 2014/15 to scope and define a wider information set. Scoping work will also include an assessment of the impact on councils to capture the wider information set and to report information electronically in future.

Technical instructions

Appendices 1 and 2 of this document include a definition of each data field required and explain the appropriate response. Appendix 1 outlines the tabulated information required for each individual plan-making process and each resource consent. Appendix 2 outlines the annual summary information required. The information requirements will also be provided to your local authority in a Microsoft Excel template. In the Microsoft Excel template each of the required data fields will be in a separate column.

Information can be provided as a data extract from your systems, provided it is in a Microsoft Excel or CSV format and agreed ahead of time with Ministry officials. Where only partial information can be extracted from systems, it may need to be supplemented with the additional information before it is submitted. Alternatively, all information can be manually entered into the Microsoft Excel template provided.

It is important to ensure that the data fields reported can be matched to those in the Microsoft Excel template. Where possible, the data fields that were not relevant to a process should be reported as Not Applicable, rather than being left blank.By reporting the information required, your local authority is declaring that the information is true and correct to the best of its knowledge and acknowledging that the information reported is official information and subject to the Official Information Act 1982.

Questions/support

Ministry officials will work closely with each local authority throughout the 2014/15 financial year to support the capture and reporting of information. In the meantime, if you have questions or need assistance please email or phone the Resource Management Performance and Monitoring team on 04 439 7490.

NMS Priority Information Collection 2014/2015 Financial Year – with Supplementary Guidance October2014 1

Appendix 1 – Tabulated information

Section 1.1 – Policy statement and plan reviews

This section requires the reporting of information on each policy statement or plan that is reviewed in full under RMA section 79. Partial reviews will be identified separately through Section 1.2. Information is required for each full review that was underway, started or completed during the 2014/15 financial year.

Data field

Description of data field

Example

Name of review

The name of the policy statement or plan undergoing a full review of a policy statement or plan. This needs to be unique and will be used to identify it from other reviews. (Open text).

Review of the Eureka District Plan 2005

Date review commenced

The date that a decision was made to advance the full review, through resolution of council or other formal decision. (Date).

1/09/2013

Review outcome

Confirmation of whether or not the policy statement or plan required alteration following the full review. Acceptable responses are:

Requires alteration

Does not require alteration

Section 1.2 – Preparation of policy statements and plans, changes and variations

This section requires the reporting of information on each process to prepare, change, or vary a policy statement or plan or to vary a change. Information is required for each process that was underway, started or completed during the 2014/15 financialyear. In the Microsoft Excel template, a row of data is required for each separate planning process.

Guidance notes
This section does not require the reporting of information for plan processes that were completed prior to 1 July 2014.
This section does not require the reporting of information on amendment processes undertaken via clause 16(2) or clause 20A of Schedule 1. That is, where such an alteration is of minor effect, or is to correct any minor errors.
If a planning process is separated part way through, for example, decisions are released sequentially or sections of a plan become operative at different times, councils are asked to add new rows of data into the Microsoft Excel template. Where data fields are duplicated for separated parts of a process they can be copied into the new row/s.
When reported, the data for this section is required to be up to date as at 30 June 2015. Data fields should be populated (either with an appropriate response or Not Applicable) for all events that occurred prior to 1 July 2015. Blanks following the most recent event will indicate those events have not yet occurred. Further data fields for those processes will be progressively filled in subsequent data collections.

Data field

Description of data field

Example

Guidance

Name of the planning process

The name of the proposed policy statement or plan, change or variation. This needs to be unique and will be used to identify it from other processes. (Open text).

Plan Change 3 to the Eureka District Plan

Type of planning process

The type of proposed policy statement or plan, change or variation. Acceptable responses are:

Proposed plan (new)

Variation to proposed plan

Change to operative plan

Variation to a change

Private plan change request (accepted by council)

Private plan change request (adopted by council)

Change to operative plan

Part of a rolling review

If changing an operative plan or varying a change, whether the change or variation is part of a rolling review. (Yes/No).

Yes

Type of planning document

What type of planning document(s) the planning process relates to. Acceptable responses are:

Regional policy statement

Combined regional policy statement with another regional council

Regional plan

District plan

Combined regional policy statement and regional plan(s)

Combined regional plan with another regional council

Combined regional policy statement, regional plan(s) and district plan(s)

Combined regional plan(s) and district plan(s)

Combined district plan with another local authority

District plan

Extent of provisions under planning process

The name of the parts, sections, policies and/or rules covered by the proposed policy statement or plan, change or variation. Reported at the highest level (eg, Sections 3 and 10 if it included changes to a number of policies within those sections). (Open text).

Eg 1 - Sections 3 and 10

Eg 2 – Entire Plan

Subject matter covered

The subject matter of the proposed policy statement or plan, change or variation. (Open text).

Eg 1 - Residential density and Infrastructure

Eg 2 – Technical amendments & corrections

Reason for planning process

Confirmation of the reason(s) for the proposed policy statement or plan, change or variation. Acceptable responses are (can be multiple):

To be consistent with or give effect to a national instrument/s

s79 review no alteration required (but notified)

s79 review alteration required

Section 35 monitoring identified issue for change

Result from state of the environment monitoring

New issue emerged

To give effect to a regional policy statement

To be consistent with a regional plan

To be consistent with a water conservation order

To address Treaty of Waitangi settlements

Community driven based on their concerns/aspirations

Technical amendment

Environment Court direction

Decision on a private plan change request

Other

To be consistent with or give effect to a national instrument/s

New issue emerged

National instrument driver

If the reason for the proposed policy statement or plan, change or variationwas a need to be consistent with, or give effect to, a national instrument, confirm which instrument it related to. Acceptable responses are (can be multiple):

Not Applicable (did not relate to a national instrument)

NES Air Quality

NES Sources of Human Drinking Water

NES Telecommunications Facilities

NES Electricity Transmission

NES Assessing and Managing Contaminants in Soil to Protect Human Health

NPS Electricity Transmission

NPS Renewable Electricity Generation

NPS Freshwater Management

Water conservation order

Section 360 Regulations

New Zealand Coastal Policy Statement

NPS Electricity Transmission

National instrument driver – all or part

If the proposed policy statement or plan, change or variationwas driven by a need to be consistent with or give effect to a national instrument(s), confirm whether this reflected all or part of the instrument(s). Acceptable responses are:

All

Part

Not Applicable (did not relate to a national instrument)

Part

National instrument driver part(s)

If the proposed policy statement or plan, change or variationwas driven by a need to be consistent with or give effect to part of a national instrument(s), name the sections or policies of the instrument driving the process. (Open text or Not Applicable).

Policies 1, 2, 3 and 5.

Date process commenced

The date that the decision was made to proceed with the proposed policy statement or plan, change or variation, through resolution of council or other formal decision. (Date).

10/01/2014

If there was no formal decision to proceed with the plan change, the date can be approximate but a date is required.

This date will be used as the start date to calculate the total time taken for the planning process.

Pre-notification consultation

Confirmation of what pre-notification consultation was undertaken. Acceptable responses are:

No pre-notification consultation undertaken

Targeted consultation with landowners or other stakeholders

Targeted consultation with iwi/hapū

Public feedback on issues and options

Public feedback on draft document

Community collaboration

Other

No pre-notification consultation undertaken

These options are for pre-notification consultation that was undertaken over and above the statutory requirements under clause 3(d) of Schedule 1.

Date Notified

Date the proposed policy statement or plan, change or variationwas publicly notified, as per clause 5 or clause 26 of Schedule 1. (Date).

07/06/2014

Section 32 evaluation

Whether the section 32 evaluation report identified how it was determined which costs and benefits would be quantified. (Yes/Noor Not Applicable).

Yes

To answer yes, the evaluation report would include an explanation of which costs and benefits have been quantified or not quantified and would include an explanation of why. Yeswould indicate that the evaluation has met the new section 32(2)(b).

If the new section 32 requirements do not apply to a planning process, this data field can be Not Applicable.

Environment Court Order under s86D for rules to apply early

Whether your local authority applied to the Environment Court under section 86D for rule(s) to apply earlier. (Yes/No).

Council resolution under s86B to delay rules coming into effect

Whether your local authority made a resolution under section 86B to delay rule(s) coming into effect until the proposed plan becomes operative. (Yes/No).

Date Submissions close

Date when submissions on the proposed policy statement or plan, change or variationclosed as per clause 5(3) of Schedule 1. (Date).

08/07/2014

Date of public notice of the availability of Summary of submissions Notified

Date public notice was given of the availability ofthe summary of submissions were notified, as per clause 7 of Schedule 1. (Date).

10/09/2014

Date Further submissions close

Date further submissions closed under clause 7(d) of Schedule 1. (Date).

11/09/2014

Date Pre-hearing meetings start

First day of pre-hearing meetings under clause 8AA(1) of Schedule 1. (Date or Not Applicable).

15/11/2014

Date Pre-hearing meetings conclude

Last day of pre-hearing meetingsunder clause 8AA(1) of Schedule 1. (Date or Not Applicable).

17/11/2014

Pre-hearing meeting days

Number of pre-hearing days in total. Rounded to the nearest half day (eg, a hearing held on one evening should be recorded as 0.5) and exclude days where no physical meeting occurred. (Number or Not Applicable).

Date Mediation starts

First day of mediation under clause 8AA(3) of under the Schedule 1. (Date or Not Applicable).

Not Applicable

Date Mediation concludes

Last day of mediation under clause 8AA(3) of Schedule 1. (Date or Not Applicable).

Not Applicable

Mediation days

Number of mediation days in total. Rounded to the nearest half day (eg, a hearing held on one evening should be recorded as 0.5) and exclude days where no physical meeting occurred. (Number or Not Applicable).

Not Applicable

Date Hearings start

First day of hearings. (Date or Not Applicable).

15/01/2015

Date Hearings conclude

Last day of hearings. (Date or Not Applicable).

25/01/2015

Hearing days

Number of hearing days in total. Rounded to the nearest half day (eg, a hearing held on one evening should be recorded as 0.5) and exclude days where no physical hearing occurred. (Number or Not Applicable).

5.5

Site visits should be included as part of hearing days.

Not Applicable should be used where no hearing was required.

Date Decisions notified

Date the decision on the provisions and matters raised in submissions was notified, as per clause 10(4)(b), of Schedule 1. (Date).

25/02/2015

Date Plan change withdrawn

Date on which the proposed policy statement or plan, change or variationwas withdrawn under clause 8D of Schedule 1. (Date or Not Applicable).

Not Applicable

Date becomes becameoperative in part

Date the proposed policy statement or plan, change or variation became operative in part under clause 1720 of Schedule 1. (Date or Not Applicable).

Not Applicable

If parts became operative at different times, then a Date became operative in part is required for each part.

Eachdate should link to the name and subject matter of the part identified in the data field Parts/section/policies that became operative in part.New rows should be added as per guidance notes on page 6 of this document.

Parts/section/policies made that became operative in part

The name and subject matter of the parts that became operative under clause 1720 of Schedule 1. (Open Text or Not Applicable).

Not Applicable

Date became operative in full

Date the proposed policy statement or plan, change or variationbecame fully operative as perunder clause 20 of Schedule 1. (Date).

25/03/2015

Total council costs

The best estimate of total council costs relating to the planning process on completionto operative in full. This is total cost for the period between the dates given in the fields Date process commenced and Date became operative in full. Include all cost including staff, consultants and overheads. ($).

$750,000

Reporting of total council costs is only required for completed processes.

Cost data for processes under way will need to be captured by councils for future reporting.

Council Costs – pre-notification

Optional data field.

The best estimate of total council costs relating to the planning process for the period between the dates given in the data fields Date process commenced and Date Notified. Include all cost including staff, consultants and overheads. ($).

$150,000

Reporting on these data fields is optional. Data fields have been added to the right hand end of the Microsoft Excel template alongside the data field Comment/summary of the process.

These data fields allow costs to be separated across the fundamentally distinct phases of plan-making.

If more than a reasonable effort is required to provide a best estimate of costs split by stage, the total cost can be reported.

Reporting of costs is only for completed stages.

Cost data for stages under way will need to be captured by councils for future reporting.

Council Costs – notification to decisions

Optional data field.

The best estimate of total council costs relating to the planning process for the period between the dates given in the data fields Date Notified and Date Decisions notified. Include all cost including staff, consultants and overheads. ($).

$250,000

Council Costs – decisions to operative