Arabic LMS in Qatar: Managing Arabic and English in One Pathway

Imagine the quarterly compliance report at a company in Doha. The code of conduct course shows more completions than there are employees in the target group, yet dozens of those same employees are listed as overdue. Nobody skipped the training. The course exists twice in the Arabic LMS, once in Arabic and once in English, and many employees were assigned both. They finished one version, kept receiving reminders about the other, and now appear in the report as both complete and late.

For organizations whose teams work in both Arabic and English, offering each course in both languages is a sensible decision. Qatar’s Permanent Constitution, in the English translation published by the Constitute Project, states that the official language of the State is Arabic, so the Arabic version is rarely optional. The difficulty is not the translation. It is that an Arabic LMS can treat two language versions of one requirement as two unrelated courses.

This article shows HR, IT, and procurement teams in Qatar how to link equivalent language versions inside one learning pathway, and how to test an Arabic LMS so that each employee receives one assignment and each report counts one completion.

Why One Course Becomes Two in an Arabic LMS

The problem usually starts with a reasonable upload decision. The learning team receives the Arabic and English versions as two packages, loads each one as a separate course, and adds both to the pathway so that employees can choose. From that moment, the Arabic LMS sees two requirements where the organization intended one. The effects appear in three places:

• Assignment: rules that target a role or department assign both versions, so employees receive two enrolments, two deadlines, and two sets of reminders.

• Progress: an employee who starts in English and switches to Arabic begins again from zero, and the pathway may still wait for the version they abandoned.

• Reporting: completions count twice for some employees and appear as overdue for others, so the completion rate stops meaning anything.

None of this shows up in a sales demo of an Arabic LMS, where each course is presented on its own. It appears only after you load both versions, assign them by rule, and run the report a month later.

Decide What Makes Two Versions Equivalent

Before configuring anything, agree on when an Arabic course and an English course count as the same requirement. Linking versions that are not truly equivalent hides real gaps; refusing to link versions that are equivalent creates the duplicates described above. A practical equivalence rule for your Arabic LMS can require that both versions:

• Share the same learning objective and cover the same procedures, policies, and examples.

• Use the same assessment standard: matching questions, the same pass mark, and the same number of attempts
• Carry the same version number and effective date.

• Use the same approved terms for the same concepts, with system labels shown exactly as employees see them.

When a version fails the rule, for example because the English course has an extra module for one department, treat it as a different course with its own record. Name one version as the master that every content change starts from, and record in the Arabic LMS catalog which versions belong together. The discipline of a shared glossary described in our article on designing eLearning for multilingual hotel teams in Qatar applies here as well: if the two versions use different words for the same step, they are not yet equivalent.

Link Equivalent Versions Under One Learning Item

Once equivalence is defined, the Arabic LMS pathway should contain one learning item per requirement, with the language versions attached to it, rather than two separate courses. Each learning management system structures this differently, so do not assume that an Arabic LMS on your shortlist works the way you expect. Ask each provider to show you, in a sandbox loaded with your own two versions:

• How the two versions are linked to one requirement in the catalog and in the pathway.

• How an employee chooses or is given a language, and whether they can switch later.

• What happens to progress, attempts, and the assessment result when they switch.

• Whether completing either version satisfies the pathway step and any prerequisite that depends on it.

Metadata helps the link survive exports and a later move to another Arabic LMS. Tag each version with a standard code: the W3C’s guidance on language tags in HTML and XML explains that language tag syntax is defined by the IETF’s BCP 47 and that the golden rule is to keep the tag as short as possible, so ‘ar’ and ‘en’ are usually enough.

If your Arabic LMS records activity using xAPI, the xAPI data specification published by ADL offers a useful model. It requires that an activity id always references the same activity, defines an activity’s name and description as language maps keyed by language tags, and lets each record state the language in which the experience mainly took place. In other words, one activity can carry an Arabic and an English name while each record still shows which language the employee used. Ask providers whether and how their platform applies this; do not take it for granted.

Prevent Duplicate Assignments in Your Arabic LMS

Assignment rules should target the learning item, never the individual language versions. The Arabic LMS then needs to know which version to offer each employee. Agree on the sources of that decision and their order of priority:

• A language preference field in the employee record, ideally fed from HR data and used as the default.

• The employee’s own choice at the start of the course, if your policy allows it.

• An HR override for roles where one language is required, for example because the procedures that role follows exist in only one language.

Then try to break the setup. Assign the pathway by rule, and ask a line manager to assign the English version manually to someone who already has the Arabic one; a sound setup blocks the duplicate assignment or at least flags it. Change one employee’s language preference, rerun the rule, and check that the Arabic LMS swaps the version rather than adding a second enrolment. Our article on managing employee role changes in an Arabic LMS in Qatar covers what should happen to open assignments when the role itself changes.

Reminders deserve the same test. In a well-configured Arabic LMS, one requirement produces one reminder sequence, in the employee’s language, and it stops as soon as either version is completed.

Keep Arabic LMS Reports Free of Duplicates

Reports are where duplicates do the most damage, because they reach senior managers and auditors. A completion report for a linked item should show one row per employee per requirement, with the language as a column rather than as a separate course. Check that each Arabic LMS report includes:

• The learning item, the language version completed, and its version number.

• One status per employee: not started, in progress, completed, or overdue.

• The completion date and assessment result from the version the employee actually took.

• A completion rate based on the number of employees assigned the requirement, not the number of enrolments.

Then reconcile the Arabic LMS figures. Count the employees in the target group, the rows in the completion report, and the completions; the three numbers should tell a consistent story. Ask how the Arabic LMS issues certificates as well: an employee should receive one certificate per requirement, in a language set by a rule you have agreed, even if they opened both versions.

The same reconciliation matters when one pathway runs across several companies in a group, where reports must combine figures without mixing employers. Our guide to separating data and consolidating reports for Qatar business groups looks at that structure in detail.

A Hypothetical Example: A Facilities Management Company in Doha

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

A facilities management company with sites in Doha and Lusail builds a five-item onboarding pathway for new maintenance supervisors: safety induction, permit to work, customer communication, logging faults in the work-order system, and the code of conduct. Each item exists in Arabic and English. In the company’s existing Arabic LMS, the ten courses were assigned separately, and the monthly report regularly showed more completions than supervisors.

Before choosing a replacement, the learning team loads all ten versions into the sandbox of each shortlisted Arabic LMS with 40 test employee records, half set to Arabic and half to English. It runs five checks: assign by rule, switch one employee’s language mid-course, attempt a manual duplicate assignment, complete the permit-to-work item in Arabic and confirm that the next item unlocks, and run the completion report.

One platform links the versions cleanly but restarts progress when an employee switches language; the company accepts this after deciding to set each supervisor’s language from HR data at enrolment. Another platform allows the manual duplicate without any warning, and its provider offers a written fix date. The team records each result with screenshots and exported files, and writes the five checks into its acceptance terms so they are repeated after go-live.

Test How the Arabic LMS Handles a Change to One Version

Language versions rarely change on the same day. When the Arabic version of a course is updated first, decide in advance what the Arabic LMS should do: keep the earlier English version live until its update is ready, or pause new enrolments in English. Either way, the version numbers in both records should make the gap visible.

Check how your Arabic LMS treats completions under the old version. Some organizations require employees to retake the updated course; others accept the earlier completion until the next renewal. Whichever rule you choose, test that it applies to both languages equally, so employees who studied in English are not treated differently from those who studied in Arabic.

Summary

Arabic and English versions of the same training belong in one Arabic LMS pathway as one requirement. Define what makes two versions equivalent, link them under one learning item, and drive assignment from the employee’s language preference rather than from separate courses.

Then test the Arabic LMS where duplicates hide: manual assignments, language switches, reminders, prerequisites and the completion report. An Arabic LMS pathway that passes these checks gives organizations in Qatar reports that count each employee once, whichever language they learn in.

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