Staff TrackerGPS attendance exceptions: review missing and unusual records
A missing arrival or unexpected departure needs context. This guide shows supervisors how to investigate attendance exceptions, preserve the original evidence and record a fair operational resolution.
Treat an exception as an unanswered question
An attendance exception is a record that does not fit the expected sequence. Examples include an arrival with no departure, several brief visits during one shift, or no recorded entry for someone who says they attended. The exception tells you that the available information needs review. It does not, by itself, establish why the sequence differs from the plan.
Start by describing what is actually visible. “There is an arrival at 08:52 and no later departure” is an observation. “The worker forgot to finish their shift” is an interpretation that may be wrong. Keeping those two things separate makes the review easier for everyone involved and reduces unnecessary conflict.
Staff Tracker's location and geofence records provide useful operational evidence, but phones and networks can produce incomplete observations. The purpose of the review process is to resolve the practical question with appropriate supporting information, not to force every event into a perfectly complete timeline.
Create a consistent exception category list
Use a small set of categories that supervisors can apply reliably. Too many categories make the process cumbersome, while one generic “error” label hides recurring causes. Begin with missing arrival, missing departure, unexpected site, repeated transitions, stale location and disputed timing. Add a category only when it changes the investigation or resolution.
Keep the category separate from the cause. A missing departure might result from a depleted battery, a reporting restriction or an actual overnight presence. You can classify the observation immediately and record the cause later if it becomes clear. This avoids filling a cause field with a guess simply to make the record look complete.
Agree what needs review and what can remain as ordinary variation. If the organisation does not require second-level precision, avoid escalating every small timing difference. The threshold should reflect the business purpose and the relevant policy, with a human judgement route for cases that do not fit a simple rule.
Gather the minimum useful evidence
Begin with the site's expected working arrangement and the relevant time window. Then check the latest location timestamp, the sequence of entries and exits and any known device issue. Limit the investigation to the information needed to answer the question. A single disputed visit does not automatically justify examining unrelated movements.
Ask the worker for an explanation in neutral language. “The record shows an arrival but no departure; can you help confirm what happened?” invites useful context. A message that assumes misconduct before checking the technology can undermine trust and make future reporting less candid.
- State the date, site and specific missing or unusual event.
- Preserve the original timestamp and observation.
- Check whether the device continued to report afterward.
- Ask for relevant context from the worker or site supervisor.
- Record the resolution and any uncertainty that remains.
Where supporting records exist, check that they refer to the same person, site and time period. A general job completion note may help establish attendance, but it may not establish an exact arrival minute. Match the strength of the conclusion to the strength of the evidence.
Review a missing arrival
If a person has a recorded departure but no arrival, look at the observations preceding the departure. The device may have started reporting while already inside the workplace. In that case, the system may not have received the outside-to-inside transition needed to infer an entry in the usual way.
Check whether the client was enabled before the journey and whether the first location has a plausible timestamp. Also review the site boundary: an entrance outside the configured area can cause a valid visit to be represented poorly. A repeated pattern affecting several people at the same site is a useful clue that the boundary deserves attention.
For the current exception, record the best supported operational resolution. For prevention, test the device or boundary separately. Do not use an unverified configuration change as retrospective proof of an exact time that was never observed.
Review a missing departure
An open visit can remain when reporting stops before the person leaves. First check whether newer locations exist anywhere else. If a later point places the phone away from the site, the problem is different from a device that has not reported at all since the afternoon.
Ask whether the phone lost power, connectivity or permission during the relevant period. If the person confirms a departure time, document that it is a reported time rather than an automatically observed event. Preserve the distinction in any summary used by another department so the origin of the figure is not lost.
Do not calculate an implausibly long visit and pass it onward without review. An overnight duration may be genuine for some shifts, but it can also be the consequence of an incomplete record. Compare the observation with the scheduled arrangement and resolve the exception before treating the duration as final.
Review repeated entries and exits
Several short transitions can reflect actual movement across a boundary. A worker might visit a vehicle, cross to a nearby building or take a break outside the site. The same pattern can also appear when location observations vary around the edge of a tight geofence. The event list alone does not distinguish these explanations.
Look at where the reported points sit relative to the boundary and ask whether the movement makes operational sense. If the pattern repeats while the phone is stationary, run a controlled test at that location. Document the test conditions so a future reviewer knows why the boundary was changed.
Avoid automatically merging every short gap into a single visit without a defined rule. Such a rule may be useful in some processes, but it changes the interpretation of the evidence. Make the rule explicit and keep a route for reviewing unusual cases that would otherwise be misrepresented.
Review a disagreement about minutes
Small timing disputes often arise because one person means physical arrival at a doorway while the system records the first received inside location. Clarify which event each timestamp describes. A location-based observation and a manual clock reading can both be accurate descriptions of different moments.
Explain the reporting model before discussing the individual case. Location updates are observations delivered through a phone and network, not an uninterrupted measurement of a person's movement. This helps avoid a debate in which either the worker or the software must be declared categorically wrong.
If the difference affects pay, a contractual deadline or another consequential decision, use the organisation's established review policy and appropriate advice. An operational guide cannot supply a universal legal tolerance or payroll rule. Do not invent one because the interface displays a precise-looking time.
Example: three workers, one site boundary
A supervisor notices missing arrivals for three people at the same warehouse. Each device reports normally before and after the visit. The initial reaction is to ask all three workers to reinstall the client, but the shared location suggests another possibility.
The supervisor walks the route and finds that the staff entrance moved during building works. The old geofence covers the previous entrance and part of the building, while the new route reaches an area outside it. The team updates the boundary and tests a normal visit before changing any phone settings.
The outstanding records are reviewed with site context, and the configuration issue is documented separately. The lesson is to look for the common factor. When several otherwise healthy devices fail at one workplace, a site-level explanation may be more useful than repeatedly treating each phone as an isolated problem.
Keep a correction trail that someone else can understand
A good exception note is concise but complete. It identifies the original observation, the relevant explanation, who reviewed it and the operational outcome. If the product does not provide the exact note fields you need, use an approved internal process without claiming that the application has features it does not expose.
Avoid ambiguous notes such as “fixed” or “all good” in the underlying evidence record. Those phrases do not tell a later reviewer what changed or why. A better note might say that an open visit was reviewed with the site supervisor and that the departure time is based on a confirmed handover, while the original automatic record remains incomplete.
Apply access and retention arrangements appropriate to the information. Attendance notes can contain personal details, so keep them focused on the relevant issue. There is rarely a need to reproduce an entire private conversation to document a straightforward technical exception.
Turn repeated exceptions into improvements
Review patterns at a sensible interval. Count recurring issues by site, device and category, then choose the most useful corrective action. One device repeatedly going stale suggests a different investigation from every device producing extra transitions near one entrance.
Measure whether the change reduces the actual exception, not whether a setting has been altered. After adjusting a boundary, run a comparable route. After resolving a phone restriction, test background reporting. Close the technical issue only when the intended behaviour has been observed.
Share simple lessons with the team. A short reminder about replacement-phone handover or a corrected site entrance can prevent repeated problems. Keep the message factual and avoid publicly identifying a worker when the useful lesson concerns the process rather than the individual.
Frequently asked questions
Does a missing GPS arrival mean someone was absent?
No. It means the expected arrival observation is missing. Check reporting, the site boundary and relevant supporting information before deciding what the attendance record means.
Should supervisors overwrite uncertain timestamps?
They should follow the organisation's correction process and preserve the distinction between automatic observations and reviewed information. Do not replace uncertainty with an invented precise time or remove the reason for the correction.
What is the best first check for an open visit?
Look for the latest device timestamp and any later locations. That helps distinguish a missed transition from a device that stopped reporting entirely. Then compare the result with the actual working arrangement.
How can we reduce the review workload?
Group recurring exceptions by cause and fix the underlying setup. Clear workplace boundaries, representative device tests and a consistent handover process usually make investigations more efficient than repeatedly asking everyone the same questions.