Staff TrackerCleaning team attendance across multiple client sites
Build a reliable attendance process for cleaning teams working across offices, shared buildings and changing shifts. Combine site arrivals with clear handovers and a simple exception review.
Define the service visit before measuring it
A cleaning visit can mean different things across a contract. One team may work a fixed evening shift in a single office. Another may complete several short visits across shared buildings. Before choosing an attendance process, describe the service unit you are trying to verify: a scheduled shift, a visit to a named site or completion of a defined cleaning task.
Location-based attendance can help establish that a phone was observed at a workplace. It does not prove which rooms were cleaned or whether the work met the agreed standard. Keep attendance and service quality connected but distinct. A useful client report might combine a reviewed visit record with a separate completion checklist or supervisor inspection.
This distinction prevents a common reporting mistake: using time on site as the only measure of service. A long visit can include access delays, missing supplies or an unexpected spill. A shorter visit can still meet a well-defined scope. Investigate the actual service outcome rather than assuming duration tells the whole story.
Organise the site list around daily operations
Create names that staff and supervisors recognise. Large clients may have several buildings, floors and entrances, so “Main Office” alone may be ambiguous. Include a practical location identifier in the site documentation and make sure the attendance boundary corresponds to the place the team actually enters.
For buildings with shared car parks or shopping areas, test whether ordinary pass-by journeys appear as visits. A cleaner may travel near the site on the way to another contract. A broad boundary can make that journey look like attendance if it includes the surrounding road or neighbouring premises.
Keep access instructions separate from the map label. Door codes, key arrangements and private contact information need appropriate handling. The attendance view should identify the workplace, while the shift briefing provides the controlled details needed to enter it safely and carry out the job.
Prepare staff phones for the real shift
Staff Tracker connects phones through Traccar Client, so include device readiness in onboarding. Check that each phone reports under the intended staff assignment and that a fresh observation reaches the workspace. Then repeat the test with the screen locked, because cleaning staff will usually keep their phones away while working.
Test the actual environment. Basement storage areas, internal corridors and large commercial buildings may behave differently from the outdoor setup location. Do not assume that a successful test by a window establishes reliable observations throughout the building. Focus on whether the overall arrival and departure process works well enough for the operational purpose.
Explain what staff should do if the device is unavailable, out of charge or not reporting. A fallback attendance message to the designated supervisor may be appropriate under your process. The important point is that staff know the route before a problem occurs, rather than trying to invent a workaround during a busy shift.
Use a short pre-shift check
A supervisor does not need to inspect every location point before every shift. A brief readiness check can identify the exceptions that deserve attention: a new starter whose setup is incomplete, a replacement phone, a changed entrance or a site with a known reporting problem.
- Confirm the expected team and sites for the shift.
- Check unresolved device issues from the previous handover.
- Tell staff about any changed access route or workplace boundary.
- Identify the person responsible for attendance exceptions that evening.
- Make the fallback contact route easy to find.
Keep this check proportionate. Requiring every worker to send multiple screenshots can create more administrative work than the system removes. Concentrate on changes and unresolved issues, then let ordinary arrivals populate the shared view.
Review arrivals without interrupting everyone
At the start of the service window, look for expected arrivals and check the age of the latest observations. If someone is missing from the expected site, consider the assignment and known conditions before calling. They may be collecting supplies, covering a different entrance or waiting for access.
Use neutral language when asking about an exception. “We do not yet have a recent arrival for the west building; is access working?” is more productive than assuming lateness or absence. The question may uncover a locked entrance that affects the whole team, which is an operational issue rather than an individual attendance problem.
When several devices show the same site-level anomaly, investigate the shared cause. A changed access route, a misplaced boundary or a coverage problem can affect multiple colleagues. Reinstalling the client on every phone without checking the site first wastes time and may introduce new setup errors.
Handle travel between nearby contracts
A worker serving several nearby offices may leave one workplace and arrive at the next with a short gap. Make sure the site definitions do not overlap so heavily that the sequence becomes difficult to interpret. If two contracts occupy the same building, location alone may not distinguish the work performed for each client.
Use assignment information to complement the map. The visit record can support a timeline of presence, while the work schedule establishes which service was planned. Do not invent a precise allocation of time between two clients simply because the phone remained inside one broad geographic area.
Travel time also needs an explicit business policy if it is relevant to another process. The attendance view cannot decide contractual or payroll treatment by itself. Keep the technical record separate from the policy decision and refer consequential questions through the organisation's established review route.
Example: evening cleaning in a shared building
Imagine two cleaning teams working in separate offices within one commercial building. Both use the same entrance and lifts. A geofence around the building can help confirm their general arrival, but it cannot reliably prove which floor each person cleaned throughout the evening.
The supervisor uses location-based arrivals for coordination and a separate task checklist for the client-specific work. At handover, one team reports that an office was inaccessible because a meeting ran late. The attendance record shows presence, while the checklist explains the incomplete task and the agreed follow-up.
The resulting report is more useful than a claim that a location pin proves every service obligation was met. It tells the client what was completed, what was delayed and how the issue will be handled. This example is illustrative and does not describe a verified customer outcome.
Make end-of-shift exceptions easy to resolve
Review open visits and missing departures before the next supervisor takes over. A phone that stopped reporting should not silently turn a two-hour visit into an overnight duration. Check whether later observations exist, ask for the relevant context and record the resolution under your internal process.
Preserve the difference between automatic observations and a reviewed correction. If a departure time comes from a supervisor's confirmation, say so. That distinction helps anyone using the summary understand why the final operational record differs from the raw event sequence.
Avoid broad group messages containing individual attendance disputes. Use the designated private support or review channel. A team-wide message is better reserved for a shared instruction, such as a corrected entrance location or a reminder about replacement-device setup.
Build a useful client-facing summary
A client generally needs a clear account of service delivery, not an unrestricted location history. Decide what the contract and the reporting purpose require. A concise summary can identify the site, service date, reviewed attendance window, completion status and any unresolved access or quality issue.
Check the summary for unsupported precision. If a location-based arrival was delayed by reporting behaviour, do not present it as an exact door-entry time. If the cleaning task was confirmed through an inspection, make clear that the quality evidence comes from that inspection rather than the map.
Keep personal information limited to what is appropriate for the reporting arrangement. A named worker's full movement sequence may be unnecessary for a client who only needs to know that a contracted visit occurred. Review sharing arrangements before making detailed records routinely available outside the operational team.
Improve the process after the first month
Look at the exceptions that consumed the most supervisor time. If the same building repeatedly produces uncertain arrivals, retest the boundary and access route. If replacement phones cause identity confusion, improve the device handover. If staff do not know whom to contact, simplify the support instructions.
Ask cleaners whether the process fits the shift. They may identify practical problems that a coordinator cannot see, such as a charging arrangement that fails between back-to-back jobs or an instruction that assumes an office is open when it is usually locked. Treat this feedback as part of configuration quality.
Measure success against the operational goal: fewer unnecessary check-in calls, clearer handovers or more reliable service summaries. Do not equate collecting more location points with better management. The right process should make the service easier to coordinate while keeping the evidence understandable.
Frequently asked questions
Can GPS prove a cleaning task was completed?
No. It can support an account of presence at a place. Task completion and cleaning quality need appropriate evidence such as a checklist, inspection or agreed service record.
What if two cleaning contracts share one building?
Use location as evidence of general presence and combine it with assignment and task information. A single geofence may not distinguish floors, rooms or client-specific work accurately enough on its own.
How should we handle a phone that stops reporting mid-shift?
Use the agreed fallback process, preserve the original observations and review any missing departure with the relevant person. Investigate the device separately so the same problem does not repeat unnoticed.
What belongs in a client report?
Include the information needed to explain service delivery and exceptions under the reporting arrangement. Avoid sharing unnecessary personal movement detail or claiming greater timing precision than the evidence supports.