How Geofenced Staff Attendance Works: GPS Accuracy, Fair Review and Privacy

Published 12 October 2026 · 9 min read · By SOID Technologies Limited

In short

Geofenced attendance lets staff clock in from their phone, and the system checks whether they were inside the assigned work area at that moment. Done well, it also compares the time with the shift, watches for signs of cheating, sends every unusual case to a person for review, and protects staff privacy. This guide explains how each part works and what to look for in a system.

1. Why attendance records matter

An attendance record is more than a timesheet. It decides who gets paid for what, shows who was on site during an incident, supports health-and-safety duties, and is the first thing asked for in a dispute. When records are kept on paper registers or shared spreadsheets, three problems appear again and again:

Forgetting. People sign in late, or not at all.
Buddy punching. One person signs in for another.
Weak evidence. When a record is challenged, nobody can show how it was made or whether it was changed afterwards.

A geofenced system aims to fix all three: it makes clocking in quick, ties each clock-in to a place and a time, and keeps a trail of what happened.

2. How geofenced clock-in works

A geofence is a virtual boundary around a work location. It can be a circle with a set radius, such as 150 metres around an office, or a custom shape drawn around a site. Each member of staff is assigned to one or more locations.

When someone taps Clock in, their phone reports its position and an accuracy figure, which is the phone's own estimate of how far off the reading might be. The system then compares the two.

Dot = reported position. Ring = the phone's accuracy estimate.

Our own rules work like this, and they are a good model for any fair system:

Confident inside: the distance from the centre plus the accuracy ring still fits within the boundary.
In range, weak signal: the reported spot is inside, but the accuracy ring crosses the edge, so we can't be sure.
Out of range: even allowing for the accuracy ring, the person is outside. The distance is recorded.

Notice that the third case is not "rejected". We come back to that in section 6. You can try these rules yourself on our interactive geofence demo.

3. Why GPS is imperfect (and what that means for design)

Phone location is good, not perfect. A system that ignores this will punish honest people. Common causes of error include:

Indoors or underground. Buildings weaken satellite signals, so the accuracy ring grows.
Tall buildings and dense areas. Signals bounce, so positions can drift.
Cold starts. A phone that has just turned location on may take a moment to settle.
Computers instead of phones. A laptop usually estimates its position from Wi-Fi or its internet address, which can be kilometres out. A sensible system treats desktop clock-ins as unusual.
Stale readings. A position captured minutes ago may no longer reflect where someone is now.

The design lesson: use the accuracy figure, not just the dot. Show staff a live accuracy meter so they know when to step outside or wait a moment. And never let a weak reading alone decide that someone was absent.

4. Time, shifts and grace periods

Where someone is only answers half the question. The other half is when.

Trust the server's clock, not the phone's. Phone clocks can be changed. A reliable system records time on the server and flags a large mismatch.
Shifts and windows. A typical setup opens clock-in a little before the shift, allows a short grace period, and marks anything later as late, with the minutes recorded.
Most specific rule wins. Different sites, teams or individuals can have different shifts. The rule closest to the person should apply.
Local time zones. Each location should be judged in its own time zone.
Missed clock-outs. People forget. A good system closes an open session automatically after a set time and marks it so a person can correct it.

5. Fraud and tampering: signals, not walls

Where there is money, some people will try to cheat. Typical methods are fake-location apps, signing in for a colleague, sharing one phone between several people, or changing the phone's clock. Good systems look for signals such as:

a device that isn't registered to that person, or one device used by several people;
impossible travel (two clock-ins too far apart in too little time);
a network or time zone that doesn't match the location;
readings that look artificial, such as perfectly round accuracy values or identical coordinates every day;
signs of automation rather than a human tap.

Two design choices make this stronger. First, tie each clock-in to the person's own device using a passkey, so the request is cryptographically signed and can't simply be replayed by someone else. Second, don't tell staff which checks fired. Showing only the issues they can act on, such as "move outside and retry", avoids teaching people how to defeat the checks.

Importantly, these signals should raise a flag and a risk score, not block the clock-in. High-risk cases can alert a supervisor immediately, so the response is human and quick.

6. Fairness: record everything, review exceptions

The most important principle in attendance design is this: a person should always be able to clock in, and anything unusual should be recorded and reviewed by a human, never silently rejected.

Why? Because systems make mistakes, and the cost of a silent rejection falls on an honest employee who then has no record at all. A fair workflow looks like this:

The clock-in is always saved, with the evidence that came with it.
Unusual cases land in a review queue with a clear reason, such as "out of range: 420 m" or "late: 12 minutes".
A supervisor views the case, on a map, and approves, declines or adds a note. They can't review their own record.
If a record needs correcting, the correction is a separate entry, proposed by one person and approved by a second. The original is never edited.
Every action is written to an audit log, ideally one where changes to history can be detected.

The only things that should be refused outright are technical impossibilities: a forged or expired signature, a second clock-in while one is already open, or malformed data.

7. Privacy and staff trust

Location is personal data, and staff will accept location-based attendance only if they trust how it is used. Good practice includes:

Collect location only at clock-in and clock-out, with no background tracking between them.
Tell staff clearly what is collected, why, who can see it and for how long, before they start.
Limit who can see precise positions, and record every view. Letting staff see who has looked at their own data builds trust.
Protect the data: encrypt precise coordinates and restrict access by role.
Reduce data over time. After a retention period, exact positions can be rounded to an approximate area, keeping what attendance needs and dropping the rest.
Give staff their rights: a way to see and download their data, and a named person to contact.

In Nigeria, the Nigeria Data Protection Act 2023 applies to this kind of personal data, so employers should have a clear lawful basis, keep collection proportionate to the purpose, and take advice on their own obligations. This article is general information and not legal advice.

8. What to look for in an attendance system

Whether you buy or build, use this checklist:

Does it use the accuracy of each reading, and show it to staff?
Is time recorded by the server, per location, with sensible shift and grace rules?
Are clock-ins tied to the person's device (for example passkeys) rather than just a password?
Are unusual events flagged and reviewed, not silently rejected?
Are records append-only, with two-person approval for corrections?
Is there a tamper-evident audit trail for admin actions?
Is location collected only at clock time, protected, and reduced over time?
Can staff see and export their own data?
Can supervisors see a live board and export reports for payroll?
Can each customer's data be kept separate from others?

9. How our Staff Attendance Portal approaches it

We built the Staff Attendance Portal around exactly these ideas. Staff clock in from a phone with a passkey. The server decides on location and time. Anything unusual is saved and flagged for a supervisor, never dropped. Corrections need a second approver. Precise coordinates are encrypted, location is read only at clock time, and staff can see who viewed it. Each customer runs on its own isolated deployment.

One note on connectivity: in our portal a clock-in needs a connection to the server, by design, so that the time and location decision is made by the server and not left to the phone.

If you'd like to see it with your own sites and shifts, we're happy to walk you through it.

Explore the portal Request a walkthrough

Frequently asked questions

Does geofenced attendance track staff all day?

It shouldn't. A well-designed system reads location only at the moment of clock-in and clock-out. Always ask any vendor whether there is background tracking.

How accurate is phone GPS for clocking in?

Usually within a few metres to a few tens of metres outdoors, and less accurate indoors or in dense areas. That is why a good system uses the phone's accuracy estimate and flags unclear cases for review instead of rejecting them.

Can staff clock in from home or on the road?

That depends on how the employer sets it up. Staff are assigned to specific locations, so remote or field work needs its own location or rule. Clock-ins outside any assigned area are recorded and flagged for review.

What stops someone using a fake-location app?

No single check is perfect, so good systems combine several: device-signed requests, unusual-reading checks, travel and network consistency, and human review of anything suspicious. These raise flags and risk scores so a person can look at the case.

What happens if a phone has no signal?

That depends on the system. In ours, a clock-in needs a connection to the server so the server can decide on time and location. Staff are shown a clear message and can try again when connected.

Is it legal to use location for attendance in Nigeria?

Employers can use it, but it is personal data, so the Nigeria Data Protection Act 2023 applies. Be transparent with staff, collect only what you need, protect it, and keep it for a limited time. Take advice from a qualified adviser for your own situation.

This article is general information, not legal advice. Features described for the Staff Attendance Portal reflect its design at the date of publication.