Example process - making a plan change operative
This example is part of the process Auckland City Council follows in making a plan change operational. The same process applies in making a whole plan or part of a plan operational. Regional coastal plans have a number of differences.
| Step | Contact | Activity | Timeframe |
|---|---|---|---|
| 4 | Planner | Prepares Committee report to Council meeting requesting plan change be made operative | 10-30 working days (depends on agenda closing date for next Council meeting) |
| 5.1 | The Council resolves to make the plan change operative. Democracy Services will send out a minute following the meeting | ||
| 5.1.1 | Planner | Discuss with manager whether a pamphlet is required to be prepared on the content of the plan change | |
| 5.2 | Planner | Prepare public notice for City Scene* advising that the plan change is operative on a particular date | Note: Operative date must be at least 5 working days after the notice is published |
| Planning technician | Notice in City Scene* stating the operative date of plan change | ||
| Planning technician | Arranging for Plan change to be sealed | 5 working days (simple) 10 working days (complex) |
|
| 5.3 | Planning technician | Final version of the plan change sealed by the Mayor | |
| 5.4 | District Plan is amended as per approved plan change | ||
| 5.4.1 | Planner | Provide the planning technician with the updated pages of the District Plan as amended by the approved plan change | |
| 5.4.2 | Planning technician | Council website and GIS updated as necessary, paper copies of replacement pages and operative plan change distributed | |
| 5.4.2 | Planner | Organises and culls plan change file(s) and forwards to the records team |
*City Scene is recognised as a newspaper circulated in the Auckland City area and used by the Auckland City Council for notification purposes under the RMA.
