Multilingual Articulate Storyline Safety Training: Case Study
This Storyline safety training case study shows how IKHYA helped a global industrial equipment manufacturer launch one 30-minute Articulate Storyline 360 safety course in 9 languages at 14 sites on the same day, 5 weeks after kickoff. All 9 language versions live in one master file, and 91% of learners completed the course in the first 30 days.
Get a Free Quotation
Scoped proposal delivered within 48 hours
- 9languages, live on the same day
- 14sites, none left on an outdated version (3 were before)
- 5 weeksfrom kickoff to launch (the last update took 4 months to reach every site)
- 91%completion in the first 30 days
Project snapshot
| Item | Detail |
|---|---|
| Industry | Manufacturing (industrial equipment) |
| Client | Global industrial equipment manufacturer, about 6,500 employees, name withheld |
| Region | 14 plants and service sites in Europe, Latin America and Asia |
| Audience | 6,500 production, warehouse and field-service staff |
| Scope | 1 course, 30 minutes, 4 branching hazard scenarios |
| Languages | English, German, French, Spanish, Brazilian Portuguese, Polish, Czech, Simplified Chinese, Thai |
| Tools | Articulate Storyline 360 with Articulate Localization; Review 360 for language validation |
| Output and LMS | SCORM 2004, one package for all languages, client's own LMS |
| Timeline | 5 weeks |
| Team | Instructional designer, Storyline developer, localization project manager, native linguists |
| Reviews | 2 English review rounds + 1 in-country review per language |
About the client
The client designs and services heavy industrial equipment and runs 14 plants and service sites across Europe, Latin America and Asia. A central EHS team sets one global safety standard, and each site's training coordinator rolls it out locally. The company asked us not to publish its name.
The challenge: one safety standard, many local versions
Each site translated the global safety course on its own. The last update took 4 months to reach all 14 sites, and 3 sites were still running an outdated version. Local versions also differed in content, so the EHS team could not show that every site trained the same rules.
The constraints
- A fixed global launch date tied to a new safety standard.
- Languages with longer text (German) and different scripts (Simplified Chinese, Thai).
- A limited budget for voiceover.
- Shift workers who could give the course 30 minutes, not a half day.
Goals
All 9 languages live at all 14 sites on one date.
Identical content in every language and at every site.
One file to update, so the next change is made once.
Completion visible per language and per site in the client's LMS.
What we built
4 branching hazard scenarios
Forklift traffic, working at height, machine guarding and chemical storage. In each one, the learner makes the call a worker would make on the floor and sees what happens next.
Translation-ready layouts
Text containers and buttons sized for 35% text growth, with fonts checked in the published course for every script, including Simplified Chinese and Thai.
No text inside images
Signs, labels and callouts were built as editable text, because text inside images is not translated automatically.
One multi-language project file
All 9 languages sit in one Storyline 360 file, translated with Articulate Localization and the client's safety glossary, then checked line by line in context by native linguists.
Voiceover in every language
Human voiceover in 6 languages and AI voiceover in 3, a budget decision agreed with the client. Native speakers reviewed every script.
Localized player
Buttons, menus and messages in the course player appear in each learner's language.
The smart decision: one master file. Instead of 9 separate course files, we kept every language in one master file and published it as a single SCORM 2004 package. Learners pick their language when they launch the course, and the next update happens once.
Why one master file: the Storyline translation routes
Storyline 360 offers two ways to translate a course. The choice decides how much work every future update takes.
| Compared | Manual XLIFF or Word translation | Articulate Localization |
|---|---|---|
| How it works | Export the text (XLIFF 1.2, XLIFF 2.0 or Word), translate it, then import it into a copy of the project | Storyline translates the project and stores all languages in the same file |
| Files to maintain | One project file per language | One file for all languages |
| Updates | Repeat the export and import for each language copy | Storyline finds changed source text and retranslates only those changes |
| Review | Translators work in the exported XLIFF or Word file; the author then checks the imported text in each copy | Native validators suggest edits in context in Review 360; the author imports them |
| Done by hand | Trigger conditions and player text labels; closed captions are translated separately | Layout fixes, helped by the built-in Layout Issue Finder |
Two more facts shaped the build. XLIFF and Word export are not available inside a multi-language course, so a team that wants that route has to save each language as its own file. And for LMS delivery, a multi-language project can be published as one package: learners choose their language at launch, and in SCORM 2004 Storyline reports the learner's language code in cmi.learner_preference.language, if the LMS supports that field. In an LMS, the chosen language is saved with the learner's progress, and the progress has to be reset before the learner can choose another language.
For this client, the deciding factor was the next update. Nine copies meant nine export and import cycles every time the safety standard changed. One file meant one change, one validation pass on the changed lines, and one publish.
How we worked: 5 weeks, step by step
- 01
Design
Week 1Discovery with the EHS team, a design document and a translation-ready storyboard, and a safety glossary agreed for all 9 languages.
- 02
English build
Weeks 2 to 3The full course in Storyline 360, with 2 review rounds by the client's safety experts. Translation started only after English sign-off.
- 03
Languages
Week 4Translation, voiceover and one in-country review per language, with native reviewers validating every slide in Review 360.
- 04
Testing and launch
Week 5Every language tested in the client's LMS (language choice, completion and scoring), then launch at all 14 sites on the same day.
Results
| Result | What was measured | Baseline | Period and source |
|---|---|---|---|
| Live at 14 sites in 5 weeks, on the same day in all 9 languages | Launch date per site | Last update took 4 months to reach every site; 3 sites on an outdated version | Launch dates from the client's LMS |
| 9 language versions from 1 master file | Number of source files to maintain | A separate local version at each site | Project file at handover |
| 91% completion across all sites | Completions out of enrolled learners | No comparable figure: old local versions were not tracked the same way | LMS completion reports per language, first 30 days after launch |
Honest caveats: AI voiceover was used for 3 lower-volume languages, and the client plans human voice in the next update. Completion shows reach, not safer behavior; the client tracks safety outcomes separately, and they are not reported here.
What the client has now
One multi-language Storyline 360 file for all 9 languages. When the safety standard changes, the team edits the English text, retranslates only the changed lines, sends those lines to the native validators and publishes one updated package.
As on every IKHYA project, the client received the editable Storyline source files for future revisions.
What the client said
"Nine languages from one Storyline master file, all live on the same day at fourteen sites. Every version was tested in our LMS before launch, and the next update is one change instead of nine translation projects."
Planning a safety course for several sites and languages?
Tell us your languages, sites and LMS. Your free quote includes a recommended route and a timeline for the project.
