A commercial cleaning company runs thirty buildings a night with crews that start at 6 p.m. and finish past midnight. The schedule lives in a supervisor's head and a group text. When a cleaner does not show, the first signal is usually the client emailing at 8 a.m. asking why the lobby still has yesterday's coffee cups.
How the night actually runs
A supervisor assigns crews to buildings the way a dispatcher works a board, except the board is a group text and three years of knowing who is reliable. Each cleaner gets a site or a short route, a start time, and the access details: a lockbox code, an alarm sequence, which door actually opens after 9 p.m. Clock-in, where it exists, is a punch app, a text that says “on site,” or nothing at all.
Most of this holds most nights on the supervisor's memory. The cracks show on the nights the supervisor is off, the week a steady cleaner quits with no notice, or the Monday a new building gets added and the route math changes for everyone downstream.
Where coverage breaks
A cleaner does not show. There is no rule for what happens next, so the supervisor finds out when they happen to check the thread, or when they do not. With no record of who was scheduled where, a skipped site stays invisible until the client emails the next morning about the lobby nobody touched.
Filling the gap is its own scramble. The supervisor runs a mental list of who is off tonight and who is already near that part of town, then whether any of them is cleared for that building. By the time someone covers it, the shift is half gone, and reconstructing what happened for payroll or for the client takes a morning of phone calls.
The proof gap
Commercial contracts increasingly want proof the work happened, not just an invoice. The cleaner signed a paper checklist taped inside a supply closet, or texted a photo that lives on one phone, or did neither. When a client disputes whether the third-floor restrooms were serviced on the 12th, there is no timestamped record to answer with, so the company eats the credit to keep the account.
This is the same gap that costs renewals. A facilities manager deciding whether to keep a vendor wants a clean record of attendance and completion. A shoebox of texts is not that.
What an operations layer changes
An operations build for night cleaning starts with the schedule as data: every site, shift, assigned cleaner, and access detail in one place instead of a supervisor's head. Clock-in is tied to the site, by a code or location, so a shift that does not start throws an alert at 6:15 instead of an email from the client at 8. Proof of service, a timestamp and a photo against the site's checklist, is captured by the cleaner on the way out and attached to that account.
The supervisor works a board that shows the night filling in, spots the one site that has not started, and covers it from a ranked backup list before the client knows there was a question. The owner gets a record that answers disputes and holds renewals. We have built this dispatch-and-proof shape for a facilities operator running fifteen properties, and the moving parts are the same for a cleaning company running thirty.
Before you build it
This pays off only when the routes are real. A company with recurring sites, regular crews, and a supervisor who can name the schedule has something to systematize. A company whose work is one-off deep cleans booked ad hoc does not yet, and software there would just add overhead to chaos.
Map one week first. List every site and shift, who is assigned, how a no-show surfaces today, and how long it takes to fill. That afternoon tells you whether the real gap is scheduling, coverage, or proof, and which one to build against. Often it is proof that costs the most, because it is the one the client sees.