Work Software & web

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.

Barcode scanner
Barcode scanner Photo: Raimond Spekking, CC BY-SA 4.0

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.
Badge time clock lifecycle Built on a teammate's first version from May 21. May 26: rolled out and badges handed out. June 19: email receipts and daily summaries. June 23: admin portal for timecard review. July 6: hash-chained ledger with signed checkpoints. August 5: read-only self-service portal. September 8: retired, with a restore-tested archive. Fifteen weeks from rollout to retirement. Rollout to retirement in 15 weeks built on a teammate's first version, May 21 Rollout May 26 · badges handed out Email receipts Jun 19 · and daily summaries Admin portal Jun 23 · timecard review Signed ledger Jul 6 · hash-chained punches Self-service portal Aug 5 · read-only role Retired Sep 8 · tested archive
Rollout, payroll features and retirement, based on a teammate's first version.

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.

Privacy