Club Development Framework for Canadian Community Sports

Open the standard club development self-assessment that most provincial sport organisations distribute and you’ll find roughly the same structure. Eight to twelve domains — governance, finance, facilities, coaches, athletes, volunteers, communication, programming, sometimes a few more. Each domain has a maturity scale, usually four or five levels. The board is invited to score each domain, identify gaps, and write a development plan to close them.

It is a sensible framework. It produces consistent data for the PSO. It looks impressive at the AGM. It almost never produces real change in the club.

The reason is straightforward. A club running on volunteer hours has the capacity to make one significant structural change per year. Maybe two if everyone is unusually motivated. The framework tells the board there are twelve domains needing attention and invites them to make twelve micro-improvements simultaneously. The result is twelve domains that move from “developing” to “developing” with slight rewording, no real change in operations, and a board that’s exhausted by July from trying to make progress on everything at once.

The version that produces actual change is structurally different. It asks one question.

The one question

What is the single bottleneck in this club — the one thing that, if it weren’t a problem, would make most of the other things easier?

Almost every community sports club has one. It’s usually not a secret. The chair could tell you in a sentence. Examples:

• “Our junior program is healthy but we can’t get juniors to stay through the senior transition.”
• “Our coaching base is one person — if she leaves we lose everything.”
• “We have decent facilities but the committee is six people who all want to retire.”
• “Our membership numbers are fine, but we run a deficit every year because the canteen barely breaks even.”
• “Our governance is solid but nobody is doing communications and the membership feels disconnected.”

Each of these is one structural problem. Each is genuinely the dominant constraint in that club. Solving it would make the next year’s club development questions easier. Failing to solve it means every domain on the framework will keep moving sideways.

Pick the one. Write it down. That’s your development priority for the year. The other domains will sort themselves out in the slipstream — not because they don’t matter, but because they were always going to be downstream of the one constraint.

Why frameworks resist this

The PSO version of the framework is designed for portfolio reporting. The provincial body needs to roll up data across hundreds of clubs and report system-level trends to the funder. That report requires consistent multi-domain scoring across the system. So the framework is built for the PSO’s aggregation needs, not the individual club’s capacity to act.

This isn’t a complaint against PSOs — they have real reporting obligations and the framework serves them. But the framework is being used by the wrong audience when it lands on the volunteer-run club board and is treated as a development tool. For that audience, it’s the wrong shape.

The clubs that grow consistently year-on-year tend to either ignore the framework and focus on one priority, or fill in the framework for the PSO and then ignore it internally while focusing on one priority. Either approach produces the same outcome. The clubs that genuinely try to use the framework as their internal development tool tend to plateau.

What “one priority” actually looks like in practice

A football club in southern Quebec identified, in 2023, that its single bottleneck was that the same five volunteers ran every event, all twelve months, with no rotation. They were burning out. The club had thirty other adult members who were not involved in anything beyond playing.

Instead of working through a twelve-domain self-assessment, the board ran one piece of work for the year: build a rotating volunteer structure where every event was owned by a different two-person team, with shadowing from someone who had run it the previous year. They created a one-page handover document per event. They explicitly recruited members who were not currently helping.

That single piece of work took the board’s attention for the season. It produced a healthier volunteer base by the following AGM. The club’s facilities, finances, and coaching arrangements barely changed — but because the volunteer base was working, all three of those domains were easier to manage going forward. The PSO’s framework, if they’d filled it in honestly, would have shown most domains unchanged. The clubhouse would have shown that the club had genuinely become a different organisation.

What the chair should actually do

Three things, in order. Together they take a single committee meeting.

Ask the board what the dominant constraint is. Let people answer in their own words, without the framework’s vocabulary. Listen for the constraint that two or three directors name independently. That’s almost certainly your one priority.

Name a single person to own work on the priority for the year. Define what “done” looks like, even roughly — what would the club look different by next AGM? Carve out time in committee meetings to report progress, not as an item under “any other business” but as a standing agenda item.

Fill in the PSO framework if you have to. Be honest, but be brief. Note, in writing, that the club’s actual development focus this year is the named priority, and that the other domains are being held steady rather than actively developed. The PSO contact will read this and either understand (most of them do) or push back (in which case a conversation about what realistic club development actually looks like is overdue).

That’s the framework. The rest is the work itself.