Spill response procedures for cleaning staff at Matraville industrial premises

A procedure that starts with instructions assumes the person already knows what they are dealing with. On an industrial floor that is rarely true at two in the morning. Classifying first, by substance and volume, gives the cleaner a decision they can actually make: is this on the known list at a volume I am equipped for, or is it not. Everything else follows from that single question.

The known list should be short and specific to the site: the products routinely used, the volumes typically spilled, and the equipment provided for each. Anything outside the list is treated as unknown regardless of appearance, because a substance that looks like water on a manufacturing floor may not be. That default protects the cleaner and removes the pressure to guess. Keeping the list on the wall of the cleaner's store, rather than in a document, is what makes it usable at the moment the decision has to be made.

A spill that reaches a stormwater drain becomes an environmental matter with consequences well beyond cleaning. Proximity to a drain should therefore escalate the response regardless of substance or volume. That means knowing where the drains are, which is information the site holds and the cleaner usually does not, and it belongs in the induction rather than in a document.

Containment equipment has to exist and be reachable. Absorbent material, a drain cover or bund, and something to isolate the area should be stored where a cleaner can get to them quickly, not in a locked store with a business-hours key. Sites frequently write an excellent procedure and locate the equipment somewhere the night shift cannot access it. Walking the drain locations during induction, rather than describing them, is what makes the rule usable by someone working alone at two in the morning.

Every spill response should generate a short record: what, where, how much, what was done, who was contacted and what remained outstanding. That is useful for the immediate incident and considerably more useful in aggregate, because repeated spills in the same location almost always have a cause that can be addressed by equipment, handling or storage changes. Keeping those records with the site's own incident log, rather than in a contractor file, means the pattern is visible to whoever reviews site safety.

Clean Best reports spills encountered as well as those responded to, including small ones that were dealt with routinely. A site that only hears about significant events has no visibility of the pattern building underneath them, and the pattern is usually where the preventable cause sits. That reporting is part of the service rather than an optional extra.