Dubai · What differs here

Running a Non-Desk Workforce in Dubai

The software questions that only matter once your staff are spread across mainland sites, free-zone premises and more than one emirate — and why the generic answer stops being useful at that point.

Book a 20-min demo View AED pricing

AED billing · GST-hours support · Arabic and English staff app · Multi-emirate by design

Most workforce software is written for one office in one city

A Dubai operation rarely looks like that. Staff are spread across sites that may sit under different legal entities, some inside free zones and some on the mainland. A shift can begin in one emirate and end in another. The commute is long enough that it shapes the roster. And the workforce itself is multilingual, largely non-desk, and often on rotating patterns. None of that is exotic here — it is Tuesday. This page is about those specifics. For what the product does, see the platform overview.

One workforce, several legal entities

Groups here commonly operate more than one licensed entity — a mainland company, a free-zone company, sometimes several. Staff records, contracts and payroll exports have to stay separated by entity even when the same manager supervises across them.

Free-zone and mainland sites in one view

Premises inside a free zone and premises on the mainland differ administratively but are one operation to the person running the roster. Sites carry their own presets while rolling up into a single operational picture.

Shifts that cross emirates

A driver, an engineer or a security supervisor may cover posts in more than one emirate in a day. Each post keeps its own geofence, so movement between them is legible in the record rather than looking like a location failure.

Dense sites, tight geofences

Towers and industrial parks here put separate sites within a few hundred metres of each other. Geofence radii are set per site rather than globally, because a radius that works for a remote yard will silently accept the wrong building downtown.

The commute shapes the roster

Peak-hour travel across the city is long enough that back-to-back shifts on distant sites are unrealistic. Rest rules and travel between assignments are constraints the scheduler respects rather than a manager remembering.

A staff app people can actually read

A non-desk workforce here is multilingual. A check-in flow that only works in English pushes the burden onto supervisors, who end up doing attendance on everyone else behalf — which is exactly how records stop being evidence.

The sector mix is the point

Construction, security, facilities management, logistics, hospitality and healthcare dominate the non-desk workforce here. Each has its own shift shape — rotating posts, split shifts, on-call — and none of them fit a nine-to-five leave calendar.

Priced and supported in the same time zone

Billing in AED against a local entity, and support during Gulf working hours rather than a follow-the-sun queue that answers after your shift has ended.

What a multi-entity, multi-emirate rollout actually looks like

Map entities before sites

Establish which licensed entity each group of staff belongs to first. Getting this wrong later means re-cutting every payroll export.

Define sites and their radii individually

Each site gets a geofence sized to its actual footprint. Dense locations get tight radii; remote yards get generous ones.

Encode the shift shapes you really run

Rotating posts, split shifts, night cover and on-call are configured as they are worked, not forced into a standard week.

Roll out by operation, not by headcount

One site or one contract at a time. A workforce spread across emirates is easier to onboard in operational units than in one organisation-wide switch.

Reconcile per entity

Hours, overtime and end-of-service accruals export per legal entity, so each payroll run matches the company it belongs to.

The compliance points specific to operating here

Working-hour rules apply per entity

UAE Labour Law limits on daily hours, rest and overtime (Federal Decree-Law No. 33 of 2021) are configured per entity and per site, because a group with several licences is not one uniform employer.

End-of-service accrues from the correct start date

Staff who move between entities within a group need their service history handled deliberately. The gratuity calculation reads the record rather than assuming continuous service.

Payroll exports match the paying entity

WPS-ready exports are produced per entity, so the file a bank receives corresponds to the company that employs those staff.

Biometric consent under the UAE PDPL

Consent is captured at enrolment in a language the employee reads, and staff can see what is held about them through the app.

Frequently asked questions

We have a mainland company and a free-zone company. Is that one account or two?▾

One account with the entities separated inside it. Managers see the operation they are responsible for regardless of entity, while staff records, working-hour configuration and payroll exports stay bound to the correct licensed company.

Our supervisors cover sites in Dubai and Sharjah on the same day. Does that break attendance?▾

No. Each post has its own geofence, so a check-in at one and a later check-in at another is a normal sequence rather than an anomaly. Travel time between assignments can be treated as a scheduling constraint.

Our sites are in the same tower block. Will geofencing tell them apart?▾

Geofence radius is set per site rather than globally, which is what makes dense locations workable. Check-ins also record the accuracy the device reports, so a vague fix is visible instead of being accepted as precise.

Most of our staff do not read English comfortably. Does that matter?▾

It matters more than most feature comparisons admit. If the staff app is not usable, supervisors end up checking people in on their behalf, and the attendance record stops being first-hand evidence.

Are you billed in AED?▾

Yes, in AED against a UAE entity, with support during Gulf working hours.