Scaling global training: 90 languages in one Dynamic SCORM package

Most organisations do not struggle to find a tool that can translate a course. They struggle with everything that happens afterwards: keeping company terms consistent, managing a separate SCORM file for every language, and updating every version when the policy changes.

CourseAgent now translates courses into 90 languages, including right-to-left Arabic, Hebrew, Farsi and Urdu. All 90 course languages are fully live for authors and learners, with native-speaker review complete. The Academy portal interface, emails and certificates are now available in all 90 languages too. The language count matters, but the bigger change is what surrounds it.

The real cost of localisation is maintenance

A translated course is not finished when it is published. Regulations change, products are renamed and procedures are updated. With a traditional workflow, each change means exporting text, sending it to a translator, re-importing it and uploading another package for every language.

Multiply that by ten or twenty languages and a one-line edit becomes a project.

1. Translate into 90 languages in minutes

Translation in CourseAgent happens inside the editor. The whole course is translated together - text, interactions and quiz questions, options and feedback - and each language version stays fully editable so a local reviewer can refine wording before publishing.

Translation uses AI credits (15 credits per course per language), so the cost is visible before you start. See AI course translation for the details.

2. Keep brand and compliance terms safe

Mistranslated product names, job titles and legal terms are the most common localisation complaint. CourseAgent protects names automatically and lets you set shared glossary rules:

• Do not translate - keep a product name, brand or acronym exactly as written.
• Translate as - always use your approved term for a word in a given language.

Glossary rules guide the AI rather than acting as an exact find-and-replace, so human review of important courses is still recommended.

3. One Dynamic SCORM package for every published language

This is the distribution change that saves the most time. Instead of uploading one ZIP per language, a single Dynamic SCORM package can serve all of a course's published languages. Learners see the language they need, and when you republish, the LMS picks up the update without a new upload.

For organisations running the same compliance course across many countries, that means one LMS record to manage rather than dozens. Learn more on the SCORM publishing page.

4. Linked language versions that can still differ

Each language sits in a linked course family. You can update the source and re-translate, or make local adjustments to one version without breaking the others. That suits courses that need a local example, a regional regulation or a different policy contact.

How this compares

Several authoring tools offer translation, and some list a higher raw language count. When comparing, look past the number and ask:

• Are quizzes, interactions and narration translated, or only text?
• Can you protect brand and compliance terms?
• How many LMS packages do you need to manage per course?
• What happens to every language when the source changes?

We have set out the detail, with sources, on our multilingual e-learning comparison.

Where to start

Pick one high-impact course, such as a code of conduct or health and safety induction, translate it into the two or three languages most of your workforce needs, add your glossary terms and publish it as a single Dynamic SCORM package. Once that works, extending to more languages is a click rather than a project.

Start a 7-day free trial to try it with your own course.