How to Track Cleaner Performance Fairly

If a cleaner’s performance score falls, the first question should not be “what is wrong with this person?”

The site may have changed. The scope may be unclear. The shift may be understaffed, the equipment may be unavailable or the inspection may have happened after the area was used again. The record can still point to a real performance problem, but it needs context before it becomes a judgement.

This is where performance tracking easily turns into micromanagement. The company collects more data because it wants a fairer view. Then every clock-in, location event and checklist tap begins to look like a verdict.

I think the better approach is narrower: define the work, collect the evidence needed to manage it, review exceptions with a person and give the cleaner a way to explain or correct the record.

Start with work the cleaner can control

A fair measure needs a clear responsibility.

The cleaner can usually control whether they follow the assigned procedure, complete the work they accepted, report an obstacle and respond to feedback. They may not control building access, missing consumables, a late schedule change, an unrealistic workload or how the public uses the area after cleaning.

Write down the expected work before measuring it:

Assigned location and area
Shift or service window
Required tasks and procedure
Observable cleaning outcome
Evidence required for specific work
How to report an exception
What happens after a failed inspection or complaint

If the expectation exists only in a supervisor’s head, the performance record will not be consistent.

Use several signals, not one secret score

No single number describes cleaning performance well.

Attendance confirms presence. A checklist records assigned actions. An inspection evaluates a condition. A complaint records a service problem. Corrective work shows how the team responded. These signals are related, but they are not interchangeable.

A practical review can consider the following areas separately.

Attendance and reliability

Record whether the cleaner attended the assigned shift and whether the manager was notified when they could not.

A time or location record can confirm an event. It cannot explain every delay. Review exceptions such as a clock-in outside the agreed location or time instead of treating a raw timestamp as the complete story.

For a broader process around absence and replacement coverage, see how to reduce no-shows in a cleaning operation.

Assigned work completed

Use a site-specific task checklist to show what was assigned and what the cleaner recorded as completed, blocked or not applicable.

Checklist completion on its own does not prove cleaning quality. It does show whether the person followed the required workflow and reported exceptions. A checklist that only accepts “done” produces weak evidence because it encourages a false completion when access, stock or equipment prevents the task.

The cleaning checklist system guide explains how to keep task instructions separate from inspection outcomes.

Inspection outcomes

Inspection results can show whether the finished area met the agreed standard.

Review the item and location behind the result. Do not let a site-wide average hide a repeated failure in one critical area. Also check when the inspection happened and whether the cleaner was responsible for that area during the relevant service window.

The purpose is to find a coaching, process or site issue. It is not to turn one inspection into a permanent label.

Response to feedback and corrective work

A failed item matters, but what happened next matters as well.

Did the cleaner understand the expected standard? Was corrective work assigned? Was it completed? Did the same issue return? A person who reports a problem early and closes it properly should not look worse simply because their records contain more exceptions than someone who reports nothing.

Site and team context

Keep a separate record of conditions that can affect the work:

Access blocked or delayed
Missing or faulty equipment
Consumables unavailable
Scope changed without a schedule update
Unusual foot traffic or an event
Another worker absent
Inspection completed long after the service

Do not bury these notes in a final comment after a score is calculated. They are part of the review.

Avoid the GPS productivity trap

Location verification can answer a narrow question: was the work event recorded at the assigned site?

It is much less useful for judging how well someone cleaned. A moving dot does not show whether a washroom met its standard. A stationary phone does not prove that no work happened. Continuous location history can also collect far more information than the supervisor needs for the decision.

Use the least intrusive record that answers the operational question. For example, a location check attached to clock-in may be enough to flag an attendance exception. The company may not need to watch a cleaner’s live route throughout the shift.

The exact legal requirements depend on where the company and worker are located. In Singapore, the Personal Data Protection Commission’s employment guidance says employee personal data that is reasonable for managing an employment relationship may be collected, used or disclosed without consent under the stated exception, but employees must be notified of the purposes. The guidance also says organisations should act as a reasonable person would consider appropriate in the circumstances and should not retain personal data without a defined purpose.

This is general operational guidance, not legal advice. Check the law and employment terms that apply to your workforce before introducing monitoring.

Tell people what is collected and why

A cleaner should not discover the measurement system only when a manager raises a poor result.

Explain in plain language:

Which events and records are collected
Why each record is needed
When location is checked
Who can see the information
How long it is kept
How it contributes to a performance review
How the cleaner can raise an error or add context

The system should not quietly expand from attendance verification into continuous productivity surveillance. If the purpose changes, review the data collection and tell the affected team.

Singapore’s Ministry of Manpower lists fair treatment, respect, progressive HR practices, development opportunities and fair reward based on ability, performance, contribution and experience among its fair employment principles. A transparent review process is one practical way to apply those principles to daily operations.

Give the cleaner access to the record

Performance data can be wrong.

A shift may be assigned to the wrong person. A supervisor may inspect the wrong area. A site exception may never reach the office. A photograph may be attached to a different task.

Before using a record for a consequential decision, let the cleaner see the event, the expectation and the evidence. Give them a way to correct a factual error or add context. Keep the original record and the resolution rather than silently replacing it.

Human review is especially important when software flags an exception. An alert can decide what needs attention. It should not decide the person’s explanation in advance.

A simple performance review structure

You do not need an opaque rating formula. Use a short review that stays connected to the underlying work.

Review area	Evidence to examine	Question to discuss
Attendance and notice	Assigned shifts, clock events, absence notice and approved changes	Were agreed shifts attended or communicated properly?
Assigned work	Checklist items, exceptions and linked procedure	Was the required workflow followed and were obstacles reported?
Cleaning outcome	Applicable inspection items and timing	Did the assigned area meet the defined standard?
Corrective action	Failed items, coaching and follow-up work	Was feedback understood and closed?
Repeated pattern	Comparable records over time	Is there a recurring issue rather than one isolated event?
Site context	Access, equipment, stock, workload and schedule changes	Did conditions outside the cleaner’s control affect the result?

The supervisor should finish with a specific next step. It might be coaching on one procedure, repairing equipment, changing the schedule, clarifying the scope or checking the same outcome again under comparable conditions.

“Improve quality” is not a useful next step. It does not tell the cleaner what should change.

Keep team, site and individual problems separate

Suppose several cleaners fail the same inspection item at one location.

That pattern may point to training, equipment, scope or the way the standard was written. Treating it as several unrelated individual failures would miss the shared cause.

Compare results across:

The same cleaner at different locations
Different cleaners at the same location
The same task before and after a procedure change
The same area under similar inspection timing

This is not about finding a more complicated score. It is a way to avoid blaming the nearest person for a system problem.

For the site-level inspection process, use the commercial cleaning quality audit guide. For the client’s view of an outsourced provider, use the separate guide to measuring cleaning contractor performance.

How CleanLog supports fair review

CleanLog connects schedules, clock events, task checklists, inspections, issues and corrective work to the relevant site. A supervisor can review the exception and then open the record behind it.

The useful part is not having more employee data. It is being able to separate the questions:

Was the person assigned?
Was the attendance event recorded at the site?
What work was required?
What exception was reported?
What condition did the inspection find?
What follow-up happened?

Those records still need human judgement and a fair company process. Software should make the evidence easier to review, not turn it into a verdict.

Start with one disputed record

Take one recent performance issue where the manager and cleaner understood the event differently.

Write down the expectation, the available evidence, the site context and the decision that was made. Then ask what was missing. If the answer is “we needed to see the person all day,” narrow the question. You may only need a clear assignment, a verified work event, an inspection result or an exception note.

That is the standard I would use for any new performance measure: collect enough to manage the work fairly, and no more than the purpose can justify.

If you want to see how CleanLog connects the site record without reducing it to one hidden score, talk to us. We can start from the review you already need to run.