A general contractor in Dubai approves a quarterly headcount plan across four job sites. Three manpower agencies confirm deployment against it: 60 workers here, 85 there, 40 on the last site.
On paper, the project is fully staffed and the manpower budget is on track. What the plan does not show is whether those 185 workers were actually present on any given day, at any given site, since the deployment number came from each agency's own muster register, not from anything the contractor independently verified.
Most headcount planning guidance is written for a single company with its own employees on its own payroll, not for a project running several contractor agencies across sites with a rest day, a Ramadan schedule shift, and a WPS payroll cycle to hit every month.
This article covers where a headcount plan actually breaks down for contract and multi-site GCC operations, then walks through the forecasting process, a manpower budget template, and the compliance anchors that hold it together, closing on the question most headcount plans in this region quietly skip: how do you know the headcount you approved is the headcount that showed up?
Key Takeaways
- A headcount plan forecasts ending headcount using starting headcount, planned hires, expected exits, and transfers, but every one of those inputs depends on attendance data someone has actually verified.
- Deployed headcount (what a manpower agency reports) and verified present headcount (who is actually on-site) diverge on multi-agency, multi-site projects, and that gap is where manpower budgets quietly run past plan.
- The core calculation is: projected headcount = starting headcount + planned hires + internal additions - expected exits - transfers out, adjusted for workload and demand assumptions.
- Expected exits = average headcount x attrition rate. A 100-worker site at 12% annual attrition needs about 12 replacement hires a year just to hold capacity steady.
- Reforecast quarterly, review monthly, and reconcile approved headcount against verified present headcount, by site and by agency, at every review.
Why Planned Headcount and Actual Headcount Drift Apart on GCC Sites
Most headcount planning guidance treats "current headcount" as a fixed, known number you plug into a formula.
On a GCC project running multiple manpower agencies across several sites, the current headcount is not a fixed number. It is a claim, and the claim comes from three different places that rarely agree:
- The headcount approved on the work order
- The headcount an agency says it deployed
- The headcount actually present and verified at the site that day.
The gap between deployed and verified headcount is where manpower budgets go wrong, and it goes wrong quietly. A contractor invoice built from an agency's own attendance register is internally consistent and can still be wrong, because nobody outside the agency checked it against an independent record.
This matters most on large single-site infrastructure projects, where 1,000 or more workers across several trade contractors is a routine scale in the region, and a few percentage points of unverified headcount translates into real money on the monthly bill.
Deployed Headcount vs. Verified Present Headcount
Deployed headcount is what a manpower agency reports as sent to a site, usually from its own muster roll or muster report. Verified present headcount is who actually punched in there, confirmed by biometric identity verification and GPS-confirmed location, on that specific day, independent of any agency's own attendance register.
The two numbers should match. On a project with poor visibility into contractor attendance, they usually do not, and the deployed number is what most headcount plans and manpower budgets are built on by default.
An agency-reported register is not independent evidence of attendance. It is the agency's own record of its own workers, produced by the organization that bills against it. That does not make the number dishonest, but it does make it unverified, and a headcount plan built entirely on unverified numbers inherits every error in them without any way to catch it before the invoice lands.
This is also where replacement hires (restoring headcount lost to an exit) get confused with growth hires (net-new positions tied to new demand). A plan with no framework for the distinction tends to auto-approve every agency request by default.
Every opening should be labeled as replacement or growth before approval, and checked against workload and overlap with other agency staff on the same site, since a replacement request from one agency can actually be covering a gap another agency's underused workers could fill, and a plan with no agency-level visibility has no way to see that.
A headcount plan that treats every reported vacancy as an automatic replacement is really outsourcing hiring decisions to whichever agency asks first. Build a review step before any replacement request converts into an approved opening.
For a facility management operator running client sites with sub-contracted cleaning or maintenance crews, the same reconciliation gap shows up as a client-facing problem, not just an internal one: a client auditing site coverage has no way to tell whether the headcount on the invoice matches the headcount on the floor unless the verification is independent of the sub-contractor's own record.
How to Reconcile Approved Headcount Against Verified Present Headcount
The fix is not a bigger spreadsheet. It is a reconciliation practice: compare approved headcount, agency-reported deployment, and verified present headcount, by site and by agency, on a recurring cadence rather than only when an invoice dispute forces the question.
That comparison only works if the third number comes from something independent of the agency's own record.
This is the specific gap Truein is built to close. Truein is an AI-powered time and attendance management system that verifies identity and location at the moment of clock-in using face recognition and GPS geofencing, on any Android or iOS phone or tablet, with no dedicated hardware, fingerprint terminal, or fixed biometric kiosk required.
A face-match failure blocks the punch immediately and prompts a retry, so an unverified worker cannot enter the attendance record in the first place.
Because the punch itself is verified rather than self-reported, the "verified present" side of the reconciliation is built from an independent record instead of the agency's own muster register.
Truein also supports multiple contractor agencies and subcontractors under a single account: each agency's supervisor gets a scoped Contractor View limited to their own workers and sites, per-agency headcount and daily clock-in caps prevent overbilling and unauthorised deployment, agency-specific pay rates and attendance policies can be configured separately, and worker and contractor document expiry is tracked automatically so renewals are flagged before they lapse.
The honest framing here is visibility and controls to spot and prevent overlap or overbilling across agencies working the same site, not an automatic guarantee that overlap is caught.
On sites with poor or zero connectivity, a routine condition on large infrastructure and desert-adjacent GCC projects, offline attendance is captured on-device and syncs once the network returns, flagged as ‘captured offline’ for review.
Those records only appear on the dashboard after sync, so real-time visibility applies to connected punches, not every attendance capture mode.
Every verified punch, whether captured online or offline, feeds a single per-worker, per-site, per-agency attendance record, what GCC construction and facility management operators would recognize as a digital muster roll. That record is what a reconciliation review actually compares against the agency's deployment claim, not a spreadsheet rebuilt from site notes after the fact.
Enova Facilities Management and KAD Construction are among the GCC contractors running verified attendance this way across multiple sites.
What Headcount Planning Actually Means for a Contract or Multi-Site Workforce
With the reconciliation problem on the table, it is worth being precise about what headcount planning covers and where it sits relative to broader workforce planning, since the two terms get used interchangeably and that causes confusion at budget review time.
Headcount planning decides the number of workers, by role, site, and time period, an operation needs within an approved manpower budget.
Workforce planning is the broader discipline, covering skills, capacity, succession, contractor mix, and organizational design, of which headcount is one output among several.
Headcount Planning vs. Workforce Planning
Headcount planning is the narrower, more mechanical exercise, and it sits inside workforce planning rather than replacing it. For most GCC contractors and facility management operators, headcount planning is recurring, month-to-month work; workforce planning happens less often and shapes the assumptions headcount planning runs against.
In practice, the two connect through the same underlying data: a headcount plan is only as reliable as the attendance and man-day (A man-day is one worker present for one working day at one site, the unit most GCC manpower contracts are billed in.) data feeding it, which is why GCC operators increasingly treat verified attendance data, not the agency-submitted muster register, as the shared input for both the monthly headcount review and the less frequent workforce planning cycle.
Who Owns Headcount Planning on a GCC Contract or Multi-Site Operation
Headcount planning on a project with contractor agencies is not a single department's job. HR maintains the headcount baseline and hiring timelines, Finance validates the manpower budget, site leaders confirm requested headcount matches workload on the ground, and manpower agency coordinators own the deployment side: confirming what each agency has committed and flagging where deployed headcount and site reality have started to drift.
A plan that skips that last role tends to treat agency-reported deployment as fact by default, the exact gap the reconciliation section above addresses.
On the buying side, this is also where a Digital Transformation Lead or IT Manager tends to get pulled in alongside HR and Finance, since fixing the reconciliation gap is usually a systems decision (which data source counts as verified) before it is a policy decision.
The Headcount Forecasting Formula
Once the reconciliation practice is in place, the standard forecasting formula becomes something you can actually trust, because the inputs feeding it are verified rather than assumed.
Projected ending headcount = starting headcount + planned hires + internal additions - expected exits - internal transfers out.
Required hires should then be adjusted against workload and growth assumptions, since a plan that only tracks net change without checking it against actual demand will drift from operational reality even if every number in the formula is individually correct.
A Worked Example: Task-Hours Across Multiple Sites
A facility management operator handling 20,000 monthly task-hours across three client sites, with each productive worker delivering roughly 160 task-hours a month, needs about 125 productive workers before adding a capacity buffer for leave, Ramadan-hour reductions, or approved growth.
A common approach adds 5 to 10% on top of the base requirement, depending on the site's absence and turnover history. For the 125-worker example, a 6% buffer brings the planning target to roughly 133, rounded up since partial workers are not deployable.
Calculating Expected Attrition
Expected exits = average headcount x expected attrition rate
A 100-worker site running 12% annual attrition should plan for roughly 12 replacement hires over the year just to hold current capacity, before any growth hires are added on top.
On a 500-worker GCC infrastructure project, even a modest 10% annual attrition rate means roughly 50 replacement hires a year moving through recruitment and deployment, a volume worth planning for rather than absorbing as an afterthought.
Attrition in contract-heavy GCC operations is not evenly distributed. It clusters around contract renewal cycles, project-phase end dates, and seasonal labour movement, so a flat annual rate applied evenly across the year will underbuild the hiring pipeline right before the periods that need it most.
How to Build a Headcount Plan
With the formula and the reconciliation practice both established, building the plan itself is a sequence of steps as follows:
- Define the planning period: Most GCC operations run a 12-month operational forecast, extended to 18 to 36 months for a new site, a major project phase, or a long recruitment-cycle role.
- Establish current headcount, verified: This means owned staff plus contract labour by agency and site, checked against verified attendance data rather than the last submitted muster register.
- Collect business-growth assumptions: Project pipeline, new site mobilization, contract renewals, and seasonal demand all belong here.
- Forecast workload or demand: in task-hours, production volume, or another operational unit the site can actually measure.
- Identify role and site gaps: between required headcount and current verified headcount.
- Account for attrition and internal movement: including transfers between sites and agencies.
- Calculate required hires by role and site: labeling each as replacement or growth.
- Validate against the manpower budget: translating every proposed role into total employment cost rather than base pay alone.
- Set a review cadence: and lock in who reconciles deployed versus verified headcount at each checkpoint.
Building in a Hiring Lead Time Buffer
Even a complete data set only helps if the plan builds in enough runway to act on it before a gap becomes a site problem.
If a skilled trade role takes 60 days to recruit and mobilize plus 30 days to fully onboard on-site, hiring needs to start roughly 90 days before the worker is expected to be productive. On GCC projects, visa processing and labour card issuance add their own lead time on top of recruitment, so that 90-day window is often optimistic rather than conservative, and a plan that assumes instant hiring will consistently discover gaps too late to close without an expensive short-term fix.
Turning the Headcount Plan Into a Manpower Budget
Everything above produces a hiring number. A headcount number without a cost attached is not a budget input, and what Finance actually approves is the manpower budget, not the headcount plan itself.
On large GCC infrastructure and facility management contracts, manpower is typically the single largest controllable cost line, so a plan Finance cannot cost accurately gets rejected at review regardless of how sound the workload forecasting behind it was.
What to Include in Total Employment Cost
Base pay is the starting point, not the total. A defensible manpower budget also accounts for gratuity accrual (an end-of-service obligation that compounds with tenure), the payroll cost structure tied to WPS compliance, recruitment and mobilization costs, and site-specific allowances.
Truein does not calculate or process gratuity or WPS payments, generate a Salary Information File, or submit wage data on a company's behalf; it is not payroll software or a WPS compliance tool.
What it provides is a payroll-ready attendance export, verified man-day and payable-hour totals by worker, site, and contractor agency, synced to a company's existing payroll or HRMS platform through API or FTP, so the hours behind the cost calculation are hours actually verified on-site rather than hours self-reported by an agency.
Recruitment and mobilization costs also scale differently by nationality mix on a GCC project: visa issuance, labour card fees, and repatriation provisions vary by worker nationality and contract type, and a manpower budget that prices every hire at a flat recruitment cost will understate the true cost of sourcing certain nationalities over others.
A Sample Headcount Planning Template
This is a starting structure, not a finished budget. Every AED figure needs your own site-specific cost data, and every row should carry a replacement-or-growth label so Finance is reviewing hiring rationale, not just a headcount total.
Headcount Compliance Anchors for the GCC
A headcount plan that ignores regional compliance requirements will produce a hiring number Finance approves and Operations cannot legally execute on schedule, so this section covers the anchors that shape GCC headcount timing.
All six GCC states operate a Wage Protection System (WPS), requiring wages to move through approved payment channels. WPS itself is not optional in any of the six, though the specific Salary Information File (SIF) format and administering authority differ by country, so a payroll process built for the UAE does not automatically transfer to Saudi Arabia or Qatar without confirming the local file format first.
Saudization (Nitaqat) and Emiratisation are workforce-nationalization quota programs, not wage-protection systems, and the distinction matters for headcount planning specifically.
Accurate headcount reporting by site and nationality supports Nitaqat and Emiratisation tracking, but no attendance platform, including Truein, verifies nationality or quota status, and none should be described as guaranteeing nationalization compliance.
What a verified attendance and headcount system can provide is a clean, per-site, per-nationality headcount count, built from confirmed clock-ins rather than a self-reported muster register, that feeds directly into a company's own Nitaqat or Emiratisation reporting process.
Shift and overtime planning has to account for the Friday, or Friday-to-Saturday, weekly rest day observed across most of the GCC, alongside statutory Ramadan working-hour reductions, commonly a two-hour daily cut.
A headcount buffer calculated on standard working hours will run short the moment Ramadan scheduling takes effect, and outdoor sites in Saudi Arabia and the UAE also work around mandated midday-heat bans during summer, which compresses the working day further and should be built into the plan.
This is regional operating context every GCC headcount plan has to account for on its own, separate from whatever attendance and shift policy tooling a company runs, since configurable overtime and shift rules are designed to support compliance with local requirements.
Disclaimer: This section does not constitute legal advice. The information presented is based on available references at the time of writing and may contain inaccuracies or omissions. Readers are advised to verify details independently or consult a qualified professional.
How Often to Reforecast, and What to Reconcile Each Time
A headcount plan built once a year and never revisited drifts from reality within a quarter, especially on projects with the deployment volatility multi-agency GCC sites see regularly.
Maintain an annual plan, reforecast formally every quarter, and review monthly whenever hiring velocity, attrition, or site-level deployment shifts materially.
Every review should reconcile three numbers side-by-side: approved headcount, agency-reported deployed headcount, and verified present headcount, by site and by agency.
Tracking planned versus actual headcount and forecast variance (actual headcount minus forecast headcount) at each review turns this into an early-warning system that catches drift before it shows up as a manpower budget overrun nobody can explain.
A unified, real-time dashboard across every site, contractor, and shift makes this recurring reconciliation practical instead of a manual spreadsheet exercise rebuilt from scratch each quarter, the same reconciliation discipline covered earlier in the article, applied on a recurring schedule instead of only when an invoice dispute forces the question.
Frequently Asked Questions
1. What is the difference between headcount planning and manpower planning?
In GCC construction and facility management, the two terms are used almost interchangeably, though "manpower planning" more often refers specifically to contract labour and agency-supplied workers, while "headcount planning" can include both owned staff and contract workers.
Either way, the plan should track current headcount, expected attrition, and approved openings by site, with contract labour broken out by agency rather than folded into a single company-wide number.
2. How do you know if the contractor headcount matches what you are paying for?
Compare three numbers for each site and agency: the headcount approved on the work order, what the agency reports as deployed, and what is independently verified present through a system like face recognition and GPS-verified clock-in.
If your only source for the third number is the agency's own attendance register, you do not have independent verification, and any reconciliation built on it will show false confidence rather than an actual match.
3. How do you reconcile approved, deployed, and verified headcount?
Put the three numbers side by side for each site and agency on a fixed cadence: the headcount approved on the work order, what the agency reports as deployed, and what is independently verified present through face and GPS-verified clock-in. Run it monthly, not only when an invoice dispute forces the question, so drift shows up before it reaches the bill.
3. Does headcount planning need to account for WPS and gratuity in the GCC?
Yes. A manpower budget that only tracks base pay understates true employment cost, since WPS governs how wages are paid and gratuity is an end-of-service obligation that accrues with tenure across the GCC. Neither is something an attendance platform calculates directly.
Both need to be built into the cost-per-hire figure in the headcount template before Finance reviews it, using payroll-ready attendance data as the input rather than a manually reconstructed timesheet.
4. How do you calculate a headcount buffer for leave and absence?
Take the base productive headcount your workload requires, then add 5 to 10% depending on your site's historical leave and absence pattern, rounding up since partial workers cannot be deployed.
A site needing 50 productive workers with a 6% buffer plans for roughly 53, and that buffer should be recalculated separately for Ramadan and summer heat-ban periods rather than applied as one flat number year-round.
5. Can attendance software replace a headcount planning process?
No, and this is worth stating directly because it comes up often. Attendance software verifies who is actually on-site and feeds that data into the planning process; it does not set hiring targets, approve manpower budgets, or replace the review cadence between HR, Finance, and site leadership.
Truein's role is supplying the verified attendance and headcount data a plan needs, not running the planning process itself.
6. How does headcount planning differ between a construction project and a facility management contract in the GCC?
Construction headcount is project-phase-driven: mobilization ramps up at project start, peaks during structural phases, and demobilizes as the project closes, so the plan has a defined end date built in.
Facility management headcount is contract-renewal-driven instead: the workforce stays roughly steady for the life of the client contract, and the planning risk sits at renewal, when a client can change scope or headcount requirements with comparatively short notice.
Both still run on the same reconciliation practice, comparing approved, deployed, and verified headcount, but the review cadence differs: construction reconciles against project milestones, facility management reconciles against the contract's SLA and renewal date.
Closing Thoughts
Building a headcount plan that survives contact with a multi-agency, multi-site GCC operation means treating attendance data as an input to the plan, not as an afterthought you check only once a dispute forces the question.
The formula, the buffer, and the manpower budget template all still apply, but every one of them inherits the accuracy of the numbers feeding them, and for contract labour spread across sites, those numbers are only as good as the verification behind them.
If your headcount plan currently runs on agency-submitted registers with no independent check, a guided walkthrough of how Truein verifies attendance and contractor headcount across GCC sites is a reasonable next step.
