A local chapter is not decided on a cluster of members. It is decided on one person ready to run it and on a written mandate saying what they may do alone. Four points must be settled before the announcement: the territory, how money moves, who speaks for the association, and what happens the day the organiser stops. On the tooling side, the rule is a single database split into organisational units, with rights delegated by territory, rather than one platform per city. If nobody volunteers, a local group attached to the national platform does the same work without creating governance debt.
A chapter is born from a person, not from a member count
The request almost always arrives in the same words: "we have a lot of people in Montreal, we should have a chapter there". The cluster is a useful clue, it is not a sufficient cause. We deliberately give no membership threshold above which to open one, because none survives scrutiny: a city whose members already know each other and meet every month needs nothing, and a city where a long list of names sits in the directory without anyone ever having spoken will not produce a chapter by spontaneous generation.
What makes a chapter comes down to three conditions, checked in this order. The first is a named organiser, a person who publicly accepts the role, not a group of goodwill. The second is a written mandate, setting out what that person may commit to without going back to the national board. The third is a minimum of means, which means access to the members in the territory, a way to contact them, and a budget, even a symbolic one, for the first gathering.
None of the three substitutes for the other two. An organiser without a mandate spends the first months asking for permission, then gives up. A mandate without an organiser is a box on an org chart. And means with nobody to use them produce an empty page on the platform, which is worse than nothing: a member who clicks on the name of their chapter and finds no activity concludes that the whole association is asleep.
Geography helps choose between candidate cities, not create candidates. Seeing where members actually are remains the starting point, and it is exactly the first use we describe in the interactive map of a diaspora: it shows where a chapter would make sense, it does not say whether it will hold.
What the chapter decides alone, and what stays national
This is the conversation boards postpone, and the one that determines whether the chapter survives. It is settled by sorting decisions into three families, once and for all, rather than case by case under pressure.
- Local by nature. The calendar of local gatherings, the choice of venues, welcoming newcomers, nearby partnerships with no financial commitment, the tone of exchanges inside the group. A chapter that has to get the date of a drinks evening approved is not a chapter, it is a letterbox.
- National by nature. Membership and its price, public statements in the name of the association, ownership and security of member data, use of the name and logo. These commit the whole legal entity, and a chapter cannot carry them without exposing the others.
- To be negotiated, therefore written down. The local budget and where it comes from, the chapter's external communication, the right to recruit new members, and the chapter's representation on the national board. These four produce the conflicts, precisely because they do not fall obviously on either side.
A simple principle settles the edge cases: the chapter decides what commits only itself, the national level decides what commits the other chapters. A failed evening in Lisbon has consequences only in Lisbon. A public statement signed with the association's name has consequences everywhere, including in the cities that will hear about it only when someone asks them.
Write the mandate before announcing the chapter
The mandate fits on one page, and its merit is not legal: it forces the conversation while it is still easy. Written after the first disagreement, the same text reads as a sanction and will be received as one. Written beforehand, it reads as a framework, and the organiser mostly finds protection in it.
Five points are enough. The territory, named without ambiguity, including what happens to members living just outside it. The term, with an end date and an explicit renewal, because a mandate with no end is never taken back without a crisis. What the chapter may commit, in money and in name. What it reports back, and how often. And finally how it ends, on both sides, without it being experienced as a personal failure.
One more point belongs there and is almost always forgotten: the chapter's working language. A chapter set up in a country whose language is not the association's will naturally shift to the local language for its internal exchanges. That is neither a problem nor a betrayal, provided it is decided rather than endured, and provided the information that concerns everyone keeps circulating in the reference language. We cover that trade-off in running a community in three languages without splitting it in two.
Choosing the scale: city, metropolitan area or country
The way the map is cut looks incidental and is not, because it is very hard to revisit once chapters carry names and people identify with them. Two symmetrical mistakes are waiting.
A scale that is too fine produces anaemic chapters: splitting a region into municipal chapters gives as many organisers each struggling to gather a handful of people, where a single regional chapter would have filled a room. A scale that is too broad does the opposite: a national chapter in a large country ends up organising only online gatherings, for lack of a venue anyone can reach, and loses exactly what makes a chapter worth having.
The practical test is the journey. A chapter is the right size when its members can come to an evening gathering and get home the same night. That test gives very different territories from one country to the next, and that is normal: the consistency to look for is not in surface area, it is in what the member actually experiences.
Two precautions complete the choice. Name the territory after its area rather than its central city when it extends well beyond, otherwise members in neighbouring towns will not feel concerned. And plan from the start for the member who belongs to two chapters: multiple membership must be possible, otherwise it will resolve itself as duplicates in the database.
One database, delegated territories
The most common reflex is also the most expensive: opening a messaging group per city, or worse, a separate platform account for each chapter. Both amount to splitting the community in order to structure it, when the point is to do the exact opposite.
The rule that holds is a single database split into organisational units. A chapter is not a separate database, it is a scope carried by profiles and by content. Members, events and listings can then belong to each chapter while still being managed from the same administration space, and rights are delegated by scope: the chapter organiser administers their territory, not the national database. This is the same logic we describe for a multi-campus alumni network, where the question arises with the same constraints and the same traps.
Three benefits follow, and they are the real reason not to fragment the tool. A member who moves is reassigned instead of signing up somewhere else, so their history follows them. The national board sees each chapter's activity without having to ask for it by email. And a chapter that stops does not leave with its members, since they never left the shared database.
It is worth being clear about what this requires on the plan side. Gatherings with registrations rely on the events module, available from the Pro plan onwards, as are the map and membership management. The Starter plan includes the directory, the activity feed and messaging: a chapter can exist and talk there, but cannot manage its own registrations. Better to know that before announcing a programme of local events. For the comparison with the solution nearly every chapter tries first, see WhatsApp group or diaspora platform.
Money, voice and data: three questions to settle in advance
Money. The question arises at the first paying gathering: who collects, and who keeps? Three models are equally defensible, provided one is chosen and written down: membership stays national and the chapter receives an allocation, membership is shared according to a key fixed in advance, or the chapter invoices its own activities and leaves membership to the national level. The only bad choice is not choosing: the cash from a first event then ends up in a personal account, and nobody will dare raise it. The payment methods available locally add a constraint we cover in collecting membership fees from abroad.
Voice. A chapter quickly becomes the natural counterpart for the institutions of its territory, and that is good news. It also becomes, in the same movement, the voice those institutions will attribute to the whole association. The rule to set fits in one sentence: the chapter speaks about its activity, the national level speaks about the association's position. When a document goes out to a consulate or a local authority, the standards of caution are those we set out in producing a credible report for a consulate or a local authority, and they apply to a chapter just as much as to the board.
Data. This is the most often neglected point and the hardest to fix afterwards. A chapter administers a scope, it does not own its members. In practice, that means the contact details of members in the territory stay in the association's database, not in the organiser's address book, and that a local export is justified by a specific use rather than by convenience. The principle matches that of data portability on a platform: the association must be able to take back what belongs to it at any time, including from a chapter that falls out with it.
Opening a chapter in seven steps
- Find the organiser before anything else. Until the person is identified and has agreed, the chapter does not exist, however dense the member map looks.
- Define and name the territory. An explicit area, a name that speaks to neighbouring towns, and a written answer for the member who straddles two chapters.
- Write the mandate and have the board approve it. One page: territory, term, what may be committed, what is reported back, how it ends.
- Create the unit on the platform and delegate the rights. The organiser must see and manage their territory, and only that, from the same administration space as the rest of the network.
- Attach existing members without asking them anything. People in the territory are already in the database: they should discover the chapter, not fill in a sign-up form.
- Open with a service, not an announcement. A first useful gathering, a welcome for newcomers, a concrete piece of mutual help. An institutional announcement convinces nobody to travel.
- Set a dated review. A review at a known date, with the organiser and the board, to adjust the mandate or to conclude that it should stop. Without a date, nobody will reopen the subject.
When a local group is enough, and better
Creating a chapter is not always the right answer, and it is better said before the board meeting than after. At least three situations call for something lighter: a local group on the national platform, with no mandate, no budget and no governance of its own.
- Nobody wants to run it. This is the most common case and the worst handled. A chapter created without an organiser because "the city deserves one" produces an empty shell. A local group lets members organise among themselves and reveals, when the time comes, the person who naturally takes charge.
- The population is passing through. A university city where members stay for the length of their studies will not sustain a structure: each mandate would need redoing before it had produced anything. A group, by contrast, survives the turnover.
- The community already meets elsewhere. If members in the territory already see each other in an existing setting, whether associative or professional, creating a competing chapter divides rather than unites. Better to attach a group to it and let both settings coexist.
The test is simple: if the only thing missing is a place to talk, a group is enough. If what is missing is someone who decides, organises and commits, then a chapter is justified. Moving from one to the other is painless when the database is shared, one more reason not to fragment the tool. The same reasoning, applied to an alumni network, is developed in creating and running regional alumni clubs.
Plan for the end from day one
A local chapter usually goes quiet for a single predictable reason: the organiser stops. A move, fatigue, a change of job. It is not an accident, it is the normal cycle, and the only question worth asking is what remains the next day.
Three things must live somewhere other than in the organiser's head and phone. The list of members in the territory, which must be a view of the shared database and not a personal file. The history of gatherings, agendas and notes included, because a successor takes over a chapter in motion rather than a blank page. And the local contacts, those field relationships that take years to build and disappear in one evening if they were never written down.
Finally, a chapter must be allowed to close. A dormant period announced as such, with members reattached to the national scope and a door left open, costs far less than a chapter officially alive whose last activity is old. Members read the difference between an acknowledged pause and an abandonment very well, and it is one of the traps we list in the seven traps of a diaspora platform.
In short
How many members do you need before opening a local chapter?
There is no threshold that holds up, and we decline to invent one. The decisive criterion is having someone ready to run the territory and to accept a written mandate. A cluster of members without an organiser produces no chapter; a motivated organiser in a modest city produces one.
Does each chapter need its own platform?
No, and that is the most expensive mistake. The right structure is a single database split into organisational units, with rights delegated by territory: each chapter manages its own members, events and listings from the same administration space. A member who moves is simply reassigned instead of signing up again.
Which plan is needed for chapters with their own events?
The events and registrations module is available from the Pro plan onwards, at 149 € per month, as are the map and membership management. The Starter plan, at 69 € per month, includes the directory, the activity feed and messaging: a chapter can exist and talk there, but cannot manage its own registrations.
What happens when a chapter organiser steps down?
Plan for it beforehand. The list of members in the territory, the history of gatherings and the local contacts must live in the association's database, not in the organiser's phone. If nobody takes over, announcing a dormant chapter and reattaching members to the national scope costs far less than displaying an active chapter with no activity.
Method and sources. This is a method article: it relies on no external source and puts forward no market figure. What it describes comes from field observation with diaspora associations, not from measurement. We deliberately publish no membership threshold justifying the opening of a chapter, and no demographic data on diasporas, for lack of a verifiable measure to cite. The only figures mentioned are Terrilink's public prices, and module availability follows the plan matrix: events and registrations, the map and membership management are included from the Pro plan onwards, while the directory, the activity feed and messaging appear in every plan. The association governance questions raised here, in particular the mandate and the sharing of resources, depend on your own statutes and call for your own analysis.