Details last reviewed on 5 October 2026. Rules and products change often. This is general information, not legal advice, so confirm specifics with your own counsel.
Once a business has more than one site, attendance stops being a register on a desk. Staff mark it from a phone at a warehouse gate, a shop, a client site or a delivery route, and HR is left asking two questions: was this person where they say they were, and what do we do when the system is wrong?
This guide covers attendance geo-fencing: what a geo-fence is, how to choose boundaries for different sites, how to treat field and remote staff, the real limits of location, and a clean correction (regularisation) workflow. It then covers employee data privacy, because location and attendance are personal data. Stalled approvals are a wider problem, covered in stop chasing approvals.
What a geo-fence is, and what it is not
A geo-fence is a boundary drawn around a site. A check-in made from inside the boundary counts; a check-in from outside does not. That is the whole idea, and it is useful because it replaces a judgement call ("he says he is at the depot") with a rule that applies the same way to everyone.
What a geo-fence is not: proof of a person. It tells you where a phone was when the check-in was made. Treat it as one signal, and design the rest of the process around the cases where that signal is wrong.
Choosing boundaries for different sites
One radius for every site is the most common mistake. A single-building office, a campus with several gates and a yard with trucks entering and leaving need different shapes and sizes.
| Site type | What to consider | Boundary approach |
|---|---|---|
| Single office or shop | Phones may drift a little indoors | A modest radius that covers the whole building with some margin |
| Large campus or plant | Staff arrive at far gates or parking | A larger area, or several fences for the same site |
| Warehouse or yard | Vehicles come and go; signal is patchy | Cover the gate and loading area, review misses regularly |
Start from the places people actually stand when they check in, not from the building outline. Walk the site with a phone, set the boundary from where check-ins land, and review it after a few weeks using the genuine misses.
Field staff, remote work and shifts
Field staff
For GPS attendance for field staff, a fixed fence often makes no sense: the job is to be elsewhere. Common options are a fence around each assigned client site for the day, a larger area for a territory, or no fence with a recorded reason and manager approval. Pick one rule per role and write it down.
Remote and hybrid work
Do not draw a fence around a home address unless the person has clearly agreed, and ask whether you need the location at all. For remote days, a plain "working remotely" mark approved by the manager records the day without collecting more personal data than needed.
Shifts and late marks
A check-in only means something against a shift. Define start time, a grace period if you use one, and what counts as a late mark, in the shift itself, so the rule is the same on every site. Night shifts that cross midnight should attach to the day they started. Ask your counsel what applies to you.
The honest limits of location
Phone location is not exact. Accuracy varies indoors, inside basements or metal sheds, between tall buildings and in dense areas, and different phones and settings behave differently. A person can be at their desk and register as outside the fence, or the reverse.
So do not rely on a single signal. Combine location with the shift, the reporting line and a manager who knows the team, and keep a way for people to correct genuine misses. A geo-fence reduces casual mismarking; it is not a guarantee, and no location setup should be described as impossible to spoof.
A clean attendance correction workflow
Misses will happen, so the attendance correction workflow decides whether HR trusts the data. Attendance regularisation done in chat threads, spreadsheets and phone calls leaves nobody able to say who approved what. A clean workflow has five parts.
- Reason. The request says what happened and for which date, in the employee's words, chosen from a short list plus free text.
- Approver. The reporting manager decides, because they know the team's day.
- Deadline. Set a window for the employee to raise a request and for the approver to answer. Pick the numbers yourself.
- Escalation. If the approver does not answer, the request moves to the manager's manager rather than waiting.
- One record. Reason, approver, decision and time stay on the attendance record, so there is one place to look.
The same pattern suits any approval, as the move from spreadsheets to one platform shows.
Employee data privacy for attendance and location
Attendance and location records are personal data about identifiable people, and a location trail says a lot about someone's day. Handle them accordingly.
- Mask by default. Employee records should show personal details masked, not in the clear for anyone with access to the screen.
- Restrict who can reveal. Only people with a defined need and permission should be able to unmask.
- Log every reveal. Record who revealed what and when, so a reveal can be reviewed later.
- Collect only what the purpose needs. A location at check-in is not tracking through the day.
- Tell people. Say what you collect, why, who can see it and how long you keep it.
India's Digital Personal Data Protection Rules were notified on 13 November 2025, and the main obligations are reported to take effect around mid-May 2027. Those dates come from secondary reports, so confirm with counsel.
That is not in force today, but giving notice and recording consent to that standard now avoids a rebuild later. Ask your counsel what records you must keep, and for how long, because we do not state record-keeping requirements here.
Checklist before you roll out
- One boundary per site, set from where people actually check in
- A written rule for field staff and for remote days
- Shift start, grace period and late-mark rule defined per shift
- Location treated as one signal, not the only one
- Correction request with reason, approver, deadline and escalation
- One attendance record holding the request and the decision
- Personal data masked, reveal limited by permission and logged
- Notice given to employees about what is collected and why
Common mistakes
- One radius for every site. Sizes and shapes should follow the site.
- Treating GPS as proof. It is a signal that can be wrong in both directions.
- No way to correct. Genuine misses then become disputes or quiet manual edits.
- Corrections without an owner. Requests sit in an inbox because no escalation exists.
- Showing everything to everyone. Open employee records are a privacy risk.
What OpsGrids has today
This article is a guide to designing attendance well. OpsGrids HRMS today has employee records with lifecycle transitions and reporting lines. Personal data (PII) is encrypted, with an audited unmask, so a reveal is logged. It has check-in and check-out, shifts, and geo-fences.
It also has attendance regularisation with an approval chain, and this is the one join live end to end in the product today: a correction request routes up the employee's reporting line, escalates to the manager's manager if unanswered, and applies to the record on approval. No other approval chain is live yet.
HRMS has no leave ledger and no payroll today, so leave balances and salary calculation need to be handled elsewhere. See the HRMS section of the products page and how privacy works across the platform.
FAQ
What is attendance geo-fencing? A boundary drawn around a work site so that a check-in counts only when it is made from inside it. It is one signal about where a phone was, not proof of a person.
How accurate is GPS attendance for field staff? It varies. Indoors, in dense areas and on different phones, accuracy can drift, so do not rely on a single signal and keep a correction route for genuine misses.
Who should approve an attendance correction? The reporting manager, with escalation to their manager if they do not answer within the deadline you set. Keep reason, approver and decision on one record.
Is location data covered by data protection rules? Location and attendance data are personal data. India's DPDP Rules were notified in November 2025, with main obligations reported for around mid-May 2027 and not in force today. Confirm timing and duties with your counsel.
Talk to us about attendance
If you want geo-fenced check-ins and a correction route that escalates properly, Talk to our team.
Sources (checked 5 October 2026)
- Digital Personal Data Protection Rules, 2025: dates are from secondary reports; confirm on meity.gov.in before relying on them