UAE mainland companies with 50 or more employees must raise Emirati representation in skilled roles by 2 percentage points a year toward 10%, with monthly penalties per unfilled position. Meeting it reliably requires a verified Emirati talent pool and defensible, auditable selection records.
- Applies to mainland firms with 50+ employees; free-zone entities are outside the quota.
- Penalties accrue monthly per unfilled position, so a shortfall compounds.
- Nationality may inform sourcing and reporting — never the score itself.
- Keep selection records defensible: what was measured, and why each decision followed.
What the rule requires
Mainland UAE companies employing 50 or more people must increase Emirati representation in skilled roles by 2 percentage points each year, working toward 10%. Penalties are assessed monthly, per unfilled position — which is why a small shortfall left unaddressed becomes a large number by year end.
Free-zone entities sit outside the quota. Many still adopt the target internally, because the talent-market dynamics are the same.
The two problems teams actually hit
Sourcing. The pool of Emirati candidates for a given skilled role is smaller than the general pool, so generic job-board sourcing under-delivers and teams end up filling positions late.
Defensibility. Hitting a nationality-linked target while running a fair process sounds contradictory. It is not — but only if you keep the two concerns in separate places.
Where nationality belongs, and where it must not
This is the distinction that keeps a programme lawful:
| Use | Allowed |
|---|---|
| Sourcing and outreach | Yes |
| Compliance counting and reporting | Yes |
| Assessment score or ranking | Never |
Nationality as a scoring input creates direct discrimination exposure and destroys the defensibility of the whole record. Score on demonstrated skill; count separately for reporting.
A process that satisfies both
- Build a verified pool. Emirati candidates complete one skills assessment and hold a portable verified profile, so qualified candidates are identifiable before a vacancy opens.
- Assess blind. Rank on ability with identity withheld. The score cannot be influenced by nationality because nationality is not on the evaluation surface.
- Reveal on consent. Identity unlocks for shortlisted candidates only.
- Report from the record. Produce headcount and target progress from the same data the hiring decisions came from, not a parallel spreadsheet.
Keep the audit trail exportable
Assume you will be asked to show your working. For every skilled hire, retain the role requirements, what was assessed, the ranked outcomes, and the approving decision-maker — in a form you can export. Reconstructing this after the fact is where programmes fail.
See the compliance console for residency and audit-trail controls, or the trust center for how we handle evidence.
Frequently asked questions
- Which companies does Emiratization apply to?
- Mainland UAE companies with 50 or more employees are subject to the skilled-role targets. Free-zone entities fall outside the quota, though many adopt equivalent goals voluntarily.
- Can nationality be used as a scoring input?
- No. Nationality can inform sourcing and compliance reporting, but it must never affect an assessment score or ranking. Doing so creates discrimination exposure and makes the record indefensible.
- What evidence should we retain?
- For each hire: the role requirements, what was assessed, the ranked outcomes, and who approved the decision. Retain it in a form you can export on request.