Dispatch, crews, checklists, inspections, linen and cleaner pay — in the same system as the calendar that creates the work.
Because the clean is scheduled by the booking, not copied into another app by someone at 9pm.
Eighteen screens, from today’s board to payroll — built for someone running a hundred turnovers a week, not ticking off a to-do list.
Assign by building, zone or crew. Zones can be suggested from where the properties actually are, and auto-assign fills a day against your rota rather than leaving it to whoever answers first.
Each job carries the checklist as it was when the job was created, so editing a template never rewrites history on work already done. Inspections open against a policy, not a hunch.
Par levels derive from the beds in each property. The office sees portfolio totals; the cleaner gets a pick list for the van before they leave.
Billing rate and crew pay sit on the same job, so you can see what a clean earned while there is still time to do something about it. Monthly margin rolls up from the same numbers.
Not the dashboard on a small screen. A phone-first app with the day’s jobs, the checklist, the linen list and their pay — and nothing else.
A field-only cleaner is a member of your organisation, so they are fenced out of every money table at the database level rather than by hiding a menu.
The damage found on a Tuesday turnover is the work order raised on Tuesday, costed, assigned and billed to whoever owes it.
Turnovers are created by the booking calendar, and priced from the cleaning fee the guest already pays — so nobody re-keys a rate that is configured two screens away.
Run it standalone with no properties of your own: your own clients, your own rates per client, invoices, and margin per job. An unpriced job stays visibly unpriced rather than quietly guessing.