Assembling a defensible cleaning compliance file for a Sydney CBD tenancy

Building management wants to know the contractor is insured, inducted and approved for access, and it will check before allowing anyone into the tower. An insurer, if a claim arises, wants to know what happened, who was present and what the condition was beforehand. Internal governance wants to know that the arrangement was set up properly, is reviewed, and is delivering what was agreed.

The overlap is substantial: insurance, screening, induction, service records and a review mechanism cover all three. Building the file with the three audiences in mind mainly changes emphasis rather than content, but it does prevent the common outcome where a tenancy has excellent access documentation because building management asked for it, and nothing at all about what was actually done in the tenancy last quarter. Building it once, at mobilisation, is also considerably cheaper than assembling three partial files in response to three separate requests.

The written scope, because almost every subsequent question refers back to it. Attendance records showing who was in the tenancy and when, which answer both security and claim questions. Periodic completion records with dates, which resolve the most disputed category at any review or exit. Inspection findings with closures, which demonstrate a system rather than an assurance. And the insurance certificate, current and naming the right entity.

Five documents, and four of them accumulate automatically once a process produces them. The scope is the only one requiring deliberate effort, and it is also the one that determines what the others mean. A file with detailed records measured against a vague scope cannot settle anything, because there is no agreed standard to measure the records against. Together those five cover almost every question a tenancy will face, and four of them require no ongoing effort once the process producing them is running.

CBD tenancies change: floors are added or given up, headcount shifts, fit-outs happen, managers move on. A file that was accurate at mobilisation drifts steadily, and the drift is invisible because each individual change seems too small to warrant reissuing a scope. Two years later the document describes a tenancy that no longer exists and the records describe work performed against it. Fit-outs deserve particular attention, since a refurbished floor changes both the areas and the surfaces and rarely prompts anyone to revisit the cleaning arrangement.

An annual review catches most of this in ten minutes: does the scope describe the tenancy, are the named cleaners the ones attending, has building management added a requirement, and is every document current. Attaching that to an existing annual cycle gives it a prompt. Clean Best raises the review rather than waiting, since a drifted file reflects on both parties equally.