How to Schedule Cleaners Across Multiple Sites

The recurring schedule is usually not the difficult part.

The difficulty begins when a cleaner is absent, a client changes the access time, periodic work is added or the person who knows the site is already assigned elsewhere. The schedule may still look complete while the real plan is spread across a spreadsheet, several messages and one supervisor’s memory.

A reliable multi-site schedule needs more than names in time slots. It needs one approved version, explicit coverage requirements and a clear way to handle exceptions.

Start with the service requirement, not the employee list

Define what each location needs before deciding who will work there.

For every recurring service window, record:

Location and exact access point
Date, start window and expected end
Required role or number of people
Tasks or service package attached to the shift
Skills, training or clearance required
Keys, access cards or contact instructions
Equipment or transport constraints
Supervisor responsible for the site
Client notification rule when coverage changes

This becomes the coverage requirement. The assigned cleaner can change without changing what the site needs.

When the requirement and the person are stored as one thing, managers often copy last week’s schedule forward and accidentally copy an old compromise as well.

Keep one approved schedule

The team needs to know which record is current.

If the spreadsheet is the schedule, a replacement agreed in chat should not remain only in chat. Update the approved record and preserve who changed it, when and why. The cleaner, supervisor and payroll process should all refer to the same assignment.

Use a simple status for each service window:

Unassigned: coverage is required but no worker has accepted it
Proposed: a worker has been asked but has not confirmed
Assigned: the worker has accepted the shift
Changed: the approved assignment changed after publication
Completed: the work event was recorded
Exception: attendance or service requires review

Do not use colour alone to communicate the status. A label is easier to understand in exports, screenshots and conversations.

Record availability before assigning work

Availability should be a maintained input, not a question asked again for every schedule.

For each cleaner, keep:

Regular available days and times
Approved leave or unavailable periods
Preferred or agreed locations where relevant
Maximum or contracted hours under the applicable arrangement
Skills, training and access eligibility
Transport constraints that affect particular sites
Other assignments that create travel conflicts

Availability does not guarantee assignment. It tells the scheduler which options are valid before messages are sent.

When availability changes, give it an effective date. Otherwise the team may overwrite the record and lose the reason an earlier assignment was made.

Check five conflicts before publishing

1. Overlapping shifts

The same person should not be assigned to service windows that overlap, including realistic handover and travel time.

2. Travel between locations

The end of one shift and the start of the next may fit on paper while the journey does not. Use the actual access points and the transport method the cleaner uses.

3. Hours and premiums

Review each person’s total planned hours across all sites. Apply the working-time, rest and pay rules relevant to the employee and jurisdiction. A site-level view is not enough if premium thresholds depend on the person’s combined work.

4. Skills and access

Check that the cleaner is allowed and prepared to perform the work. A free time slot does not replace site induction, specialised training, security clearance or possession of the correct key.

5. Continuity and handover

Where site knowledge matters, avoid replacing the whole experienced team at once. If a new person is assigned, attach the current site instructions and make the handover an explicit task.

The cleaning SOP guide covers how to keep those instructions usable at the point of work.

Publish the schedule with confirmation

A schedule is not published when the manager finishes editing it. It is published when the affected people can see the approved assignment and know what requires a response.

The notice should include:

Site and service window
Role or work assigned
Access instructions
Current checklist or procedure
Person to contact about a problem
Confirmation deadline, if acceptance is required

Do not ask people to confirm in several places. If one cleaner replies in a private chat and another reacts in a group, the manager has to reconstruct acceptance manually.

Keep confirmation separate from attendance. Accepting a future shift does not prove that the person attended it.

Build the call-out process before someone calls out

An absence protocol should state what happens without relying on the manager improvising under pressure.

Step 1: Receive and record the absence

Give cleaners one clear route to report that they cannot attend. Record the affected assignment, report time and any information the company is permitted and needs to manage the absence.

Do not make a public group chat the place where someone has to disclose private health or family details.

Step 2: Assess the service risk

Check the site requirement:

Can the work move within the agreed service window?
Can the remaining team complete the scope safely?
Is specialised access or skill required?
Does the client need to approve a change?
Which tasks are critical if full coverage is not possible?

Step 3: Find valid replacements

Filter by availability, location, skills, access, travel and total hours before contacting people. A long message to the whole team moves the filtering work onto every employee and can still produce an invalid assignment.

Contact replacements in the order your company has defined. Keep the offer, response and final assignment attached to the shift.

Step 4: Update the approved record

Once a replacement accepts, change the assignment. Notify the original cleaner, replacement, site supervisor and any client contact required by the service agreement.

Step 5: Close the exception

After the service window, verify attendance and the work outcome. Record any reduced scope, late start, recovery work or client follow-up.

For the workforce process around repeated absence, see how to reduce no-shows in a cleaning operation.

Use deadlines that come from the service window

There is no universal confirmation or escalation timeline for every cleaning business.

Work backwards from the point at which the site would be at risk:

When must the replacement be physically present?
How much travel and access time is required?
When does the supervisor need enough time to intervene?
When should an unconfirmed worker be contacted?
When must the client be told that the service plan may change?

Write those deadlines into the site’s coverage rule. An early-morning secure facility and an evening office do not need the same sequence.

Do not solve every gap with the same reliable person

The fastest available replacement may already carry the most work.

Before offering the shift, check:

Planned and worked hours across all sites
Required rest or break rules
Travel created by the additional assignment
Whether the person has repeatedly absorbed call-outs
Whether another qualified person needs the opportunity or site experience

This is both an operating and a fairness issue. A schedule can appear fully covered while depending on the same people to rescue it.

Track why each unplanned change happened and who covered it. The trend can show a location with a bad service window, a gap in the backup pool or a schedule being published before availability is known.

Separate the schedule from the proof of work

The schedule answers who was expected at the site and when.

Attendance records whether the work event occurred. A task checklist records the assigned actions. An inspection evaluates the result. A client issue records a service problem.

Do not make one record pretend to answer all four questions. A cleaner appearing on the schedule does not prove attendance, and a clock-in does not prove quality.

Keeping them connected but separate makes an exception easier to investigate:

Who was assigned at the time?
Was a change approved?
What attendance event was recorded?
What work or exception was recorded?
What condition did the supervisor or client find?

A weekly scheduling review

Review exceptions, not every ordinary shift.

Use the completed period to ask:

Which service windows remained unassigned close to start?
Which assignments changed after publication?
Which sites repeatedly required replacements?
Which cleaners repeatedly absorbed extra coverage?
Which shifts created travel or hours conflicts?
Which changes were not reflected correctly in payroll?
Which sites need a different service window, staffing plan or backup arrangement?

Assign an owner to each recurring problem. “Keep an eye on it” is not an action.

If you want to quantify the repeated administration and recovery work, use the manual scheduling cost worksheet. It uses your own time and incident records rather than a generic savings figure.

When it is time to move beyond a spreadsheet

Do not use a fixed number of cleaners or sites as the threshold. The important signal is coordination complexity.

Review the process when:

Several people maintain different versions
Coverage changes are accepted outside the approved schedule
Availability, hours or skills cannot be checked before assignment
The client and supervisor receive changes through separate manual messages
Payroll cannot trace an assignment change to the person who approved it
Managers cannot see uncovered work across locations in one view

Those conditions can happen in a small complex operation or much later in a stable one.

How CleanLog supports multi-site scheduling

CleanLog keeps recurring shifts, assignments and changes connected to each location. Managers can view coverage across sites, while cleaners see their assigned work and site instructions on mobile.

Clock events, checklists, inspections and issues stay connected to the same location and service record. That means a manager can move from the plan to the attendance or work exception without searching a separate chat history.

The system does not decide which person should cover a sensitive site or what the client agreement permits. It gives the person making that decision one current record and the relevant constraints.

Start with the change that caused the last scramble

Take the last unplanned schedule change and reconstruct it from report to completed work.

How many places had to be checked? Who knew which version was current? Were availability, hours, travel and access checked before the replacement was asked? Did payroll and the client receive the same final answer?

Turn the missing step into an explicit rule. Then test the rule on the next change.

If you want to map that workflow in CleanLog, talk to us. Bring one real schedule and one recent call-out; that is enough to see where the process is breaking.