Attendance fraud is the most expensive quiet problem in physical security. You bill for a post that was covered, you pay a guard who was there on paper, and the client usually notices before you do. Here is how to close the gap.
1. Geofence every site
Record real coordinates and a sensible radius per site, then reject clock-ins from outside it. This one control eliminates clocking in from home or from the matatu. Keep the radius realistic — 100 metres suits most sites, large compounds need more. Set it too tight and guards will fail legitimate clock-ins and lose trust in the system.
2. Make offline capture the default
The most common reason attendance controls get switched off is that they fail in low-signal areas. If the app captures the clock-in offline — with the real timestamp and GPS fix — and syncs when signal returns, guards keep using it and your data stays honest. Without that you will be pressured into allowing manual overrides, and manual overrides are where fraud lives.
3. Separate "late" from "absent" — and act on both
Most companies only chase absence. Chronic lateness is more corrosive because it gets tolerated. Track late minutes automatically against shift start and review the pattern weekly rather than shift by shift.
4. Report by exception, not by roster
Nobody reads a 300-line duty list. Supervisors need a short list: who has not clocked in 15 minutes after shift start, and which posts are uncovered right now. Everything else is noise.
5. Remove the incentive, not just the opportunity
Controls alone create workarounds. Look at why no-shows cluster:
- Rosters published too late for guards to plan transport.
- Sites genuinely unreachable in time for the shift start.
- Late or incorrect pay — the fastest way to lose reliable guards.
Fixing pay accuracy and publishing rosters earlier usually cuts no-shows more than any technical control will.
What good looks like
Within a month you should be able to answer, without phoning anyone: what was coverage yesterday, which sites had gaps, which guards are repeatedly late, and does billed cover match paid cover. If you cannot, the reporting is not doing its job.
SecureForce enforces geofenced clock-in with offline capture and surfaces coverage and exceptions per site. See how attendance works.