Job management for a cleaning company
The client calls to say something was not cleaned. The office does not know whether the crew was on site, whether a skipped room was marked, or whether this is a repeat complaint on the same building.
Who it is for
For a company with several standing sites and crews that rotate between them. A poor fit for a solo cleaner in one home, with no checklist and no client who expects a report.
Problems this page addresses
A site with no scope
A floor was added or a room was dropped. The crew works from what they remember, and the client pays against an old agreement nobody opened.
A shift with no names
Someone was missing this morning. A person was moved from another site, and the end-of-day report still names the original crew.
A complaint with no link to the visit
The client writes that the kitchen was not cleaned. There is no checklist from that morning, so the argument is word against word.
What you get
A site card
Address, scope, frequency, and what sits outside the agreement. A scope change is written before the crew arrives, not after a complaint.
A shift with names
Who was placed, who was replaced, and who finished. The replacement is logged from the site lead’s phone.
An exit checklist
Before leaving, the crew marks what was done and what was skipped, with a reason. A complaint opens on this visit, not on the site in general.
Common questions
Why not a WhatsApp group per site?
The group is fine for an urgent message. It does not say what the scope is, who was on the shift, or what was skipped. Without that, every complaint starts as a search through messages.
Will the crew fill a checklist?
Only if it is short and marked on site, not a long form back at the office. A skip needs a short reason. Done is a mark, not a paragraph.
How is this different from a security company?
Cleaning closes a visit against a scope and a checklist. Security closes a shift against a post and an incident. Same kind of field crew, a different decision at the end of the shift.
Related pages
A CRM shaped around how you already work
An off-the-shelf CRM asks the team to adopt someone else’s stages and fields. We build the record around the approvals, statuses, and fields that already decide who the customer is and what happens next.
A mobile app on the same core as the web
The office works comfortably on a large screen, and the field stays on screenshots and group chats. We build the phone actions on the same server and the same permissions, not as an app with a database of its own.
Shift management for a security company
The client requires a guard on a post. In practice someone was replaced in the middle of the night, and the incident was written in a group. In the morning nobody can show who was there and what was handled.