Dawmo 2026.9 is out — rendered payslips, a public API and calendar feeds. See what changed
For FM and cleaning companies with staff spread across client buildings, on rosters that change by site, where the hours worked have to be proved to the client as well as paid.
One team is in a mall, another in a tower basement, a third in a cold store. One clocking method cannot fit all of them, and GPS reads nothing underground.
How Dawmo handles it
The punch method is set per site and per role. A geofence is drawn per building, a Bluetooth beacon proves presence in a basement, a cold store or a tower core, and a rotating code on one shared tablet covers a whole shift.
Shifts move with each contract and each building, and a gap shows up on the morning a site is left uncovered.
How Dawmo handles it
Shift patterns are built once and rolled forward, with coverage visible before the week starts. A missed punch is corrected by request rather than by edit, so the fix carries who asked and who approved.
A client pays for the hours worked on their site, and a timesheet rebuilt from three sources is hard to defend when they query an invoice.
How Dawmo handles it
Timesheets are kept per person, per site and per project, and export in the shape your client invoices want. Salary cost is split across sites on the rules Finance sets.
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.