Cleaning multiple locations requires more than just "who is where and when." You have to deal with keys, badges, alarm codes, travel time, windows for tenants or managers, and a handover that provides proof of what has been done. In this article, you'll build a lightweight yet robust model: secure windows and access, cluster routes with buffers, record handovers with checklists and photos, handle incidents efficiently, and export time accurately—without spreadsheets and without noise.
Why multiple locations make planning more difficult
With a single building, you'll often have to resolve things ad hoc. With 5–50 locations, making minor adjustments starts to cost you time, margin, and trust. Common problems:
- Keys and badges get lost or circulate without a log; alarm codes are not uniform or outdated.
- Windows (Access times) are unclear, resulting in teams arriving while the building is closed or the tenant is still present.
- Routes are not clustered; travel time eats up productive time and tasks are postponed.
- Transmission is verbal or through individual messages; evidence is lacking in the case of complaints or discussions about quality.
Target: Predictable routes with guaranteed access and a handover that proves itself. Less recovery, more rest, and a clean logbook.
Secure windows and access
For each location, record four things: window opening/closing, access type, emergency contact, and security policies (alarm, camera, key safe). Keep these centralized and up-to-date.
| Location | Window | Access | Alarm | Duration task | buffer | Emergency contact |
|---|---|---|---|---|---|---|
| Office A (3 floors) | 19:00 AM – 22:00 PM | Key safe 4827 | Code & on/off | 120 min | 15 min | Administrator +31 6 1234 5678 |
| Shop B (street) | 07:00 AM – 09:00 PM | Reception badge | na | 45 min | 10 min | Branch 020-111 22 33 |
| Medical C | 20:30 AM – 22:00 PM | Key + alarm | Off/On + Log | 60 min | 15 min | Property management 024-555 66 77 |
Practical: Use a single "access card" per location (one screen). Everything the team needs to know is listed there: where the key is, the alarm steps, who to call, and what absolutely is not allowed (e.g., no vacuuming in treatment rooms after 21:30 PM).
Cluster routes and reduce travel times
Don't plan by job, but by route. Build clusters based on neighborhoods/zip codes and windows. The trick is to arrange stops so you minimize travel and respect windows.
- ClusteringGroup locations by neighborhood and window (morning or evening). Use fixed names (West A, Center B) so everyone understands them immediately.
- Buffers: set realistic travel time buffers between stops (traffic, parking) and small access buffers (key cabinet, badge, reception).
- Cap per routeDon't cram everything into one block. Better to have 10 minutes of free space than a 30-minute delay for the last customer.
| Route | Block | Stop | Location | Window | Start | End | Travel buffer | Access buffer |
|---|---|---|---|---|---|---|---|---|
| Center-B | Morning | 1 | Shop B | 07:00 AM – 09:00 PM | 07:00 | 07:45 | 8 min | 2 min |
| Center-B | Morning | 2 | Office D | 08:00 AM – 10:00 PM | 08:05 | 09:20 | 10 min | 5 min |
| West-A | Evening | 1 | Office A | 19:00 AM – 22:00 PM | 19:00 | 21:00 | 12 min | 3 min |
Tip: Make routes visible for each team member in the app (a single list). No more searching for individual addresses or separate codes via WhatsApp.
Transfer: evidence with checklists and photos
A handover isn't a long report. It's a short, repeatable checklist with optional "before/after" photos where that adds value. You want proof that tasks have been completed, that details have been noted, and that the key/alarm has been handled correctly.
- Checklist per location (5–10 points): floors, bathroom fixtures, pantry/kitchen, trash, high-touch (door handles, railings), windows/glass (if applicable), alarm/lockout.
- Photos: only where useful (at complaint locations, specials, delivery).
- Additional information: defects/incidents, closed spaces, extra time spent, materials replenished.
| Log field | Example | Why |
|---|---|---|
| Location + time | Office A, 21:03 | Traceability |
| Checklist score | 7/7 completed | Completeness |
| Photo (optional) | Pantry after cleaning | Evidence in case of complaints |
| Special feature | Glass wall fingerprints at main entrance; additional 8 min | Transparency ≠ discussion |
| Access | Alarm on, key back in safe 4827 | Security guaranteed |
Communicate simply: "Check off your checklist, add photos where necessary, briefly note down details, and log the alarm/key." This way, your audit trail will be created automatically.
Incident path and escalations
Incidents happen: access denied, alarm failed, additional contamination, water leaks. You don't want panic, but a short script that everyone knows.
- No access: Call emergency contact (max. 2 attempts per 10 minutes), take a photo of the situation (without sensitive information), log "no access," move the stop to the end of the route, or mark it for rescheduling. Never force the alarm.
- Alarm or key problemStop immediately, call emergency contact or security, wait for instructions. Log everything (time/step/name).
- Extra pollution: note down “additional work” (briefly), carry out if it fits within the time, otherwise report for order adjustment.
- Calamity: Follow the safety protocol (BHV), call 112 if necessary, then contact the client/planner; keep a concise record of facts, no interpretations.
Escalation list1) Client contact, 2) Property management, 3) Security. One place in the app with current numbers.
Lock and swap: stability before the start
Lock the route at T-24 (or T-48 for critical properties). After that, only exchange with approval. This prevents last-minute gaps or unqualified replacements.
- Exchange flow: Employee A requests a swap → the system checks driving distance, window, access codes, and alarm capability → when the light is green: the car is delivered before T-24; after T-24: the manager approves → confirmations are sent to A/B/planner → log.
- Critical locations (medical/high-security): always manager approval, regardless of T.
- Shortlist: Authorized colleagues in the same cluster/window with access knowledge; let the system suggest them in order of travel time.
Team text (copiable): Routes are locked 24 hours in advance. Swapping is possible, but only with approval after the lock. Critical properties always require approval. You'll always receive confirmation.
Time registration and export
Without accurate hours and deviations, you'll face disputes and rejections from payroll. Keep it small and consistent.
- Check-in/out at every stop (start/end) and automatically registering travel time between stops.
- Differences (additional work/no access/extra waiting time) briefly record with one reason and, if necessary, approver.
- Day check: Planner checks deviations after the last route and approves within 24 hours.
| Field | Example | Explanation |
|---|---|---|
| Employee ID | CLN-058 | Unique employee number |
| Date | 2025-10-06 | ISO notation |
| Location code | LOC-A-003 | Link contract |
| Start | 19:00 | Start cleaning |
| End | 21:00 | End of cleaning |
| Travel time | 12 min | Between previous and current |
| Divergence | +8 min glass wall | Short reason |
| Approver | MGR-07 | Only in case of deviation |
export: Keep fields stable (ID, date, location, start, end, travel time, deviation, approver). Less variation = fewer errors and less feedback.
Measuring what counts (4 KPIs)
No dashboard maze. Four numbers guide behavior and guarantee margin.
- Travel time per stop — month-on-month decrease due to better clustering.
- Incidents per 100 stops — decrease due to clear access/windows and a refreshed escalation list.
- Recovery tasks (aftercare/complaints) — down with photo/checkbox proof.
- Late changes (< 24 hours) — decrease due to lock and shortlist exchange.
Rhythm: Every Monday, spend 10 minutes reviewing the four KPIs, record one action for each, and communicate it at the start of the day. Small and consistent wins.
Frequently asked questions
What if a key or badge is missing
Use key management in the app (issue/return + location). If missing: log "no access," call emergency contact, and schedule a return visit at the end of your route or the next day. Never improvise with unauthorized access.
How to prevent alarms from going wrong
Enter the exact sequence (door → alarm → section) on the access map. Add a photo or sketch if this helps. Practice once with the team at critical buildings.
What to do in case of unexpected pollution (event/renovation)
Note any additional work and only carry it out if it fits within the timeframe. Otherwise, request approval or issue a separate order. Always log it briefly for invoicing.
How do you ensure quality with rotating shifts?
Work with fixed routes for each team and a short handover in the app (special details). Only use photos where necessary; otherwise, you limit noise.
What if a location is structurally running late?
Increase the buffer or adjust the task duration. Discuss with the client whether the window can be moved. Use the log data (deviation + reason) as a basis.
Get started now
- Create a location per location access card (window, key/badge, alarm step, emergency contact).
- Construction clusters/routes per district and window, with realistic travel and access buffers.
- Put one checklist + photo field in the app; log short and factual.
- Activate lock on T-24 expats must register with the local municipality and obtain a exchange flow with checks and audit.
- Rule hours at the source and a fixed export mapping (ID, date, location, times, travel time, deviation, approver).
- Monitor 4 KPIs and adjust every week with one small measure.
This approach makes cleaning across multiple locations predictable. Access is guaranteed, routes run smoothly, handovers are straightforward, and administration is streamlined. You save time, quality, and trust—with customers and your team.
Go back to the overview