A container used in a food or other regulated application has to be cleaned, and it has to be shown to have been cleaned. Those are two separate requirements, and the second is the one that fails in an audit. Where a wash process is running well but nothing is written down, the operation is compliant in substance and non-compliant on paper, which is how most findings are raised.
What the record has to show
What was cleaned, when, by what method, with what detergent at what concentration and temperature, and who did it. Six fields. Where a record has the first three and not the rest, it demonstrates that cleaning happened and not that it was adequate – and adequacy is what the question is about.
Why the detail matters
A wash at the wrong temperature or the wrong concentration does not achieve what the process claims, and the record is the only way to show it was right. Where a record says only “washed”, it cannot demonstrate anything about the conditions, and an auditor will reasonably treat it as no record at all.
Verification, not just recording
A record says what was done; a verification says it worked. The usual verification methods are a visual check against a standard, a swab test for residue or microbiological contamination, or an ATP test where that is the accepted method. Where a hygiene programme has records and no verification, it is documenting an assumption.
How often to verify
Often enough to detect a failure before it affects product, which in practice means a routine schedule plus an additional check whenever something changes – a new detergent, a new operator, a change in throughput. Where verification happens only annually, a problem can run for months inside a documented process.
Where the container design helps
A container that is easy to clean and easy to inspect makes the whole programme easier. Smooth surfaces without deep recesses, no crevices at the wall-to-base joint, drain holes that let water out, and a material that tolerates the cleaning regime. All four are specification items and they are the difference between a hygiene programme that works and one that is a permanent struggle. The cleaning side is in what polypropylene tolerates in a wash.
What happens with mixed duties
A container that carried a non-food product and then carries a food product needs a validated cleaning step between the two, and it needs to be identifiable as having had it. Where a fleet serves both, segregation by container is far simpler than validating a changeover – which is why many operations simply keep separate fleets.
How long to keep the records
Usually the longer of the product’s own shelf life plus a period, or a defined retention in the customer’s or the standard’s requirement. Where a fleet serves several customers with different requirements, the longest applies. Keeping records that long is cheap once the system exists and impossible once they have been disposed of.
What an auditor will ask
To see the procedure, the record for a specific date, the verification results for the same period, and what happens when a check fails. The fourth is the one most operations cannot answer, because the failure path was never defined. Defining it – what gets re-washed, what gets scrapped, what gets investigated – is a short piece of work that closes the most common finding.