Keeping training current across languages

The maintenance problem nobody budgets for, and a routine that stops nine language versions drifting apart.

edon.ai · Draft · 7 min read

The Tuesday problem

The expensive part of multilingual training is not making it. It is the Tuesday, eight months later, when a procedure changes and somebody has to work out which of the nine language versions still says the old thing, fix all of them, and show that every site got the new one.

Nobody budgets for that Tuesday. It lands on whoever is nearest, usually without a schedule and always without a line item.

One master, many versions

The single most useful structural decision is to have one master per module and treat every language as generated from it, never edited independently. The moment a language version becomes its own document, you have nine documents to maintain instead of one, and no reliable way to know which have diverged.

Terminology drifts, quietly

A piece of safety equipment gets translated three different ways across four modules because three different people made a reasonable choice. Nobody notices until an auditor or a new hire does. Fix the term list once, centrally, and apply it rather than relying on consistency between translators who never meet.

Who approved what

The question that catches teams out is not “is this translation good” but “who said it was, and when”. Decide who signs off each language and keep the record somewhere that is not an email thread.

A routine that works

1. Monthly: list what changed in the source content. If nothing did, that took two minutes.
2. For each change: update the master, regenerate the affected languages, and send only those for review.
3. Quarterly: check the term list against what shipped and reconcile the drift.
4. On publication: record which version went to which audience, on the day, while it is still trivial to know.

None of this is clever. It is just written down, which is the part that usually goes missing.