Chapters, regions and the website nobody ownsChapters, regions and the website nobody owns

Any association with chapters, regions or operator groups knows the pattern. Head office runs the main website and the AMS, the association management system that holds members. Each chapter, meanwhile, has its own site, built by a volunteer three years ago on whatever was free at the time. Some are current. Most are not. One has a login nobody remembers.

Head office cannot fix them, because it does not own them. Chapters cannot keep them up, because volunteers rotate. Members cannot rely on them, so they email instead. The chapter website is the page nobody owns.

Why chapters go their own way

Because the association's system gave them nothing. A typical AMS has no idea of a chapter beyond a field on the member record. There is no chapter page, no chapter event, no chapter member list a chair can see, no way for a chapter to send its own email. So the chair builds something outside, and the association's data and the chapter's activity part ways.

What chapters actually need

Less than they build. Talk to chapter chairs and the list is short: a page members can find, a list of who is in the chapter, a way to announce and register for chapter events, a way to email chapter members, and a place for the minutes. Most chapter websites are an elaborate way of delivering those five things badly.

A chapter as part of the platform

When the association runs on one member platform, a chapter is not a separate website. It is a space inside the system with its own page, its own event calendar, its own member list, drawn live from the same record as everything else. The chair gets a role, not a login to a second system. A member who moves cities moves chapters, and the chapter list updates itself.

Chapter events sit on the same calendar and the same registration flow as the annual conference, so a member registers on their own account and the chapter treasurer sees the list without a spreadsheet. Chapter email goes to the current member list, not to the copy someone exported in March.

What head office gains

Visibility, mostly. Which chapters are active, which events fill, where members are engaged and where they are not. And control of the brand: chapter pages carry the association's design on the association's domain, so a member in one region sees the same organization as a member in another.

It also gains an answer to the oldest chapter argument, which is who pays for what. When the chapter's page is part of the platform, there is no chapter hosting bill and no chapter web volunteer to replace.

A chapter's year, inside the platform

Take the Benelux chapter of a fictional trade network. In January the chair posts the year's four meeting dates on the chapter page; they appear on every Benelux member's calendar and on the society's public calendar, marked as chapter events. In March a member moves from Antwerp to Frankfurt, updates her office in the portal, and drops off the Benelux list and onto the German one without anyone being told.

In September the chair emails the chapter about the Antwerp meeting from the platform, to the eighty-six members who are current that morning, not the ninety-two who were on a spreadsheet in May. Registrations land on the member records and on the chapter's attendee list. In December the treasurer sees chapter dues collected per member, without a separate bank reconciliation, and head office sees which chapters met, how often and with how many.

Nothing in that year required a chapter website, a chapter mailing list or a chapter spreadsheet. The chair did four things and the platform did the rest.

What chapters give up

Their own thing. This matters, and it is worth being honest with chairs about it. A chapter used to complete freedom over its site loses some. The trade is that the site works, stays current after the chair steps down, and is used. In practice, chairs who have spent a weekend recovering a lost hosting password are not hard to persuade.

The chapter chair as a role

The quiet change in all of this is that a chapter chair becomes a role on the platform rather than a person with a separate login somewhere else. The role can edit the chapter page, create chapter events, email chapter members and see the chapter's renewals. When the chair changes at the annual meeting, the role moves to the new chair with one click, and the old chair keeps ordinary membership. No password handover, no orphaned website, no six-month gap while the new chair finds out what the old one built.

Where to begin

Inventory the chapter sites first. How many, on what, who has the login, when last updated. Then ask three chairs what they actually use theirs for. The answers shape the chapter space in the platform, and they usually shrink the project rather than grow it.