Time tracking for construction
Field workers log hours from their phone and submit the month. Admins review every site from one dashboard and export the month to Excel or PDF.
The month, end to end
Every rule below is enforced on the server, not in the app. What a worker can change, and when, is never decided by the phone in their hand.
Tap a day, pick the project, enter the hours. A run of days on the same site is selected together and filled in once.
Three days before the month ends, anyone who has not submitted gets an email naming the exact days still missing.
The worker confirms the month's totals. After that the month is closed to them — no quiet edits to hours already counted.
Admins check the month across every site and export to Excel or PDF. Corrections stay possible, and every one is recorded.
Rules that hold
A worker fills in today or a day already past. Nobody books time they have not worked yet.
Submitting locks it for the worker. Admins can still add a day that was missed, and the change is attributed.
Absence is never added into the hours worked, so a month of leave never reads as a month of labour.
Work is logged against a project the worker is assigned to. Finished sites stop accepting new hours.
Three days after the month closes, whoever still has not submitted hears about it — and so does their manager.
One deployment serves several firms. Every query is scoped to the company, all the way down to the database.
Who uses what
Workers never open the dashboard; signing in there sends them to the mobile app instead.
Sign in to the dashboard, or ask your administrator for an account.