Cicada SolutionsCicada Solutions
Back to notes
Saudi Tech Brief

July 4, 2026

Nitaqat 2026: what your HR system now has to track

Saudization is no longer one ratio you check twice a year. It is profession-level, salary-weighted, and tied to Qiwa documentation, and the safety band that used to warn you is gone.

A Saudi HR compliance dashboard shows workforce records, Saudization risk gauges, contract checks, and cicada-wing data paths.
Field notePOS, invoicing, and compliance workflows

Takeaway

Saudi Arabia's 2026 Nitaqat phase removed the Yellow band and tied Saudization credit to Qiwa-documented contracts. Saudization is now a live, profession-level number your HR system has to track.

If you employ people in Saudi Arabia, the number that decides whether you can issue a work visa, renew an iqama, or bid for a government contract became harder to hold in 2026. The Ministry of Human Resources and Social Development started a new three-year phase of the Nitaqat Saudization program, and separately tied Saudization credit to whether each employee's contract is documented on the Qiwa platform. There is no AI angle here. It is a data-and-alerts problem: Saudization has quietly turned from a single ratio you check every few months into a live operating metric your HR system has to track per profession, per contract, and per salary, the same way it tracks payroll.

What happened

Two official changes landed close together. First, the Ministry announced a new phase of the Nitaqat Mutawar program starting in 2026 and running three years, aimed at localizing more than 340,000 additional private-sector jobs for Saudis. Nitaqat has, since 2021, published a multi-year Saudization plan and used a smooth relationship between headcount and the required Saudization rate rather than fixed size bands, so a rising target is a normal, scheduled event, not a surprise.

Second, on 12 April 2026 the Ministry updated the rules for documenting employment contracts on Qiwa. Per the Saudi Press Agency, establishments must reach an 85% contract-documentation rate from 30 April 2026 and 90% by 30 June 2026, where the rate compares documented contracts to total employee contracts at each establishment, and access to services "linked to compliance indicators" now depends on meeting it. Advisory firms reading the change went further on what it means in practice: EY notes that Qiwa-documented contracts now directly affect both immigration and labor services and Saudization calculations, so an undocumented contract can quietly pull a worker out of your Nitaqat headcount. GOSI registration is still necessary, but it is no longer sufficient on its own.

Alongside these, specialist labor advisers tracking the 2026 phase report that the Yellow band, the old buffer between compliant Green and penalized Red, has been removed, that profession-by-profession quotas now cover on the order of 269 roles, and that a Saudi employee must clear a minimum monthly salary to count fully, with those below it counted at half a person. The exact percentages, salary floors, and covered roles vary by ministerial decision and by how many people you employ in each role, so they need to be verified against your own establishment on Qiwa rather than taken as a single national figure.

Why it matters for operators

The practical shift is that the margin for error shrank in three ways at once. Removing the Yellow band means there is no warning zone: a small change in headcount, a lapsed contract, or a raised target can move an establishment straight from Green to Red, and Red is expensive in operations, not just fines. A Red classification can block new work visas, block iqama renewals, freeze profession changes and sponsorship transfers, and remove eligibility for government tenders, while letting expatriate staff transfer sponsorship without your consent.

The Qiwa documentation rule changes what "a Saudi employee" even means for the count. A person can be on your payroll and registered with GOSI, but if their contract is not documented and authenticated on Qiwa, advisers warn they are effectively invisible to the Nitaqat calculation. A company that has not migrated its contracts can watch its Saudization rate drop without hiring or firing anyone.

And because quotas now apply per profession, a healthy company-wide ratio can hide a department that is out of compliance. An establishment can sit comfortably in Green overall while its accounting, engineering, or administrative functions each breach a role-specific quota. Classification is calculated on a rolling multi-week weighted average and the underlying Qiwa data updates continuously, so the damage accumulates quietly between the ministry's periodic reviews. By the time a twice-a-year glance catches it, the average has already moved.

What your HR system now has to track

The through-line is that headline Saudization is no longer a sufficient statistic. A system that only stores a single company-wide percentage cannot see the risks that now matter. To manage Nitaqat as it actually works in 2026, an HR or compliance system needs to hold and watch a few things per employee, not per company: whether each Saudi worker's contract is documented on Qiwa, whether their salary clears the threshold that lets them count fully, and which quota-covered profession they occupy so the ratio can be computed department by department, not just in aggregate. For technical roles it also needs to record accreditation status, because an unaccredited engineer or health professional may not count even when properly contracted and paid.

It also has to model the counting rules that make Saudization non-obvious: a GCC national counts as Saudi, an employee with a disability counts as several, a part-time or contract worker at sufficient hours can earn a full point, and a foreign owner-operator is counted on the Saudi side. Miss any of these and the projected number is wrong in a direction you will not like. The most valuable feature is not a prettier report; it is an alert that fires before the rolling average tips, using a self-imposed buffer to replace the Yellow band the regulator deleted. That is a threshold-and-notification problem your dashboard can solve today.

Where AI helps and where it is premature

It is worth being clear, because the temptation in 2026 is to reach for an AI feature. AI does not make you compliant with Nitaqat, and treating it as the answer here is premature. The failure mode is missing or un-computed data, an undocumented contract, an unmapped profession, a salary below the line, not a lack of intelligence. A language model cannot know a contract is missing from Qiwa unless that status is wired into your system, and once it is wired in, a simple rule already tells you what you need to know.

Where AI does earn a place is on top of correct data, not instead of it. Once your system holds accurate, profession-level Saudization figures, a model can turn them into a plain-language monthly brief a manager will actually read, or run a what-if a spreadsheet makes tedious: if these two Saudi accountants resign, which professions fall below quota, and does the establishment drop a band? That is genuinely useful, but only after the numbers underneath are trustworthy. Build the data and the alerts first; add the summary layer when it has something reliable to summarize.

Cicada Solutions view

Our advice to operators is to treat the 2026 Nitaqat changes as a systems project, not a policy memo. Start by getting every Saudi employee's contract documented on Qiwa, because that is now the difference between a headcount that counts and one that does not. Then model Saudization the way the regulator does, per profession and salary-weighted, and set alerts with your own safety margin to stand in for the Yellow band that no longer warns you. Verify your exact quotas and thresholds role by role on Qiwa rather than trusting any single published percentage, since they differ by decision and by establishment size. Put the resulting number in the same weekly review as revenue and cash, because it now moves continuously and gates your ability to hire and operate. This is exactly the kind of live compliance metric a custom dashboard handles better than a static HR export or a spreadsheet updated once a quarter. AI can help later, once the data is clean, but the work that protects you this year is unglamorous: correct records, correct mapping, and an alert that arrives in time to act. None of this is legal advice; confirm your obligations with HRSD, the Qiwa platform, or qualified counsel before you rely on any specific figure.

Sources

Want this built into a dashboard, booking workflow, POS, CRM, ERP, or HR system?

Start a project