It is 5:40 p.m. on a Tuesday. Two cleaners just texted that they are not coming in, one of them for a 42,000 square foot medical office that has a Wednesday morning walkthrough. Your supervisor is already on the road and cannot answer.
So you start dialing. Seven calls, three voicemails, one person who says yes then stops answering, and by 7:15 you have covered one of the two buildings. The other gets a partial clean and an apology email on Wednesday.
That evening is not a staffing problem. It is a dispatch problem. Staffing is who is on your roster; dispatch is how fast you can reach them, assign them, confirm they arrived and prove the work got done. Most cleaning companies have invested heavily in the first and almost nothing in the second.
What mobile dispatch actually means in a janitorial context
Borrowed from HVAC and plumbing, "dispatch" usually means routing a technician to a service call. Commercial cleaning works differently. Most of your labor is scheduled recurring work, so dispatch is the exception handling layer that sits on top of a fixed schedule.
Mobile dispatch means those exceptions get handled from a phone, by the people closest to the work, with a record of what happened. Not by one dispatcher with a contact list and a landline.
| Dispatch event | What it really is | Who usually handles it today |
|---|---|---|
| Callout / no-show | An open shift that must be filled or reassigned before the building's access window closes | Owner or account manager, by phone |
| Client callback | A complaint that requires someone on site within hours, not days | Whoever answers the office line |
| Add-on work order | Extra scope (strip and wax, carpet extraction, post-construction touch-up) that needs a crew and a start time | Sales, then handed off verbally |
| Supply gap | A closet is out of liners or floor pads, and the task cannot be completed tonight | Cleaner texts a supervisor who may or may not see it |
| Access failure | Key, code or badge does not work; crew is standing outside on the clock | Phone chain, often 20 to 40 minutes |
| Scope change on site | Client's on-site contact asks for something outside the contract | Nobody, until it shows up as an unbilled hour |
The cost of a phone tree, worked out
The numbers below are an illustration, not a study. Run them with your own figures and they will still be uncomfortable.
Say your operation runs 60 cleaner-shifts a night across 22 buildings. Assume you get four callouts in a typical week. Each fill takes your dispatcher an average of six calls at roughly two minutes each, plus follow-up texts, plus a call to the client when you cannot cover.
| Line item | Illustrative figure | Notes |
|---|---|---|
| Dispatcher time per fill | 18 minutes | Calls, voicemails, confirmation texts |
| Fills per week | 4 | 72 minutes of manager time weekly |
| Annualized manager time | About 62 hours | Time not spent on inspections or sales |
| Shifts filled after start time | 1 in 4 (assumed) | Late start compresses the work into fewer hours |
| Overtime premium on fills | Varies | The person who answers is often the person already at 38 hours |
The manager hours are the visible cost. The invisible cost is worse: you fill with whoever answers rather than whoever fits, which quietly drives overtime, mismatched skills and repeat callbacks on the same account.
The eight benefits that actually show up in your numbers
1. You broadcast instead of dialing
A phone call reaches one person at a time and fails silently. A broadcast to a location channel or an open-shift list reaches everyone qualified at once and first acceptance wins.
The practical change is that your time to fill stops scaling with the size of your roster. Filling a shift from a 40-person roster takes the same effort as filling from a 12-person roster.
2. You dispatch on fit, not on who picks up
Not every cleaner should be sent to a surgery center, a food plant or a data center. Filters that matter: current certifications, bloodborne pathogen training, badge or background clearance for that client, floor machine experience, and hours worked so far this week.
When those attributes live in the same system that sends the request, you stop making the two expensive mistakes: sending an uncleared person to a restricted site, and sending someone into their 41st hour.
3. Arrival is confirmed, not assumed
Geofenced clock-in gives you a hard timestamp and a location at the start of the shift. If nobody clocks in at a building by 10 minutes past the scheduled start, you know while you can still do something about it.
Be honest about what this does and does not do. It confirms someone was inside the geofence when they clocked in. It does not follow them around the building, and no clock-in system replaces inspections.
4. Travel pay stops being a guess
When you dispatch a cleaner from Building A to Building B mid-shift, that travel is generally hours worked. The U.S. Department of Labor treats travel that is part of the employee's principal activity, including travel from job site to job site during the workday, as compensable time.
Verbal dispatch leaves no record of when the second assignment was issued. Mobile dispatch timestamps it, which protects you in a wage claim and tells you what multi-site nights truly cost.
5. Callbacks close with evidence, same night
A client emails at 9:15 a.m. about restrooms in the south wing. Under a phone workflow, that becomes a note, a reminder and a conversation at 4 p.m., and the fix gets verified by nobody.
Under mobile dispatch, it becomes a work order attached to that location with a due window, assigned to the night lead, closed with two photos. You reply to the client with the photos before they have to follow up. That single change does more for renewal conversations than any quarterly business review.
6. Supply gaps stop becoming missed tasks
A cleaner who finds an empty liner case at 8 p.m. has two options: text someone and hope, or skip it. Most skip it, and the skipped task shows up as an inspection deduction three weeks later.
A supply request submitted from the phone, tied to the building, gives you a queue your supervisor can pull from before the next visit. It also gives you consumption data per site, which is how you find the account that is quietly eating your gross margin.
7. Your dispatcher stops being a single point of failure
In a lot of companies, one person knows which cleaner will pick up on a Friday night, who has a car, and who cannot work the east side building. That knowledge is not written down anywhere.
When dispatch runs through a system, availability, skills and site restrictions become data. Your night supervisor can cover for your operations manager without a two-hour handoff call.
8. Instructions reach crews in the language they read
Building cleaning is a multilingual workforce. A dispatch message that is only in English gets read by the crew lead and relayed imperfectly, if at all.
Systems that present the interface in Spanish or Portuguese remove one full step of translation loss between your intent and what actually gets cleaned.
Response time targets to hold yourself to
There is no published industry standard for janitorial dispatch response. These are targets many operators set internally and are a reasonable starting point. Adjust them to your access windows and client SLAs.
| Event | Acknowledged within | Resolved within | Escalates to |
|---|---|---|---|
| Callout, more than 4 hours before start | 15 minutes | 2 hours | Account manager |
| Callout, less than 4 hours before start | 10 minutes | 60 minutes | Owner or ops manager |
| Missing clock-in at scheduled start | 10 minutes past start | 45 minutes past start | Night supervisor |
| Access failure (locked out) | 5 minutes | 20 minutes | Client emergency contact |
| Client callback, standard | 1 business hour | Next scheduled service | Account manager |
| Client callback, health or safety related | 30 minutes | Same day | Owner |
| Supply request | Same shift | Before next scheduled service | Supervisor |
| Out-of-scope request on site | Same shift | Quote issued in 2 business days | Sales |
A 30-day rollout that will not blow up in your face
Do not launch this to every crew at once. Cleaners have seen management systems come and go, and a botched first week creates resistance you will fight for a year.
Week-by-week rollout
- Days 1 to 5, get the data right: load every location with the correct address, access instructions, scheduled hours and on-site contact. Bad addresses are the number one cause of geofence complaints.
- Days 6 to 10, define your events: write down the six or seven dispatch events you actually have, who owns each one, and the target response times. One page. Post it.
- Days 11 to 14, pilot two buildings: pick one easy account and one difficult account. Run every exception through the new process. Keep the phone as backup but log everything.
- Days 15 to 18, fix what broke: geofence radius too tight for a large campus, cleaners without data plans, a supervisor who keeps reverting to text. Solve these before scaling.
- Days 19 to 25, roll out by supervisor: expand one supervisor's book of business at a time, not one region at a time. Supervisors are the adoption gate.
- Days 26 to 30, turn off the old channel: announce a date after which callouts sent by personal text to a manager's phone are not considered received. Enforce it the first week or it will not stick.
Common mistakes
- Treating dispatch as surveillance: if the first thing crews hear is that you can now see where they are, you will get compliance theater and turnover. Lead with what it fixes for them: faster answers when they are locked out, credit for the work they did, no more unpaid drive time.
- Promising capabilities you do not have: clock-in location capture is not continuous tracking. If you tell a client you can see crews "in real time all night," you will eventually have to walk that back in front of the account.
- Broadcasting every open shift to everyone: untargeted blasts train people to ignore notifications. Filter by qualification and proximity first, then widen if nobody accepts inside your target window.
- No overtime guardrail: if the fill logic does not consider hours already worked this week, mobile dispatch will make it faster to create overtime. Check weekly hours before you offer the shift.
- Leaving the old channel open: if callouts still arrive by text to a personal cell, that is where they will keep arriving, and your data will be worthless.
- Skipping written access instructions: the single highest-value field in your system is the access note. Alarm code sequence, which door after 9 p.m., where the freight elevator key hangs. Write it once, and every fill after that is 20 minutes faster.
- No offline fallback: basements, loading docks and mechanical rooms have no signal. Decide in advance what a cleaner does when the browser will not load, and make sure it is not "guess."
What to measure once it is running
Four metrics tell you whether mobile dispatch is working. Track them weekly for the first quarter, then monthly.
| Metric | Formula | What it tells you |
|---|---|---|
| Time to fill | Median minutes from callout received to shift accepted | Whether your broadcast reach is real |
| Unconfirmed start rate | Shifts with no clock-in within 15 minutes of start, divided by total shifts | Your true no-show exposure, including silent ones |
| Coverage rate | Open shifts covered before start time, divided by total open shifts | How often a client actually feels a callout |
| Callback closure time | Median hours from client complaint logged to photo-verified fix | The number that drives renewals |
| Fill-driven overtime | OT hours originating from filled shifts, divided by total OT hours | Whether speed is costing you margin |
How often to review
- Nightly: unconfirmed starts. This is a 60-second check by whoever is on duty, not a report.
- Weekly: time to fill, coverage rate, open callbacks past their due window. Fifteen minutes in your ops meeting.
- Monthly: fill-driven overtime by account, supply requests by building, callback volume by account. This is where you find the account that is underpriced.
- Quarterly: geofence radius audit for sites that generated repeated clock-in complaints, plus a review of access notes on every location you gained in the last 90 days.
- Annually: re-check your response time targets against what you have actually committed to in client contracts. They drift apart.
Where CleanTrack360 fits
CleanTrack360 covers the dispatch layer described above: drag-and-drop scheduling with recurring shifts and work orders, geofenced GPS clock-in and clock-out with a configurable radius (150 m by default), location-based team messaging so callouts reach a building's crew instead of one phone, supply requests, and quality inspections with custom checklists, photo evidence and automatic scoring. Clients see schedules, inspection reports and their own service requests in a browser-based dashboard, which removes most of the "did anyone go last night?" email traffic. The interface runs in English, Spanish and Portuguese.
One thing to be clear about: crews use the phone browser today. The native mobile app is still in development, and location is captured at clock-in and clock-out, not continuously between them. Plans are Starter at $99/month for up to 5 team members, Pro at $199/month for up to 20, and Business at $249/month for up to 50, priced per plan rather than per user. There is a 14-day free trial with no credit card, which is enough time to run the two-building pilot described above.