Automatic timesheets
Punches are grouped per person and week; nobody copies numbers by hand.
Every clock-in and clock-out builds the timesheet — breaks, corrections and manager approval included.
Punches are grouped per person and week; nobody copies numbers by hand.
Missed breaks or wrong times are corrected by a manager, with the change recorded.
Hours are reviewed and approved before they leave the system.
Every hour is attached to a location, which makes costing possible.
Without signal the punch is stored on the device and syncs later.
Approved hours export as a file for your payroll provider or accountant.
When hours are rebuilt from notes at month end, it costs a day of admin and starts arguments. A timesheet that fills as the shift runs is visible to both the employee and the manager the whole time.
Every edit to a time shows who changed it and when. That builds trust in the team and removes the back-and-forth when payroll comes around.
Before you commit to any workforce software, get these points in writing — from us and from every other vendor. Our answers are below; we go deeper in the demo.
Yes. We provide a DPA under Art. 28 GDPR and sign it with you before your team starts using the app.
Hosting and database run on Supabase. The exact region and the sub-processor list are set out in writing in the DPA — not only on request.
Location sharing is opt-in per person — refuse it and clock-ins still record, just without coordinates. Reporting and access scope can be restricted per role. The contested points are settings you negotiate concretely in a works agreement.
Time and absence records stay for the legal retention period, then are deleted. All core and time data exports as CSV/Excel — you take your data with you when you switch.
No. It delivers verified hours; pay is calculated elsewhere.
Yes, everyone sees their running total in the app.
Yes, by authorised roles, and every correction is logged.
Yes, capture continues offline and syncs later.