`An LMS for Contractor Training on Saudi Projects`

Six months into a large construction project near Jeddah, the main contractor’s HSE manager reviews the training platform. More than three hundred subcontractor workers still have active accounts, although their companies left the site weeks ago. The monthly compliance report for the company’s own employees looks worse than it should, because hundreds of overdue contractor site inductions are counted in it. And when one subcontractor’s safety refresher lapses, the site supervisor, the subcontractor’s office and the HSE team each assume that someone else is chasing it.

The LMS software did what it was told. Nobody had told it that contractors are not employees. They arrive through another company, stay for weeks or months, may work for several firms on the same project, and leave when their scope ends. Training them in the same LMS software as employees can work well, but only if the setup reflects those differences from day one.

This article explains how Saudi project owners and main contractors can set up LMS software for contractor training around three decisions: time-limited accounts, clear ownership of follow-up, and a firm separation between contractors and employees. It is written for HR, IT and procurement teams, together with the HSE and project functions that depend on them.

`Why Contractors Do Not Fit the Employee Model`

Most learning management systems are configured around the employee lifecycle. Accounts are created from the HR system, people sign in with their company identity, managers come from the organization chart, and leavers are removed when HR closes their record. Contractor workers arriving in your LMS software have none of these anchors: no HR record, no company email address, no line manager in your organization chart, and no leaving date that HR will ever see.

That is why contractor training needs its own design in the LMS software rather than a workaround inside the employee setup. It also differs from training your own short-term staff, who are still employees with an HR record; our guide to training permanent and temporary new hires covers that case. Project workforces are also multilingual, so contractor courses in the LMS software often need Arabic, English, and other languages used on site, and must work on the phones workers actually carry.

`Time-Limited Accounts in the LMS Software`

Every contractor account should have an end date from the moment it is created. Link it to something that already ends, such as the subcontract, the work order, or the site access period, and configure the LMS software to disable the account automatically on that date unless a named sponsor in your organization extends it. Account expiry should be the default, and extension the exception.

Limit what the account can reach as well as how long it lasts. NIST describes least privilege as restricting users’ access to the minimum necessary to accomplish assigned tasks. For a contractor, that means the courses for their trade and site only, no access to the employee catalogue or directory, and no view of other people’s results.

Apply data minimization to registration and keep only what the training actually needs: name, contracting company, trade, site, project, end date, and a reference such as a site pass number. The Implementing Regulation of the Personal Data Protection Law requires controllers to collect and retain only the minimum personal data necessary for the purpose. Its Article 31 also restricts copying official documents that identify their holders, except at the request of a competent public entity or to implement a law, and requires such copies to be destroyed once their purpose ends unless a legal requirement says otherwise. Do not ask contractors to upload identity document copies into the LMS software just to open an account; agree the registration fields with your data protection officer.

On large projects, the same worker may move from one subcontractor to another. Decide whether the LMS software keeps one record per person across companies, linked by the site pass number, or a separate account for each company. One record per person avoids repeating training the worker has already completed; separate accounts make each company’s responsibility clearer. Whichever you choose, write it down and test it.

Finally, decide what happens when a contractor account in the LMS software expires. The worker can no longer sign in, but the training record may still be needed as evidence for the project. Agree how long contractor records are kept, and who may see them, with your data protection officer and legal team.

`Who Owns Follow-Up for Contractor Training?`

Follow-up fails when ownership is shared but never written down. Other regulators have faced the same question. In the United States, OSHA’s guidance on temporary workers states that staffing agencies and host employers are jointly responsible for a safe work environment, including training, and that they should set out their respective responsibilities in their contract. That is US guidance, not a Saudi requirement, but the principle applies directly to subcontractors on Saudi projects.

Write the split into the subcontract or its training annex, and mirror it in the LMS software:

The host organization defines which courses each trade and site requires, and owns the LMS software and its reports.

Each contracting company names a contractor coordinator who registers its workers in the LMS software, chases overdue training and confirms when workers leave.

The site supervisor confirms practical competence on the job, where a course alone is not enough.

The HSE or project team decides what happens when training lapses, for example, whether site access is paused, according to the project’s own procedures.

Give each contractor coordinator a limited manager view in the LMS software that shows only their own company’s workers, their due dates and their status. A coordinator who can see the overdue list without phoning the host organization is far more likely to act on it.

Decide too how reminders reach workers who rarely read email. Depending on what your tests confirm, a reminder from the LMS software may go to the coordinator, who raises it at the morning site briefing, or through a messaging channel the workers already use. A reminder that reaches no one is not follow-up.

`Keeping Contractors Separate from Employees in the LMS Software`

Separation protects both groups. Set up contractors as a distinct audience in the LMS software, with their own catalogue, their own assignment rules and their own certificate template showing the contracting company. Then check three boundaries:

Reports: employee compliance figures exclude contractors, and contractors appear in separate reports by company and site.

Visibility: contractors and their coordinators never see employee records, and employees’ managers see contractors only where they supervise them on site.

Integrations: contractor accounts are not created in, or pushed into, the HR system or employee sign-on by accident.

The same permission logic that keeps one branch from seeing another applies here; our guide to managing LMS permissions across Saudi company branches explains how to structure it.

Separation also matters when the project ends. Archive the contractor audience as a whole rather than deleting it, so that the LMS software can still show who was trained, through which company and before which date, for as long as your agreed retention period requires.

`Testing the Setup Before the First Contractor Arrives`

Run a short script in a test environment of the LMS software before the first contractor company mobilizes:

Run the employee compliance report and check that no contractor appears in it.

Extend an account through the sponsor route and confirm that the approval is recorded.

Complete a contractor course on a basic phone, in Arabic and in English.

If you are still choosing LMS software, include these steps in a practical demo test before contracting. They are easy to pass with prepared data, and far more revealing with your own.

`A Hypothetical Example: A Hospital Construction Project`

The following example is hypothetical and only illustrates the method.

A main contractor building a hospital in the Eastern Province expects nine subcontractors and up to six hundred workers over two years. Before mobilization, it sets up contractor training in its LMS software as a separate audience with time-limited accounts linked to each subcontract’s end date.

Each subcontractor names a coordinator with a view of its own workers only in the LMS software. The training annex states that coordinators chase overdue courses within a set number of days, and that the HSE team decides what happens after that. Registration uses the site pass number instead of identity document copies, as agreed with the data protection officer.

When the first subcontractor demobilizes, its accounts in the LMS software expire automatically, and its records remain available to the HSE team. The employee compliance report is unaffected, and monthly contractor reports from the LMS software go to each coordinator rather than to the main contractor’s HR department.

`Summary`

Contractor training on Saudi projects works in the same LMS software as employee training only when the setup reflects how contractors arrive, work, and leave. Time-limited accounts with minimum data prevent open access after demobilization, written follow-up ownership closes the gap between host and subcontractor, and a separate audience keeps reports and permissions clean.

Agree these decisions before the first contractor company mobilizes, test them in the LMS software with a short script, and review them whenever a new subcontractor joins the project.

Click here. If you are setting up LMS software for contractor training on a Saudi project, you can discuss your account, ownership, and reporting requirements with the SkillUp MENA team.