Construction Manpower Planning: Why GCC Contractors Run Out of Labour at the Wrong Time

Every construction PM has felt it: three weeks from a critical milestone, your subcontractor was supposed to have 180 formwork carpenters on site, and 110 show up. The project slips. The client asks why. You are scrambling for answers that do not make you look like you did not see this coming.

The truth is, labour shortfalls are almost always predictable. The problem is not the subcontractors — it is that most GCC contractors have no systematic way to map what the schedule demands in terms of labour, by trade, by week. Without that map, you are not managing manpower. You are reacting to it.

Why Construction Labour Planning Breaks Down

Four failure modes appear repeatedly on GCC construction sites, and each one is avoidable.

No Labour Histogram from the Schedule

The Primavera programme tracks activity durations and float, but resource assignments are absent or left as placeholder figures. When the project accelerates past baseline, nobody has recalculated the workforce requirement. The site manager asks for more people two weeks after they were needed.

Subcontractor Commitments Treated as Guarantees

A subcontract package for SAR 35M in civil works includes a clause saying the subcontractor will provide "adequate resources." On week 12, adequate turns out to mean 60% of the headcount the GC's QS assumed when pricing the schedule. There is no commitment register, no weekly headcount tracking, no early warning mechanism.

Iqama Expiry Blind Spots

In the GCC, a construction worker without a valid Iqama cannot be on site legally. On a project with 800+ labourers, the expiry wave is constant. Without systematic tracking, you discover an expiry problem when a worker is turned away at the gate — not 45 days earlier when there was still time to renew or replace.

Summer Restriction Planning as an Afterthought

Saudi Arabia's mid-day outdoor work ban runs from June 15 to September 15. GCs who do not model this into their manpower plan discover in late July that productivity assumptions were wrong by 20–25% for three months — hitting float and milestones at the same time.

What a Manpower Plan Actually Looks Like

A structured manpower plan does three things: it shows what the schedule demands, it tracks what is committed, and it flags gaps before they become crises.

Labour Histogram from the Programme

Every WBS activity gets resource assignments: 12 rebar fixers for 3 weeks, 8 MEP first-fix electricians for 10 days. Roll those up weekly and you get a staffing curve — the S-curve of headcount across the project life. The peak demand number is usually the first surprise: a SAR 180M residential project in Riyadh might need 420 workers at peak but started with 280. The ramp-up plan should be built into the programme, not discovered when it is already late.

Trade-Level Breakdown by Subcontract Package

A single headcount number per week is not enough. You need it by trade: civil labourers, carpenters, rebar fixers, masons, MEP trades. Each trade comes from a different subcontractor, with different resource pools and different Iqama pipelines. Aggregating by trade lets you see, for example, that civil labour is adequate but MEP electricians are short by 30 through the fit-out phase — which is exactly when MEP is on the critical path.

Weekly Subcontractor Delivery Tracking

The commitment register records what each subcontractor agreed to provide by phase. The weekly tracking record shows what was actually on site. When the gap between committed and delivered hits 15%, that is a conversation. At 25%, it triggers a formal notice and alternative sourcing.

A subcontractor who is consistently 20% under commitment on a SAR 40M package is costing the project roughly SAR 1.2M in schedule float — recoverable as a delay claim if documentation exists, invisible if it does not.

Iqama and Visa Tracking: The Compliance Layer Most GCs Ignore

In Saudi Arabia, every non-citizen worker needs a valid Iqama to be on site legally. Aramco, NEOM, and ROSHN check at the gate. A worker denied entry is a direct productivity hit — and on a site running 800 tradespeople, even 3% blocked at entry wipes out a meaningful portion of the day's planned output.

The typical project carries Iqama expiry risk on 15–25% of the workforce in any given 90-day window. Without a tracked expiry register, the project relies on individual subcontractors to manage their own documentation — and the variance in administrative capability between a tier-1 subcontractor and a small specialist firm is significant.

A basic workforce compliance register tracks:

Worker ID, trade, nationality, and subcontract package
Iqama number and expiry date
Residency transfer status
Medical examination validity
Site-specific induction completion

The register needs to be current, and it needs to trigger 45-day renewal alerts. A worker renewed on time costs SAR 700–1,200 in fees and a day of admin. An emergency departure and replacement costs SAR 8,000–15,000 in recruitment and mobilisation — plus the schedule impact of the gap period.

Saudi contractors using the Musaned platform need to reconcile their site roster with the Musaned record to pass Aramco or Ministry audits. A unified workforce register that feeds both your manpower plan and your compliance reporting eliminates the reconciliation step and the risk of audit surprises.

The Summer Restriction Problem

Every GCC contractor knows about the June 15 to September 15 mid-day outdoor work ban. Very few build it into their manpower planning model correctly.

The issue is productivity, not just attendance. A carpenter who works 8 hours in October works 6.5 effective hours in August under the split-shift restriction: 6:00–12:00, then 15:00–17:30. For activities with day-length dependencies — concrete pours, waterproofing, external facade work — the restriction effectively cuts output by 25–35%.

A manpower plan that does not seasonally adjust productivity assumptions produces optimistic resource loading during summer months. The right approach: flag all outdoor WBS activities, apply a summer productivity factor (typically 0.70–0.80 depending on activity type and start time), and recalculate the labour requirement needed to hit the same output target. Sometimes this means increasing headcount for those activities. Sometimes it means re-sequencing to shift critical outdoor work out of the summer window.

On projects running from Q1 through Q4, the summer productivity adjustment can compress the float on outdoor critical-path activities from 15 days to near zero. That is not a problem to discover in June when the restriction is already in force.

Connecting Manpower Planning to Cost

Labour planning is not just an operational discipline — it directly affects the cost report.

When actual headcount delivered by subcontractors comes in 20% below the committed schedule, two things happen:

Activities take longer, consuming float and eventually delaying milestones.
Labour cost per unit of output rises, because fixed overhead and supervision costs are spread over lower productivity.

A project tracking work confirmations against planned quantities can measure this directly. If the rebar fixing subcontractor delivered 310 tonnes in a month instead of 420, the shortfall shows up as a productivity variance in the cost report — not just as a schedule flag. That variance is the business case for escalating the subcontractor before next month compounds the problem.

The FIDIC documentation angle matters here too. Weekly headcount records and formal notices to subcontractors who consistently under-deliver on staffing commitments form part of the contemporaneous record under Clause 20. If the GC ultimately pursues a time-related claim, the subcontractor shortage log is evidence. If the subcontractor disputes back-charges for accelerated resources brought in to compensate, the same log is the counter-argument.

Five Starting Steps

You do not need to rebuild your planning system to start managing manpower properly.

Export the labour histogram from your programme. If Primavera lacks resource assignments, use your subcontract packages and BOQ to back-calculate headcount by trade. A rough weekly number per subcontractor is enough to start.
Create a commitment register. For each subcontract package, record agreed headcount by phase. Review it weekly. Mark actual delivered headcount next to committed. The gap is your risk register entry.
Pull all Iqama expiry dates for site workers. Your HR or gate management system should have them. Sort by expiry date. Flag anything expiring within 60 days. Assign renewal responsibility to each subcontractor in writing.
Mark outdoor activities in your programme. Identify which WBS activities require outdoor work. Apply the summer productivity adjustment factor for the June 15–September 15 window. Recalculate headcount requirements for affected activities.
Set a weekly manpower KPI. Track one number: committed headcount versus actual headcount by subcontract package. Anything below 85% of committed triggers a formal conversation. Consistently below 80% triggers a formal notice.

The Competitive Edge

GCC projects that miss milestones do not usually do so because of dramatic events. They slip week by week as subcontractors deliver 30 fewer workers than planned, and nobody does the arithmetic until the milestone is three months late.

Contractors who manage manpower with the same rigour they apply to programme dates and cost budgets have the documentation — commitment registers, weekly headcount records, Iqama compliance logs — that supports schedule delay claims and subcontractor back-charges when the data eventually shows who failed to deliver.

On a SAR 280M programme contract, one week of critical-path delay costs roughly SAR 850,000 in preliminaries, liquidated damages risk, and extended overhead. Managing the headcount that prevents it does not require a complicated system. It requires a daily count, a weekly comparison, and someone whose job it is to act on the gap.