
Managing Regional Sports Trusts and Affiliated Clubs in New Zealand
Table of contents
- Key takeaways
- What a development officer actually does in a week
- Why "whoever calls first" is the wrong triage rule
- A triage matrix that actually fits an RST
- What this needs from the data
- What Sport NZ will want to see at the next outcome report
- What to do this quarter if you're the RST GM
- How TidyConnect fits the RST view
- References
Key takeaways
- New Zealand's 14 regional sports trusts are a governance layer that doesn't exist in most other countries - they sit between Sport NZ and local clubs, providing cross-sport support
- NZ Rugby (600+ clubs), Football NZ, and NZ Cricket each have their own regional structures (provincial unions, federations, associations) that overlap with but don't map to regional sports trust boundaries
- Sport NZ's Community Sport Strategy emphasises participation, physical literacy, and values-based sport - and regional sports trusts are the primary delivery mechanism
- With 5 million people and high per-capita participation rates, NZ clubs are often smaller than their Australian or UK equivalents, making the volunteer burden proportionally higher
A regional sports trust looks deceptively manageable on paper. One organisation. A defined territory. A Sport NZ funding agreement that sets out clear deliverables. A team of development officers who go out and support clubs.
Then you map it. Sport Waikato has 42 territorial authority boundaries inside its region, six sport codes that account for most participation, another twelve that account for the long tail, and roughly 400 affiliated and unaffiliated sport organisations. Sport Canterbury covers an area the size of England with a development team of nine. Harbour Sport works across Auckland's North Shore and Rodney with one of the highest population densities in the country and the matching volume of demand. Every RST team across the country has the same problem in a slightly different shape: too many clubs, too few hours, too many sports, too many funding-tied deliverables, and no triage system that survives a busy week.
This is the piece for the RST GM or development manager who knows that the current model β first responder mode, whichever club calls first gets the visit β isn't sustainable and isn't producing the outcomes Sport NZ is actually paying for. What follows is one way to think about deploying a small team across a large field, and what the data infrastructure has to look like to make it possible.
What a development officer actually does in a week
The RST development officer role looks different at every trust, but the underlying work falls into four buckets. Knowing the mix matters because each bucket has a different time-to-impact curve.
Reactive support. A club committee that's just lost its treasurer. A constitution that needs urgent updating before an AGM next month. An incident report that requires immediate response. Reactive work is unavoidable and high-stakes, but it's also the kind of work that fills a week if nothing else is being prioritised against it.
Capability programmes. Governance workshops, treasurer training, safeguarding sessions, the New Zealand version of "Volunteer Friday." Sport NZ funding agreements typically require a number of these per year, and they're the most visible part of the role β clubs see the offer, sign up or don't, and someone counts the heads.
Embedded development. A multi-month relationship with a specific club, working through a strategic plan, a facility upgrade business case, or a merger conversation between two adjacent clubs. This is the work that produces structural change β but it eats officer time at a rate that competes with everything else.
Programme delivery. KiwiSport, Healthy Active Learning, Balance is Better activations, He Oranga Poutama. RST-funded programmes that need someone running them. These have hard deadlines, fixed deliverables, and contracts attached.
In the average week, reactive work and programme delivery dominate. Capability programmes happen on the calendar dates they're scheduled. Embedded development is what gets squeezed when the other three are busy β which is most weeks. The triage problem is essentially this: the highest-leverage work is the most squeezable, and there's no system for protecting it.
Why "whoever calls first" is the wrong triage rule
The default mode at most RSTs is responsive rather than strategic. A club calls; an officer responds. A funder asks for a programme report; an officer writes one. A school principal mentions that they'd like more KiwiSport sessions; an officer adds it to the list.
This is reasonable behaviour from individual officers, but it produces a structurally bad outcome: the clubs that get the most support are not necessarily the clubs where support has the most effect. The well-organised club with an engaged committee asks for help, gets it, and improves. The disorganised club that needs the most help never picks up the phone, and slowly drifts toward dissolution. The RST's outcome data shows lots of activity and modest improvement β concentrated in clubs that were already improving.
Sport NZ knows this pattern. The Community Sport Strategy's emphasis on the underserved β women and girls, MΔori and Pasifika, low-decile communities, disability sport β is partly a corrective to the gravitational pull of the easier work. RSTs are increasingly being asked to demonstrate not just how many clubs they supported but which clubs, and what difference it made.
The implication is that triage can't be passive. Someone has to look at the full set of clubs in the region, decide who needs what, and decide what not to do this quarter.
A triage matrix that actually fits an RST
The framework that produces the best outcomes in practice is a two-axis grid: how much intervention does this club need, and how ready is the club to engage with it.
Intervention dose required. Some clubs need an hour of advice and they're fine. Others need a six-month embedded relationship to fix a governance crisis. The dose is determined by the gap between where the club is and where it needs to be β financial stability, ISA 2022 compliance, safeguarding maturity, member engagement, leadership succession.
Club readiness. A club with an engaged committee that's already asking the right questions is ready to absorb help. A club with a depleted committee that's in denial about its problems isn't β even if the dose required is the same, the work has to go differently. Trying to deliver high-dose intervention to a low-readiness club produces no outcome and consumes officer time. Trying to deliver low-dose intervention to a high-readiness club is a wasted opportunity.
The four quadrants and what to do with each:
High dose, high readiness β embed. This is the highest-yield work in your portfolio. The club knows it has problems, the committee is willing to engage, the gap is significant. Assign a named officer for a defined period (typically 3β6 months) with specific milestones. Protect this work in the calendar. The clubs in this quadrant are where measurable governance, participation, and capability gains will come from.
High dose, low readiness β pre-work. The club needs significant change but isn't ready. Don't assign embedded support yet β it'll fail. Instead, run the pre-work: a single conversation with the chair about what the club's three-year picture looks like, a board observer arrangement, an invitation to a peer learning session with a club that's been through similar change. The goal is to move the club from low to high readiness over 6β12 months, then graduate it to embedded support.
Low dose, high readiness β service. The club needs targeted advice and they know it. Template constitution clauses, a treasurer's checklist, a connection to a grant funder. Run this through your standard channels β workshops, templates, the RST website, an office hours session. The officer time per club is low and the per-club outcomes are real.
Low dose, low readiness β monitor. The club doesn't need much and isn't ready to engage anyway. Don't ignore them β keep them on the watchlist β but don't allocate ongoing officer time. The signal you're watching for is a change in readiness: a new committee, a near-crisis, a sudden growth event. When that happens, they move to a different quadrant.
The quadrant assignment isn't permanent. Clubs move. The annual planning conversation is essentially: which clubs moved quadrants last year, and where are we deploying officer time this year accordingly.
What this needs from the data
This triage works in theory and fails in practice if the development team can't see club status across the region. Most RSTs can't, currently, because club data lives in disconnected places.
Membership and registration data lives at the club, or in the club's NSO regional body β which doesn't share with the RST. Constitution and governance data lives with the Companies Office register, which the RST can pull but doesn't routinely. Programme participation data lives in the RST's own programme delivery records. Funder relationships sit in the territorial authority's grants system. Financial health is opaque unless the club volunteers a snapshot.
The minimum viable cross-sport dashboard for an RST has four signals per club:
Governance currency. ISA 2022 registration status, constitution last-updated date, committee composition (full / partial / missing key roles). Most of this can be derived from the Companies Office register plus the affiliation declaration the club signs annually.
Activity signal. Is the club active? Submitting registrations, running competitions, holding AGMs on schedule. The proxy is registration data from the NSO regional body, which requires the RST to have a data-sharing relationship with each NSO.
Demographic profile. Who plays here? Age bands, gender mix, ethnicity (where the club collects it), disability inclusion indicators. Sport NZ's KPIs around underserved communities need this data at club level, not aggregated.
Officer-touch history. When did the RST last engage with this club, and for what? A simple log that prevents the situation where two officers visit the same club in a fortnight to discuss similar things, or where a struggling club hasn't had an officer visit in two years.
None of this is hard data, individually. The problem is that pulling it from four sources every time a development manager wants to triage the region's clubs is so painful that no one does it monthly. Triage becomes annual at best, and reactive in between.
What Sport NZ will want to see at the next outcome report
The Community Sport Strategy's reporting expectations are shifting from output measures (workshops delivered, clubs visited) to outcome measures (clubs in good governance health, participation growth in underserved demographics, system capability indicators). For RSTs, this means the funding conversation in 2027 is going to look different from 2024.
Three specific shifts to plan for:
Demographic segmentation of participation data. Aggregated regional participation numbers aren't going to be sufficient. The breakdowns Sport NZ is interested in β by ethnicity, gender, age band, deprivation index β require club-level data that most RSTs currently can't access.
Club health as an outcome, not an input. The number of governance workshops you delivered matters less than how many clubs are now in good governance health as a result. That measurement requires baseline and re-measurement data per club.
Cross-sport delivery against single-sport reporting. Sport NZ funds the RST to deliver across all sports in the region. NSOs report their sport's data through their own channels. Reconciling these views β which clubs are touched by which programmes, where the cross-sport gaps are β is currently very manual.
An RST that has a single dashboard answering these three questions in 2027 is in a fundamentally different conversation with Sport NZ than one still compiling them from spreadsheets.
What to do this quarter if you're the RST GM
Four moves, none of which require a software procurement.
Map your current officer time against the triage matrix. Pull the last quarter's officer time logs β or reconstruct from memory if you don't keep logs. Which clubs got how many hours? Are those clubs concentrated in the high-dose / high-readiness quadrant where the yield is highest, or scattered across all four? Most teams discover the distribution doesn't match the strategy.
Pick five clubs to formally move to embedded support. Not the loudest clubs. The clubs where a 3β6 month relationship is most likely to produce a step change in governance, participation, or capability. Brief the assigned officer on what success looks like by month six. Protect the time.
Build a simple cross-sport club register. A shared spreadsheet, if that's all you can manage this quarter. One row per club, columns for the four signals (governance, activity, demographic, officer-touch). Update it monthly at the team meeting. You don't need a platform to get the discipline β but having the discipline first makes the platform decision much clearer when you make it.
Have one conversation with your three biggest NSO regional bodies about data sharing. Provincial union of [your dominant sport], regional federation of [your second dominant sport], state association of [your third]. What would a data-sharing arrangement look like? The goal isn't a signed agreement this quarter β it's understanding what each NSO would and wouldn't agree to so you can plan the actual ask for next year.
How TidyConnect fits the RST view
TidyConnect's cross-sport dashboard is built for exactly this problem: visibility across hundreds of clubs in multiple sport codes, without requiring every club to be on the same system. Clubs already running TidyHQ connect automatically. Clubs in other systems connect through API, scheduled export, or β for the long tail β a lightweight portal. The development team sees one register with the four signals, refreshed continuously rather than reconstructed annually.
For the GM, the report Sport NZ wants in 2027 is generated from the same data the officers use weekly. For the development officers, the triage matrix isn't an annual exercise β it's the operating view of the region. For the clubs, the touchpoint with the RST is more useful because the officer arrives knowing the context.
The Sport Waikato dev officer driving between two clubs on a Tuesday is still doing the work no software replaces. The difference is whether she's responding to whoever called first, or working through a triaged list that reflects where her time produces the biggest gain for the region.
References
- Sport NZ β Community Sport Strategy, RST investment framework, Active NZ
- Aktive (Auckland's RST) β One of the country's largest RSTs
- Sport Waikato β Reference RST, Hamilton-based
- Sport Canterbury β South Island RST model
- Companies Office β Incorporated Societies β ISA 2022 registry
Header image: by Ollie Craig, via Pexels
Don't miss these

Sports Club Grants in Saskatchewan: Complete Funding Guide
Sask Sport, Lotteries Trust, and community foundations - here's every grant pathway for Saskatchewan sports clubs.

Writing a Vision and Mission Statement for Your Canadian Sports Club
Most club mission statements are forgettable sentences that could apply to any organisation on earth. Here's how to write one that actually means something to your community.

Policy Checklist for Singapore Community Sports Clubs
The Societies Act, PDPA, safeguarding obligations - here's which policies your Singapore sports club actually needs, which can wait, and where to find templates.