Running a community in three languages without splitting it in two

Multilingualism is not a translation problem

An association discovering its own multilingualism looks first for a tool that translates, a volunteer who proofreads, a budget for subtitles. The instinct is sound, and it is never enough. The translations arrive, and the symptom remains: part of the membership learns of decisions after everyone else, another part stops speaking up, and the board ends up concluding that these people have lost interest.

The reason is that translating answers a narrow question: how to say the same thing elsewhere. The real problem of a trilingual community raises four others. Who decides what gets said? In which language does what gets said prevail? Who answers when somebody writes in their own? And what becomes of information that exists in one version only? These are governance questions, and no translation tool settles them on the board's behalf.

The test is simple. In a community that has settled its language governance, a member who writes in their own language gets an answer and does not wonder whether they missed something. In a community that has settled only translation, all three versions genuinely exist, and yet everyone permanently feels they are in the room next door.

What breaks when language settles itself

Nobody decides to split a community in two. It happens by default, through a series of small concessions, none of which is serious on its own. Four come up almost every time.

• The board's language becomes the association's language. Minutes appear in the language of whoever writes them, because it is faster, and because everyone around the table understands. The decision was never taken, it settled in.
• Conversations migrate to a single space. One messaging group takes over, in one language, and becomes the place where things are actually said. Other members stay subscribed to an official channel where nothing happens. It is one of the mechanisms described in our comparison between a WhatsApp group and a diaspora platform.
• Important announcements go out in one version only. The membership fee call, the notice of meeting, the registration deadline for an event. Those who do not read that language do not reply, and the conclusion drawn is that they are inactive.
• Newcomers pick a side at sign-up. They join the group they understand, and that first-minute choice becomes permanent.

In time, the association has two communities sharing a logo, a treasury and a general meeting. They do not argue, they ignore each other, which is far harder to repair. A language split is among the quietest mechanisms we describe in the pitfalls of a diaspora platform.

Decide which language prevails, and write it down

The least popular decision is also the one that best protects minority languages. A reference language is not a superior language: it is the version that prevails when two translations of the same text diverge. Without it, an association one day finds itself with two drafts of its internal rules that do not say the same thing, and nobody can settle the matter without appearing to arbitrate between communities.

The criterion is neither majority nor country of origin by default. It is the association's ability to guarantee the quality of its texts in that language over time, including after the board changes. A reference language chosen because the current secretary masters it becomes a problem the day they leave. A language chosen because the association will always find a writer for it holds up.

That rule has to be written, short, and available in the same place as the bylaws. Four sentences are enough: which language prevails, in which languages official documents appear, within what time frame translations follow, and whom to ask when a version is missing. A written rule turns a potentially inflammable subject into a plain matter of organisation. An implicit rule leaves everyone free to assume an intention.

Three layers not to be confused

The most common method error is treating all content the same way. Yet a multilingual community handles three layers that call for neither the same effort, nor the same owners, nor the same standard.

• The interface. Menus, buttons, labels, automated emails. It is set once, in the tool, and each member sees it in the language they chose. No governance decision is needed, and no load falls on volunteers.
• Official content. Bylaws, internal rules, membership procedure, notices of meeting, fee calls, minutes, dated event announcements. These bind the association and open rights. They are the ones that require a decision and follow-up.
• Conversations. Posts, comments, private messages, discussion threads. They live in the language of whoever is speaking, and that is exactly as it should be.

Confusing these layers produces two symmetrical errors. Translating conversations exhausts volunteers, slows everything down, and kills the spontaneity that makes a community alive. Not translating official content deprives part of the membership of rights they acquired by joining. The first error tires an association out, the second divides it.

This is where a multilingual platform provides a precise and limited service: it settles the interface layer effortlessly, each member browsing in their own language without anyone having to translate anything. It does not settle the other two layers, which remain human decisions. Knowing what the tool carries and what it does not avoids believing the matter closed because a menu displays in three languages.

What must exist in all three languages, and what can stay in one

One simple rule settles the arbitration without renegotiating each time: translate what opens a right or calls for action within a deadline, not what tells a story. It breaks down into three levels.

• Always. Notice of general meeting, membership fee call, bylaws and internal rules, membership procedure, personal data information, and any message carrying a deadline. These are the texts whose absence in one language deprives somebody of a right.
• Often worthwhile. Announcements of events open to all, meeting minutes, calls for volunteers, the association's presentation to a third party. These gain from existing everywhere, but a few days' delay on one version harms nobody.
• Rarely necessary. An account of an evening, a photo album, a tribute, a themed discussion thread, a congratulations message. Translating them costs a lot and adds almost nothing.

This hierarchy has a concrete advantage: it makes the load bearable, therefore sustainable. An association that commits to translating everything keeps that promise for a few months at most, and the day it cracks, it cracks on the important texts as much as on the rest. An association that commits to a narrow core keeps that commitment for years, and that core is enough for nobody to be shut out of a decision.

The same reasoning applies to documents you send outside. A report for a consulate or a local authority is written in the language of the institution that will read it, and has no reason to exist in all three. Confusing internal and external documents adds work without adding readers.

Name who carries each language

A language without an owner is not a language of the association: it is an intention. As long as translation rests on "somebody will do it", it in fact rests on whoever is most available, until that person tires. The arrangement that holds is more modest and more explicit: one lead per language, named, with a deputy.

The role does not require a professional translator. The lead proofreads what goes out in their language before publication, answers the messages arriving in it or routes them to the right person, and tells the board what is missing. Their main contribution is not linguistic, it is political in the plain sense: they guarantee that part of the community has somebody to turn to.

Two precautions are worth setting from the start. The first is not to confuse a language lead with a country representative: language is not territory, and loading both roles onto one person creates expectations they cannot meet. The second is to appoint the deputy at the same time as the lead, because a single unavailable lead blocks the whole publication chain at the worst moment, typically in the run-up to a general meeting.

This is also what makes the time frame announced in the written rule realistic. A deadline is committed to when somebody carries it. Without a lead, it is only a sentence in a document.

Target by country of residence without assigning anyone a language

Targeting announcements by country of residence exists so as not to flood everyone with information concerning only part of the membership: an administrative procedure specific to one host country, a meet-up in one city, a change to opening hours. It rests on data members declared themselves, which assumes the work of mapping the community has already been done.

The trap is to confuse country of residence with reading language. The two correlate without coinciding: a member long settled in Spain may still prefer to read in French, and another born there may master only the host country's language. Deriving the language automatically from the declared country amounts to assigning everyone a linguistic identity they did not choose, and doing precisely what the association wanted to avoid.

The right division is simple. Country of residence serves relevance: it determines who is concerned by a piece of information. Language serves reading comfort: it stays an individual choice, shown in the profile, changeable at any time. The two settings combine without ever being derived from one another.

The principle goes beyond language. It meets the trade-off we describe for running an event across several time zones: a technical setting is never neutral, because it implicitly designates who is really being invited.

When separating spaces by language remains the right call

It would be dishonest to present the single community as always preferable. There are cases where keeping it is a costly fiction, and where separation serves everyone.

The first case is when the groups share neither the same needs nor the same counterparts. Members organising around administrative procedures specific to one host country gain nothing from having those exchanges translated for members settled elsewhere, who will understand none of it and will tire of the noise. The second case is a community part of which formed well before the association, with its own habits: forcing it into a common space loses both.

The line to hold is then this: separate what is contextual, never separate what makes people belong. Separate conversation spaces by language or by country, yes. One common directory, one treasury, one general meeting, one set of rules, always. Themed groups serve exactly that purpose, and they are available from the Pro plan, at 149 € per month, whereas the Starter plan, at 69 € per month, does not include them.

The warning sign runs the other way and is easy to spot: if the separation starts reaching memberships, accounts or bylaws, these are no longer distinct spaces but two associations that have not yet said so. Better then to acknowledge it and organise it openly, as we discuss in the context of bringing a regional diaspora together online, than to maintain a unity nothing supports any more.

Setting up a trilingual community, step by step

1. Write down the languages actually spoken. Not the ones the board masters, but the ones your members already write to you in. The gap between the two lists is the subject of this article.
2. Choose the reference language and have it minuted. A board decision, recorded, with the reason for the choice. The criterion is the ability to guarantee quality over time, not the number of speakers.
3. Sort your content into three layers. Interface, official content, conversations. The sorting takes one sitting and saves a great deal of pointless translation.
4. Name a lead and a deputy for each language. Two names per language, written where members can read them.
5. Set up the tool. Multilingual interface on, language left to each member in their profile, announcements targeted by country of residence.
6. Translate the mandatory core first. Bylaws, membership procedure, standard notice of meeting, fee call, personal data information. The rest will follow.
7. Review the rule once a year. At the general meeting, alongside the accounts. A community changes in composition, and its language rule has to be able to change with it.

What the tool can carry for you

That leaves the practical question: what in all this can stop depending on one person's goodwill. The multilingual interface is part of it, since each member picks their display language and no longer has to ask. So is targeting announcements by country of residence, since it avoids sending the whole community information that concerns one country. The rest, the written rule, the named leads, the translated core, remains governance work that nobody can automate.

That is the division we stand by with Terrilink for Diaspora: a multilingual platform that removes the technical friction, and decisions that stay the board's. An association expecting a tool to settle its language question will be disappointed; an association that has set its rule and wants to keep it without spending its evenings on it will find what it needs. For the framework applying to your members' data, including when they live in several countries, our GDPR guide for a diaspora platform sets out the obligations.

In short

Method and sources. This is a method article: it draws on no external source and puts forward no statistics on language use in diaspora communities, for want of a verifiable official source. Sorting content into three layers, and separating country of residence from reading language, come from field observation, not from measurement. The product points cited are checked against internal documentation: the multilingual interface and each member's language setting belong to the core included in every plan; discussion groups, events and memberships are available from the Pro plan and absent from the Starter plan. For any statutory or legal question specific to your association, refer to the applicable texts or to professional advice.