Branch Management for New Zealand Associations and Governing Bodies

The national president of a New Zealand professional association called a meeting last spring to discuss the branch management software procurement. Twelve branches, ranging from Auckland’s 800 members to the West Coast’s 23. The Auckland branch had wanted Slack, a CRM, and proper event management for two years. The West Coast branch chair had emailed to say he didn’t see why the national body needed to know anything beyond his annual report.

The national CEO had been advocating for a unified platform that would give the national office visibility, give branches modern tooling, and reduce the regulatory work around incorporated society compliance that had been creating friction since the 2022 Act came in.

The procurement stalled. It’s been stalled for over a year.

The reason it stalled isn’t that the right platform doesn’t exist. It’s that “branch management” is not actually one problem. It’s three problems with conflicting requirements, and trying to solve all three with one platform produces the conversation that the association above has been stuck in.

Three problems pretending to be one

The compliance problem. Are branches up to date with their Incorporated Societies Act 2022 requirements? Have they re-registered? Are their constitutions consistent with the parent body’s rules? Do their committee members exist and meet quorum requirements? This is a national-office concern. The national body has reporting obligations, including to its members and increasingly to funders who want to see governance consistency across branches.

The activity visibility problem. What are branches actually doing? How many events did Auckland run last year? Is the Wellington branch growing or shrinking? Are branches collecting subs, hosting professional development, contributing to advocacy? This is a strategic concern — the national body wants to see which branches are healthy and where to direct support.

The branch’s-own-operations problem. What does the Auckland branch use to run its 800-member chapter? What does the West Coast branch use to run its 23-member chapter? These are not the same software. Auckland needs event registration, member communication, possibly a CRM-light experience. West Coast needs a spreadsheet and a Gmail account.

The procurement conversation usually treats these as one problem and looks for one platform. That’s where it gets stuck. The Auckland branch wants more tooling than the West Coast branch is willing to learn. The West Coast branch wants less tooling than the national office needs to satisfy compliance. The platform that compromises between them satisfies nobody.

Splitting it correctly

The healthier approach is to admit these are three different problems and solve them with three different mechanisms.

For compliance, the national office runs a register. Not a platform — a register. One person at the national office is responsible for keeping it up to date. The data sources are mostly external: the Companies Office’s Incorporated Societies register, the branch’s annual report, an annual signed declaration from the branch chair confirming key facts. The register is a Google Sheet or a small Notion database that the national office updates four times a year. This solves the compliance question without imposing anything on branches.

For activity visibility, the national office asks branches to send a quarterly two-paragraph update. Not data fields. Two paragraphs. “What did we do last quarter? What’s coming up?” These get compiled into a national newsletter or annual report. This is information-rich for the national office and minimal friction for the branch. The reason most associations don’t do this is that they’re trying to collect structured data when narrative would be more useful — and easier to extract.

For branch operations, the national office’s job is to provide options, not mandates. Auckland can use TidyHQ, can run a Stripe account, can have an active events programme. West Coast can have a Gmail account and a spreadsheet. Both are fine. The national office subsidises tooling for branches that want it (a centrally-paid TidyHQ licence per branch that wants one, for example), but does not force smaller branches onto infrastructure they don’t need.

What this does that the single-platform approach doesn’t

It respects branch autonomy. The Incorporated Societies Act 2022 is built around the principle that each branch (if separately incorporated) is its own entity with its own governance. The single-platform model implicitly assumes the national body can dictate operations to branches. That’s not how the legal structure works, and it’s not how the social contract works either. The volunteer branch chair who has been running the West Coast branch for fifteen years is doing the national body a favour by existing. Telling her she needs to learn a new platform to keep doing it is a quick way to lose her.

It solves the compliance problem cleanly without making it about software. The national office’s responsibility is to know whether each branch is legally compliant and structurally functional. A register held centrally does that. The branches don’t need to be on a shared platform for it to work.

It allows for the genuine variation in branch capability. Some branches are professional organisations with paid administrators. Some are three volunteers who meet quarterly at a café. Pretending they should run on the same software is the actual mistake the procurement conversation is making.

What TidyHQ fits, and what it doesn’t

TidyHQ tends to fit naturally for the branches that need actual operational software — usually the larger branches. It runs membership, events, communications, finances. The branches that want it can use it; the branches that don’t, don’t have to.

What TidyHQ explicitly isn’t is the national compliance register. That’s a national-office responsibility and should be held in whatever lightweight tool the national office prefers — usually a spreadsheet or Notion. The mistake of trying to make a branch operational tool also be the national compliance tool is the source of most of the friction in these procurements.

What the national CEO should actually do

Pause the platform procurement. Build the register first (it’ll take a week, mostly populating data from the Companies Office). Define the quarterly two-paragraph update process (one email template, sent quarterly). Then, separately, offer branches the option to adopt operational tooling, subsidised centrally, on an opt-in basis.

The national body gets the visibility it needs. The Auckland branch gets the platform it’s been asking for. The West Coast branch chair keeps doing exactly what he’s been doing. The procurement stops being a fight and starts being a service. That tends to be when these things actually move.