Service records the strata manager cannot argue with.
I run two cleaning companies, so this is not theory. On recurring commercial and strata work, the building manager has a system and you have a run sheet, and when a clean gets queried that asymmetry costs you the invoice. Here is what a record has to carry to end the argument.
The query you cannot answer
A committee member emails the building manager to say the common areas were not done on Tuesday. The building manager emails you. You know your crew was there, because they are reliable and because the run says so. But the run is a spreadsheet, the crew have gone home, and the only thing you can honestly send back is an assurance.
An assurance does not beat a written complaint. So you credit the visit, or you do a make-good for free, and either way the month's margin on that site is gone. Do that three or four times a year across a portfolio and it is a real number.
When the building manager's records are the only records, the building manager's records win. Not because anyone is lying, but because only one side wrote it down.
What a defensible record carries
- A time on site. Arrived and departed, captured automatically rather than written down later. This one fact settles most disputes on its own.
- Who attended. Useful for the query, and more useful for training when the same site keeps generating complaints.
- What was done against scope. Not a free-text note. The actual scope items for that site, ticked, so a gap is visible rather than inferred.
- Photos of the things that get queried. Foyer, lifts, bin room, common-area bathrooms. You learn quickly which three a given building cares about.
- Exceptions, at the time. Bin room locked, function on in the hall, water off. Recorded on site in two taps, not remembered at the depot a week later.
The test is one minute. If a manager queries a clean, can you answer with something dated inside a minute, without ringing anyone? If not, you do not have records, you have recollection.
The second problem: the contract view
Proving one visit is the easy half. The harder half is the contract: showing that the whole month ran, that no site quietly dropped off the round when a cleaner left, and that what you invoiced matches what you actually serviced.
That last one is where the money usually is. Sites get added mid-contract, make-goods get done as favours, an extra fortnightly visit gets squeezed in for a difficult building. If the run sheet and the invoice are two documents maintained by two different people, the gap between them is work you did for nothing. A waste operator I built for had that gap running at around $30,000 a month, evidenced once every service carried a timestamp and a photo. The Howyabin case study has the detail.
Same shape in the neighbouring trades
If you also run, or compete with, pest control, pool servicing, hygiene services or facilities maintenance, the problem is identical and so is the fix. It is the run shape that matters, not the task: recurring sites, a driver who knows the round, and work that becomes invisible the moment it is finished. The general version of this is on proof of work for service crews.
Where to start
Start with the single site that generates the most queries, not with the whole portfolio. Get arrival, scope tick-off and two photos captured properly on that one, run it for a month, and see whether the queries stop. They usually do, and then you know what the rollout is worth before you pay for it.
Builds start from $1,500 fixed for a smaller one and $3,500 for a bigger one, or inside Ops Care from $1,500 a month, which is where most contract cleaners land because scopes change constantly. The Trades Tech Leak Audit maps your setup first, free, and the cleaning-specific version of this conversation is on the cleaning page.
What contract cleaners ask me about proving the work.
What should a strata cleaning service record actually contain?
Enough to end an argument in one link: the site, the date and time on site, who attended, what was done against the scope, and a photo of anything a committee is likely to query. Bins, foyer, lifts, common-area bathrooms. It does not need to be elaborate. It needs to be dated, attributable, and produced without ringing the cleaner who was there.
A building manager says a clean was missed and it was not. What now?
If you have nothing dated, you usually wear it, because their record is the only record. That is the whole problem. Once every visit carries a timestamp and a photo, the conversation changes shape entirely: you send one link, and the dispute ends there rather than in a credit note.
We already use a cleaning app with photo upload. Is that enough?
For a single clean, often yes. It falls down on the contract view: proving the whole month ran, spotting the site that has been quietly skipped three weeks running, or producing twelve months of history for one building when the contract goes to tender. Most cleaning apps are built around the visit, not around the contract.
Do the cleaners have to do more paperwork?
They should end up doing less. The version that works is a few taps at the site: arrived, done, here is a photo, here is the exception. If it takes longer than that it will not get done properly, and a half-filled record is worse than none because you start relying on it.
What does this cost?
A smaller build starts from $1,500 fixed and a bigger one from $3,500, scoped in writing first. Most contract cleaners end up on Ops Care from $1,500 a month instead, because sites and scopes change constantly and the system needs to change with them.
Not sure what fits your shop? Ask me, not a sales rep.
A 30-minute Tech Leak Audit and a one-page written finding inside 48 hours. Three prioritised fixes, no pitch, and the report is yours either way.