Software for commercial cleaning: what matters

Because it happens where conditions are worst. Cleaning takes place early in the morning or late at night, often in underground car parks, basements and stairwells with no mobile reception, carried out by teams who visit several sites in one day.

Many systems quietly assume a connection exists. In practice that produces a dangerous behaviour: the app reports a successful clock-in although the data never arrived. The employee assumes it was recorded, and at month end the hours are missing.

An honest solution records offline, visibly shows what has not been transmitted yet, and syncs automatically once there is reception again. Ask suppliers specifically what happens without a network, and have them demonstrate it.

The software has to follow the path a job takes anyway: from the site through the planned assignment and the work performed, to the invoice and into payroll. Anything that interrupts that path creates duplicate work.

Honesty towards the employee. A system that reports "green" when in doubt is worse than one that openly shows: not transmitted yet. Only then can someone react before payroll runs.

The second point is simplicity. Someone standing outside a building at six in the morning wearing gloves has no patience for menus. A few large buttons, no login for every assignment, no mandatory fields nobody can fill in.

The third is traceability in both directions. Corrections must be possible but stay visible. Who changed what and when should be recorded. That protects the company and the employee equally.

By having planning, proof of service and invoicing use the same data. The planned assignment becomes the completed assignment, the completed assignment becomes the proof of service, the proof becomes an invoice line. Where that works, most of the monthly office work disappears.

In practice it usually fails on details: extra services that were not in the plan. Sites billed by area rather than by hours. Customers who expect a particular breakdown on their invoice. Check exactly those cases before you decide.

Think about the other direction too: supplier invoices for materials and subcontractors should be assignable to a site. Otherwise you know your revenue per site but not your costs.

With thin margins, success is decided not by total revenue but by individual sites. A site that has been consuming more hours than calculated for two years barely stands out in an annual report and still costs money continuously.

That requires three figures per site: planned time, actually recorded time, and the assigned costs for materials and staff. Only together do they show whether a contract carries itself.

Timeliness matters. A report that only exists after the annual accounts arrives too late to renegotiate. A monthly look is usually enough to correct course early.

Recorded hours are rarely identical to payable hours. Premiums, break rules, contractually agreed working days, holiday entitlements and absences all have to be taken into account. If the software does not model that, the work still happens, just in a spreadsheet on the side.

It is therefore worth treating payroll preparation as part of the system and clarifying the interface to your payroll office early. Ask what format your tax adviser or payroll program expects before choosing a system.

On the legal side: requirements for working-time documentation and retention change and depend on your specific case. Have this confirmed for your company by an employment lawyer. We model what you need, but we do not replace legal advice.