Saudi Project-Management Saudization Is Rising to 70% — But the Headcount Is Missing

Last verified: 1 September 2026. Saudi Arabia has set a 70 per cent Saudization requirement for three project-management occupations, effective 14 February 2027. For covered employers, this is not a target attached to a construction project, a client contract or a company’s entire workforce. It is a mandatory ratio calculated at establishment level across workers registered in specified occupational codes. [S1] [S2]

The distinction is decisive. The policy will reach the consultancies, contractors, developers and service companies executing Saudi Arabia’s investment programme, but it does not disclose how many of their employees it covers. Nor does the August procedural guide publish the present Saudi share in the three occupations, the number of affected establishments or the number of additional Saudi appointments needed.

What can be measured is the regulatory jump. The previous project-management regime set a 35 per cent first phase and 40 per cent second phase. The new rule raises the requirement by 30 percentage points from that second-phase level—a 75 per cent increase in the required Saudi share. On a constant denominator of 100 covered jobs, Saudi positions rise from 40 to 70 and the maximum non-Saudi positions fall from 60 to 30. [S3]

This is a substantial labour-market intervention. It is not yet possible to turn it into a defensible jobs number.

The rule covers three codes, not everyone who manages a project

Ministerial Decision 41454 covers private-sector establishments employing at least three workers in any of the targeted occupations. The procedural guide identifies:

• 121314 — Project Management Manager;
• 214909 — Project Management Engineer; and
• 242108 — Project Management Specialist. [S2]

The 70 per cent ratio is applied to the total number of workers registered in those occupations at the establishment. Compliance is calculated automatically from General Organization for Social Insurance records and the occupational titles registered there. The guide also warns employers that assigning the duties of a localized occupation to a non-Saudi registered under another title can be treated as a violation. A database label is therefore central to enforcement, but it is not permission to disguise the work.

The denominator is narrower than “all project managers” in ordinary business language. A programme director, construction manager, contracts manager, scheduler, cost engineer or management consultant may perform work that supports project delivery without falling inside one of these three codes. Conversely, a worker registered under a covered code is in the calculation even if the employer uses a different internal title.

That makes occupation mapping the first compliance task. Employers need to reconcile HR records, GOSI classifications, contracts and actual duties. A top-down estimate based on LinkedIn titles, company headcount or construction employment would be unreliable.

The new list also differs from the seven codes published in the 2023 English procedural guide. That older list included project manager, project-management office specialist, communications project manager, business-services project manager and transport project manager alongside the management and specialist roles. [S3] The new rule adds a project-management engineer code while presenting only three occupations. Firms cannot safely apply 70 per cent to the old seven-code denominator; they must classify their current workforce against Decision 41454.

Rounding makes the rule uneven for small teams

The guide says the product of the covered headcount and 70 per cent is rounded to the nearest whole number. Its own example starts with five covered workers—two Saudis and three non-Saudis. Five multiplied by 70 per cent is 3.5, rounded to four; the establishment must reach four Saudi workers. [S2]

The resulting minimum is lumpy at low headcounts:

*The comparison holds the same workers and occupational scope constant. The old and new occupation lists are not identical, so it is an illustration of the rate effect, not a forecast of hiring.

Adding a Saudi employee does not always solve a gap one-for-one because recruitment enlarges the denominator. If the five-person example retained everyone and added Saudis, six workers would require four Saudis, but seven would require five. Replacement, redeployment and growth produce different calculations.

The rule applies independently of an establishment’s Nitaqat colour band, according to the guide. A company cannot point to good overall Saudization performance as a substitute for meeting this occupation-specific quota. If a covered profession is also subject to another localization decision at a different rate, the higher rate applies. [S2]

The missing denominator is the biggest evidence gap

Saudi Arabia’s private-sector labour market remains heavily expatriate overall. HRSD’s latest real-time table, updated in December 2025, lists 12,618,765 workers: 2,453,976 Saudis and 10,164,789 non-Saudis. That is a Saudi share of 19.45 per cent and a non-Saudi share of 80.55 per cent. [S4]

Those figures explain why a 70 per cent occupation rule is strategically important, but they do not show that project-management roles have the same nationality mix. Project management is a professional segment; its Saudi share could be far above the workforce average. Applying 80.55 per cent to the covered occupations would be an unsupported estimate.

HRSD has not published, with Decision 41454:

• the number of workers registered under codes 121314, 214909 and 242108;
• their current nationality split;
• the number of establishments with at least three such workers;
• the distribution of gaps by establishment size, sector or region;
• vacancies, turnover or Saudi jobseeker supply for the three codes; or
• the number of workers who moved into compliance under the 2023 phases.

Without those fields, claims that the decision will create a particular number of jobs are not auditable. The same 70 per cent rule could require modest incremental hiring if firms already localised the relevant roles, or a large adjustment if the covered workforce remains predominantly expatriate.

Publication of an anonymised baseline would improve the policy. HRSD could report establishment counts and worker counts by occupation, nationality, sector and size band, plus quarterly compliance after February. It would not need to identify an employer. It would turn a formal rate into a measurable labour-market programme.

The giga-project effect runs through employers, not projects

The decision lands during a more selective phase of Saudi project execution. Developers are sequencing capital, contractors are managing delivery risk, and consultancies are expected to transfer more capability to Saudi teams. Project-management functions sit at the junction: scope control, programme governance, schedules, cost, interfaces, risk and change.

The 70 per cent requirement can accelerate the transfer of institutional knowledge if Saudi managers receive authority over decisions, clients and delivery teams. It can also deepen the local base of professionals who carry lessons from one project to the next. That is the durable Vision 2030 case: not merely replacing a name in a register, but retaining programme-delivery capability inside the domestic labour market.

The exposure, however, cannot be calculated project by project. A giga-project developer may contract with dozens of separately registered employers. A multinational consultancy may operate through more than one establishment. A contractor may have project-control workers recorded under engineering, administrative or technical occupations outside the three codes. The relevant compliance unit is the covered employer registration described in the guide, not the value or prestige of the project.

The public data also do not permit a defensible ranking of the construction and consulting sectors facing the largest gap. That would require the current Saudi share, covered headcount and vacancy data by employer activity and occupation code. Programme-management consultancies, engineering advisers, contractors and developer-side delivery teams may face different constraints; assigning the largest shortage to any one group without those denominators would be speculation.

This also means the policy does not imply that 70 per cent of every project team, project budget or project leadership committee must be Saudi. Those are different denominators. Procurement contracts may add separate local-content or workforce conditions, but they should not be conflated with Decision 41454.

Recruitment is only the first implementation test

Project management is an experience-compounding occupation. Certifications can establish a common vocabulary, but they do not substitute for having managed claims, interfaces, design changes, safety incidents, schedule recovery or handover. Employers facing a February deadline therefore have four broad options: recruit experienced Saudis, promote and reclassify existing Saudi staff, train Saudi workers into covered functions, or restructure the workforce and occupational mix.

Each option carries a quality test. Rapid promotion without authority can produce nominal compliance. Reclassification without matching duties can create an enforcement risk. Replacing experienced expatriates before knowledge transfer can weaken delivery. But retaining parallel expatriate control while giving Saudis only titles would defeat the policy’s economic purpose.

The six-month grace period is best used for succession plans tied to actual project milestones. Employers should identify each covered position, the incumbent’s nationality and registered code, required capability, named Saudi successor or recruitment route, training evidence and decision rights. Clients can then test whether localization is changing who controls work rather than merely who appears in a payroll category.

HRSD says its support system can assist recruitment, candidate search, training, employment and retention, with Human Resources Development Fund programmes available to qualifying employers. [S2] The performance measure should be retention and progression after subsidy—not only appointments before the enforcement date.

Two rule intersections need clarification

The 2023 procedural guide required a Saudi employee to have a monthly GOSI contribution wage of at least SAR6,000 to count toward the ratio. [S3] The August 2026 guide does not state a minimum wage.

That omission is not enough to conclude that the floor has been abolished. The new decision changes the ratio and covered codes, while the relationship between the two instruments is not explained in the text reviewed for this article. HRSD should state explicitly whether SAR6,000 continues, is replaced or no longer applies. Employers should not design pay or compliance systems around an inference from silence.

There is also a potential intersection with the engineering-professions rule. From 30 June 2026, HRSD raised Saudization to 30 per cent across 46 engineering professions at establishments employing at least five covered engineers; the ministry also requires professional accreditation from the Saudi Council of Engineers. [S5]

Decision 41454 contains a “Project Management Engineer” code and says the higher localization rate applies when decisions overlap. But the public project-management guide does not specify whether that code is among the 46 engineering occupations, whether the engineering SAR8,000 wage condition described in its procedural framework carries across, or how accreditation is tested where the two regimes intersect. The safe conclusion is not that every project-management engineer automatically faces both sets of conditions. It is that HRSD should publish a crosswalk of codes, wage rules and professional-accreditation requirements before February.

Countercase: the deadline does not prove a project bottleneck

A 70 per cent quota is a strong constraint, but it does not by itself establish a shortage, wage spike or construction delay. Employers have known since 2023 that project-management localization was policy, Saudi universities and professional programmes have had time to expand supply, and many large employers may already exceed the new rate in the three specified codes.

The narrower new occupation list may also reduce some firms’ denominator relative to the old seven-code schedule, offsetting part of the higher percentage. Automation and better project controls can raise each manager’s span without reducing delivery quality. Some employers will meet the rule through normal turnover and promotion.

The adverse case becomes credible only with evidence: high vacancy durations, rising compensation for scarce skills, project-control errors, delayed approvals, or employers repeatedly failing inspections. None of those outcomes follows mechanically from the announcement.

Nor should every post-February project delay be blamed on Saudization. Scope changes, funding, design maturity, supply chains, contractor performance and client decisions can dominate a schedule. Causal attribution requires project-level evidence.

What would falsify this assessment

An HRSD baseline showing that at least 70 per cent of workers in the three codes are already Saudi would make the aggregate transition far less disruptive than the rate increase suggests. A published crosswalk proving that the old and new denominators are identical would remove the scope uncertainty identified here. Formal guidance that expressly carries forward—or removes—the SAR6,000 floor would settle the wage question.

After 14 February 2027, the most useful evidence will be the number of covered establishments, compliant establishments, Saudi and non-Saudi workers in each code, average registered wages, inspection findings and six- and twelve-month retention. Project employers should also report whether Saudis occupy client-facing authority and control functions, not simply qualifying titles.

The policy’s ambition is clear. The implementation burden is not. Until HRSD publishes the missing denominator, the defensible conclusion is that Saudi Arabia has ordered a large increase in the required share of three project-management occupations—not that it has already quantified the jobs created or the delivery risk. The world-class outcome would be 70 per cent compliance with deeper Saudi capability and no loss of project control. That can be measured only after the workforce baseline becomes visible.

Related Vision 2030 Context

• PIF’s 11% contribution to Saudi non-oil GDP needs a methodology
• New Murabba’s SAR1 billion private hospital remains a planned investment
• Diriyah’s SAR2 billion financing shifts execution risk into a funded structure

Sources

1. [S1] Ministry of Human Resources and Social Development, “Procedural Guide for the Decision to Localize Project Management Professions,” Decision 41454, issued 13 August 2026, effective 14 February 2027. https://www.hrsd.gov.sa/knowledge-centre/decisions-and-regulations/regulation-and-procedures/
2. [S2] Ministry of Human Resources and Social Development, Arabic procedural guide attached to Decision 41454, August 2026; archived editorial copy. HRSD procedural-guide PDF
3. [S3] Ministry of Human Resources and Social Development, “The Decision to Localize Project Management Professions,” Decision 141749 and procedural guide, 2023. https://prod.hrsd.gov.sa/en/knowledge-centre/decisions-and-regulations/regulation-and-procedures/181444
4. [S4] Ministry of Human Resources and Social Development, Labour Sector Indicators real-time table, updated 24 December 2025. https://www.hrsd.gov.sa/knowledge-centre/data-and-statistics/open-data/real-time-data/mol-inquiry
5. [S5] Ministry of Human Resources and Social Development, “Implementation Begins for the Decision to Raise Nationalization Rates in Engineering Professions,” 8 July 2026. HRSD engineering-professions announcement