Dawmo 2026.9 is out — rendered payslips, a public API and calendar feeds. See what changed
For contractors running crews across sites and camps, where coverage drops, the machine at the gate will not export, and a visa can lapse unnoticed in a workforce that size.
A labour camp has no coverage, a tower core has no GPS, and half the crew does not carry a smartphone. The timesheet gets rebuilt at month end from memory.
How Dawmo handles it
The punch is written to the phone and syncs on its own when the signal returns, so a week in a camp syncs on the drive back. Crews without smartphones tap an NFC card at the gate, and the punch method is set per site and per role.
Across a large workforce a passport, visa, labour card or Emirates ID is always close to lapsing, and nobody finds out until it already has.
How Dawmo handles it
Every document’s expiry is registered from the scan and lands on one dashboard, with the PRO named against it. Vehicle registration and insurance dates sit on the same dashboard as the visas.
Salary is one line. Accommodation, transport, visas, tickets and gratuity sit in other spreadsheets, so the cost of a project is known only after it closes.
How Dawmo handles it
Salary cost is split across projects, sites or entities on the rules Finance sets. Visa, insurance, accommodation, transport, tickets and gratuity accrual are shown per head and per site, against budget.
The rest of the platform switches on later, on the same employee record, with nothing to migrate.
Twenty minutes, on a call, with your payroll rather than our demo data. Bring last month’s run and we will compare it line by line.
In the call
No slides and no obligation. Book a time that suits you.