Arabic LMS in Libya: Initial Requirements for a Multisite Company

A company with a head office in Tripoli and sites in Benghazi, Misrata, and the south decides it is time for an Arabic LMS. The first requirements document runs to three pages, most of it copied from provider brochures: course catalogs, gamification, mobile app, dashboards, certificates. Every provider who reads it answers ‘yes’ to almost every line. Six weeks later, the evaluation team still cannot tell the options apart.

The problem is not the providers. It is that the document describes features instead of the company. A useful first brief for an Arabic LMS fits on one page and answers five questions about your own organization: who counts as a user, which audiences will learn and how, which reports you need on day one, who will support people at each site, and how you will trial the platform locally before rolling it out everywhere.

This article walks HR, IT and procurement teams in multisite Libyan companies through those five Arabic LMS requirements. Each section ends with what to write in the brief, so that providers answer questions about your situation rather than about their brochures.

Requirement 1: Define Who Counts as a User

The word ‘user’ hides more decisions than any other in an Arabic LMS project. Permanent employees are obvious; contractors, interns, temporary site staff and people from partner companies are not. Each group affects who gets an account, who pays for it in the licence model, and who must be removed when they leave.

Technical standards offer a helpful checklist. The IETF’s SCIM core schema (RFC 7643), written to make identity management across cloud systems easier, includes a user type attribute for the relationship between the organization and the user, with typical values such as employee, contractor and intern, and an active attribute for administrative status. Its enterprise extension lists fields such as employee number, cost center, organization, division, department, and manager. You do not need to adopt the standard to use the list: it reminds you which facts about each person the Arabic LMS will need.

For your brief, decide and write down:

• Which groups of people will have accounts, and which will not?

• The unique identifier for each person, usually the employee number, and who issues it for contractors.

• The fields that every account must carry: site, department, job title, and line manager.

• Who creates an account, who closes it, and how quickly after someone leaves.

• An estimate of users per site and per group, for later licence discussions with Arabic LMS providers.

Multisite companies also need a rule for people who work across sites: a maintenance engineer who covers two depots, or a supervisor seconded to another city for three months. The brief should state that each person keeps one account and one training history in the Arabic LMS, whatever site they are attached to, and say which site their records count towards in reports.

Clean employee data makes every later step easier; our guide to preparing employee data for LMS implementation covers that work in more detail.

Requirement 2: Describe Each Audience and How It Will Learn

Users are individuals; audiences are groups that learn in the same way. A multisite company usually has several, and an Arabic LMS that suits one may frustrate another. Describe each audience in two or three lines:

• Head office staff: own laptops, regular hours, comfortable with online systems.

• Site and depot staff: shared computers or personal phones, shifts, short gaps between tasks.

• Supervisors: need a quick view of their team and a way to confirm practical checks.

• HR and the training team: assign, follow up, report, and answer questions.

• External trainers or partners, if any: limited access to specific courses.

For each audience, note the device, the language they prefer for training, when they can realistically learn, and any site conditions that matter. If some sites have unreliable connections, say so plainly; it changes what you will ask Arabic LMS providers to demonstrate. This description lets each Arabic LMS provider show how the platform would work for real groups rather than for a generic learner.

Then rank the audiences. Not every group needs to join in the first year, and a short list of priority audiences keeps the first phase of the Arabic LMS manageable. Many companies start with the audience whose training is mandatory or most often audited, and add the others once support and reports are working.

Requirement 3: Name the Arabic LMS Reports You Need on Day One

Most companies ask Arabic LMS providers for ‘full reporting’ and receive a long list of report templates. A better brief names three to five reports the learning management system must produce for you in the first months, with their reader, frequency, and format. For example:

• Mandatory training status by site, monthly, for the operations director.

• New-hire onboarding progress, weekly, for HR.

• Team view for each supervisor, always available on a phone.

• A full export of training records, quarterly, for the HR file.

Add one report that looks beyond completion. If training is meant to change how procedures are applied at each site, the Arabic LMS should help supervisors record what they observe afterwards; our article on following up on procedure application after eLearning in Libyan companies explains what that follow-up involves. Ask for each report to be shown with Arabic names, mixed Arabic and English course titles, and your own site and department structure.

State who may see each report as well. A depot manager in Misrata normally needs his own site’s figures, not every site’s; the operations director needs all of them. Writing these visibility rules into the brief now saves a permissions redesign after the Arabic LMS is live.

Requirement 4: Specify Arabic LMS Support for Every Site

Support is where multisite Arabic LMS projects often struggle after launch. An employee at a distant depot who cannot sign in needs an answer the same day, in Arabic, from someone who understands the site. Decide in advance how support will be layered:

• First line: a named coordinator at each site who handles passwords, course access, and simple questions.

• Second line: your central training or IT team for configuration, reports and data issues.

• Third line: the provider, for faults in the Arabic LMS itself, with an agreed way to log and escalate tickets.

In the brief, ask each Arabic LMS provider to state in which language support is given, during which hours, through which channels, and how quickly tickets receive a first response. If some sites work in shifts or outside head office hours, make sure the support hours you request cover them. Ask, too, what training the provider offers your site coordinators, because they will carry most of the daily load.

Coordinators work best with short Arabic guides for the questions they will hear most often: how to reset a password, how to find an assigned course, and what to do when a certificate does not appear. Ask whether such guides exist for the Arabic LMS or who will write them, and include them in the brief.

Requirement 5: Plan a Local Trial Before Rolling Out

The last requirement is a commitment to test before scaling. The UK Government Digital Service describes a private beta in which a team starts by inviting a limited number of people to use a service, so it can get feedback and make improvements before opening it up more widely. The same logic suits an Arabic LMS in a multisite company.

Write the trial into the brief: two sites with different conditions, such as head office and a distant depot; real accounts created under your user definition; one or two real courses; the day-one reports produced from live data; and support requests handled through the layers you designed. Set the trial length and the criteria for moving on before it starts. Starting with one job role often makes the trial clearer, as our guide to an L&D plan in Libya that starts with one job role explains.

During the trial, keep a simple log: support requests by layer and how quickly each was solved, any report figures that did not match site records, and the time coordinators spent on the Arabic LMS each week. At the end, hold one decision meeting with HR, IT, procurement and both site coordinators, and decide whether to extend the Arabic LMS to more sites, fix specific issues first or reconsider the choice.

A Hypothetical Example: A Consumer Goods Distributor’s One-Page Brief

The following example is hypothetical and is included only to show how the five requirements fit on one page.

A consumer goods distributor has its head office in Tripoli and depots in Benghazi, Misrata and Sabha. Its first brief for an Arabic LMS reads, in summary: users are permanent staff and contract drivers, identified by employee number, with contractors’ numbers issued by HR; accounts close within one week of departure. Audiences are office staff, depot staff on shared computers and personal phones, and depot supervisors. Day-one reports are mandatory safety training by depot, onboarding progress, and a supervisor team view. Support runs through a coordinator at each depot, then the HR training officer, then the provider, in Arabic, with response times to be proposed by each provider.

The Arabic LMS trial covers Tripoli head office and the Sabha depot for six weeks, with the driver safety induction and one office course. The company will move on only if the safety report matches depot records and most support requests are solved at the first line. Three Arabic LMS providers receive the same page, and their answers can finally be compared line by line.

Summary

A multisite Libyan company gets better answers from Arabic LMS providers when it describes itself rather than listing features. Define who counts as a user, describe each audience, name the reports you need on day one, set out support for every site and commit to a local trial.

Those five requirements fit on one page, make proposals comparable and give HR, IT and procurement a shared basis for choosing an Arabic LMS that works at the depot as well as at head office.

Click here if you want Skillup MENA to help you.