Saudization — the Saudi government's programme to increase the proportion of Saudi nationals in the private-sector workforce — is the single most strategic HR metric in the Kingdom, and Nitaqat is the framework that operationalises it. Every Saudi establishment is classified into one of four bands — Platinum, Green, Yellow, or Red — based on the proportion of Saudi nationals in its workforce, weighted by job category and salary band. The band determines the establishment's access to government services, visa quotas for expat workers, and renewal of labour files. This guide walks through how U HR handles Nitaqat reporting natively — from the per-entity Saudization ratio computation, through job-category weighting, to Mudad integration and MHRSD reporting. The goal is to move Nitaqat from a defensive compliance exercise — sending monthly spreadsheets to a consultant — into a workforce-planning capability that the HR team uses to target recruitment, training, and Saudization-improvement investments.
What Nitaqat actually measures #
Nitaqat is not a simple headcount ratio. The raw Saudi-to-expat percentage is weighted by job category and salary band — a Saudi engineer counts for more in the weighted ratio than a Saudi gate-guard, because the government wants to see localisation in higher-skill roles, not just in low-wage positions. The weightings differ by activity category (contracting, retail, manufacturing, professional services, healthcare), and the bands — Platinum, Green, Yellow, Red — are computed against thresholds that MHRSD publishes and updates periodically. A mid-sized Saudi contractor, for example, may have an overall Saudization ratio of 35% but find themselves in the Yellow band because the ratio is concentrated in low-skill positions while engineering and supervisory roles remain expat-heavy. This is why a generic HRIS that reports only the raw Saudi-to-expat percentage is misleading: the same percentage can place an establishment in Platinum or Yellow depending on the job-category distribution. U HR's Position Catalog carries the job-family tag that weights the ratio correctly, and the per-entity Nitaqat dashboard surfaces both the raw ratio and the weighted band — so the HR Manager sees the lever that actually moves the band.
The four Nitaqat bands and what they mean #
The four Nitaqat bands carry progressively severe consequences for the establishment. Platinum is the highest band — Saudi-rich establishments with strong localisation in higher-skill roles — and rewards include preferential visa processing, exemptions from certain fees, and a positive signal in government-tender evaluations. Green is the compliant band — the establishment meets the minimum Saudization threshold for its activity category and can continue normal operations, including visa renewals for expat staff. Yellow is the warning band — the establishment is below the threshold and faces restrictions: no new expat visas, restrictions on visa transfers, and a defined period to improve before further sanctions. Red is the non-compliant band — the establishment is significantly below threshold and faces severe restrictions: no visa renewals, potential closure of the labour file, and inability to bid on government tenders. The thresholds for each band are activity-category-specific and updated periodically by MHRSD, so the HR system must compute against the current thresholds rather than a static table.
Per-entity Saudization ratios in U HR #
The Saudi holding group is the structural pattern that breaks single-entity Nitaqat computation. A group with three legal entities — one for general contracting, one for MEP, one for facilities management — has three separate Nitaqat establishments, each with its own MHRSD establishment code, its own activity category, and its own band. Computing Nitaqat as a blended group ratio is incorrect: MHRSD evaluates each entity against its own activity category's thresholds, and a blended ratio hides an entity that is failing. U HR's Organizations → Companies → Departments hierarchy is what enables correct per-entity Nitaqat: each Company is a legal entity with its own establishment code, the Employee Profile of each employee is scoped to a Company, and the Saudization ratio is computed per Company against that entity's activity category thresholds. The group CHRO sees all entities' bands in the Employee Manager dashboard's Org-Wide Visibility view, with per-entity trends over time — so the entity that is drifting toward Yellow is visible before the MHRSD portal flags it. This is the structural difference between U HR and a single-entity HRIS retrofitted with a 'locations' workaround.
Weighted by job category: the contracting example #
The contracting activity category is the clearest illustration of why job-category weighting matters. MHRSD's Nitaqat weightings for contracting assign higher weight to Saudi engineers, project managers, and supervisors than to Saudi labourers — because the government's intent is to localise higher-skill construction roles, not just to inflate the headcount ratio with low-wage positions. A contractor with 50 Saudi labourers and 0 Saudi engineers may have a raw Saudization ratio of 35% but find themselves in the Yellow band, because the weighted ratio — which discounts the labourer count and rewards the engineer count — places them below the Platinum threshold. The same contractor with 30 Saudi labourers and 20 Saudi engineers would be in Platinum, despite a lower raw headcount ratio. U HR's Position Catalog is where this weighting lives: each position carries a job-family tag, and the per-entity Nitaqat dashboard computes the weighted ratio by applying the MHRSD weightings to each employee's job family. This transforms Nitaqat from a defensive compliance metric into a workforce-planning lever: the HR Manager can see which job families are dragging the band down and target recruitment and training investments precisely, rather than relying on blunt headcount targets.
Mudad integration and MHRSD reporting #
Mudad — the Saudi Ministry of Finance's digital services platform — is the operational integration point between the employer's HR system and MHRSD's Nitaqat dashboard. Mudad consumes structured payroll and workforce data, validates it, and feeds it to MHRSD's Nitaqat computation. U HR's WPS SIF file generation — described in detail in our GOSI & WPS compliance guide — produces the structured payroll data that Mudad consumes, and the per-entity workforce-composition data (Saudi headcount, expat headcount, job-family distribution, salary-band distribution) is reportable from the Employee Manager app in the format MHRSD expects. For a multi-entity group, this reporting is generated per Company against that entity's activity category thresholds, with the group consolidation available as a roll-up view. The reporting layer also retains historical snapshots — so the HR Manager can show the entity's Nitaqat trend over the past 12 or 24 months, which is what MHRSD auditors ask for when investigating a band change. This historical depth is what distinguishes a genuine Nitaqat reporting capability from a one-off snapshot.
From compliance to workforce planning #
The strategic shift for Saudi HR teams is to move Nitaqat from a defensive compliance metric — produced in a spreadsheet the night before an audit — into a workforce-planning capability that informs recruitment, training, and budgeting decisions. U HR's per-entity Nitaqat dashboard, weighted by job category, with historical trends, is the data foundation for that shift. A Saudi construction group can see which of its three legal entities is in Platinum, which is in Green, and which is drifting toward Yellow; within the drifting entity, the HR Manager can see which job families are pulling the band down; and the recruitment team can target those specific job families for Saudi hiring over the next two quarters, with the Skill Catalog identifying the competencies that need to be developed internally versus hired externally. This is the operational meaning of 'Saudization as workforce planning': the Nitaqat band becomes an output of the HR team's quarterly planning cycle, not a surprise from the MHRSD portal. U HR's three-app model supports this — the HR Manager configures the framework, the Employee Manager surfaces the trends, and the group CHRO sees the strategic picture.