The frequency at which a reusable container should be washed is one of the questions that gets answered by habit: either every trip, which is expensive, or when it looks dirty, which is not a standard. The correct interval is determined by what goes into the container next and what the consequence of contamination is, and those differ by lane rather than by container.
What washing is actually for
Two different things, and they have different intervals. Removing contamination that would affect the next load – oil, swarf, product residue, anything that transfers. And demonstrating cleanliness where an auditor or a customer requires it. The first is a technical requirement that can be assessed; the second is a documentary one that has to be met regardless. Where the two are conflated, containers get washed for appearance on lanes where nothing needs it.
The next load decides
A container that carried raw castings and will carry raw castings again does not need washing between trips. The same container carrying finished parts for assembly does. Where a fleet serves several duties, the interval is per lane – and that means the containers have to be identifiable by lane, which is a marking question rather than a washing one.
What visual inspection misses
A container can look clean and carry an oil film, a fine metal dust, or a residue from a previous product. Those are invisible and they are exactly what transfers to the next load. Where cleanliness matters, the standard has to be a test rather than a look – a wipe test, a visual check under good light at close range, or a documented wash. A “looks clean” standard fails the first time it is audited.
Where washing every trip is genuinely required
Food contact, pharmaceutical and medical applications, anything with a documented hygiene requirement, and any lane where the previous contents could contaminate the next in a way that matters. In those cases the interval is not a decision, it is a requirement, and the cost is part of the cost of that application rather than something to be optimised away.
Where it is not required
Closed loops carrying the same part between the same two points, internal lanes with non-sensitive contents, and any application where the container is effectively dedicated. A container that carries the same casting from the same foundry to the same machine does not need washing between trips, and washing it is a cost with no corresponding benefit.
The cost of over-washing
Water, energy, detergent, labour, floor space, and the container’s service life – because every wash cycle is handling, and handling is what wears containers out. A fleet washed every trip on a lane that did not need it is paying for the washing and losing containers faster. Where a washing programme is being justified, the container life cost is the term usually missing.
Setting the interval
Identify what the container carries, what it carries next, and what the consequence of cross-contamination is. Where the consequence is nil, wash on condition with a defined inspection. Where it is a quality risk, wash every trip. Where it is a documented requirement, wash every trip and record it. Three answers, and the lane tells you which applies.
Recording it
A wash record – which containers, when, by what method – is cheap to keep and it is what turns a washing programme from an assertion into evidence. Where a customer asks how containers are cleaned, the record is the answer, and where it does not exist the answer is an explanation that will not satisfy an auditor. The method itself is covered in what polypropylene tolerates in washing.