Emiratisation Compliance Software: Track It in Zoho

The Problem Is Not Hiring. It Is Knowing Where You Stand

Ask an HR manager in Dubai what their company’s current Emiratisation ratio is, and you usually get one of three answers. A number from a spreadsheet somebody updated last quarter. A number the PRO quoted after their last MoHRE visit. Or, most honestly, “I’d have to work it out.”

That third answer is the real problem, and it is not a competence problem. It is a system problem.

Emiratisation runs on a half-yearly clock with a published, escalating, per-head cost attached to missing it. Yet in most UAE businesses the figure that determines that cost is not held in any system — it is reconstructed manually in the weeks before a deadline, exactly when there is no longer time to fix a shortfall.

Hiring an Emirati national takes time: sourcing, offer, notice period, visa and work permit processing. Discover in late November that you are two skilled roles short, and you have not discovered a hiring task. You have discovered a cost.

This article covers how to close that gap — what data you need, how to hold it in Zoho People, how to turn it into a live ratio and a forward forecast, and what Zoho will not do for you.

What the Rules Actually Require

A short, accurate summary, because many UAE businesses are working from a half-remembered version.

Companies with 50 or more employees (mainland). The UAE Cabinet set Emiratisation rates for skilled jobs to rise by 2% annually, moving toward an overall 10% target by 2026, delivered in two half-yearly steps of 1%. MoHRE confirmed 30 June 2026 as the deadline for the first-half 2026 target, requiring 1% growth in Emirati skilled professions. The second checkpoint falls at year end.

Non-compliance for this group carries a monthly contribution for each Emirati not employed against target. Per the UAE Government portal, this started at AED 6,000 per month in 2023 and increases by AED 1,000 each year through 2026. Ahead of the first-half 2026 deadline, MoHRE stated that contributions of AED 10,000 per month for each unfilled position would apply to non-compliant companies from 1 July 2026.

Companies with 20–49 employees. A separate regime applies in 14 designated sectors, including information and communications, healthcare, construction, hospitality, real estate, finance and retail. These companies were required to employ at least one UAE national by the end of 2024 and a second by the end of 2025. Published contributions were AED 96,000 in January 2025 for a 2024 shortfall and AED 108,000 in January 2026 for a 2025 shortfall.

Two things to note. The measure is skilled roles, not total headcount — which is where most internal calculations go wrong. And these thresholds are set by MoHRE and subject to change: verify your specific obligation with MoHRE or your adviser before acting on any published summary, including this one. Techvaria is a Zoho implementation partner, not a legal or labour-law adviser.

Why Spreadsheet Tracking Fails — and What It Costs

Spreadsheets handle many HR tasks perfectly well. They fail at this one for reasons particular to how the calculation works.

• The denominator moves constantly. Your ratio changes with every joiner, leaver and role change — including changes nothing to do with Emirati headcount. Hiring ten expatriate engineers moves it the wrong way without anybody noticing. A sheet updated monthly is wrong most of the month.
• Classification gets decided once and forgotten. Whether a role counts as skilled is not obvious for every title, and when it is decided informally by one person it is not reproducible, not reviewable, and not defensible. When that person leaves, the logic leaves with them.
• Pending movements are invisible. The number that matters is your ratio on the deadline, which requires knowing who is serving notice, whose contract ends, and who has accepted but not started. A static sheet holds none of it.
• There is no audit trail. “Here is a spreadsheet” is a weak answer if your position is questioned.

The direct cost of finding out late is published and easy to calculate: each unfilled role against target accrues a monthly contribution for as long as the shortfall persists. The indirect costs are what change behaviour. Panic hiring rarely produces a good hire, and one who leaves within the year puts you back where you started with the cost already incurred. Non-compliance can affect establishment classification and access to certain services, which reaches work permit processing for your whole workforce. And MoHRE has publicly pursued arrangements designed to appear compliant without genuine employment — any shortcut here carries risk disproportionate to the cost it avoids.

The Four Questions Your HR System Should Answer Instantly

If your system cannot answer these in under a minute, on any given day, you are managing this metric blind.

1. What is our skilled-role Emiratisation ratio right now? Not last quarter. Today.
2. What will it be on the deadline, accounting for notice periods, contract endings and accepted offers not yet started?
3. How many hires do we need, and by when, allowing for notice and visa processing?
4. Can we evidence it? Who classified each role as skilled, when, and on what basis.

Building the Data Foundation in Zoho People

The problem is that the data needed for the calculation does not exist in one structured, current place. The capability is Zoho People as the workforce system of record. The outcome is a ratio you can trust without rebuilding it.

Four fields do the heavy lifting, and they need deliberate design rather than inheritance from a generic template:

• Nationality, as structured data rather than free text. Free-text nationality is the single most common reason a ratio cannot be automated.
• Skilled classification, as a controlled field on the role rather than a judgement made at reporting time — with the MoHRE occupational code alongside it, so the classification traces to something external rather than to someone’s opinion.
• Entity and licence, because a group running several mainland licences has a separate obligation per establishment. A consolidated group ratio is not the number MoHRE is looking at.
• Employment status and dates, including notice period and last working day, so pending departures are visible before they become actual ones.

Custom fields hold the UAE-specific attributes a generic HR template omits — work permit details, Nafis registration status, and the classification rationale.

Workflows keep it current. A promotion can trigger a classification review rather than silently changing the denominator. A resignation can flag its effect on the ratio the moment it is entered.

Approvals create the audit trail. Setting or changing the skilled classification through an approval step records who decided, when, and on what basis — as a by-product of normal HR work rather than a separate compliance exercise.

The number stops being something somebody calculates and becomes something the system knows.

Turning the Data Into a Live Ratio and a Forecast

Clean data is necessary but not sufficient. The value is in what you do with it.

The live ratio. Zoho People’s own reporting handles current state — skilled headcount, Emirati skilled headcount, ratio, by entity. For day-to-day monitoring that is usually enough.

The forecast. This is where Zoho Analytics earns its place. Blending the employee master with pending movements — notice served, contracts ending, offers accepted — projects the ratio forward to the deadline rather than reporting it backward. That projection is the number that lets you act while acting is still possible.

The gap, expressed in roles. “We are 1.3% below target” means nothing to a hiring manager. “We need two more Emirati hires in skilled roles, starting before 15 November to clear notice and permit processing” is an instruction someone can execute.

The alert and the board view. A scheduled check that flags a projected shortfall to people who can act, so the problem surfaces in September rather than December — and one executive page showing current ratio, projected deadline position, gap in roles, and the financial exposure if it is not closed. Finance leaders respond to that last figure in a way they do not respond to a percentage.

On Zoho Creator. Where a business genuinely has unusual requirements — a complex multi-licence structure, a bespoke classification approval chain, evidence documents held against each hire — Zoho Creator can hold that alongside Zoho People. For most companies it is unnecessary, and we would say so.

Closing the Gap: The Hiring Pipeline

Knowing you need two hires only helps if the hiring happens.

Zoho Recruit can run the Emirati pipeline as a tracked process rather than an email thread: requisitions flagged as counting toward target, sourcing, interview stages, offer status, and expected start dates that feed straight back into the forecast.

The lead-time reality. Between a signed offer and a person counted in your ratio sit a notice period, visa or work permit processing, and onboarding. Your hiring deadline is materially earlier than your compliance deadline, and the gap is measured in weeks. Build that lag into the forecast rather than discovering it.

Nafis. The federal Nafis programme is the UAE’s platform supporting Emirati employment in the private sector, and the route most companies use for sourcing and support. Keep candidate records in your ATS; treat Nafis as the authoritative channel for the programme itself.

Retention is the half nobody plans for. A hire made in March who leaves in September costs you the hire and leaves you the gap. Companies that treat this as a hiring task rather than a retention task repeat the exercise every year.

What Zoho Does Not Do — and What That Means

This section matters more than the three before it, because it determines whether your project succeeds.

There is no Emiratisation module. Zoho does not ship a pre-built feature that calculates your quota out of the box. What you are building is a structured HR data model plus reporting configured for a specific UAE requirement — design and configuration work, not a switch to turn on. Anyone saying otherwise is selling something.

Zoho does not file anything with MoHRE. Your obligations are discharged through MoHRE’s own channels by your PRO or in-house team.

Classification is your decision, not the software’s. The system can hold a classification, enforce approval on it, and make it auditable. It cannot tell you whether a job title qualifies as skilled.

Zoho Payroll UAE is adjacent, not the same thing. It generates SIF files for WPS, calculates end-of-service gratuity for expatriate employees, tracks leave and attendance, and flags expiring documents. Often part of the same project — but WPS and Emiratisation are different obligations. Confirm pension and statutory handling for UAE nationals against current documentation rather than assuming coverage.

Data quality is the project. If nationality sits in forty spellings and half your job titles have no classification, no dashboard design will produce a reliable ratio. The remediation is where the time actually goes.

UAE-Specific Considerations

Mainland versus free zone. The targets here apply to mainland establishments; free zone entities sit under different arrangements. Businesses operating both — common in Dubai — need that distinction in the data model from the start. A blended ratio across both is not a meaningful number for any obligation.

Multiple licences mean multiple obligations. A group with three mainland licences has three establishment positions, not one. Entity has to be a first-class field and every report filterable by it. This is the most frequent structural mistake we see in UAE HR configurations.

Document expiry is operationally entangled with all of this. Visa, Emirates ID, labour card and passport expiry affect who is validly employed — worth switching on Zoho Payroll UAE’s expiry alerts as part of the same project.

Arabic and English. Zoho’s applications support Arabic, which matters for adoption in organisations with Arabic-speaking staff. Where documentation may be reviewed by an authority, confirm the language requirement for that context rather than assuming English suffices.

It intersects with the finance calendar. Corporate tax, VAT and e-invoicing readiness are all claiming CFO attention. The practical argument for handling Emiratisation tracking in the same programme is that both rest on the same foundation — clean master data in a connected system — and both are evidenced to a UAE authority.

Implementation: A Realistic Sequence

1. Establish the baseline — headcount by entity, current classification, Emirati headcount in skilled roles. Expect it to surface data problems. That is the point of doing it first.
2. Agree the classification method with your advisers: how a role is determined skilled, who decides, when it is reviewed. A business decision, before any configuration.
3. Design the data model — nationality, classification, MoHRE occupational code, entity, status, notice dates — with nationality and classification as controlled fields.
4. Remediate the existing data. Usually the longest step.
5. Configure Zoho People — fields, workflows on role change and resignation, approvals on classification.
6. Build the live report, then the forecast. Current state first; it is quick and builds confidence.
7. Set the alert threshold and name an owner. An alert with no owner is a notification nobody reads.
8. Connect the hiring pipeline, feeding expected start dates back into the forecast.
9. Review quarterly, not half-yearly. Reviewing on MoHRE’s rhythm means learning about problems when MoHRE does.

Best Practices

1. Treat it as a managed metric with a named owner, reported monthly.
2. Make nationality and skilled classification controlled fields. Free text makes automation impossible.
3. Hold the MoHRE occupational code alongside your internal job title.
4. Model entity properly from day one if you hold more than one licence.
5. Forecast forward, do not report backward.
6. Express the gap in roles and dates, not percentages.
7. Build notice periods and permit processing into the forecast — your real hiring deadline is weeks earlier.
8. Put the financial exposure on the executive dashboard. It is what secures the hiring budget.
9. Approve classification changes, so the audit trail builds itself.
10. Plan for retention, not just hiring.
11. Verify your obligation with MoHRE or your adviser before acting on any summary.

Common Mistakes

• Calculating on total headcount instead of skilled roles. A comfortable number that is not the one being measured.
• Nationality as free text. No automation, manual reconciliation forever.
• One blended ratio across multiple licences. Not the number any establishment is assessed on.
• Classification by memory. Not reproducible, not defensible, and lost when the person leaves.
• Ignoring pending leavers. Your ratio on the deadline is not your ratio today.
• Forgetting that expatriate hiring moves the ratio. A growth quarter can push you below target with no HR decision involved.
• Starting the hiring conversation at the deadline. Notice periods make that arithmetically impossible.
• Building dashboards on dirty data. Confident wrong answers, faster.
• Treating it as HR’s problem alone. The penalty lands in finance; finance should see the forecast.

An Illustrative Scenario: A Dubai Engineering Services Firm

A composite illustration built from patterns common in the UAE market. It is not an account of a specific named client.

Consider a Dubai engineering services business with around 180 employees across two mainland licences and a free zone entity, growing on infrastructure contracts.

Before

Emiratisation lived in a workbook maintained by one HR coordinator and updated before each deadline. Nationality was free text. Skilled classification was a column filled in from memory with no record of the reasoning. The free zone entity sat in the same sheet, which made the mainland ratio look healthier than it was. The company had met its targets twice by hiring in the final weeks, both times under pressure and at unbudgeted cost.

What Was Implemented

The first step was not software. The leadership team, with their PRO and legal adviser, documented how a role is classified as skilled and who owns that decision — two working sessions that became the specification for everything else.

Zoho People was then configured with nationality and classification as controlled fields, MoHRE occupational codes against each role, and entity modelled as a first-class attribute separating the mainland licences from the free zone entity. Workflows made a role change trigger a classification review and a resignation flag its ratio effect immediately. Data remediation took the longest, and produced the finding management valued most: the mainland ratio had been overstated, because free zone employees were sitting in the denominator.

Zoho Analytics then delivered a current ratio by entity and a forward projection including notice periods, contract endings and accepted offers, with a monthly alert to the HR and finance directors when the projection fell below target.

After Two Quarters

The most useful outcome was a change in timing rather than a number: the projected shortfall surfaced in the second month rather than the eleventh, turning a penalty conversation into a recruitment conversation with a realistic runway. The finance director’s standing view of the exposure, in dirhams rather than percentages, was what secured the budget without debate.

Industry Use Cases

• Construction and engineering services. Large mainland headcounts, multiple licences, project-driven hiring that moves the denominator unpredictably — among the most exposed sectors, and one of the 14 designated for the 20–49 employee regime. See construction solutions.
• Healthcare. Mixed clinical and administrative workforces where classification needs care, with document-expiry and licensing obligations alongside. See healthcare solutions.
• Logistics and transport. Large workforces and high turnover — the profile that defeats periodic manual tracking. See logistics solutions.
• Trading and distribution. Multi-entity structures are the UAE norm here, making correct entity modelling the deciding factor. See trading and distribution solutions.
• Manufacturing and professional services. In manufacturing the skilled/unskilled boundary genuinely affects the calculation; in professional services the skilled denominator is close to total headcount, so the target means more hires than leaders expect. See manufacturing and IT services ERP.

Approach Comparison