Time Tracking for Cleaning Companies

A time record should answer when work started and ended, which assignment it belonged to and what happened when the record was wrong.

GPS can add location context to a clock event. It cannot prove that the cleaning outcome was achieved, and continuous tracking can collect far more information than payroll or attendance needs.

The right system depends on the purpose, the sites and the employment rules that apply. Start there before comparing tracking features.

This article is operational guidance, not employment or privacy legal advice. Check the law, contracts, policies and collective arrangements relevant to your workforce.

Define the record you need

For each shift or work period, decide which facts the company needs to maintain:

Employee and assigned role
Location and service window
Scheduled start and end
Actual start and end
Breaks
Paid travel or work between locations
Applicable ordinary and premium categories
Method used to create the record
Location or device context collected at the event
Schedule changes
Manual edits and reason
Employee or manager approval
Payroll period and export status

Do not collect a field simply because the app offers it. Each field should have an operational, contractual or legal purpose.

Requirements differ by country and worker. For example, Singapore’s Ministry of Manpower says employers must maintain specified employment records, including working hours and relevant salary information for employees covered by the Employment Act. In the United States, the Department of Labor describes FLSA recordkeeping for covered non-exempt workers, including daily and weekly hours and wage records. These are jurisdiction-specific examples, not a complete compliance checklist.

Keep schedule, attendance and payroll connected but separate

The schedule says what the company planned.

The attendance record says what work event was recorded.

The approved timesheet says what the company accepted for the pay period after reviewing changes and exceptions.

Do not overwrite one with another. If a replacement works the shift, preserve the schedule change and the attendance event. If a manager corrects a missed clock-out, keep the original record, editor, time, reason and approved value.

This makes three questions answerable:

What was the approved plan at the time?
What did the worker record?
What did the company approve for payroll, and why?

The multi-site scheduling guide covers the first part.

What GPS at clock-in can verify

A location check attached to a clock event can show that the device reported a position near the assigned site when the person attempted to start or end work.

It may help identify:

Clock event outside the configured site area
Assignment linked to the wrong location
Cleaner using an unexpected access point
Event that needs manager review before approval

It does not establish:

The identity of the person holding the device unless another control supports it
Cleaning quality
Every minute spent working
Whether the worker stayed inside the area
The reason the reported position was inaccurate
Whether the site boundary was configured correctly

Treat an outside-area event as an exception to review, not automatic proof of misconduct.

Geofence, QR or NFC?

Different sites may need different verification methods.

Geofence or GPS event

The phone reports its location when the clock action occurs and the system compares it with the configured site area.

This can work where a reliable position is available and the site boundary is meaningful. Tall buildings, indoor areas, underground locations, weak signal and the chosen access point can affect results.

Site QR code

The cleaner scans a code placed at the location.

This confirms access to the code, not necessarily the person’s identity or continued presence. Protect the code from casual copying and define what happens when it is damaged or unavailable.

NFC tag

The cleaner taps a tag installed at the site.

This creates a close-range event at a known point. The company still needs a fallback for a missing, damaged or inaccessible tag.

Manager or kiosk record

A supervisor or shared site device may record attendance where personal phones or location permissions are unsuitable.

The right choice depends on the question and the site. A company can use different methods while keeping the resulting time record consistent.

Prefer event verification to continuous tracking when it meets the purpose

If the purpose is to verify that a clock-in occurred at the assigned site, a location check at that event may be enough.

Continuous tracking gathers a route over time. That is a different and more intrusive form of monitoring. It may capture travel, breaks or activity outside the intended work context, particularly when a personal phone is involved.

Before introducing it, define why event-based verification cannot meet the need, which locations will be collected, when tracking starts and stops, who can access the route and how long it is kept.

The UK Information Commissioner’s Office says worker monitoring should be lawful and fair, have a clear purpose and use the least intrusive means that achieves it. Its current worker-monitoring guidance also emphasises necessity, proportionality, transparency and data minimisation. This is UK guidance, but the questions are useful for any company designing a less intrusive process.

Tell workers what happens

Give workers a clear notice before collecting attendance or location data.

Explain:

The purpose of the time record
What data is collected
When location is checked
Whether tracking continues after the event
What happens when permission or signal is unavailable
Who can access the record
How it affects schedule, payroll or performance review
How long it is kept
How a worker can correct an error or raise a concern
What changes if the company introduces a new purpose

Do not describe event-based GPS verification as continuous tracking, or continuous tracking as a simple clock-in check. The notice should match the product configuration.

In Singapore, the Personal Data Protection Commission’s employment guidance says employee personal data reasonable for managing an employment relationship may fall under an exception that does not require consent, while employers must still notify employees of the purposes. It also says organisations should act as a reasonable person would consider appropriate and should not retain personal data without a defined purpose. Apply the current law and advice to your circumstances.

Design the exception flow

Time tracking fails in ordinary ways. The phone may be offline, the cleaner may forget to clock out, the site boundary may be wrong or the schedule may have changed without reaching the device.

Define a workflow for:

Outside-area event
Missing clock-in or clock-out
Duplicate event
Wrong site or assignment
Offline event submitted later
Break or travel correction
Replacement not reflected in the schedule
Device, permission, QR or NFC failure
Manager edit
Employee disagreement

For each exception, record the original event, explanation, supporting evidence, editor, approved value and decision time.

Do not allow a manager to silently replace the event. The edit history is part of the reliability of the record.

Let workers review the time being approved

Give cleaners a practical way to see their shifts and time records before or during the payroll review process.

They should be able to identify:

Missing work
Incorrect assignment
Wrong start, end or break
Travel or premium category needing review
Edit they do not understand

The approval process should show who accepted the correction and why. A dispute should remain visible until resolved under the company’s process.

This is also good data hygiene. A location exception that everyone knows is caused by a bad site boundary should not keep entering payroll and performance conversations.

Do not use attendance as a quality score

A cleaner can attend and still miss the required outcome. A cleaner can also produce good work while the time record contains an explainable exception.

Keep the signals separate:

Attendance for presence and paid-time review
Task checklist for assigned actions and exceptions
Inspection for cleaning outcome
Issue record for a complaint or service problem
Corrective work for follow-through

For a fair individual review, see how to track cleaner performance. For the client’s service view, use the separate contractor-performance scorecard.

Evaluate time-tracking software with a real scenario

Ask vendors to demonstrate one clean shift and one messy one.

Use this scenario:

A cleaner is scheduled at one site
The supervisor moves them to another site
The phone is temporarily offline
The clock event reports outside the original site boundary
The cleaner forgets to clock out
A manager corrects the record
The cleaner reviews it
Payroll receives the approved version

Check whether the system preserves the schedule change, original events, edit history, reason and approval. A perfect clock-in demonstration does not show how the product handles the exceptions that create payroll work.

Also ask about access controls, retention, export, deletion, hosting, subprocessors, incident response and what happens to records when the contract ends.

How CleanLog handles time and attendance

CleanLog connects the shift assignment to the cleaner’s attendance record and location. Depending on the configured workflow, sites can use GPS, QR or NFC verification. Managers review time exceptions and approved records remain connected to the schedule and location.

The time record also sits beside the work record. Checklists, inspections and issues answer different questions without turning a clock event into proof of cleaning quality.

The exact payroll rules and privacy basis remain the employer’s responsibility. Configure the workflow around the rules that apply to the worker rather than a generic industry setting.

Start with one corrected timesheet

Choose a recent shift where somebody changed the recorded time.

Can the cleaner and payroll reviewer see the original event, schedule version, reason, editor and approved value? Can they tell what location information was collected and why? If the answer depends on a separate message, the audit trail is incomplete.

If you want to test that scenario in CleanLog, talk to us. Bring a real exception, not only a perfect shift.