Staff TrackerMulti-site attendance: organise visits without losing context
Manage attendance across several workplaces with consistent site definitions, clear assignments and a review process for overlapping visits, transfers and incomplete records.
Choose the unit you need to understand
Multi-site attendance becomes confusing when a single total tries to answer several different questions. A manager may need to know whether each workplace received a visit, how long a person was observed at a site, or which team was available in an area. These questions require related but distinct views of the working day.
Start by defining the unit of analysis. A visit is a period associated with a particular workplace. A shift is a working arrangement that may include several visits and travel. A completed task is an outcome that may occur within a visit. Avoid treating those units as interchangeable when preparing reports or discussing exceptions.
Staff Tracker's latest locations and geofence events can support the workplace view. Use the team's assignment and task records to supply the additional context. A well-organised process can connect the pieces without pretending that one data source proves everything about the day.
Create a consistent workplace register
Use one naming convention across the organisation. Include enough detail to distinguish sites with similar names, while keeping labels short enough to recognise on a map. A regional office, depot and client building should not all appear as “Main site.”
For each workplace, record the operational meaning of the boundary, the usual entrance and the person responsible for changes. A site register can also note known limitations, such as a shared car park or two client contracts inside the same building. Keep confidential access instructions in the appropriate controlled system rather than a general label.
Review the register when a new site opens or an old one closes. Stale names and unused boundaries make the map harder to interpret. The person maintaining the workplace list should know when contracts, entrances or access arrangements change, rather than learning about them only after attendance exceptions accumulate.
Avoid ambiguous overlapping boundaries
Two nearby workplaces may be difficult to separate using a broad location boundary. If the geofences overlap, a phone can be associated with more than one place during the same period. That may be geographically understandable but operationally unhelpful when the report assumes each minute belongs to exactly one site.
Test the boundaries along the actual route between sites. Include the shared road, parking area or entrance where ambiguity is most likely. Do not solve the problem by drawing an unrealistically tight shape that performs poorly with ordinary phone observations.
Where location cannot reliably distinguish the work, acknowledge the limitation and use assignment or task information. For example, two clients on different floors may need separate service records even though the phone is inside one building-level geofence. An honest combined process is better than a precise-looking allocation with no reliable basis.
Connect visits to the working plan
A location sequence is easier to interpret when the expected assignments are clear. Before the shift, make sure coordinators know who is expected at each site and whether anyone is covering multiple workplaces. Changes should reach the person reviewing attendance, not remain in a separate private conversation.
Use the existing scheduling process as the source of the working plan. Do not assume the tracking application provides a particular rota or assignment feature unless it is available and configured. The important requirement is that the plan and the observations can be compared by an authorised reviewer.
When a worker changes sites unexpectedly, record the reason at the appropriate level. A simple operational note about covering an urgent request may explain the sequence. There is no need to turn every minor route change into a detailed personal narrative.
Review a day as a sequence of visits
Read the timeline in order: the latest observation before the first site, the arrival, the departure and the next workplace. Check timestamps and gaps before adding durations. An incomplete departure can make later totals misleading if the process assumes continuous presence.
Look for plausible transitions rather than forcing every point into a perfect itinerary. A short gap may reflect travel, a missed observation or an off-site task. If the distinction matters, use supporting information and record the outcome. If it does not affect the operational question, avoid collecting extra detail merely to fill every blank.
- Confirm the intended workplace for each visit.
- Check the age and order of the location observations.
- Identify open visits before calculating summaries.
- Compare unexpected transitions with assignment changes.
- Preserve uncertainty where the evidence does not support an exact answer.
This approach makes review more efficient because it focuses on the points where interpretation can change. Routine, consistent visits need less attention than incomplete or contradictory sequences.
Keep travel and site time separate
Time between workplace observations is not automatically travel time. A person may have taken a break, collected equipment or completed an approved off-site duty. Conversely, some work journeys may begin before the first geofence arrival or continue after the last departure.
If travel matters to the report, define what evidence and policy establish it. A tracking sequence can provide context, but it cannot determine the organisation's contractual or payroll treatment. Consequential decisions should follow the relevant internal process and appropriate advice.
Use labels that describe the data honestly. “Observed time on site” is different from “total working hours.” A summary becomes easier to trust when its scope is explicit and when reviewed adjustments are distinguished from automatic observations.
Example: one technician, three workplaces
A technician begins at a depot, visits an office and finishes at a client warehouse. The depot record has a clear departure, the office visit is complete, but the warehouse departure is missing because the phone stops reporting late in the day. A naive total would leave the warehouse visit open indefinitely.
The coordinator reviews the open visit, checks the subsequent information and confirms the operational end of the visit through the usual process. The summary records the warehouse departure as reviewed information while preserving the original incomplete sequence. The device issue is assigned for a separate test before the next shift.
The resulting report can explain the three visits without claiming that every interval is automatically verified. It also identifies the technical problem that needs prevention. This is an illustrative example of reviewing a sequence, not a promise about a specific reporting feature.
Design summaries for the audience
A regional manager may need a list of sites visited and unresolved exceptions. A local supervisor may need the current team picture. A client may need a concise service summary for their own premises. These audiences do not necessarily need the same level of individual movement detail.
Start with the question the summary must answer and include only the relevant information. Keep a route back to the underlying evidence for authorised reviewers, but do not automatically distribute a full location history with every report. More detail is not always more useful or more appropriate.
Check that totals do not double-count overlapping visits. If one observation can be associated with two site definitions, explain the reporting rule before presenting a combined number. A misleading total can survive long after the original ambiguity is forgotten.
Make site changes part of operational change control
A moved entrance, temporary compound or new client area can change the meaning of a boundary. Include attendance configuration in the site-change checklist. The person managing access should know who maintains the workplace definition and how to request an update.
After a change, run a representative arrival-and-departure test. Check nearby pass-by routes as well as legitimate visits. Keep a short record of the reason for the change and the test result so later reviewers understand why records may behave differently across the change date.
Avoid changing boundaries repeatedly in response to individual events without examining the pattern. A single uncertain observation may be a device issue. A consistent issue across several devices is stronger evidence that the site definition needs attention.
Use exceptions to prioritise improvement
Group unresolved records by site and type. A site that produces many missing arrivals may need a boundary review. A device that produces gaps everywhere may need a configuration check. Distinguishing these patterns prevents the team from applying the same remedy to unrelated problems.
Review whether the process reduces coordination effort. Useful measures include unresolved visits at handover, repeated requests for attendance clarification and time spent correcting the same recurring fault. Keep workload changes in mind when comparing one period with another.
The goal is a manageable operational picture across workplaces. A successful rollout should help supervisors act with less confusion, not create a requirement to inspect every location point. Refine the workflow around decisions and exceptions rather than data volume.
Multi-site rollout checklist
- Each workplace has a clear, recognisable name and owner.
- Boundaries reflect the intended meaning of a visit.
- Shared entrances and overlapping areas have been tested.
- Coordinators can compare observations with current assignments.
- Open visits are reviewed before totals are finalised.
- Summaries identify their scope and any reviewed adjustments.
- Site changes trigger a configuration review and a practical test.
Frequently asked questions
Can one person attend several sites in the same shift?
Yes, the operational process can treat the day as a sequence of visits. Keep visit records distinct from the overall shift and use assignment information to explain the intended work at each place.
What if two workplaces are in the same building?
A location boundary may not distinguish them reliably. Use building-level presence as supporting information and separate task or assignment records for the client-specific work.
Can we add every site duration to calculate working hours?
Not without understanding incomplete records, overlaps, travel and the applicable working arrangement. Observed time on site is a specific measure, not automatically a complete payroll or working-time total.
Who should maintain workplace boundaries?
Assign an operational owner who receives information about entrance, contract and site changes. That person should coordinate practical tests and document why a boundary was changed.