Depot and workshop cleaning planning for Bankstown civic and service sites

Depot amenities carry an unusual load. Crews arrive together at the start of a shift, use the facilities within a short window, and return together at the end. Lockers, boot areas, showers and lunchrooms absorb mud, dust and moisture in concentrated bursts rather than steadily, and a frequency set for an office environment will always look inadequate against that pattern.

The scope should be built around those two peaks. A reset before the morning arrival and a second attendance after the afternoon return will hold the standard far better than a single mid-shift clean, even if the total hours are similar. Consumables need checking against the same pattern, since a dispenser that empties by mid-morning is effectively empty all day. Where crew numbers vary seasonally, the plan should say how the amenity attendance changes with them rather than holding a fixed figure through the year.

A depot store contains tools, parts, consumables and small plant, much of it belonging to identified staff or recorded on an asset register. Cleaning around those items is straightforward. Moving them is not, because relocation creates a search the next morning and can put an item outside its recorded location. That distinction should be explicit rather than left to judgement.

The workable rule is that the cleaner cleans surfaces, floors and access routes, and does not move, sort or dispose of stored items. Where an area is genuinely inaccessible because of accumulated material, that is reported as an exception. The depot then clears it or accepts that the floor beneath will not be reached, and both parties know which. Recording the rule in the proposal means a new attendant applies it without needing to ask, which matters on a site where the depot supervisor is rarely present at cleaning time.

Public-sector and civic operators usually need a record rather than an assurance. That does not require an elaborate system. A simple attendance record showing date, zones completed and exceptions raised, held in a form the client can retrieve, answers most questions before they escalate and gives a supervisor a basis for reviewing performance against the agreed schedule.

The record is also what makes a review meaningful. If the same exception appears three months running, that is a scope problem rather than a performance problem, and it can be fixed by changing frequency or method. Without a record the conversation is about impressions, and impressions tend to be formed on the worst day rather than the average. Holding the record somewhere the client can retrieve it without asking is what makes it useful, since a record that requires a request is rarely consulted.