Staff Tracker
A reliable GPS attendance review separates three things: what the phone reported, what happened at the workplace, and what a supervisor has confirmed. Keep those separate until an exception is explained. A map point can help locate a team; it cannot, by itself, approve working time or explain why somebody was somewhere.
A green dot feels reassuring. Unfortunately, it has never met your shift supervisor, read a timesheet policy or learned which gate the cleaners actually use. This guide gives a field team a practical way to move from location information to a documented decision, without making the map responsible for things it cannot know.
Start with the decision, not the dashboard
Write down the question you need to answer. “Has someone reached the north office?” is different from “How many hours should be approved?” The first concerns an operational observation; the second requires an agreed attendance process, breaks, corrections and an accountable reviewer. Combining them into one label hides uncertainty precisely when a team needs clarity.
For a first rollout, choose one narrow outcome: identify arrivals that need checking before the next handover. Define the workplaces included, the person who reviews exceptions and the ordinary alternative when a device cannot report. Tell staff how the information will be used. A location system is easier to operate when everyone understands the question it supports.
Use three distinct records
The raw observation is the location and timestamp reported by the device. A workplace interpretation describes whether that observation appears inside a configured boundary or forms part of a visit. The reviewed record adds the supervisor's conclusion, supporting explanation and any correction. Keep a link between these records so a later reviewer can understand the reasoning.
Do not silently replace the original timestamp with a corrected arrival. Record the correction separately, with its reason. That makes the history useful when the same issue appears again. It also avoids a familiar administrative magic trick: yesterday's ambiguous record becomes today's apparently perfect evidence, and nobody remembers how.
| Observation | What it can support | What still needs checking |
|---|---|---|
| Fresh point inside a workplace | The device reported that location | Identity, task and attendance context |
| Old point outside the boundary | The last available report was outside | Connectivity and subsequent movement |
| Several points during a visit | A location pattern over time | Breaks, duties and approval rules |
| No arrival event | An expected event is missing | Entrance, boundary, device and reporting gaps |
Design an exception queue people can finish
An exception queue should contain unresolved questions, not every movement made during a shift. Useful categories include missing arrival, stale location, overlapping visits, wrong device assignment and departure not observed. Give each exception a workplace, relevant time window, owner and next review time. Keep sensitive supporting details in the appropriate restricted record.
Use plain statuses such as “needs explanation”, “configuration issue”, “reviewed with correction” and “reviewed without correction”. Avoid marking uncertainty as absence automatically. The first review should establish whether the problem concerns the phone, the workplace definition or the attendance information. Different causes need different fixes, even when the dashboard symptom looks identical.
- Check whether the timestamp is fresh enough for the intended decision.
- Confirm the device belongs to the expected person or shared-device assignment.
- Compare the actual entrance with the workplace boundary.
- Ask for relevant context through the established team process.
- Record the explanation, reviewer and outcome without unnecessary movement history.
Investigate the phone before changing the boundary
A phone that reports correctly while open but stops updating in a pocket suggests a different investigation from a phone that reports fresh points just outside the workplace. For background issues, review the current device setup instructions, permissions, connectivity and power settings. Repeat an ordinary locked-screen journey. Do not assume a successful demonstration at a desk proves a full shift will report reliably.
For boundary issues, walk the normal approach and identify where a legitimate arrival should count. An office tower may have a staff entrance behind the street address. A large depot may share an access road with neighbouring businesses. Making the boundary enormous can hide one missing-arrival problem while creating false visits from passing traffic.
Build a fair review worksheet
A small worksheet can be more useful than a large export. Include a case reference, workplace, expected shift window, observed event, freshness, explanation, decision and reviewer. The reference should let an authorised person find evidence without copying personal location data into multiple spreadsheets. Agree which fields are mandatory and which apply only to unusual cases.
Write observations neutrally. “No new report after 18:12” is stronger than “left early”, because the first states what is known. Ask the person for context before drawing a consequential conclusion. A dead battery, reassigned phone, unusual entrance or work away from the usual site can change the interpretation. The worksheet should make reasonable review easy, not reward confident guessing.
Worked example: two offices, one missing arrival
Consider a fictional evening cleaning team covering North Office and Riverside Office. The supervisor expects four arrivals at each building. Seven devices show recent reports inside the relevant boundaries. The eighth reports at 18:04 beside the rear service entrance to Riverside, then continues reporting in approximately the same area. The exception is a missing boundary entry, not an established missed shift.
The supervisor checks the assignment and asks the cleaner which entrance was used. The cleaner used the normal staff door, which sits outside the original boundary. A workplace contact confirms the handover. The supervisor records that explanation and follows the team's attendance correction process. Separately, the configuration owner adjusts the boundary and repeats an arrival and pass-by test.
Those are two outcomes: an attendance review for this shift and a configuration improvement for future shifts. Closing only the individual exception would leave the team investigating the same door tomorrow. Changing only the boundary would leave today's record unexplained. The combined review fixes the immediate question and its recurring cause.
Decide who owns each kind of problem
Supervisors should not need to become phone specialists to finish a handover. Give device setup to a named support owner, workplace changes to a configuration owner and attendance decisions to the appropriate manager. One person may fill several roles in a small team, but the responsibilities should still be distinguishable.
Agree how unresolved cases move between shifts. A useful handover says what is known, what has been checked, who is waiting for an answer and when to review again. “GPS broken” transfers frustration. “Phone reports in foreground; background test booked with support tomorrow; attendance reviewed separately” transfers usable information.
Review access and staff expectations
Location information deserves a clear operating policy. Explain when tracking is expected, who can see it, the purpose of the records and how a person can raise a correction. Check your organisation's applicable privacy and employment requirements before deployment. This operational checklist does not determine your legal basis or replace local advice about monitoring.
Keep access aligned with responsibility. Someone arranging a current site handover may need a different view from someone resolving a historical attendance dispute. Avoid distributing detailed location exports to broad groups merely because export is convenient. Review access when responsibilities change, and apply an agreed retention policy instead of keeping everything indefinitely.
Measure the review process rather than collecting more dots
Track a few useful measures: unresolved exceptions at handover, time to resolve them, repeated configuration problems and routine arrival calls. Compare similar shifts and note unusual workload or connectivity conditions. A falling exception count is encouraging only if cases are being resolved properly, rather than hidden by a larger boundary or an automatic approval rule.
Sample a few closed cases each week. Can another reviewer understand the evidence and decision? Did a repeated device problem reach support? Were staff corrections considered? This small quality check keeps the process honest and gives you better training material than a dashboard screenshot showing an attractive row of green symbols.
Run a one-week improvement cycle
On the first day, define categories and review ownership. During the next few ordinary shifts, record exceptions without changing several settings at once. Midweek, identify the most common repeatable cause and test one targeted improvement. At the end of the week, compare the review workload and inspect a sample of resolved cases.
Keep the successful instruction short enough to reuse. A photograph of the correct entrance, a device setup check or a clearly named escalation contact may be the most valuable result. Expand only after the team understands both the normal process and the fallback. For the earlier setup stage, use the staff tracking pilot guide.
Frequently asked questions
Does a GPS visit prove someone worked for that entire period?
No. It describes location evidence, subject to device and configuration limitations. Duties, breaks, identity and approval rules need their own context. Use visits to support an attendance review, not as a substitute for every part of that review.
Should we enlarge every boundary that misses an arrival?
No. First check freshness, device assignment and the actual entrance. Change a boundary when the workplace definition needs correcting, then test a genuine arrival and a nearby pass-by. A larger boundary can introduce a different error.
What is the minimum useful exception record?
Record the workplace, relevant time, observed issue, owner, checks made and outcome. Add enough evidence for an authorised reviewer to understand the decision, while avoiding unnecessary duplication of personal location data.
Where does Staff Tracker fit?
Staff Tracker helps teams view staff locations, workplace arrivals and time on site. Use those observations within the review process described here. The worksheet is an operating practice you can adopt; it is not a promise of automatic payroll approval or a particular integration.