Twenty-one plans, one checkbox

Twenty-one plans, one checkbox

Auckland's local board plan is sold as the moment a community writes its own future. Read all 21 and the illusion dies. They are not 21 strategies. They are one corporate document, reprinted with a different mihi and a different chair's signature. The ritual is legally required. The substance is optional. That is the box-ticking exercise.

The 2023 plans are still the adopted ones. The 2026 drafts have been consulted on and are due for adoption by 31 October 2026. The packaging changed. The method did not.

The law asked for a choice. The organisation delivered a brochure.

Section 20 of the Local Government (Auckland Council) Act 2009 is not vague. Each board must adopt a plan no later than 31 October in the year after the election, using the special consultative procedure. The purpose is not "share a vision." It is to:

• reflect community priorities and preferences on the level and nature of local activities for the next three years
• give the board something real to take to the Governing Body under s 16
• form the basis of the annual local board agreement
• inform the next Long-term Plan on which non-regulatory work should sit locally
• create accountability, and a genuine chance for people to participate in decisions about local services

Then comes the part almost nobody quotes, because it is the part that would make the document useful. The plan must include:

• the default levels of service for local activities
• an explanation of every proposed variation from those defaults
• the extra cost or saving of each variation
• an indicative budget that either fits the allocated funding or names the local revenue that will pay for the overspend — targeted rate, fee, or other local source

That is a service-level document with a price tag. It is not a mood board.

Open a 2026 draft. You will not find 21 different answers to those questions. You will find five headings: Community, Natural environment, Built environment, Economic development, Transport. Aotea / Great Barrier drops one heading because an island cannot pretend it has a metropolitan built-environment programme. Everyone else files their suburb into the same five drawers.

The "About this document" paragraph is near-verbatim across boards. So is the origin story: previous plan feedback, annual plan feedback, People's Panel, then a local engagement window. That is not 21 communities independently arriving at the same sentence. That is a template.

This is not a secret inside the building. An AUT study of Auckland local board members recorded the line that should have been printed on the cover:

"We don't write our own Local Board plan. We negotiate it with Council officers and each other but at the end of the day, a lot of the proposals that go in and the writing of it come from Council officers."

Members also said the calendar is the other author. The plan has to be built between the inaugural meeting after the election and a statutory deadline, across the summer shutdown. There is not enough time to research what the community actually wants, so the organisation reaches for last cycle's structure and last cycle's convenient projects. Generic climate actions that spend a targeted rate are easier to write than a fight over which library hour dies.

If you wanted a box-ticking machine, you would build exactly this: a fixed outline, a fixed consultation window, a fixed set of "outcomes," and a chair letter that insists the document was shaped by you.

Consultation that satisfies the Act without disturbing the draft

The special consultative procedure in s 83 of the Local Government Act 2002 is a process test, not a quality test. The authority must:

• adopt a statement of proposal, and a summary if one is needed for public understanding
• make the proposal and the process publicly available
• leave at least one month for views
• circulate the summary as widely as reasonably practicable
• give people a chance to speak, including by audio or audiovisual link

Do those things and you have consulted. You have not necessarily changed anything.

Watch the 2026 sequence. Early engagement in late 2025 and early 2026. Drafts issued mid-year. Feedback open until 23 July 2026. Website now says thank you, finals in October. The consultation pages even list the same starter topics in different board areas: safer streets, parks, town centres, youth programmes, climate, cultural identity. That is not a community setting the agenda. That is the organisation offering a menu.

Spoken interaction is offered. Easy Read versions exist. Translations exist. Feedback PDFs run to multiple volumes. All of that is real work. None of it proves the final plan will contain a costed service-level choice that was not already in the staff draft. In 2023, more than one chair told readers the community had largely confirmed the draft and changes were modest. That is what a completed checkbox sounds like when it is being honest.

The legal minimum is a hearing opportunity and an open month. The political minimum is a summary report that says themes were considered. The operational minimum is a resolution to adopt. After that the organisation can move on. The plan has been "done."

Why the sameness is rational — and still a failure

Auckland Council is one organisation with 21 local boards, shared staff, shared design, shared legal risk, and a Governing Body that still holds the regional money. A single template is cheaper, faster, and safer than 21 genuinely different instruments. It also makes the plans easier to align with the Auckland Plan, the LTP, climate language, and Māori outcomes reporting. From a bureaucracy's point of view, sameness is competence.

From the Act's point of view, it is evasion.

s 20(2)(a) asks for the priorities of the communities within the local board area on the level and nature of local activities. Rodney is not Waitematā. Manurewa is not Ōrākei. Aotea is not Howick. The pain points are different: freight and wharves; intensification and open space; pest-free catchments and youth safety; growth without infrastructure. Those differences appear as place-names dropped into identical chapter structures. The architecture stays the same, so the hard questions stay unasked.

The hard questions are: which default service do we keep, which do we lift, which do we cut, and who pays? Fairer funding makes those questions unavoidable. Local operating funding is being rebased on population 80 percent, deprivation 15 percent, land area 5 percent. Some boards will have more room. Some will have less. Identical wish-lists plus unequal money will produce unequal programmes. The plan that refuses to name a service-level variation is not protecting the community. It is leaving the real decision to the annual agreement, where fewer people are watching.

Advocacy pages do the rest of the work. Boards "advocate" to Auckland Transport, Watercare, Kāinga Ora and the Governing Body for things they cannot decide. Advocacy is legitimate. Pretending advocacy is a local activity is not. s 16 and s 17 already split regulatory and regional decisions away from local boards. A plan that is 40 percent advocacy and 60 percent uncosted aspiration has used the statutory wrapper to avoid the statutory content.

What the ritual costs you

It costs attention. People spend hours on a feedback form that cannot move a heading.

It costs honesty. Communities are told they shaped the plan. Members know officers wrote most of it.

It costs the next document that actually spends money. The local board agreement under s 21 is the annual contract with the Governing Body. The work programme is how departments deliver that contract. s 23 reporting is how you check. If the plan is vague, the agreement can be vague, the work programme can recycle last year's contracts, and quarterly reports can announce "progress against outcomes" without a single killed project.

It also costs the one lawful path to doing more. s 20(3)(d)(ii) already lets a board put an indicative budget above its allocation if it names the local revenue source. That is how you fund a higher service without waiting for a gift from the regional table. A plan that never tables a targeted rate or a fee change has chosen the checkbox over the tool.

If you want an outcome, stop worshipping the plan

Treat the plan as a gate, not a gospel.

Before October. Finals are being locked now. If your item is not in the adopted text as an objective or a key initiative, you have missed the three-year mandate. After adoption you fight in the annual agreement, not in a rewrite.

Demand the s 20(3) test in public. For every initiative, ask: is this the default service, a higher variation, or a cut? What does it cost? What local revenue pays? If staff cannot answer, it is advocacy or decoration. Say that in the meeting. Put it in the minutes.

Follow the money into the agreement. s 21 is where the plan becomes a funded activity list inside the Annual Plan or LTP Volume 3. No agreement line, no project. The work programme is the delivery contract. Ask for project IDs, dollar amounts, and the quarterly report that will prove movement.

Use LGA Part 6 on later decisions. Adoption of the plan does not exhaust the duty. ss 76–82 still require options, assessment of those options, and consideration of community views on significant later choices. A vague plan is a weak shield for a specific cut.

If the board wants more than the allocation, name the rate. That is the legal framework, not a slogan. Kaipātiki's earlier warning about a Hunger Games fight over a fixed pot was crude and partly right. The alternative the Act already provides is a local revenue decision, not a nicer paragraph in chapter two.

The sentence that should replace the vision statement

A local board plan that cannot tell you which service will rise, which will fall, and who pays is not a plan. It is evidence that the organisation completed a statutory process.

That can still be lawful. s 83 does not require a rewrite. s 20 does not require originality. Both require a document that records real local service choices. Twenty-one nearly identical brochures, consulted on a shared menu, adopted on a shared calendar, fail that test while passing the audit.

The box has been ticked. The community has been thanked. The finals will be adopted in October. Then the only question left is the one the template was built to avoid: what, exactly, will be different on the ground because this piece of paper exists?

Updated 22 October 2026.