By Igor Published · Updated

SQAS Tank Cleaning Inspections: from safety round to cleaning verification

SQAS Tank Cleaning assesses a tank cleaning station on more than just cleaning quality. A full inspection program covers six areas: on-site safety inspections, storage of cleaning chemicals and (hazardous) waste, condition monitoring of technical installations and technical inspections, security inspections (including food defense), BBS behavioral observations, and — as the closing piece for food cleanings — validation and verification of cleaning programs. This article shows how to set up, carry out, and follow up on these 6 components together in one inspection program.

Why a broad inspection program makes the difference

An SQAS Tank Cleaning assessment evaluates the entire station, not just whether the compartment leaves the cleaning bay clean. A station that steers only on cleaning speed and quality and leaves the rest to chance runs into the same two symptoms, whichever component is involved:

  • The same deviations keep recurring — a drum of cleaning agent not stored on a spill tray, drivers walking around the container depot unescorted, a cleaner working on the tank without using fall protection — because the observation was made, but never followed by an action.
  • Checking for the sake of checking. As long as the round was walked, the requirement is considered met, without safety, security, or cleaning quality actually improving.

A well-designed inspection program closes those gaps: it provides evidence for an SQAS Tank Cleaning assessment or customer audit, keeps safety, security, and technical condition demonstrably up to standard, and ensures cleaning quality is a verifiable result rather than an assumption.

The seven components of the inspection program

An SQAS Tank Cleaning inspection program consists of seven themes, each with its own rhythm, owner, and checklist — but best brought together under one inspection platform with shared action follow-up.

  • On-site safety inspections — classic workplace inspections of the cleaning bay, the site, and the offices: escape routes, emergency exits, PPE use, housekeeping, hazard zones, first-aid and eyewash facilities.
  • Storage of cleaning chemicals and (hazardous) waste — storage of cleaning agents (compatibility, spill trays, labeling, ventilation), and segregated storage and disposal of hazardous and non-hazardous waste, including licensed waste streams and registration.
  • Condition monitoring of technical installations — the state and operation of pumps, water softeners, steam boilers, water treatment, compressors, piping, and rinse heads; not certifying, but flagging wear and degradation before it leads to a failure or incident.
  • Technical inspections — legally required and periodic inspections: pressure vessels and boilers, lifting and fall-protection equipment, electrical installations, fire extinguishers, ATEX zoning, gas detection equipment.
  • Security inspections, including food defense — access control to the site and critical installations, fencing and lighting, camera surveillance, locking routines, and specifically for food defense: protection against intentional contamination of food tanks, key and access management for food-related zones, and control over unauthorized access to cleaning agents and water tanks used for food cleanings.
  • BBS behavioral observations — structured observation of behavior on the floor: working at height, confined spaces (gas measurement, hole watch), hot water and steam, PPE use, depressurizing tanks.
  • Cleaning verification — compartment inspection, final rinse-water test, cleaning documentation, and the release decision; for food loads supplemented with validation and verification of the cleaning program itself (see below).

For tank cleaning stations that also carry out heating activities, or that operate a container depot and/or workshop, these themes apply equally.

Whichever regime you report under — SQAS Tank Cleaning, EFTCO FOOD, a customer-specific protocol — the execution logic of these seven components is comparable. What differs are the reporting and scope requirements: which topics you inspect, what evidence a customer or assessor expects. We focus on how you carry out these inspections effectively at a tank cleaning station that cleans tank and bulk trailers, and tank and silo containers, day in day out, in chemicals, food, and feed.

Designing the inspection program

You design a workable program around seven elements — scope, frequency, role division, time investment, training, and action management — plus analysis afterward, applied to each of the seven components.

1. Scope per component, not one checklist for everything. Each of the seven components requires its own checklist with sharp, testable questions, drawn up with the people who know that component best: the technical department for condition monitoring and inspections, the HSE officer for safety and security, the cleaning acceptor for food cleaning verification, the operations manager for BBS. One generic "station walk-through" checklist won't produce a usable result for any of the components.

2. Check on risk, not on calendar. For each component, determine how likely a deviation is and how severe the consequence is if it goes undetected:

  • High risk + high criticality — for example, cleaning verification before a food load following a difficult product: full verification, a second pair of eyes, complete documentation.
  • High risk + low criticality — for example, condition monitoring of a pump with known wear: more intensive, more frequent checks.
  • Low risk + high criticality — for example, access security to a food storage area: standardized checks with independent verification.
  • Low risk + low criticality — routine safety round: standard checks with trend monitoring.

3. Role division with independence on the heaviest decision. The cleaner or operator is the first-line checker on the floor, but place the release decision for a food tank, or the condition assessment of a critical installation, with a second person or specialist — not with whoever carried out the work itself. BBS observations must be carried out by the supervisor; technical inspections belong to a competent person or an external inspection body.

4. Time investment. Too many checkpoints at too high a frequency leads to rushed rounds, across all seven components. Don't plan more than can genuinely be assessed — a proper condition assessment or cleaning verification isn't something you do in passing.

5. Training and instruction per component. A checklist for security or technical condition monitoring requires different knowledge than a BBS round. Make sure every inspector knows what they're looking at and why — especially for food defense and food-related cleaning verification, where the risk isn't always visible.

6. One shared action management system. A finding — whether it comes from a technical inspection, a BBS observation, or a cleaning verification — is followed by feedback, assignment, a deadline, and follow-up. Bring all seven components together in one action module: this surfaces patterns that a separate checklist would miss, and an SQAS Tank Cleaning assessor specifically wants to see non-conformities followed up station-wide.

7. Analysis. Improvement requires trend analysis across all components: which installations structurally cause failures, which unsafe behavior keeps recurring, where does chemical or waste storage keep running into the same deviation? Track a handful of hard indicators per component and adjust accordingly.

Carrying out the inspection in practice

Pay attention to the following seven steps: preparing, observing, recording evidence, classifying, naming an action, closing out with the person involved, and reporting immediately.

  1. Preparation. Determine what you're going to check and why: for cleaning verification, the previous load / compliance with the cleaning program and its results; for condition monitoring, determine the checkpoints that reveal the condition; for a security round, the critical inspection points. Bring the checklist app on your phone or tablet.
  2. Into the cleaning bay or onto the site. Assess what you actually find, not what the procedure says: the condition of a pump or pipe, an operator's behavior, whether a gate or door is closed, housekeeping on the cleaning bay.
  3. Record evidence on the spot. Photograph every deviation, and preferably a compliant situation as reference too. Record measurement results (rinse-water temperature, ATP reading, pressure) and identifying data (compartment, installation, location) immediately.
  4. Classify immediately. OK / Not OK / N/A, or a percentage score per area. For BBS: classify behavior (safe / unsafe / near-miss) and severity. For food cleaning verification: non-conforming measurement results such as ATP and allergens, turbidity, conductivity, pH, or odor, block the release.
  5. Name and assign the action. Repair, clean up, take an installation out of service, a conversation about fall protection or behavior? Record the action and the owner immediately.
  6. Close out with the person involved on the spot. Read out loud what you have recorded. The person involved corrects anything inaccurate and confirms the rest — that prevents after-the-fact discussion and reinforces ownership.
  7. Generate the report immediately. With a digital app the inspection is complete as soon as findings and photos are in it: the report — inspection, examination, or observation report — is available right away.

From practice

During an SQAS assessment, the following came to light. During a chemical cleaning bay check, "discharge via a closed drain line" was routinely marked "OK," while the pump wasn't working and the line therefore couldn't be used. The cleaners hadn't reported the fault, and the checker had been more focused on ticking boxes than carrying out a genuine check. The fix lay in repair and training: repairing the pump and training the cleaners and the inspector. Cleaners must report defects immediately (this concerned their own direct safety, given exposure to carcinogenic substances). The inspector, because they hadn't sufficiently understood the importance of a critical inspection. Photos of the closed drain line in use were made mandatory.

Validation and verification of cleaning programs for food cleanings

For food loads, a T01 inspection code on the ECD is not sufficient evidence that the cleaning program itself is sound. Validation and verification of the cleaning program demonstrate that the program is capable of achieving the desired cleaning result, without this having to be proven after every single cleaning with a full test package (ATP, allergen, turbidity, pH, conductivity, millipore, etc.). Prior validation demonstrates that the cleaning program — the procedure, the chosen agents, temperature, time, and mechanical action — is structurally capable of cleaning a compartment food-safe after a given product. Verification tests whether this is actually the case. Both belong in the inspection program, but they are not the same:

  • Validation is carried out when introducing a new product–cleaning agent combination, a changed procedure, or new equipment.
  • Verification is the periodic confirmation that the validated procedure is actually and consistently being followed and delivers the correct result: demonstrating — for example with ATP measurements, microbiological sampling, or allergen tests — that the procedure achieves the intended result under real-world conditions, including a margin for variation.

This is separate from customer requirements. Some customers require a verification of the cleaning result for every cleaning, but that is not always the case.

An SQAS Tank Cleaning assessor carrying out EFTCO Food assessments wants to see both: prior validation and the verification evidence that the procedure is actually followed in practice and is effective. Include this explicitly as its own scope component within cleaning verification, with its own frequency (validation upon change, verification periodically — for example annually) and its own evidence requirements. For the full approach — which tests when, how to build a validation file, and how to set up the verification sample — see our guide Carrying out validation and verification of food and feed tank cleaning.

A finding only becomes valuable once it is immediately followed by an assigned action with a deadline and verification — regardless of which of the seven components it comes from. An inspection without action management is busywork. This is where many programs go wrong: the finding is logged and only reaches the person who needs to act on it weeks later. By then, the context is gone and the action stays half-hearted. Three rules to prevent this:

  • Strike while the iron is hot. Decide immediately after the inspection which action needs to be taken, by whom, and within what timeframe. A fall harness showing damage: discard and replace it immediately.
  • Verification is part of the action, not an afterthought. The action isn't "repaired," but "repaired and demonsrtated to now comply" — a photo, a measurement, or a re-check as evidence.
  • Recurring findings are a system signal. The same installation failing repeatedly, the same door left open, the same product that won't release? Then the procedure, the maintenance schedule, or the safety culture isn't effective. Fix the system, not the incident.

Pitfalls we encounter at tank cleaning stations

  • Isolated silos per component. Technical, HSE, security, and cleaning each keep their own list, without a shared overview — so a pattern spanning components (for example, recurring failures due to overdue maintenance) goes unnoticed.
  • Condition monitoring that only starts once something is already broken. Without periodic, structured checks, wear only becomes a finding at the point of failure — too late to course-correct.
  • Security and food defense treated as a formality. A door that's "usually" locked, or an access list that isn't maintained, isn't security in practice.
  • No evidence for a deviation. "Waste not labeled" or "pump leaking" without a photo and location becomes unrecognizable within a week.
  • Action without a verification moment. "Fixed" is not the same as "checked whether it now complies." Without effectiveness verification, you're releasing the same risk again.

Frequently asked questions

What components make up an SQAS Tank Cleaning inspection program exactly?

Six components: on-site safety inspections, storage of cleaning chemicals and (hazardous) waste, condition monitoring of technical installations and technical inspections, security inspections (including food defense), BBS behavioral observations, and cleaning verification — with validation and verification of the cleaning program as an additional component for food cleanings.

How often should I schedule each component?

That differs per component and is risk-based. Technical inspections follow the legal or manufacturer's schedule. Condition monitoring is planned based on the wear sensitivity and criticality of the installation. BBS observations and safety inspections are planned on a fixed frequency and at the risk locations. Security inspections at least periodically, with extra attention after changes to access or the site.

Who carries out these inspections?

A combination of roles: the supervisor for BBS, the technical department for condition monitoring, a competent person or external inspection body for technical inspections, and the HSE or security officer for safety and security inspections including food defense. Bring the results together in one system, even though the people carrying them out differ.

How does cleaning verification relate to validation and verification of the cleaning program?

Cleaning verification demonstrates that one specific cleaning succeeded. Validation and verification of the cleaning program demonstrates that the cleaning program itself — for a given product(group)–program combination — is suitable; it confirms that the validated procedure is actually being followed and is effective. For food cleanings, both belong in your program. See the guide Carrying out validation and verification of food and feed tank cleaning.

Can I use digital photos as evidence?

Certainly. Photo evidence strengthens a finding and shows that your judgment is based on an observation made in the field. Make sure photos are unique per inspection — reusing photos is out of the question. Dated and traceable in a controlled system, they hold up under any check.

How do I measure whether my inspection program is working?

Track a handful of indicators per component: (1) the number of re-cleanings and their causes; (2) complaints about residual load or contamination; (3) the share of BBS observations showing risk behavior, and the trend; (4) failures and rejections from condition monitoring and technical inspections; (5) security incidents or deviations in access control; (6) the share of deviations resolved within deadline with verification; (7) the outcomes of customer audits and SQAS Tank Cleaning assessments over time.

About the author

Igor Bots — SQAS/ESAD/EFTCO/CDI assessor and DGSA (ADR), ISO Lead Auditor 9001/14001/50001. Extensive experience with assessments and inspections in tank cleaning. LinkedIn

Get started today

Start a free 30-day trial with Easy to Inspect — with ready-made checklists for tank cleaning stations. Adapt them with the checklist builder and follow up non-conformities station-wide with the integrated action module — exactly what you need for an SQAS Tank Cleaning assessment. Your first inspection runs within an hour. Start your free trial.