What Your Industrial Cleaning Must Prove on Inspection Day
When a Canadian manufacturing facility gets inspected — by a provincial occupational health and safety officer, an environmental ministry inspector, a federal food safety inspector, or an insurance loss-control auditor — the cleanliness of the plant is not what determines pass or fail. The documentation behind the cleanliness is what determines it.
A clean plant with no documentation is an inspection risk. A documented cleaning program with minor deficiencies is almost always a pass with corrective-action recommendations. Here is what your industrial cleaning program needs to produce to hold up on inspection day.
The Seven Documents an Inspector Will Ask For
When an inspector walks into a plant, the documentation conversation is usually structured the same way regardless of which regulatory regime applies:
1. Written Cleaning SOPs
A Standard Operating Procedure for each cleaning task, specifying:
- Scope (what is cleaned, what is not, and why)
- Frequency (daily, weekly, per turnaround, per batch)
- Method (chemistry, equipment, temperature, dwell time)
- Roles (who cleans, who supervises, who validates)
- Acceptance criteria (what "clean" means, measurable if possible)
The SOP has to be written. A verbal process does not hold up on inspection. The SOP has to be current (recently reviewed, dated, version-controlled). And the people doing the cleaning need to be trained on the SOP they are following.
2. Cleaning Schedule and Completion Records
A calendar of scheduled cleaning activities with completion records. For each cleaning event: date, start/end time, scope completed, person or crew who performed the work, person who verified. Signatures, initials, or electronic records attributable to specific individuals.
Inspectors test this by asking for records from a random date. If you can produce records for the date requested within 5 minutes, your program is functional. If you cannot, your program has holes.
3. Chemistry Inventory and Safety Data Sheets
A list of every cleaning chemistry in use, with current SDS on file and accessible. WHMIS 2015 compliance is tested on: (a) labelling on secondary containers, (b) SDS accessibility to workers, (c) worker training records for the chemistry they are using.
The most common inspection finding in Canadian plants: secondary containers (spray bottles, mixing buckets) that lack GHS-compliant labels. This is a simple fix, and simple to audit internally — and the most common reason for minor violations on OHS inspections.
4. Validation and Verification Records
For regulated industries (food, pharma, medical device, water), cleaning validation is a scheduled activity with documented outcomes:
- ATP bioluminescence results with pass/fail thresholds defined
- Swab test results for allergens, pathogens, or target contaminants
- Microbiological plating results
- Visual inspection results against defined acceptance criteria
Validation failures should have corrective action records showing: what failed, what re-cleaning was done, what root cause analysis was performed, what prevention was put in place.
The regulator is not looking for zero failures. They are looking for a system that catches failures, responds appropriately, and improves over time.
5. Training Records
Every person who performs or supervises cleaning work needs a training file showing:
- WHMIS 2015 training, dated, refresher cycle documented
- SOP-specific training (training on the procedures they execute)
- Safety training relevant to their role (confined space, hot work, LOTO, PPE use)
- Competency verification (test, observation, sign-off by supervisor)
Agency labour and contractor crews need the same documentation. If your contractor's crew cannot produce training records on request, their WHMIS compliance is not legally transferable to your facility.
6. Audit and Corrective Action Records
Internal audits of the cleaning program, scheduled quarterly or per SOP. Findings documented. Corrective actions assigned with owners and due dates. Verification that corrections were effective.
A mature cleaning program has an internal audit log that shows: findings go from minor to zero over time as the program improves. An inspection will ask for this log.
7. Incident and Near-Miss Records
Any incident or near-miss related to cleaning work — chemical exposure, slip/trip from wet floor, equipment damage from cleaning, cross-contamination event — recorded, investigated, and documented with root cause analysis and corrective actions.
Plants that report zero incidents in a high-activity cleaning program are not safer — they are under-reporting. Inspectors know this. A documented near-miss log with investigations demonstrates safety culture.
Industry-Specific Add-Ons
Depending on the industry, additional documentation applies:
Food manufacturing (CFIA, federal + provincial):
- Preventive Control Plan (PCP) with cleaning as an identified control
- Sanitation verification logs tied to HACCP program
- Allergen control program documentation
- Pest control integration with sanitation program
Pharma and medical device (Health Canada GMP):
- Cleaning validation master plan with protocol-specific cleaning validations
- Change control records for any SOP revision
- Qualified personnel records
Environmental (provincial MECP / MELCC / AER / others):
- Spill response and cleanup documentation
- Wash-water discharge permits and compliance records
- Hazardous waste manifests for residues
- Environmental management system integration
Occupational health and safety (provincial labour ministries):
- Joint health and safety committee inspection records
- MSDS / SDS currency for all chemistry
- Written exposure control plans for specific hazards
- Working-at-heights documentation for elevated cleaning work
The Role of the Cleaning Vendor
If your cleaning is performed by an external contractor, part of the documentation is theirs and part is yours.
Contractor produces:
- Their own WHMIS training records
- Their own chemistry SDS and chemistry inventory
- Their own supervisor training and safety records
- Completion records per shift, signed by the crew supervisor
- Incident records for incidents involving their crew
You (the plant) produce:
- The site-specific SOP the contractor is executing
- The site-specific hazard briefing given to the contractor
- The internal audits of contractor performance
- Integration of the contractor's work into your validation and food safety program (if applicable)
A good contractor understands the documentation split and provides their portion automatically, usually through a cloud portal the client can access. A poor contractor produces a monthly invoice and nothing else.
The Inspection Day Conversation
When an inspector arrives, the conversation goes better when the plant manager can do three things:
-
Produce the documentation within minutes, not hours. A physical or electronic file system that is organized and current. Fumbling through binders looking for the right record is a bad signal.
-
Explain the program in plain language. "Our cleaning is scheduled through SOPs, executed by our contractor, verified by our internal team, and audited quarterly. Here are the records." Programmatic confidence sets the tone.
-
Own minor findings and propose corrections on the spot. "Yes, I agree that the secondary container labelling is inconsistent. We will have that corrected by end of week and I will send you the documentation." Ownership shifts the inspection from adversarial to collaborative.
Plant managers who have been through 20+ inspections know this rhythm. The ones who have not tend to over-explain, produce documents that are not requested, and create the impression that the program is held together by luck.
The Ferrix Documentation Standard
Ferrix maintains a documentation package for every client that includes: the cleaning SOPs we execute, WHMIS training records for every crew member on site, chemistry inventory and SDS, per-shift completion records signed by our supervisor, and monthly performance summaries.
The package is accessible to the client through a web portal, updated in real time. On inspection day, the client has one source of truth — not a binder to assemble.
If you are working with an industrial cleaning contractor who cannot produce this standard of documentation, it is worth asking why. The cost of getting documentation right is marginal. The cost of getting caught without it on inspection day is substantial.