Sanitation Standard Operating Procedures: How to Write an SSOP That Passes Audit

A sanitation standard operating procedure is the written document that says exactly how a specific thing gets cleaned, with what, how strongly, for how long, by whom, and how you prove it worked. It is the difference between sanitation as a habit and sanitation as a control.

Most SSOPs fail audit for the same reason: they describe intent rather than parameters. "Clean the filler thoroughly" cannot be monitored, corrected or verified. "Clean the filler with X at 2% concentration, 40°C, 10 minutes contact, then rinse and sanitise with Y at 200 ppm for 1 minute" can.

Not regulatory advice. Requirements under the Safe Food for Canadians Regulations and CFIA preventive control guidance are enforced by the CFIA. Follow your own plant's preventive control plan and confirm specifics with your food safety team.

Key takeaways

• Write one SSOP per area or piece of equipment, not one for the whole plant.
• Every SSOP needs five parts: procedure, monitoring, corrective action, verification, records.
• Specify parameters, not intentions: chemical, concentration, temperature, contact time, method.
• The person who does the cleaning should be able to follow it without asking questions.
• Review it when equipment, chemistry or product changes — an out-of-date SSOP is an audit finding.

What an SSOP is, and what it is not

An SSOP lives inside the plant's preventive control plan. It is evidence, and it is auditable.

A related term worth separating: sanitation standard operating procedures are sometimes called cleaning SOPs or sanitation procedures. The naming varies; the five-part structure does not.

The five required parts

Every SSOP needs all five. If one is missing, the document cannot function as a control.

1. Procedure

The steps, with parameters. This is the bulk of the document.

• What is being cleaned — the specific equipment, line or area, identified unambiguously.
• When — frequency, and critically whether it is per shift, per production run, per changeover, or per day.
• Who — the role responsible, and the role that verifies.
• Chemistry — the specific product, by name and supplier, never "appropriate sanitiser".
• Concentration — with the units, and how it is measured and confirmed.
• Temperature — where it matters, which is most of the time.
• Contact time — how long the chemical stays on the surface.
• Method — manual, COP, CIP, foam, spray, immersion; and the equipment used.
• Sequence — dry clean, pre-rinse, wash, rinse, inspect, sanitise, drain, reassemble.
• Disassembly — what is taken apart, and what must never be taken apart by cleaning staff.
• Reassembly — who does it, and how readiness is confirmed.

2. Monitoring

How you confirm the procedure was followed and effective.

• Visual inspection — for soil, residue and completeness. Subjective, so describe what to look for.
• Chemical concentration testing — titration, test strips or a meter, with the acceptable range.
• Temperature checks — for wash solutions and CIP cycles.
• Time verification — CIP cycle records, or logged start and finish times.
• Flow or pressure — where the procedure depends on it.
• ATP or protein swabs — for rapid verification of cleanliness.
• Who monitors, how often, and where it is recorded.

Monitoring must be practical. If the procedure says to test concentration every 15 minutes and nobody does, the SSOP is fiction and the audit will show it.

3. Corrective action

What happens when monitoring shows a deviation.

• Stop and re-clean. A deviation means the surface is not verified clean.
• Re-monitor after re-cleaning.
• Assess product impact. This is the plant's job, not the cleaner's — but the cleaner must escalate immediately so it can happen.
• Record it. Date, time, what deviated, what was done, who decided.
• Escalate to the named role if the deviation cannot be corrected, or if product may be affected.

The most common audit failure here is silent re-work: cleaning again without recording that the first attempt deviated. That destroys the integrity of the whole system.

4. Verification

Independent confirmation that the SSOP is effective — not just that it was followed.

• Environmental swabbing on a defined schedule and grid.
• ATP testing of surfaces after cleaning.
• Allergen-specific testing after changeover cleaning.
• Microbiological testing where the plant's programme requires it.
• Supervisory audit against the written procedure.
• Trend review — are results stable, improving or drifting?

Verification frequency and methods are usually set by the plant's food safety team. Cleaning staff often perform sample collection under direction.

5. Records

What is kept, where, for how long, and by whom.

• Cleaning records: area, date, time, shift, procedure version, operator.
• Parameter records: concentration, temperature, contact time.
• Monitoring results and verification results.
• Deviations and corrective actions.
• Training records for the people performing and verifying the work.
• Retention period, usually set by the plant and its regulatory obligations.

Writing the procedure so it is actually followed

A well-written SSOP is usable at 2am by someone who did not write it.

• Write it in the order the work happens, not in the order it is audited.
• Use plain language and short numbered steps. Many plants operate in multiple languages; comprehension matters more than elegance.
• Show, don't only tell. Photographs of correctly dismantled equipment, of what "clean" looks like, and of acceptable versus unacceptable results, are worth more than paragraphs.
• Put parameters in a table so they can be read at a glance.
• State what is forbidden. "Never use product X on surface Y." "Never move equipment between zones."
• Include the escalation route — who to call, and how quickly, when something is wrong.
• Version and date it, and keep superseded copies out of circulation. Two versions in use is an audit finding.

Parameters: getting specific

This is where most SSOPs are weakest. Compare:

The strong column can be monitored. The weak column cannot, and an auditor will say so.

Common SSOP findings

Learn these and you avoid most audit trouble.

• No measurable parameters — nothing to monitor.
• Chemistry named generically, or a product that changed without the SSOP being updated.
• Frequency described as "as required", which is unenforceable.
• No monitoring records, or records completed in batches after the fact.
• Deviations not recorded — silent rework.
• Verification missing entirely, or done by the same person who performed the cleaning with no independence.
• Out-of-date versions in circulation.
• No training records for the people named in the procedure.
• Harbourage points not addressed: drains, cracks, hollow frames, worn seals, wet corners.
• Allergen changeover not covered separately where the plant handles allergens.

Keeping SSOPs current

An SSOP is a living document.

• Review on a set cycle — commonly annually at minimum.
• Review when chemistry changes. A new sanitiser means new concentration and contact time.
• Review when equipment changes, including like-for-like replacements that behave differently.
• Review after a deviation trend or a verification failure.
• Review when the product range changes, especially new allergens.
• Retire superseded versions properly. Archive them, but keep them out of the production area.

Inspecting against the SSOP

Supervisory inspection should test the SSOP, not just the surfaces. Score these as critical:

• Food-contact surfaces clean and sanitised
• Chemical concentration within specification, verified by test
• Contact times achieved and recorded
• Equipment dismantled as the procedure requires
• Drains cleaned last with equipment changed afterwards
• No equipment travelled between hygiene zones
• Monitoring recorded at the time, not retrospectively
• Deviations logged with corrective action
• Current SSOP version in use
• Operators trained against the current version

The general method is in what a cleaning inspection is and food processing plant sanitation covers the wider programme.

Frequently asked questions

What are the required elements of an SSOP?

A procedure with specific parameters, a monitoring method, a corrective action procedure, a verification method, and a record-keeping system. All five are needed for the document to function as a food safety control rather than a cleaning instruction.

How many SSOPs does a food plant need?

As many as it takes to cover every sanitation activity specifically — typically one per area or major piece of equipment. A single plant-wide SSOP is almost always too general to be monitored or verified.

What is the difference between an SSOP and a preventive control plan?

The preventive control plan is the plant's overall food safety system, covering all controls including sanitation. SSOPs are the detailed procedures that sit inside it and implement the sanitation controls.

Who should write an SSOP?

Usually the food safety or quality team, with direct input from the people who perform the cleaning and from the sanitation supervisor. Procedures written without input from the operators are usually not followed, and audits reveal that quickly.

How often should an SSOP be reviewed?

At least annually, and immediately whenever chemistry, equipment, product range or allergens change. An SSOP that no longer matches practice is worse than no SSOP, because it documents a system that does not exist.

Document it, then prove it

An SSOP is only as good as the records behind it. The procedure says what should happen; monitoring, correction, verification and records prove it did.

NeatScore lets you build sanitation checklists that mirror your SSOPs, with parameters and critical items, photo evidence per step, and dated records that stand up to audit. Try it free for 7 days, or see pricing.