About

Fifty notes on geofenced attendance, written from the operator's side.

Who this is for

Whoever has been asked to deploy something and needs to know whether the physics allows it at their sites. Whoever will run it afterwards, usually payroll and usually not consulted. And the people clocking in, whose cooperation determines whether the record describes anything.

How the notes are written

Measurements you can take. The site walk, the overnight check, the stopwatch at shift change, the airplane-mode test.

The uncomfortable findings included. A geofence barely touches buddy punching on site. Mock location tools work and are easy to install. A punch record cannot serve as a fire roll call. Most operations find the problem smaller than the solution.

Limits stated plainly. Three notes are about what a punch does not prove, what this does not solve, and doing it without technology at all.

What is deliberately absent

How to enable background collection quietly. How to make a fallback harder to reach. How to conceal what permission an app requests.

These appear only in the notes explaining why they should not be done, and requests to help with them are declined in the same terms: a better-concealed version of the thing is still the thing.

No numbers

No accuracy figures beyond broad ranges, because they depend on the phone, the building and the time of day. No savings percentages, because vendor figures are best cases. Measure your own; the notes say how.

About this domain

This address previously belonged to a removals company in India, and by the time the site was archived it had been compromised: one page had been replaced with gambling spam, including in the page title.

None of that material is here. Every previous address returns a clear "gone" response.