Managing Version Updates in Training Translation Projects in Saudi Arabia

A retail company in Riyadh changes the refund approval limit taught in its customer service eLearning. The Arabic master is updated within a week and goes live. Three months later, a store audit in Jeddah finds that supervisors who take the English version are still applying the old limit. The English module had been translated from the previous Arabic version, and the translation services provider had updated the subtitles but not the quiz question that tested the limit. Nobody could say which language version reflected which source version.

Training translation is rarely a one-off job. Procedures, policies, and systems change, and every change has to travel from the source file to each language version, through a translator and a reviewer, and into the learning platform. When translation services are managed project by project, without a shared record, some changes arrive in one language and quietly miss another.

This article is for HR and digital learning teams in Saudi organizations that maintain training in more than one language, whether they rely on an in-house language team or on external translation services. It describes two tools: a register of source files, language versions, and reviewers, and a verification task that confirms each language has actually received the update.

Why Language Versions Drift After Translation Services Deliver

Most drift comes from ordinary working habits on both sides of the translation services relationship, not from poor translation:

• Updates are sent as an email describing ‘a small change on slide 12’, without the revised source file.

• The translation services team works from a file saved in an earlier project folder.

• The text is updated, but the voice-over, subtitles, images with embedded text, or the quiz are not.

• The revised version is uploaded to the platform in one language only.

• The reviewer who checked the first translation is never asked to check the update.

In Saudi Arabia, keeping content current is also part of the national reference for digital learning. The National eLearning Center’s eLearning standards, which target government, private and non-profit institutions that run or support eLearning, call for ensuring the accuracy, comprehensiveness and currency of digital content, and for systematically and periodically reviewing programs, courses, policies and procedures. A course is only current if every language version is current, which is why version control belongs at the center of any arrangement with translation services.

Build a Register of Source Files, Versions and Reviewers

The register is a single table, owned by the learning team, with one row for each training asset in each language, whether the work is done by colleagues or by external translation services. A shared spreadsheet is enough to start. For each row, record:

• Asset: an ID and name, such as a module, video, job aid, or assessment.

• Source version: the master language and its current version number.

• Language version: the target language and the source version it reflects, for example ‘English 3.1, based on Arabic 3.1’.

• Files: where the editable source and the published file are stored.

• Translator: the person or translation services provider who did the work.

• Reviewer: the named person who approved the translation.

• Status and date: in progress, reviewed, published, or verified.

The ‘based on’ column is the heart of the register. A glance down it shows every language version that lags behind its source, whichever team or translation services provider produced it. It only works if each asset has one master source, so choose it deliberately: usually the language in which the procedure owner writes and approves changes. Ask for editable files with every delivery from translation services, so the register always points to files you can update, not only to published exports.

Give versions a numbering rule that everyone understands. Semantic Versioning, a convention created for software, increments the major number for incompatible changes, the minor number for backward-compatible additions, and the patch number for fixes. Training content can borrow the idea: a major number for changes to structure or assessment, a minor number for changed steps or content, and a patch number for typos and cosmetic corrections. What matters is not the software rule but a shared signal, for your team and your translation services provider, of how much an update matters.

Name Reviewers Before Translation Services Start an Update

Translation quality depends on review, and reviews are easy to skip under deadline pressure. Record a reviewer for each language in the register before any update is sent to translation services, not after the files come back. Separate the roles:

• The translator, internal or from your translation services provider, produces the update.

• A language reviewer, who is not the translator, checks accuracy and terminology against the source.

• A subject-matter reviewer checks that the changed step reads correctly to the people who do the work.

Agree the review scope with your translation services provider in advance: the changed segments plus enough surrounding content to see whether the change still fits. For audio and video, review the rendered output, not only the script. If your organization keeps a terminology glossary, the reviewer checks updated terms against it; our article on translating training content in Oman explains how to build one that matches system screens and workplace terms.

Send Updates to Translation Services as Change Packages

Sending a whole revised course back to translation services wastes time and invites new inconsistencies; sending a vague description leaves the translator guessing. A change package sits in between. It contains:

• The revised source file and its new version number.

• A list of changed segments, screens, or timestamps, with the old and new text.

• Any new or changed terms.

• Affected media: audio, subtitles, images with text, quiz items, and job aids.

• The required date and the named reviewer for each language, so translation services can plan the work.

Many translation services work in tools that exchange content in XLIFF, an OASIS standard format for carrying localizable data from one step of the localization process to the next. In XLIFF 2.1, each segment can carry a state: initial, translated, reviewed, or final. You do not need to handle these files yourself, but you can ask whoever provides your translation services to report status at segment level for each update, so you know whether a changed segment has been translated only or also reviewed.

Costs and responsibilities for updates belong in the agreement with your provider; our guide to comparing training package update costs and reuse rights covers the questions to settle, including whether an update in one language includes the matching change in the other.

Verify That the Update Reached Every Language

The verification task closes the loop. After each update is published, a named person outside the translation services chain, who neither translated nor reviewed it, checks every language version in the platform, using a learner account rather than an administrator view. For each language, the verifier confirms that:

• The version number shown in the module or its record matches the register.

• Each changed screen, audio clip, and subtitle shows the new content.

• Changed quiz items and their feedback reflect the new rule.

• Related job aids and downloadable files carry the same version.

• Assignments and completion rules point to the new version.

Only when every language passes is the register row marked ‘verified’, with the date. If one language fails, the update stays open for that language alone, and your translation services provider receives the specific finding rather than a general complaint. The same discipline applies when an update comes from evaluation rather than a procedure change, for example, when testing whether Saudi eLearning moves employees from viewing to practice leads to a redesigned activity that must reach every language version.

A Hypothetical Example: A Cleaning Chemical Change at a Facilities Company in Riyadh

The following example is hypothetical and is included only to illustrate the method.

A facilities management company in Riyadh runs a safety eLearning module on handling cleaning chemicals, with an Arabic master and English and Urdu versions, produced through external translation services, for its multinational teams. A supplier change introduces a new floor cleaner with a different dilution ratio and an extra glove requirement. The safety manager approves the change, and the Arabic master moves from version 2.0 to 2.1.

The learning team prepares a change package for its translation services provider: four changed screens, two audio clips, one quiz item, and one printable poster. The register names a language reviewer and a supervisor reviewer for each language, and the provider returns segment-level status showing every changed segment as reviewed.

During verification, the English version passes. In the Urdu version, the subtitles show the new ratio, but the voice-over still states the old one, because the audio file had been reused from version 2.0. The Urdu row stays open, the audio is re-recorded and checked, and only then are all three rows marked verified. For any later audit, the register now shows which version each team learned, and when.

Summary

In training translation, the hard part is rarely the first translation; it is every update that follows. A register that links each language version to the source version it reflects, with named translators and reviewers, makes drift visible before it reaches employees.

Change packages give translation services exactly what has changed, and a verification task confirms, language by language, that the update arrived. Together they turn translation services from a series of separate jobs into a controlled process that keeps every language version current.

If you want Skillup MENA to help you, click here.