EOR
Deploying a Project Workforce Across the GCC (KSA, UAE and Qatar) Without Local Entities
June 23, 2026
Energy, engineering, and infrastructure operators increasingly run project workforces across more than one Gulf market at once: engineers on a Saudi giga-project, a commissioning team on Qatar's North Field expansion, and infrastructure crews in the UAE. Each market gates foreign-workforce deployment differently, through its own localisation rules, sponsorship system, and payroll regime, and setting up a legal entity in each one runs on a timescale measured in months while the project runs on weeks. This guide compares how Saudi Arabia, the UAE, and Qatar each control deployment, and how a project workforce is mobilised across the Gulf without a local entity in every market.
Why GCC project deployment is gated market by market
Each Gulf state controls foreign-workforce deployment through its own combination of localisation quotas, sponsorship rules, and wage-protection systems. The headline obligations differ in name and in substance: Saudi Arabia runs Saudisation through the Nitaqat banding system, the UAE runs Emiratisation through MOHRE, and Qatar runs Qatarisation under its 2024 law. Social insurance, wage protection, and end-of-service entitlements are structured differently in each market. A workforce that moves across two or three Gulf countries is therefore not one compliance problem but three, and an arrangement that is compliant in one market is not automatically compliant next door.
The entity barrier and the project clock
The core obstacle to Gulf deployment is that incorporation and project delivery run on incompatible clocks. Establishing a legal entity in any Gulf market involves an investment registration, a commercial registration, the operational registrations, a general manager, an office lease, and a corporate bank account, which takes months, and doing it in three markets multiplies the lead time and the standing cost. A project mobilisation is usually counted in weeks. An employer of record removes the barrier by employing the workforce through entities it already holds, so a crew can be deployed against the project timeline rather than the incorporation timeline, in each market and across all of them.
Saudi Arabia: Nitaqat, Saudisation and the engineering gate
Saudi Arabia gates deployment through Nitaqat, the system that bands every employer by its ratio of Saudi to expatriate staff. The band, ranging across Platinum, High Green, Mid Green, Low Green, and Red, directly controls the ability to issue and renew work permits on Qiwa, so an employer in a low band cannot mobilise expatriates at all. Engineering deployment carries an additional gate: a rising Saudisation quota for engineers, Saudi Council of Engineers accreditation, and a minimum-wage floor for the Saudi engineers who count toward the quota, all of which weigh on staffing oil, gas, and energy projects in Saudi Arabia. The expatriate workforce is sponsored through Iqamas and registered with GOSI, where the expatriate employer contribution is 2% on basic salary plus housing, and wages are paid through the Mudad wage-protection platform. Where the workforce is employed through an EOR, it sits on the EOR's Nitaqat band, and an EOR that holds its own Saudi entity keeps the crew on a band it controls rather than a third party's.
The UAE: MOHRE, the WPS and Emiratisation
The UAE gates deployment through MOHRE work permits and the Wage Protection System. Each expatriate employee needs a MOHRE work permit and a residence visa held by the employer, and salaries must be paid through the WPS, which from 2026 requires payment on the first day of each month. Emiratisation targets apply to mainland employers and are enforced with monthly penalties for shortfalls, though free-zone entities are treated differently. End-of-service gratuity is calculated on basic salary. An EOR with a UAE entity sponsors the work permit and residence visa, runs WPS payroll, manages Emiratisation obligations, and gives a project mainland reach without the operator establishing anything locally.
Qatar: sponsorship, the WPS and the North Field programme
Qatar gates deployment through employer sponsorship and its own Wage Protection System. The North Field expansion is driving heavy contractor demand against that backdrop. A foreign worker is sponsored by a Qatar-registered entity, which obtains a labour quota from the Ministry of Labour and issues the work permit, residence permit, and Qatar ID, as the complete guide to hiring employees in Qatar sets out in full; wages run through the WPS in Qatari Riyals within seven days of the due date. Qatarisation obligations apply, with petroleum operations exempt, and end-of-service gratuity is at least three weeks' basic wage per year of service. Mobility has improved since the No Objection Certificate was abolished in 2020, but residency remains employer-sponsored, so a project crew still needs a licensed local employer, whether its own entity or an EOR's.
The regulatory variance, compared
The three markets diverge on every axis that matters to a project deployment, which is why a single playbook does not transfer across them. The table below sets out the core differences a project operator has to plan around.
| Axis | Saudi Arabia | UAE | Qatar |
|---|---|---|---|
| Localisation regime | Saudisation (Nitaqat bands) | Emiratisation (mainland) | Qatarisation |
| Social insurance | GOSI; expat employer 2% (basic + housing) | GPSSA (UAE and GCC nationals only; not expatriates) | GRSIA (Qatari and GCC nationals only; not expatriates) |
| Wage protection | Mudad WPS | WPS, first of month from 2026 | WPS, within 7 days of due date |
| End-of-service basis | Gratuity on basic + housing | Gratuity on basic salary | Gratuity, at least 3 weeks' basic wage per year |
| Sponsorship | Iqama via licensed entity | MOHRE permit + residence visa | Work permit + residence permit + QID |
| Foreign-owned entity route | MISA investment registration | Mainland or free zone | Mainland or free zone |
One provider or three? Coordinating a multi-country deployment
A multi-country Gulf deployment runs either through one EOR covering all the markets or through separate entities in each. The coordination cost differs sharply between the two. Three separate setups mean three incorporation timelines, three payroll regimes, three localisation positions to monitor, and three points of failure when a regulation changes mid-project. A single provider holding entities across the markets consolidates that into one relationship, one onboarding standard, and one team tracking the regulatory position in each country, which matters when a crew phases from one market to the next or runs in two markets at once. The same logic extends to the rest of the Gulf as a programme grows, whether that is deploying engineers to Oman under OSE and SSU accreditation, meeting Bahrain's enhanced Wage Protection System, or navigating Kuwait's overhaul of work-permit fees and transfers. Phased headcount planning also has to account for each market's localisation ratio over the life of the project, since a surge in expatriate numbers can move an employer's band or quota position.
Worked example
A single energy contractor deploying three crews across the Gulf faces three separate compliance positions at once. An EPC firm wins packages on a Saudi giga-project, the Qatar North Field expansion, and a UAE infrastructure programme, and needs roughly forty engineers and commissioning specialists split across the three sites over an eighteen-month window. In Saudi Arabia the crew is sponsored on Iqamas, sits on a Nitaqat band, is registered with GOSI at the 2% expatriate employer rate on basic plus housing, and is paid through Mudad, with engineer Saudisation and Saudi Council of Engineers accreditation in scope. In the UAE the team holds MOHRE permits and residence visas, is paid through the WPS on the first of each month, and accrues end-of-service gratuity on basic salary. In Qatar the workers hold a work permit, residence permit, and Qatar ID, are paid through the WPS in Qatari Riyals within seven days, and accrue gratuity of at least three weeks' basic wage per year. Run as three incorporations, that is three lead times measured in months against a project counted in weeks. Run through an EOR holding entities in all three markets, each crew is employed, sponsored, and paid to its market's rules under one relationship, and the firm directs the work from day one.
The contractor route is the wrong tool for project crews
Engaging a project crew as independent contractors is the highest-risk way to deploy in the Gulf. Across these markets a foreign worker's right to work is tied to a sponsoring employer, so a site-based specialist working full-time under a client's direction is an employee in substance, and treating them as a contractor creates a misclassification liability and an immigration breach at the same time. The exposure includes backdated social contributions and end-of-service entitlements, penalties, and permit consequences, and it can be pursued against the firm that directed the work. For project-embedded technical staff, employment, whether directly or through an EOR, is the defensible route.
Mobilising a GCC project workforce without local entities
A project operator needs a compliant employer in each Gulf market, not an entity of its own in every one. Through an EOR holding entities across Saudi Arabia, the UAE, and Qatar, a crew is sponsored, paid through each market's wage-protection system, registered for social insurance, and kept compliant with each localisation regime, while the operator directs the work and runs the project. That decouples mobilisation from incorporation, holds the deployment to the project clock, and consolidates three compliance regimes into one relationship. For deploying project teams across the Gulf without local entities, see the Employer of Record service.
About Aspirock
Aspirock is an Employer of Record and payroll provider operating across 70+ countries, with six global offices and over 22 years of experience supporting more than 5,000 workers. Every client works with a named account team that owns the deployment end to end, so contracts, payroll, visas, and compliance filings in each market are handled by people accountable for the outcome. For employer-of-record and payroll support, see the Employer of Record service page.
Frequently asked questions
Can a company deploy a project workforce across the GCC without setting up local entities?
Yes, by employing the workforce through an employer of record that holds entities in each market. The EOR sponsors the visas, runs each country's wage-protection payroll, registers workers for social insurance, and manages each localisation regime, while the operator directs the project. This lets a crew be mobilised against the project timeline rather than waiting months to incorporate in Saudi Arabia, the UAE, and Qatar separately, and consolidates three different compliance regimes into a single relationship.
How do Saudisation, Emiratisation and Qatarisation differ for a project workforce?
They are three separate localisation regimes with different mechanics. Saudisation uses the Nitaqat banding system, where an employer's ratio of Saudi staff controls its ability to issue work permits, with an additional engineering quota and accreditation gate. Emiratisation sets quotas on mainland UAE employers, enforced with monthly penalties, while free zones are treated differently. Qatarisation prioritises Qatari nationals under the 2024 law, with petroleum operations exempt. A workforce moving across all three has to satisfy each regime independently.
How is end-of-service gratuity calculated across the Gulf?
The basis differs by market. In Saudi Arabia gratuity is calculated on basic salary plus housing allowance; in the UAE it is calculated on basic salary; and in Qatar it is at least three weeks' basic wage per year of service. The accrual rules and qualifying service also vary. For a workforce deployed across the three markets, gratuity has to be accrued and administered separately in each, which an employer of record handles per market as the legal employer.
Is it better to use one EOR across the GCC or a provider in each market?
A single EOR with coverage across the markets reduces coordination cost and risk. Three separate providers or entities mean three onboarding standards, three payroll regimes, three localisation positions to monitor, and more points of failure when a rule changes mid-project. One provider holding entities across Saudi Arabia, the UAE, and Qatar consolidates the deployment into one relationship and one team tracking each country's regulatory position, which matters when a crew phases between markets or runs in more than one at once.
Why not just engage project workers as contractors in the Gulf?
A foreign worker's right to work in the Gulf is tied to a sponsoring employer, so contracting a site-based specialist is usually unlawful. A full-time specialist under a client's direction is an employee in substance, and treating them as a contractor creates both a misclassification liability, covering backdated social contributions, end-of-service entitlements, and penalties, and an immigration breach. The firm directing the work can be pursued for it. Employment through an EOR is the compliant alternative for project-embedded staff.
Ready to Work With Us?
Partner with Aspirock for seamless global payroll, EOR solutions, and workforce management.
Contact Us