Rolled out, extended and retired a badge time clock
A teammate built the badge clock-in system. I rolled it out, added payroll features and a tamper-evident ledger, then retired it with a tested archive when the shop switched to a touchscreen clock.
Results
2,859punches archived and restore-tested
688timecard-days in the final archive
15 weeksfrom staff rollout to retirement
The problem
The first version recorded badge scans, but staff had no copy of their punches, a forgotten clock-out left the day open, payroll had no screen for reviewing timecards, and nothing would show if a stored punch were edited later.
What I did
- Added email receipts for punches, end-of-day summaries and automatic clock-out with checks for missed clock-outs.
- An admin portal for managing employees, reviewing and finalizing timecards, and running the weekly hours report.
- A tamper-evident ledger: each punch is hash-chained to the one before it, with signed checkpoints, so an edited record breaks the chain.
- A read-only self-service portal where employees check their own hours, on a read-only database role, with its own security review.
- Retired the system when the shop moved to a touchscreen clock: switched off automation, archived data off the machine and tested the restore.
What I took from it
When we replaced the clock, I documented the shutdown, archived the records off the machine and tested the restore. Payroll still had a usable copy after the old service stopped.