Running a bilingual organisation without doubling the work

A good number of Indonesian organisations have a genuinely mixed membership. An alumni association where half the cohort works abroad. A professional body whose technical vocabulary is English but whose meetings are in Bahasa. An expatriate-adjacent club, a diaspora network, an international school's parent association. In all of them, writing only in one language leaves somebody guessing, and writing in two doubles a workload that is already being carried by volunteers.

The usual outcome of that tension is not two beautiful versions of everything. It is a well-intentioned start, a growing backlog, and eventually a lot of things that never get sent at all because the translation never got done.

Decide which language is the home one

The most useful decision is also the one organisations avoid, because it feels like choosing between members. Pick a primary language. Everything is written in it first, and it is the one that is always correct and always current.

Without this you get a subtler problem than backlog: drift. Two versions of the same page, edited at different times by different people, slowly stop saying the same thing - and now a member's understanding of the joining fee depends on which language they read. A primary language means there is always one authoritative version, and the other is a translation of a known state.

Choose based on who your members actually are, not on aspiration. If ninety percent of your members are more comfortable in Bahasa, that is your home language even if your industry's jargon is English. The minority language then serves the people who need it, rather than everything being written twice for the comfort of a few.

Not everything deserves both languages

This is where most of the work disappears if you let it. Sort your communications into three piles and treat them differently.

Always both. Anything a member could get wrong at a cost: the fee and what it includes, how to join, renewal notices, venue and time for a major event, anything about money, anything with a deadline, and your privacy and refund terms. These are short, they change rarely, and translating them once is a small fixed cost with a large payoff.

Primary language only. Day-to-day chat, informal announcements, the group discussion, photo captions, the running conversation of the organisation. Trying to run a bilingual group chat is exhausting and it makes the conversation stilted for everyone. People manage far better with informal text in a second language than administrators expect.

Whichever suits the audience. A message to the committee, a note to one member, a post aimed at a specific subgroup - use the language of the people reading it and do not translate for the sake of symmetry.

Keep the second language equal, not decorative

If you do produce a second-language version, it needs to be as current as the first, or it is worse than not having one. A page that still shows last year's fee because nobody updated the English version is not a courtesy; it is a source of avoidable arguments, and the member who relied on it is entirely right to be annoyed.

The practical discipline is to treat the translation as part of publishing, not as a follow-up task. If it is not translated, it is not finished. That sounds strict, and it is the thing that keeps a second language from quietly becoming a stale archive. If you cannot maintain both, be honest and keep one - a well-maintained single language serves members better than two half-tended ones.

Let members tell you which one they want

The tidiest fix, and the one that removes most of the remaining duplication, is to ask each member their preferred language when they join and then use it. One field, chosen once, and now a renewal notice goes out in the language that member reads rather than in both, or worse, in one and a hope.

This is where a membership system earns its place. Storing a language preference against each member and sending each of them the right version turns bilingual communication from a doubling of effort into a mild extra step at template-writing time. It also gives you something useful to look at: if only eleven of your two hundred members prefer English, you have learned something about how much effort the second language deserves.

Names, forms and the details that trip people

A few practical things that cause more confusion than their size suggests.

Keep proper nouns untranslated. Your organisation's name, event names and role titles should be the same in both languages, or members end up unable to tell whether "Annual General Meeting" and the Bahasa version are the same event.

Watch dates. Writing 03/04 is genuinely ambiguous across an internationally-mixed membership. Spell the month out and the problem disappears.

Be careful with fees. Rp 250.000 is unambiguous; "250k" is not, and a member reading in their second language may not be sure what you mean.

And if your website is bilingual, make the language switch obvious and make it keep the person on the same page rather than dumping them at the homepage. Our piece on a one-page website covers keeping this simple when you have limited time to maintain any of it.

What good looks like

A bilingual organisation that has got this right is not one that publishes everything twice. It is one where the important things - money, deadlines, how to join, what you get - are unambiguous in both languages and kept current, while the daily life of the organisation happens in whichever language the room is speaking. Members can find the answer to anything that matters. Nobody is translating group chat at eleven at night. That is the version that lasts.