The Legal Position
Location at the moment of clocking is narrow, which helps. What still applies, and the two points where deployments go wrong.
Reference
The legal position
Checking a position once, at a deliberate action, is one of the easier things to justify. Two design choices throw that advantage away.
10 notes
When the System Decides Pay
A clock-in system feeds payroll, which means a technical failure becomes a wage question. The rules that follow from that.
Analysis
What to Keep and For How Long
The attendance record and the location evidence have different lifespans. Separating them is the design that satisfies both payroll and minimisation.
Procedure
Consulting Before You Deploy
A requirement in several jurisdictions and the step that produces the radii. What to consult on, and what the answers change.
Procedure
The Impact Assessment
Likely required, and short for this deployment. What to write, and why the proportionality section is where it is decided.
Procedure
Who Sees the Punch Data
Coordinates attached to every arrival are more revealing than the attendance record they support. Access designed around the actual need.
Procedure
When Someone Asks What You Hold
Attendance and location records are commonly requested, usually during a dispute. What you will produce, and the rehearsal worth doing first.
Procedure
Agency and Contract Workers
Who holds the record, whose app is on the phone, and the status question that a clock-in system can answer badly.
Analysis
Writing the Notice
Six questions people actually have about a clock-in app, answered in plain sentences on one page.
Procedure
What an Inspector Would Ask For
Three situations examine this data, each asking for different things, and most of them cannot be produced after the fact.
Procedure