This report may be cited as:
Ministry for the Environment. 2015. National Monitoring System. Information Requirements.
Guidance for the 2015/2016 financial year. Wellington: Ministry for the Environment.
Published in December 2015 by the
Ministry for the Environment
Manatū Mō Te Taiao
PO Box 10362, Wellington 6143, New Zealand
ISBN: 978-0-908339-18-1
ME: 1221
Publication number:
© Crown copyright New Zealand 2014
This document is available on websites of the Ministry for the Environment www.mfe.govt.nz
Contents
Background
4
Purpose of this guide
4
Changes to the data requirements
4
Required format of data
5
Data due date
6
1.0
Part A – Policy & plan making and resource consent processes
Section 1.1 – Policy statement and plan full 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
7
7
7
14
15
15
2.0
Part B – Annual summary information
Section 2.1 – Iwi involvement
Section 2.2 – Staff working on preparation of policy statements and plans,
changes & variations
Section 2.3 – Staff processing resource consents
Section 2.4 – Customer satisfaction
Section 2.5 – Notices of requirement (territorial authorities only)
Section 2.6 – Staff working on complaints, monitoring and enforcement
Section 2.7 – Other monitoring
Section 2.8 – Complaints and monitoring
Section 2.9 – Enforcement
27
27
29
30
31
31
31
33
34
35
Background
The National Monitoring System (NMS), which has replaced the RMA biennial survey of local
authorities, is the method whereby the Ministry for the Environment annually captures
information on the implementation of the Resource Management Act 1991 (RMA).
This monitoring information allows us to understand whether the various functions, tools and
processes included within the RMA are achieving what they were intended to, and to
determine what changes might be necessary to ensure the desired outcomes are achieved.
The NMS has now entered its second year of information gathering. Councils are required to
submit the NMS information requirements for the period 1 July 2015 to 30 June 2016 to the
Ministry by Friday 29th July 2016.
Details about the NMS project as a whole can be found on the Ministry’s website:
http://www.mfe.govt.nz/rma/rma-monitoring/national-monitoring-system.
Purpose of this guide
This guidance material should be read in conjunction with the Microsoft Excel Template
(Template), which has been already been provided to your local authority (however a copy can
be found on the website noted above).
This guidance material and the Template outline the data requirements for the current
financial year, as well as appropriate responses to each data field. The section numbering,
data fields and appropriate responses contained within the Template are replicated in this
guidance for easy reference. This document provides detailed guidance with respect to those
data fields where clarification is required (particularly in areas where we have had a number of
queries and/or in areas we have found that the data that was provided in relation to the
2014/15 data collection was inadequate and/or inaccurate).
If you have questions or need assistance, please email nms@mfe.govt.nz or phone the
National Monitoring System team on 04 439 7490.
Changes to the data requirements
The information requirements for the 2015/16 financial year closely reflect the information
required for the previous financial year (2014/15). This is to provide continuity and help make
the NMS part of normal council practice. There are, however, a few changes and
improvements that have been made to the data requirements. These changes are as a result of
the Resource Management Amendment Act 2013, feedback from councils and our data testing
process.
The changes are highlighted clearly in this guidance material and also in the Template
provided, and are summarised in the table below:
4
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Section
1.2 Preparation of policy
statements and plans, changes
and variations
New Data Requirement
Comment on total council costs.
Comment/summary or current
status of process.
1.5 Resource consents
Legal description (appellation),
GPS coordinates or GIS shape
files
Response to section 92(1)
request ie, whether the
applicant agreed to provide the
information.
Date council notified applicant
that there are affected persons
and the date that the response
to this was received.
Deferral under section 91A, and
date continued following section
91A deferral.
2.0 Annual summary information
Staff working on preparation of
policy statements, plans,
changes and variations.
Reason for Change
This has been added to provide
some context to how the total
council costs are determined by
each local authority.
This is no longer an optional
data field. This data field
requires the status of the
planning process as at 30 June
2016 to be outlined.
New data requirement. This will
allow for spatial analysis.
This has been added as an
optional data field. This adds
valuable information in terms of
the provision of further
information.
This has been added as an
optional data field. It is noted
that this adds valuable
information in terms of the
resource consent timeframes.
Added in relation to changes to
the RMA that came into force on
3 March 2015. Only relates to
those applications lodged after
this date.
This is a new data set which was
not in the previous year data
requirements.
Required format of data
The Template demonstrates the format by which we expect to receive the data required.
Information can be provided as a data extract from your system provided it is in Microsoft
Excel or CSV format. Where only partial information can be extracted from your system, the
additional information will need to be entered manually before the data set is submitted.
Alternatively, all information can be manually entered into the Template provided.
It is important to ensure the data fields reported can be matched to those in the Template.
All data fields should be populated with one of the acceptable responses outlined.
If you have specific comments to make regarding your data, please add a column at the end of
the relevant data sheet. It is preferable not to use the Microsoft Excel “comments” tool
embedded within the relevant cells as these are difficult to reveal through our data validation
process.
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
5
Note:
 all data cells should be populated with an “Acceptable Response” (unless otherwise
stipulated)
 there should be NO blank cells (unless otherwise stipulated)
 if you have copied and pasted data from your own database system, it is advised that you
paste the data as “text only” (ie, do not paste the underlying formatting from your
database into the document). Please ensure that any columns with date information are
formatted as “date”, and other columns that contain numbers and/or words are formatted
as “general”
 all date data must be in the format: dd/mm/yyyy (please do not use the American date
format).
Data due date
The 2015/2016 NMS data set is required to be reported to the Ministry by Friday 29 July 2016.
The information should be reported electronically to nms@mfe.govt.nz.
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.
6
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
1.0 Part A – Policy and plan making
and resource consent processes
Section 1.1 – Policy statement and plan full reviews
This section requires the reporting of information on each full review of any policy statement or plan
under section 79(4) of the Resource Management Act 1991 (RMA).
Information is required for each full review that was under way, started or completed during the
2015/16 financial year (1 July 2015 to 30 June 2016).
It should be noted that Partial and/or Rolling reviews (as recognised under s79(1)) are identified
separately through Section 1.2.
Data field
1.1.1
Name of review
Description of data field
The name of the policy statement or plan undergoing a
full review under s79(4). This needs to be unique and will
be used to identify it from other reviews.
1.1.2
Date review
commenced
1.1.3
Review outcome
The date that a decision was made to advance the full
review, through resolution of council or other formal
decision.
Confirmation of whether or not the policy statement or
plan required alteration following the full review.
Acceptable Response
Open Text
[eg, Review of the
Eureka District Plan
2005]
Date [dd/mm/yyyy]



Requires
alteration
Does not require
alteration
Review not yet
completed
Section 1.2 – Preparation of policy statements and plans, changes
and variations
This section requires the reporting of information on each process to prepare or change a policy
statement or plan, or to make a variation to a proposed policy statement or plan change. Information
is required for each process that was under way, started or completed during the 2015/16 financial
year (ie, between 1 July 2015 and 30 June 2016). In the Microsoft Excel Template (Template), a row
of data is required for each separate planning process. All data fields should be populated with an
appropriate response for all events that occurred within the financial year.
For planning processes that have started, or are underway, but not yet completed, each data field
(until the most recent event, and including those events that occurred prior to the 2015/2016
financial year) will need to be populated with an appropriate response (as at 30 June 2016) and the
remainder of the cells in the row are to remain blank. This will indicate that those events have not
yet occurred. In this case, commentary should be added in data field 1.2.47 (comment/summary of
the process) explaining the status of the planning process as at 30 June 2016. Further data fields for
those processes will be progressively filled in subsequent data collections.
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 horizontal
rows of data into the Template. Where data fields are duplicated for separated parts of a process
they can be copied into the new row(s).
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
7
Please note that this section does not require the reporting of information on amendment processes
under 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.
Data field
Description of data field
1.2.1
Name of the
planning
process
1.2.2
Type of
planning
process
The name of the proposed
policy statement or plan,
change or variation.
The type of proposed policy
statement or plan, change
or variation.
Acceptable Responses (please
leave cell blank if the event has
not yet occurred)
Open Text
[eg, Plan Change 3 to the
Eureka District Plan]






1.2.3
Part of a rolling
review
1.2.4
Type of
planning
document
1.2.5
Extent of
provisions
under planning
process
8
If changing an operative
plan or varying a change,
whether the change or
variation is part of a rolling
review (under s79(1)).
What type of planning
document(s) the planning
process relates to.
The name of the parts,
sections, policies and/or
rules covered by the
proposed policy statement
or plan, change or variation.


Guidance
This needs to be unique
and will be used to
identify it from other
processes.
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)
Yes
No


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
Open Text
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Reported at the highest
level (eg, Sections 3 and
10 if it included changes
to a number of policies
within those sections).
Data field
Description of data field
1.2.6
Subject matter
covered
The subject matter of the
proposed policy statement
or plan, change or variation.
1.2.7 – 1.2.12
Reason for
planning
process
Confirmation of the
reason(s) for the proposed
policy statement or plan,
change or variation.
1.2.13
National
instrument
driver 1
If the reason for the
proposed policy statement
or plan, change or variation
was a need to be consistent
with, or give effect to, a
national instrument,
confirm which instrument it
related to.
Acceptable Responses (please
leave cell blank if the event has
not yet occurred)
Open Text
[eg, Residential density and
Infrastructure]
 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
 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
Guidance
Note: There can be
multiple responses. For
such cases, multiple
columns are provided in
the Template. Use a
separate column for
each response, adding
any additional columns if
required).
Where there is more
than one National
Instrument Driver,
multiple columns are
provided (1.2.16-1.2.18)
to record each national
instrument and its two
related fields (add
another set of three
columns if additional are
required).
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
9
Data field
Description of data field
1.2.14
National
instrument
driver 1 – all or
part
If the proposed policy
statement or plan, change
or variation was 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).
1.2.15
National
instrument
driver 1 part(s)
If the proposed policy
statement or plan, change
or variation was 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.
National Instrument Driver 2


1.2.19
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 [dd/mm/yyyy]
1.2.20-1.2.22
Pre-notification
consultation
Confirmation of what prenotification consultation
was undertaken.

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
1.2.16 – 1.2.18
Acceptable Responses (please
leave cell blank if the event has
not yet occurred)
Statement
 All
 Part
 Not Applicable (did not
relate to a national
instrument)






1.2.23
Date Notified
10
Date the proposed policy
statement or plan, change
or variation was publicly
notified, as per clause 5 or
clause 26 of Schedule 1.
Guidance
Open Text
Not Applicable
Date [dd/mm/yyyy]
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Additional columns are
included in the Template
to record a 2nd National
Instrument Driver. If
there are more than
two, an additional set of
three columns will need
to be added.
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.
These options are for
pre-notification
consultation that was
undertaken over and
above the statutory
requirements under
clause 3(d) of Schedule
1.
Multiple columns are
provided to record
different types of
consultation undertaken.
Add any further columns
if required.
Data field
Description of data field
1.2.24
Section 32
evaluation
Whether the section 32
evaluation report identified
how it was determined
which costs and benefits
would be quantified.
1.2.25
Environment
Court Order
under s86D for
rules to apply
early
1.2.26
Council
resolution
under s86B to
delay rules
coming into
effect
1.2.27
Date
Submissions
close
Whether your local
authority applied to the
Environment Court under
section 86D for rule(s) to
apply earlier.


Yes
No
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 when submissions on
the proposed policy
statement or plan, change
or variation closed as per
clause 5(3) of Schedule 1.
Date public notice was given
of the availability of the
summary of submissions, as
per clause 7 of Schedule 1.
Date [dd/mm/yyyy]
Date further submissions
closed under clause 7(d) of
Schedule 1.
Date [dd/mm/yyyy]
First day of pre-hearing
meetings under clause
8AA(1) of Schedule 1.


Date [dd/mm/yyyy]
Not Applicable
Last day of pre-hearing
meetings under clause
8AA(1) of Schedule 1.


Date [dd/mm/yyyy]
Not Applicable
Number of pre-hearing days
in total.


Number
Not Applicable
1.2.28
Date of public
notice of the
availability of
Summary of
submissions
1.2.29
Date Further
submissions
close
1.2.30
Date Prehearing
meetings start
1.2.31
Date Prehearing
meetings
conclude
1.2.32
Pre-hearing
meeting days
Acceptable Responses (please
leave cell blank if the event has
not yet occurred)
 Yes
 No
 Not Applicable
Guidance
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. Yes
would 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.
Date [dd/mm/yyyy]
Rounded to the nearest
half day (eg, a hearing
held on one evening
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
11
Data field
Description of data field
Acceptable Responses (please
leave cell blank if the event has
not yet occurred)
Guidance
should be recorded as
0.5) and exclude days
where no physical
meeting occurred.
1.2.33
Date Mediation
starts
1.2.34
Date Mediation
concludes
1.2.35
Mediation days
First day of mediation under
clause 8AA(3) of Schedule 1.


Date [dd/mm/yyyy]
Not Applicable
Last day of mediation under
clause 8AA(3) of Schedule 1.


Date [dd/mm/yyyy]
Not Applicable
Number of mediation days
in total.


Number
Not Applicable
1.2.36
Date Hearings
start
1.2.37
Date Hearings
conclude
1.2.38
Hearing days
First day of hearings.


Date [dd/mm/yyyy]
Not Applicable
Last day of hearings.


Date [dd/mm/yyyy]
Not Applicable
Number of hearing days in
total.


Number
Not Applicable
1.2.39
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 on which the proposed
policy statement or plan,
change or variation was
withdrawn under clause 8D
of Schedule 1.
Date the proposed policy
statement or plan, change
or variation became
operative in part under
clause 20 of Schedule 1.
The name and subject
matter of the parts that
became operative under
clause 20 of Schedule 1.


Date [dd/mm/yyyy]
Not Applicable


Date [dd/mm/yyyy]
Not Applicable


Date [dd/mm/yyyy]
Not Applicable


Open Text
Not Applicable
1.2.40
Date plan
change
withdrawn
1.2.41
Date became
operative in
part
1.2.42
Parts/section/p
olicies that
became
operative in
12
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Rounded to the nearest
half day (eg, a mediation
held on one evening
should be recorded as
0.5) and exclude days
where no physical
meeting occurred.
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. Site
visits should be excluded
from the hearing day
calculation.
Not Applicable should be
used where no hearing
was required.
If parts became
operative at different
times, then a Date
became operative in part
is required for each part.
Multiple columns in the
Template are provided
to record the date and
its related field (add
another set of two
Data field
part
1.2.43
Date became
operative in
part 2
1.2.44
Parts/section/p
olicies that
became
operative in
part 2
1.2.45
Date became
operative in full
1.2.46
Total council
costs
1.2.47
Comment of
total council
costs
1.2.48
Total council
staff time
1.2.49
Comment/sum
mary of the
process
1.2.50
Description of data field
Acceptable Responses (please
leave cell blank if the event has
not yet occurred)
Date the proposed policy
statement or plan, change
or variation became
operative in part under
clause 20 of Schedule 1.
The name and subject
matter of the parts that
became operative under
clause 20 of Schedule 1.


Date [dd/mm/yyyy]
Not Applicable


Open Text
Not Applicable
Date the proposed policy
statement or plan, change
or variation became fully
operative under clause 20 of
Schedule 1.
The best estimate of total
council costs relating to the
planning process on
completion to operative in
full.


Date [dd/mm/yyyy]
Not Applicable

$ Amount
Record additional
information, providing
context to how total Council
costs were determined.
Open text
The best estimate of the
average council staff full
time equivalents (FTE) spent
over the life of the process,
on completion to operative
in full. (Number).
Optional field to record
additional information, such
as reasons for delays or
processes put on hold or
withdrawn; or confirm the
next step to occur in the
process.
Optional data field.
Number [e.g 1.5 FTE]


Open Text
Not Applicable
$ Amount
Guidance
columns if additional are
required.
Each date should link to
the name and subject
matter of the part
identified in the data
field
Parts/section/policies
that became operative in
part.
This is total cost for the
period between the
dates given in the fields
Date process
commenced (1.2.19) and
Date became operative
in full (1.2.45). Include all
cost including staff,
consultants and
overheads. 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.
Note: This includes the
total costs relating to
processing private plan
changes.
This is the average FTE
for the period between
the dates given in the
fields Date process
commenced and Date
became operative in full.
Please try to keep this
comment to 1-4
sentences, rather than a
lengthy commentary/
explanation.
Reporting on these data
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
13
Data field
Description of data field
Council Costs –
pre-notification
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.
($).
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 costs
including staff, consultants
and overheads.
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
Decisions notified and Date
became operative in full.
Include all costs including
staff, consultants and
overheads.
1.2.51
Council Costs –
notification to
decisions
1.2.52
Council Costs –
decisions to
operative
Acceptable Responses (please
leave cell blank if the event has
not yet occurred)
$ Amount
$ Amount
Guidance
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.
Helpful links
http://www.mfe.govt.nz/publications/rma/guide-section-32-resource-management-act
Section 1.3 – Efficiency and effectiveness monitoring
This section requires the reporting of information on any RMA section 35(2)(b) monitoring reported
(notified and/or published) during the 2015/16 financial year.
Data field
1.3.1
Date results of
35(2)b monitoring
reported
1.3.2
Policy statement or
plan, policies, rules
or other methods
covered in
reporting
Description of data field
The date when the results of efficiency and effectiveness of
policy statement or plan monitoring, as per section
35(2)(b), were made available to the public, as per section
35(2A).
A summary of the policy statement or plan, policies, rules
or other methods covered in reporting, as per section
35(2A).
Acceptable Response
Date [dd/mm/yyyy]
Open Text
[eg, Eureka District
Plan sections 5 and 6
on Utilities and
Heritage]
Helpful links
http://www.qualityplanning.org.nz/index.php/monitor/policy-and-plan-effectiveness
14
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Section 1.4 – Iwi/hapū planning documents
This section requires the capture of information on all iwi/hapū planning documents lodged,
removed or updated with your local authority within the 2015/16 financial year.
Data fields
1.4.1
Document name
1.4.2
Iwi authority
1.4.3
Date lodged/removed/
updated with local
authority
Description of data field
The name of the planning
document (iwi management
plan/customary title area
plan) lodged with your local
authority.
The name of the iwi authority
that recognised the planning
document.
The date that the planning
document was lodged with
your local authority.
1.4.4
Coverage
The iwi/hapū and local
authority area/s the planning
document relates to.
1.4.5
Summary of issues and
considerations
Summary of specific issues
and considerations, including
their geographic coverage,
relating to planning
processes.
Acceptable Response
Open Text
Guidance
Name of iwi
authority

Lodged date
[dd/mm/yyyy]
 Removed date
[dd/mm/yyyy]
 Updated date
[dd/mm/yyyy]
Open Text
Open Text
The approximate
geographical coverage
that the planning
document relates to.
This could refer to local
governing board areas or
a map.
The information sought
is a high level summary
of the key issues and
considerations identified
in the document rather
than a summary of the
planning document
itself.
Section 1.5 – Resource consents
This section requires the reporting of information about each individual resource consent process.
Include all resource consent applications that were processed through to a decision in the 2015/16
financial year. This includes resource consent applications lodged before and during the 2015/16
financial year if the decision to grant, decline, withdraw (or determined as incomplete and returned
under Section 88(3)) was made in the 2015/16 financial year.
‘Bundled’ resource consents
In the Template, a row of data is required for each resource consent that is processed to a decision,
withdrawn or determined as incomplete and returned by each Council within the financial year.
It is common practice for local authorities to process an application for a particular project which
pertains to multiple resource consents as one (aka ‘bundled’ resource consent). In such cases, we
ask that each consent that forms a part of a bundled application be reported individually, but
identified in some way as a bundled consent. In order to do this an option is to give each individual
resource consent a common identifier plus an additional unique component to distinguish between
each of the bundled consents eg, RM201589.1 (land use); RM201589.2 (subdivision) and
RM201589.3 (water permit). In this case, three rows of data would be populated, so that we could
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
15
identify the description and class of each activity; the remaining data can be recorded against just
one of the numbers (as they generally followed the same consent process).
An alternative example, use by some local authorities is the use of an ‘application identifier’, and
related ‘authorisation number’ (alternatively known as a ‘unit record identifier’). For example, below
is an extract from Horizon Regional Council’s NMs data for 2014/2015:
Council inserted
column Application number
APP-2012015716.00
APP-2012015716.00
APP-2012015716.00
Unit record identifier
Type of resource
consent
Council inserted
column – subtype
Type of
application
ATH-2014014650.00
ATH-2014014651.00
ATH-2014014654.00
Discharge Permit
Discharge Permit
Discharge Permit
Water
Air
Land
Section 88
Section 88
Section 88
In terms of the charges to the applicant (Data field 1.5.49 – 1.5.50) and amount of discount applied
(where applicable), the relevant amounts should also be put against the same single identifier, and
the other rows of data could state ‘bundled’ as an acceptable response. If you do, however, charge
for each consent separately, please note the relevant amounts to the relevant rows of data.
[It is noted that in the 2014/15 data collection that we requested that if you are unable to extract the
deposit/cost/discount for each separate resource consent individually, you should average the
deposit/cost/discount over the number of consents issued under that bundled consent. We
acknowledge that this is not the most pragmatic approach, and have changed our guidance
accordingly].
If your system has a ‘combined land use and subdivision’ consent type, they may be reported as one
line of data as long as they followed exactly the same application process, however the Class of
Activity (refer Section 1.5.6) for each needs to be clearly reported and an additional column can be
added and named accordingly. In cases where combined land use and subdivision applications do not
follow exactly the same process they will need to be recorded separately (as per Bundled Consents
above).
16
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Data field
Description of data field
1.5.1
Unit record
identifier
A unique reference used to
identify each separate row of
data as unique, such as a
consent identifier.
1.5.2
Type of
resource
consent
The type of resource
consents as per Section 87.
1.5.3
Type of
Application
The type of application
1.5.4
Description of
activity
The description of the
activity(s)
Acceptable Responses
[or Example]
Eg, RM 15/656
For Bundled Consents
Eg, RM15/89.1 (for land
use), RM15/89.2 (for
water permit),
RM15.89.3 (for
discharge permit)
 Land use consent
 Subdivision consent
 Coastal permit
 Water permit
 Discharge permit
 Combined land use
and subdivision
 Section 88
 Section 127 (change
or cancellation of
consent condition)
 Section 128 (review
of consent condition
by local authority)
Open Text
Eg, Combined land use
and subdivision resource
consent to create two
allotments and to
construct a dwelling on
each site at 27 John
Court Street, Birkenhead.
Or
To discharge to the
Orowa River up to
12,000m3/day of treated
wastewater when river
flow is at or below half
medium flow (for a
maximum 3-year period).
1.5.5
Legal
Description
(Appellation)
GPS coordinates
or GIS shape
files
The legal description of the
specific piece of land for
which the resource consent
relates or the GPS Easting
and Northing Coordinates
identifying the location of the
consented activity.
Alternatively council may
submit a GIS shape file that
provides location data for the
consented activity.
Open text
Eg, Section 1 Block VII
Mata etc.
Guidance
Each row of data (unit
record) should represent
an individual resource
consent.
For Bundled Consents:
Refer to notes above.
The description must be
worded in a manner that
should this information
be picked up in 5 years’
time by someone who
was not involved in the
application, they can
clearly understand what
the activity was
(whether it was
authorised or not). This
may be the same the
activity description in
the resource consent
decision. The
description should
match the ‘Type of
resource consent’ in
1.5.2 (eg, if the Type is a
land use consent, the
description should
describe a land use and
not a discharge to water
for example).
Please note that other
methods of location
identification can be
used if legal descriptions
are not appropriate eg,
GPS coordinates. In this
case, additional columns
to show the latitude,
longitude and grid
coordinates (known as
northings and eastings)
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
17
Data field
1.5.6
Class of activity
1.5.7
Pre-application
meeting
18
Description of data field
The class of activity relevant
to the consent, as per section
87A.
Whether a pre-application
meeting was held with the
local authority.
Acceptable Responses
[or Example]





Controlled
Restricted
discretionary
Discretionary
Non-complying
Not applicable


Yes
No
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Guidance
can be inserted and
named accordingly. GIS
shape files may also be
submitted as a separate
file.
If the consent type
noted in section 1.5.2 is
Combined land use and
subdivision, then the
Class of Activity for each
needs to be clearly
reported, and an
additional column
should be added
following this data field
and named accordingly.
Not applicable can be
used for those
applications which are
returned as incomplete
where the activity status
has not been
determined. It should
be noted that all section
127 and 128 applications
should be processed as
Discretionary Activities.
A pre-application
meeting is an arranged
meeting that is held
between the applicant
and a council officer to
discuss a proposal ahead
of its lodgement. It
includes only those
formal enough that a
record was kept of the
meeting. A phone call or
front counter discussion
is not considered a preapplication meeting in
this instance.
Data field
Description of data field
1.5.8
Date lodged
The date an application was
lodged with the local
authority.
1.5.9
Date
determined as
incomplete
under section
88(3)
If applicable, the date it was
determined the application
was incomplete under
section 88(3).
Acceptable Responses
[or Example]
Date [dd/mm/yyyy]


Date [dd/mm/yyyy]
Not Applicable
Guidance
The date that the
application is received by
council (ie, when it
physically or
electronically enters the
council).
If an application for the
same activity has
previously been
returned under Section
88, the lodgement date
should be the date the
new application is
lodged with the council
as it must be treated as a
new application under
section 88(4).
If the application was
determined as
incomplete, a date is
required in this data
field.
The row of data should
not continue after this
field (ie, left blank)
except for 1.5.37
(Decision date), 1.5.38
(Decision) and 1.5.39
(Decision maker).
Incomplete applications
should have a Unit
Record Identifier, Date
lodged etc. reported.
If another application is
lodged for the same
activity, it should be
treated as a new
application, as per
section 88(4), and does
not necessarily need to
link to the original
application. If your
system doesn’t capture
incomplete/ returned
applications, an
alternative means of
collection should capture
this information. This
may mean assigning a
dummy Unit Record
Identifier to each or if
your system uses the
same unit record
identifier for applications
that are re-lodged, you
may want to provide this
data (ie, data fields 1.5.1
– 1.5.9 and 1.5.37 –
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
19
Data field
Description of data field
Acceptable Responses
[or Example]
Guidance
1.5.39) in a separate
sheet/tab in the
Template.
1.5.10
Deferral under
section 91
1.5.11
Continued
following
section 91
deferral
1.5.12
Date of first
section 92(1)
request
Date section 91 issued for
applicant to apply for
additional consents
Date processing proceeded
following a deferral under
section 91.


Date [dd/mm/yyyy]
Not Applicable


Date [dd/mm/yyyy]
Not Applicable
The date of the first request
for further information under
section 92(1).


Date [dd/mm/yyyy]
Not Applicable
1.5.13
Response to
section
92(1)request
1.5.14
Date of
response to first
section 92(1)
request
Optional Data Field
Whether the applicant
agreed to provide the
information.
The date that information,
requested under section
92(1), was received or the
date of written notice that
the applicant refused to
provide the information.



Yes
No
Not applicable


Date [dd/mm/yyyy]
Not Applicable
1.5.15
Date of first
section 92(2)
commissioning
The date of the first
notification to the applicant
of intent to commission a
report, as per section
92(2)(b).
Whether the applicant
agreed to the commissioning
of the section 92(2) report.


Date [dd/mm/yyyy]
Not Applicable



Yes
No
Not applicable
The date of written notice
provided by the applicant as
to whether it agreed to the
commissioning of the section
92(2) report.


Date [dd/mm/yyyy]
Not Applicable
1.5.16
Response to
first section
92(2)
commissioning
1.5.17
Date of
response to first
section 92(2)
commissioning
20
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Note: On 3rd March, the
2013 RM Amendment
Act section 88 changes
took effect. This means
that for applications
received post this date,
section 88C(1)(b) and (c)
will provide that the only
section 92(1) request
that will stop the clock is
the first request,
provided it precedes
notification.
The date when that the
applicant provides the
requested information
(either within the initial
15 working days or by
the new date prescribed
by council), or the date
the applicant refuses to
provide the information.
Data field
Description of data field
Acceptable Responses
[or Example]
 Date [dd/mm/yyyy]
 Not Applicable
Guidance
1.5.18
Date council
notifies
applicant that
there are
affected
persons.
1.5.19
Date of
response to
written
approval
notification
Optional Data Field
The date that the council
notifies the applicant that
there are affected parties
under Section 95E, 95F and
95G.
Optional Data Field
The date that the written
approval(s) of affected
parties were received, or
applicant requests that the
application proceed on a
limited notified basis.


Date [dd/mm/yyyy]
Not Applicable
The date that all of the
written approvals are
received (or the date
that the applicant
notifies the council to
proceed with the
processing of the
consent without the
written approvals).
1.5.20
Notification
decision
The notification path that the
consent followed.



The date the consent was
limited notified or publicly
notified.
If limited notified or publicly
notified, the date that
submissions closed.


Non-notified
Limited notified
Publicly notified
Not Applicable
Date [dd/mm/yyyy]
Not Applicable


Date [dd/mm/yyyy]
Not Applicable
The date of request for
further information under
section 92(1) following the
notification decision.


Date [dd/mm/yyyy]
Not Applicable
The date that the
information, requested
following under section 92(1)
following the notification
decision, was received, or the
date of written notice that
the applicant refused to
provide the information.


Date [dd/mm/yyyy]
Not Applicable
1.5.25
Date of
subsequent
section 92(2)
commissioning.
1.5.26
Response to
subsequent
section 92(2)
commissioning.
The date of any subsequent
notification to the applicant
of intent to commission a
report, as per section
92(2)(b).
Whether the applicant
agreed to the subsequent
commissioning of the section
92(2) report.


Date [dd/mm/yyyy]
Not Applicable



Yes
No
Not Applicable
1.5.27
The date of written notice

Date [dd/mm/yyyy]

1.5.21
Date notified
1.5.22
Date
submissions
closed
1.5.23
Date of post
notification
decision section
92(1) request
1.5.24
Date of post
notification
decision
response to
section 92(1)
request.
The date that the council
formally requests that
the applicant obtain the
written approval of
affected parties under
s95.
Note: Although there are
no limitations on the
number of section 92
further information
requests that can be
made, there are
limitations on when the
processing clock can be
stopped (section 88C).
For applications received
post 3 March 2015, the
clock can only be
stopped once by the
council for a further
information request and
only when the request is
made prior to
notification.
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
21
Data field
Description of data field
Date of
response to
subsequent
section 92(2)
commissioning.
1.5.28
Deferral under
section 91A.
provided by the applicant as
to whether it agreed to the
commissioning of the
subsequent section 92(2)
report.
For applications lodged post
3rd March 2015:
For notified resource
consents, the date the
applicant requested
suspension of processing of
application under section
91A.
For applications lodged post
3rd March 2015:
Date processing proceeded
following a suspension under
Section 91A
1.5.29
Continued
following
section 91A
deferral.
Acceptable Responses
[or Example]
 Not Applicable


Date [dd/mm/yyyy]
Not Applicable


Date [dd/mm/yyyy]
Not Applicable
1.5.30
Start date of
pre-hearing
meeting
1.5.31
End date of prehearing meeting
1.5.32
Commencement
date of hearing
1.5.33
Adjournment
date of hearing
The first date of pre-hearing
meeting(s).


Date [dd/mm/yyyy]
Not Applicable
The last date of pre hearing
meeting(s).


Date [dd/mm/yyyy]
Not Applicable
The date of the
commencement of the
hearing.
The date that the hearing was
adjourned.


Date [dd/mm/yyyy]
Not Applicable


Date [dd/mm/yyyy]
Not Applicable
1.5.34
Completion
date of hearing
1.5.35
Number of
hearing days
The date that the hearing was
completed.


Date [dd/mm/yyyy]
Not Applicable
Number of hearing days in
total.


Number of days
Not Applicable
1.5.36
Joint hearing
Whether it was a joint
hearing with another council.
1.5.37
The date the decision was
 Yes
 No
 Not Applicable
Date [dd/mm/yyyy]
22
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Guidance
If the consent has been
on suspend under
Section 91A for 130 days
or more, the Council
must decide whether to
return the application or
to continue to process it.
If returned, the date of
this decision, the
decision itself and the
decision maker/s should
be noted in data filed
1.5.37 – 1.5.39.
Note: Under the 2013
RM Amendment Act, the
ability to adjourn a
hearing for 10 days has
been removed.
As per reference in
section 103A.
This should be 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.
This includes consents
Data field
Description of data field
Acceptable Responses
[or Example]
Decision date
issued or the application
withdrawn or returned.
1.5.38
Decision
The decision outcome.





Granted
Declined/Refused
Withdrawn
Returned
Incomplete
1.5.39
Decision-maker
The person, with the
appropriate delegated
authority, who made the final
decision on the application.

The date that any extension
under section 37 was made.




Local authority
officer
Councillor(s) acting
as commissioners
Independent
commissioner(s)
Independent
commissioner(s)
requested under
section 100A
Other (eg, mixed
panel of
councillor(s) /
commissioner(s))
Hearings panel
Not Applicable
Date [dd/mm/yyyy]
Not Applicable
The number of working days
of section 37 extension.


Number of days
Not Applicable
The method by which the
local authority extended a
time period.

Special
circumstances
(section 37A(4)(b)(i))
Applicant
agreement (section
37A(4)(b)(ii))
Applicant
agreement (section
37A(5)) - more than
twice)
Not Applicable (did
not extend time).




1.5.40
Date of section
37 extension
(extension 1)
1.5.41
Length of
section 37
extension
(extension 1)
1.5.42
Reasons for
section 37
(extension 1)



Guidance
that are determined as
incomplete under
section 88(3); or
returned under section
91A.
Incomplete should be
used if a consent has
been returned as
incomplete under
section 88(3). Returned
should be used when a
consent was on suspend
under section 91A for
130 days or more, and
the council has decided
to return the application
under section 91C.
Not Applicable should be
used if application was
withdrawn.
If the s37 extension of
time was made with the
applicant agreement
(under s37A(4)(b)(ii) or
37A(5)), the date shown
should be the date that
the applicant agreed to
the extension.
Note: The council must
ensure every person
who it considers is
directly affected by the
extension of the time
limit is notified of the
extension.
Also, where applicants
agreement has not been
obtained, the use of
special circumstances
(s37A(4)(b)(i)) should be
supported by clear
reasons why special
circumstances are
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
23
Data field
Description of data field
Acceptable Responses
[or Example]
1.5.43 – 1.5.45
Section 37
extension 2
Further/subsequent
extensions under section 37
As per 1.5.40 – 1.5.42
1.5.46
Processed
within statutory
timeframe
Whether the application was
processed within statutory
timeframe.



1.5.47
Statutory
days lapsed
Number of statutory days the
decision was made within, as
defined under the Discount
Regulations 2010.
Number of days
Yes
No
Not Applicable
Guidance
considered to exist
which require an
extension of time.
Additional columns are
added to record a
second section 37
extension. If there are
more than two
extensions, additional
sets of three columns
will need to be added.
Not Applicable should be
used when a statutory
timeframe is not
applicable to that
application (eg, the
application was
withdrawn).
Where s37 and 37A have
been used to extend
time periods,
applications should be
recorded as having been
processed within time,
provided the limits set
for processing through
the use of s37A have not
been exceeded.
Calculated by totalling
the number of working
days taken to process
the application and
deducting all excluded
days, as per the Discount
Regulations 2010.
Note: This should
EXCLUDE the number of
days extended under
section 37 (as per the
Discount Regulations).
1.5.48
Appealed
Whether the decision was
appealed to the Environment
Court.


Yes
No
1.5.49
Deposit charged
The initial deposit charged to
the applicant by your local
authority.



$ Amount
Waiver
Bundled
24
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Please specify whether
GST inclusive or
exclusive
This should record the
deposit that was paid in
accordance with
council’s fees and
charges schedule.
Where more than one
resource consent has
been processed at the
same time, and the
deposits are not paid
Data field
Description of data field
Acceptable Responses
[or Example]
Guidance
individually for each
consent , the deposit can
be recorded against one
of the consents, and the
remaining relevant rows
pertaining to the other
combined consents can
use ‘Bundled’ as the
appropriate response.
1.5.50
Total charge for
applicant.
The total charges payable by
the applicant for processing
the application.
•
•

$ Amount
Waiver
Bundled
Note: A fixed deposit or
a deposit determined via
a formula is not
considered to be a fixed
fee.
Please specify whether
GST inclusive or
exclusive
This amount should
include:
 any deposit
recorded in the
Deposit charged
data field
 any supplementary
charges as a result
of hearings,
information
gathered etc.
This does not include:
 financial or
development
contributions,
 compliance
monitoring charges
 the discount applied
under the Discount
Regulations (this
information should
be provided
separately in 1.5.52)
 charges for the
approval and
deposit of survey
plans.
As noted above, where
more than one resource
consent has been
processed at the same
time, and the total
charges are not paid
individually for each
consent, the total charge
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
25
Data field
Description of data field
Acceptable Responses
[or Example]
1.5.51
Fixed fee
application
Confirmation of whether the
applicant was charged a fixed
fee.


Yes
No
1.5.52
Amount of
discount
The amount of a discount
applied under the Resource
Management (Discount on
Administrative Charges)
Regulations 2010.


$ Amount
Not Applicable if no
discount applied).
1.5.53
Section 357
objections
Whether any objections were
received under section 357 to
357B.

Yes
No

Guidance
can be recorded against
one of the consents, and
the remaining relevant
rows pertaining to the
other combined
consents can use
‘Bundled’ as the
appropriate response.
‘Yes’ confirms the figure
identified as the Total
charge for applicant was
a fixed fee.
‘No’ indicates that the
figure identified as the
Total charge for
applicant included actual
and reasonable costs.
If the answer was ‘Yes’,
generally the same
amount would be listed
in 1.5.49 and 1.5.50.
Note: Fixed charges are
not supplemented by
additional actual and
reasonable charges once
the consent process is
complete.
Please specify whether
GST inclusive or
exclusive
Where more than one
resource consent has
been processed at the
same time for the same
project, and you can’t
extract the discount for
each consent
individually, you should
average the discount
applied over the number
of consents issued.
Helpful links:
http://www.mfe.govt.nz/publications/rma/discount-on-administrative-charges-regulations
http://www.mfe.govt.nz/publications/rma/guide-six-month-process-notified-resource-consentapplications
http://www.mfe.govt.nz/publications/rma/guide-section-88-and-schedule-4-resource-managementact-1991
26
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
2.0 Part B – Annual summary
information
As part of the staged implementation of the National Monitoring System (NMS), the data fields in
Part B are to be investigated and further defined. At this stage, these sections are place holders to
continue Resource Management Act 1991 (RMA) survey trend information and to expand the data in
some areas. As with the RMA survey, the Ministry appreciates that there is potential for different
responses and that results may not be directly comparable. The intention is to gather more detailed
and more comparable information in the future.
Section 2.1 – Iwi involvement
This section requires the capture of information on all iwi involvement in the resource management
process with your local authority within the 2015/16 financial year.
Data field
2.1.1
Budget to assist
iwi participation
in resource
consent
processing
Description of data field
Whether your local authority
made a budgetary
commitment to assist iwi
participation in resource
consent processing.
Acceptable Response
 Yes
 No
2.1.2
Other forms of
process to assist
iwi participation
in resource
consent
processing
Description of other forms of
process to assist iwi
participation in resource
consent processing. That is,
other than a budgetary
commitment.


Guidance
Includes:
 Internal council
budgetary provision
for staff costs and
consultation with iwi,
and
 Any direct payments
to iwi to assist them in
participating in
consultation, in
regard to resource
consent processing.
Does not include:
 Costs passed on to
applicants.
[Open text]
Not Applicable
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
27
Data field
2.1.3
Budget to assist
iwi participation
in policy
statement and
plan making
Description of data field
Whether your local authority
made a budgetary
commitment to assist iwi
participation in policy
statement and plan making.
Acceptable Response
 Yes
 No
2.1.4
Other forms of
process to assist
iwi participation
in policy
statement and
plan making
2.1.5
Iwi/hapū
agreements
Description of other forms of
process to assist iwi
participation in policy
statement and plan making.

28

[Open text]
Not Applicable
The number of written
agreements (eg,
memorandum of
understanding or heads of
agreement) with iwi/hapū
regarding participation in
resource management.
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Guidance
Includes:
 internal council
budgetary provision
for staff costs and
consultation with iwi
 any direct payments
to iwi to assist them in
participating in
consultation, in
regard to plan and
policy development
and incorporating
iwi/hapū advice into
plans and policy
statements
 contribution paid
towards assisting iwi
in the development of
planning documents
recognised by the iwi
authority (such as iwi
management plans).
Please try to keep this
comment to 1-4
sentences, rather than a
lengthy explanation.
This should be taken as
the total number of
current written
agreements.
Section 2.2 – Staff working on preparation of policy statements and
plans, changes and variations
This section requires the reporting of information on resourcing dedicated to plan preparation
processes at your local authority for the 2015/16 financial year. Resourcing figures should be as
accurate as possible and capture the annual average full time equivalents for the financial year.
Resourcing figures should include all staff employed to work on the preparation of policy statements
and plans, changes and variations, including staff such as administrators. The sum of all figures
provided will indicate your total staff resource for plan preparation and implementation. It is
important that figures are not double counted. If you have staff that do not neatly fit into one of the
categories, some practical interpretation is required, otherwise they can be put into Other.
Data field
Description of data field
2.2.1
Senior planners
Staff employed as senior planners by
your local authority to work on
preparation/review of policy
statements/plans, changes and
variations
Staff employed as planners by your
local authority to work on
preparation/review of policy
statements/plans, changes and
variations
2.2.2
Planners
2.2.3
Planning technicians
and administrators
2.2.4
Other
2.2.5
Additional context
Acceptable
Response
Number of FTE
Guidance
Number of FTE
This may
include
graduate
planners and
intermediate
planners
Staff employed as technicians
including administrators by your local
authority to work on
preparation/review of policy
statements/plans, changes and
variations
Other staff employed by your local
authority to work on
preparation/review of policy
statements/plans, changes and
variations
Number of FTE
Optional field to record additional
information regarding resourcing


Number of FTE
[Open text}
Not applicable
Includes any
consultants
contracted by
your council
on an ongoing
basis to
process
resource
consents
(converted
into FTE)
Please try to
keep this
comment to 14 sentences,
rather than a
lengthy
explanation.
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
29
Section 2.3 – Staff processing resource consents
This section requires the reporting of information on resourcing dedicated to processing resource
consents at your local authority for the 2015/16 financial year.
Resourcing figures should be as accurate as possible and capture the annual average full time
equivalents (FTE) for the financial year.
Resourcing figures should include all staff employed to assess, determine, change and review
resource consents, including staff such as council engineers, administrators, dedicated duty planners
etc. The sum of all figures provided will indicate your total staff resource for processing resource
consents. It is important that figures are not double counted. If you have staff that do not neatly fit
into one of the categories, some practical interpretation is required, otherwise they can be put into
Other.
Data field
Description of data field
2.3.1
Senior planners
Staff employed as senior planners
by your local authority to process
resource consents.
Staff employed as planners by your
local authority to process resource
consents.
2.3.2
Planners
2.3.3
Scientists
2.3.4
Planning
technicians and
administrators
2.3.5
Other
2.3.6
Additional
context
30
Acceptable
Response
Number of FTE
Guidance
Number of FTE
This may include
graduate planners
and intermediate
planners
Staff employed as scientists by your
local authority to process resource
consents
Staff employed as technicians
including administrators by your
local authority to process resource
consents
Other staff employed by your local
authority to process resource
consents.
Number of FTE
Optional field to record additional
information regarding resourcing,
such as issues or challenges
processing resource consents during
the year.


Number of FTE
Number of FTE
[Open text}
Not applicable
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Includes any
consultants
contracted by your
council on an
ongoing basis to
process resource
consents (converted
into FTE)
Please try to keep
this comment to 1-4
sentences, rather
than a lengthy
explanation.
Section 2.4 – Customer satisfaction
This section requires the reporting of information on customer satisfaction with resource consent
processing during the 2015/16 financial year.
Data field
2.4.1 Customer
Satisfaction
Description of data field
If your local authority ran a formal,
documented consent processing
customer satisfaction survey, what
percentage of those surveyed
indicated an overall level of
satisfaction above, and not including,
neutral.
Acceptable Response
Percentage (%)
Guidance
This should be
done on analysis
of responses for
all resource
consent
processing
questions.
Section 2.5 – Notices of requirement (territorial authorities only)
This section captures summary information on notices of requirement relevant to the 2015/16
financial year.
Data field
2.5.1
Notices of requirement
received
2.5.2
Notices of requirement
confirmed
2.5.3
Notices of requirement
recommended for
withdrawal
2.5.4
Recommended for
withdrawal appealed
Description of data field
The number of notices of requirement received
in the financial year.
Acceptable Response
Number
The number of notices of requirement that
were recommended to be confirmed in the
financial year.
The number of notices of requirement that
were recommended for withdrawal in the
financial year.
Number
The number of notices of requirement that
were appealed in the financial year.
Number
Number
Section 2.6 – Staff working on complaints, monitoring and
enforcement
This section captures information on the monitoring and compliance resourcing at your local
authority during the 2015/16 financial year. Resourcing figures should be as accurate as possible and
capture the annual average full time equivalents (FTE) for the financial year.
The sum of all figures provided will indicate your total staff resource for RMA monitoring,
compliance, investigations and prosecutions. It is therefore important that figures are not double
counted. If you have staff that do not neatly fit into one of the categories, some practical
interpretation is required.
Numbers should exclude staff at external companies contracted to respond to excessive noise
complaints.
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
31
Acceptable
Response
Number of FTE
Data field
Description of data field
2.6.1
Dedicated
compliance
monitoring staff
The number of staff dedicated to
RMA compliance monitoring.
2.6.2
Dedicated
enforcement staff
2.6.3
Dedicated
investigations staff
2.6.4
Compliance
monitoring and
enforcement
(combination) staff
The number of staff dedicated to
enforcement.
Number of FTE
The number of staff dedicated to
Investigations and prosecutions.
Number of FTE
The number of staff who do a
combination of Compliance
Monitoring and Enforcement.
Number of FTE
2.6.5
Compliance
monitoring,
enforcement and
investigation
(combination) staff
The number of staff who do a
combination of
 Compliance monitoring and
investigation;
 Enforcement and investigation;
or
 Compliance monitoring,
enforcement and investigation
Number of FTE
32
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Guidance
Includes:
 the annual
average FTEs
for the
financial year.
Excludes:
 staff dedicated
to noise
compliance.
Includes:
 the annual
average FTEs
for the
financial year.
Excludes:
 FTEs that are
accounted for
above and
below.
Includes:
 the annual
average FTE for
the financial
year.
Excludes:
 FTEs that are
accounted for
above and
below.
Section 2.7 – Other monitoring
This section captures information on other monitoring undertaken by your local authority during the
2015/16 financial year.
Practical interpretations of these data fields are required. It is acknowledged there are different
monitoring regimes in different councils. The data fields allow for monitoring activities to be put into
a local context.
Data field
Description of data field
2.7.1
State of the
environment
monitoring
Did your local authority monitor
the state of the whole or any part
of the environment (section
35(2)(a)) in the 2015/16 year.
Monitoring involves capturing a
record of what was monitored.
The total number of individual
activities which were monitored for
compliance against plan rules,
including permitted activity rules.
Does not include activities with
resource consent or complaintprompted monitoring.
2.7.2
Plan rule
monitoring
2.7.3
Delegated and
transferred
functions
monitoring
Whether your local authority
monitored the exercise of any
functions, powers, or duties
delegated or transferred by it
(section 35(2)(c)).
Acceptable
Response
 Yes
 No
Guidance


Number
Not
Applicable


Yes
No
Includes:
 proactive monitoring
of permitted activities
and
 proactive monitoring
of unconsented plan
rule breaches.
Does not include:
 the proactive
assessment of
building consent
applications against
RMA plans.
Not Applicable should
indicate your council does
not undertake any
proactive plan rule
monitoring.
Monitoring involves
capturing a record of what
was monitored.
Helpful links:
http://www.qualityplanning.org.nz/index.php/monitor/best-practice-monitoring
http://www.qualityplanning.org.nz/index.php/monitor/delegations-and-transfers
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
33
Section 2.8 – Complaints and monitoring
This section captures information on complaints and monitoring undertaken by your local authority
during the 2015/16 financial year.
Some of these data fields include proactive monitoring, but not reactive or complaint promptedmonitoring. Removing reactive or complaint-prompted monitoring allows the Ministry to gather a
more accurate picture of compliance rates. As not all consents are monitored each year, obtaining
figures in this way will allow more accurate extrapolation of compliance rates. Including complaintprompted monitoring would skew that result. You should include monitoring where a complaint(s)
was received, but the complaint did not prompt the monitoring.
The term ‘monitoring event’ is used to allow for different local practices. Activities may only be
monitored by inspections at your council whereas at another council an activity may be monitored by
reviewing sample results and not undertaking a physical inspection. Monitoring event refers to an
assessment of consent compliance where non-compliance constitutes a breach of the consent, so as
to exclude, for example, pre-construction visits where works had not yet commenced.
Acceptable
Response
Number
Guidance
The total number of complaints
recorded by your local authority, as
per Section 35(5)(i).
Number
The total number of individual
resource consents that required
monitoring for compliance, as per your
local authority's monitoring regime.
Number
Does not include
excessive noise
complaints or
complaints related to
other non-RMA local
authority functions.
Includes:
 resource consents
granted in
previous financial
year(s) and require
monitoring in this
financial year.
Does not include:
 lapsed consents
(unless
determined
differently by your
local authority).
A response of ‘0’ would
indicate that no
resource consents
required monitoring,
as per your local
authority’s monitoring
regime, for this
financial year.
Data field
Description of data field
2.8.1
Number of
excessive
noise
complaints
2.8.2
Total number
of other RMA
complaints
The total number of excessive noise
complaints recorded by your local
authority.
2.8.3
Resource
consents
requiring
monitoring
34
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Data field
Description of data field
2.8.4
Resource
consents
monitored
2.8.5
Resource
consent noncompliance
The total number of individual
resource consents monitored for
compliance.
Acceptable
Response
Number
The number of individual resource
consents, which were monitored for
compliance by your local authority and
were in non-compliance with at least
one condition.
Guidance
Does not include
reactive or complaintprompted monitoring.
Number
Section 2.9 – Enforcement
This section captures information on the enforcement activities undertaken by your local authority
during the 2015/16 financial year.
These data fields require the identification of a ‘primary issue’. Some interpretation is required, but it
is expected that sections 9-15 would trump section 16 or 17 when identifying a primary issue. It is
more important that notices are not double counted than it is to identify the primary issue. Section
16, 17, 338 etc. should be included in “Other”.
Number
Not Applicable
The number of
infringement notices
served by your local
authority, alleging a
breach of each RMA
section.
The number of abatement
notices served by your
local authority, where the
primary issue was alleged
breaches of each RMA
section.
The number of
enforcement orders
(including interim
enforcement orders)
applied for by your local
authority, where the
primary issue was alleged
breaches of RMA section.
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
35
Other - Eg, Section 16 (noise),
Section 17 (adverse effects),
Section 338 (Offences)
Section 15 (Discharges)
2.9.3
Enforcement order
applications
(including interim)
Section 14 (Water)
2.9.2
Abatement notices
Section 13 (Beds of lakes & rivers)
2.9.1
Infringement
notices
Section 12 (Coastal Marine Area)


Acceptable Response
Section 11 (Subdivision)
Description of data field
Section 9 (Land)
Data field
NMS Information Requirements. Guidance for the 2015/2016 Financial Year
Other - E.g. Section 16 (noise),
Section 17 (adverse effects),
Section 338 (Offences)
36
Section 15 (Discharges)
2.9.6
Prosecutions
initiated
The total number of cases
referred to your local
authority’s decision
maker(s) where staff made
a recommendation to
prosecute, where the
primary issue was alleged
breaches of each RMA
section.
The total number of cases
referred to your local
authority’s decision
maker(s) where decision
makers decided to
prosecute, where the
primary issue was alleged
breaches of each RMA
section.
The number of cases
where prosecutions were
initiated by your local
authority (charges laid),
where the primary issue
was alleged breaches of
each RMA section.
Section 14 (Water)
2.9.5
Decisions to
prosecute
Number
Not Applicable
Section 13 (Beds of lakes & rivers)
2.9.4
Recommendations
to prosecute
Section 12 (Coastal Marine Area)


Acceptable Response
Section 11 (Subdivision)
Description of data field
Section 9 (Land)
Data field