Phone clocking with geofence
Punches are tied to a site without paper or a separate device.
Timesheets, clocking and rosters that feed payroll and billing once.
Time and attendance captures hours through weekly timesheets, phone and kiosk clocking and rosters. Overtime and holiday rules are held as country data, and approved hours flow once to payroll, project billing and costing.
Punches are tied to a site without paper or a separate device.
Approved hours reach payroll, billing and costing without re-keying.
You can see why an hour counted as overtime.
Teams cover gaps themselves with manager sign-off.
Search or filter. Planned items are labelled; everything else is available now.
Weekly hours for projects and general work, submitted and approved.
9 featuresAttendance capture on the phone, at a site or at a kiosk.
11 featuresPlan who works when, and let teams swap.
10 featuresCountry rules held as data, ready to review.
10 featuresApproved hours flow once to payroll, projects and billing.
5 featuresSee what hours cost by project and cost centre.
5 featuresEvidence for audits and inspections.
3 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Time & Attendance.
Weeks, corrections, overtime and exceptions are approved in workflow by someone other than the person concerned.
Datasets and ready reports on hours, overtime and cost.
Datasets
Dashboards
Approved hours are published as events for payroll, projects and billing.
/v1 time resources
Events
Connectors
Work codes, holiday calendars and historical hours can be loaded through AI Migrate. No timekeeping vendor packs are planned yet.
Clock in and out, fill and submit the week, view shifts and request swaps on the phone.
Yes, with optional site boundary checks and consent for location. A shared PIN kiosk is available for sites without phones.
No. They are held as data per country and rule set and your specialists review them.
Yes, once per approval, without duplicates.
Not yet. Rosters, templates and swaps are built; demand forecasting and automatic scheduling are planned.
Only by requesting a correction that is approved.
Not yet; planned.