A private employee flow
Employees enter a PIN, see the one action that makes sense, confirm it, and leave the screen ready for the next person.
SOFTWARE / TIMEKEEPING
Timekeeping app
A tablet records clock-ins and clock-outs, saves them on the device, and brings them together for payroll records. The app is in active business use.
A missed connection should not mean a missed punch. Explore why the app saves locally first, and what working software still needs before its recovery can be trusted.
Internal workplace tool · no public signup or customer service.
Read the reliability field noteWhat it helps with.
The employee side stays intentionally small. The extra detail lives behind an administrator PIN, where it can help with roster changes, status checks, and payroll preparation.
Local first, sync second
Every punch is saved on the device before the network is involved. If the connection fails, the saved punch waits for synchronization.
Roster and payroll review
An administrator can manage employees, review clock status, choose a pay period, spot issues, and prepare summary and detail files.
Another view when needed
An invite-only web portal brings together punch history, corrections, and payroll reports without exposing the employee kiosk.
How it works.
The everyday path should take seconds. Network trouble, reporting, and account management should not get in an employee's way.
- 01Enter a PIN
The public screen does not show the employee roster.
- 02Clock in or out
The app offers the action that follows the last saved punch.
- 03Save locally
The original time is recorded on the device immediately.
- 04Review later
Cloud copying and payroll review happen without holding up the kiosk.
In use.
The business uses the app for timekeeping and payroll records. Earlier device checks also established local punch recording and synchronization.
Business use
The app is used for workplace timekeeping and payroll records.
Original times kept
During the device checks, clock-in and clock-out events were saved locally and arrived in the cloud copy with their original punch times.
Existing data preserved
A later app update was installed over the existing app without removing its local workplace file.
The release and its limits
The correction sprint is complete as of October 20, 2026, after roughly a month and a half. The existing feature is enabled, with that setting checked after release. Enabling it changed no punch or correction records.
The workflow is designed to correct punch times while preserving the original and its audit history. Payroll reporting needs to use the current correction-aware portal. Enablement is a narrower result than complete live acceptance; some verification was deliberately deferred, and this update makes no claim of proven recovery.
Field note, updated October 20: why a correction sprint took roughly six weeks, and what finally made it possible to finish.
Why the finish line kept movingFollow what develops next.
New field notes, meaningful project changes, and corrections, when there is something useful to share.
Follow App Wizzud via RSS