What is an SSOP in food manufacturing?

A Sanitation Standard Operating Procedure, a written procedure describing exactly how a specific cleaning and sanitizing task is done: scope, frequency, chemicals and concentrations, step-by-step method, monitoring, records, and corrective actions. USDA-inspected plants must maintain them under 9 CFR Part 416; FDA-regulated plants need equivalent documented sanitation controls.

What is the difference between an SOP and an SSOP?

An SOP is any documented procedure. An SSOP is specifically a sanitation procedure with regulatory weight: required by rule in USDA plants, backed by mandatory daily records, and signed by the person with overall on-site authority. Inspectors verify SSOPs directly; ordinary SOPs are checked mainly through your own quality system.

What are the 8 key sanitation conditions?

From FDA's seafood HACCP rule (21 CFR 123.11): safety of water; condition and cleanliness of food contact surfaces; prevention of cross-contamination; maintenance of hand-washing, sanitizing, and toilet facilities; protection from adulterants; proper labeling, storage, and use of toxic compounds; control of employee health conditions; and exclusion of pests. Many plants structure their SSOP monitoring around these eight.

What is pre-op sanitation?

Pre-operational sanitation is the cleaning and sanitizing completed before production starts, ending in a documented inspection of food contact surfaces. In USDA plants, FSIS verifies pre-op results and production cannot begin on equipment that fails. Operational sanitation then maintains sanitary conditions during the shift.

How long must sanitation records be kept?

USDA-inspected establishments must keep daily Sanitation SOP records, implementation, monitoring, and corrective actions, for at least 6 months (9 CFR 416.16). Customers and GFSI schemes often require longer retention, so many plants standardize on one to three years.

Under 9 CFR 416.12(c), Sanitation SOPs must be signed and dated by the individual with overall authority on-site, or a higher official, typically the plant manager. The signature makes sanitation an operations commitment, not just a sanitation-crew document, and it must be renewed when procedures change.

SSOPs: Sanitation Procedures That Pass Inspection

What separates a sanitation procedure from a wish: written steps, daily records, and a loop that catches its own failures.

SSOPs (Sanitation Standard Operating Procedures) are written procedures describing exactly how a food plant cleans and sanitizes, what gets cleaned, how, with what chemicals, by whom, how often, and how it is verified. USDA-inspected plants must have them under 9 CFR Part 416; FDA-regulated plants need equivalent sanitation controls to pass inspection.

Sanitation is where inspections are won or lost, because it is the program an inspector can see, swab, and challenge on any given morning. This post covers what makes an SSOP different from a regular SOP, the regulatory basis at USDA and FDA, the seven-step sanitation cycle, pre-op versus operational sanitation, and the verification loop that keeps the whole thing honest.

SSOP vs SOP: what's the difference?

An SOP is any standard operating procedure a documented way to perform a task. An SSOP is a specific, regulated subspecies: a sanitation procedure whose existence, content, execution records, and corrective actions are defined by food regulation and checked by inspectors. Three practical differences:

SSOPs are mandatory by rule for USDA-inspected meat, poultry, and egg product plants (9 CFR 416.11–416.17). A generic SOP is mandatory only if your own system or customer requires it.
SSOPs demand daily records. Every implementation and monitoring event, and every corrective action, gets documented, and the records are inspectable.
SSOPs carry named accountability. USDA requires the Sanitation SOPs to be signed and dated by the individual with overall on-site authority, the plant manager owns the document, not just the sanitation lead.

Who requires SSOPs, FDA or USDA?

Both, differently:

USDA (FSIS): 9 CFR Part 416 requires every official establishment to develop, implement, and maintain written Sanitation SOPs covering daily procedures, before and during operations, sufficient to prevent direct contamination or adulteration of product. It also requires routine effectiveness evaluation, corrective actions, and daily records kept at least 6 months. FSIS inspectors verify pre-op sanitation before the plant is allowed to start.
FDA: Most FDA-regulated food plants operate under the sanitation GMPs of 21 CFR Part 117 subpart B and sanitation-related preventive controls under FSMA. Written SSOPs are explicitly required in the seafood and juice HACCP regulations (21 CFR 123 and 120 recommend/require sanitation monitoring of eight key conditions, water safety, food contact surfaces, cross-contamination prevention, hand-washing facilities, adulterant protection, toxic compound labeling and storage, employee health, and pest exclusion). Even where the written document is not mandated, inspectors expect documented, verifiable sanitation, in practice, everyone writes SSOPs.

GFSI schemes (BRCGS SQF, FSSC 22000) then audit cleaning procedures, validation, and records regardless of which agency inspects you, sanitation is prerequisite-program ground zero for every HACCP-based system.

What are the 7 steps of the sanitation cycle?

Most wet-cleaning SSOPs in the industry follow the same seven-step sequence. Write yours against it:

Prepare and dry-clean. Lockout equipment, remove product and packaging, disassemble per the procedure, and physically remove gross soil, scrapers and brushes before water.
Pre-rinse. Rinse surfaces (typically warm water) to remove loosened soil so the detergent can reach the surface, working top-down.
Wash. Apply detergent at the specified concentration, temperature, and contact time, with scrubbing or foaming as written. Chemical, concentration, and dwell time belong in the SSOP, not in someone's head.
Post-rinse. Remove all detergent and soil residues with potable water.
Inspect. Visual and, where used, ATP or swab checks of cleaned surfaces, this self-inspection is the plant's own pre-op check before sanitizing.
Sanitize. Apply the sanitizer at labeled concentration and contact time; verify concentration with test strips or titration and record it.
Verify and document. Reassemble, complete the pre-op record, and release the line, with name, time, result, and any corrective action taken.

Seven steps, in order, every time. Steps 5 and 7 are the ones inspectors reconstruct from your records, and the ones plants skip when they're behind schedule.

Pre-op vs operational sanitation: two clocks

USDA's rule splits sanitation into two duties, and the split is a useful design for any plant:

Pre-operational sanitation is everything done before production starts: the full cleaning cycle above, ending in a documented pre-op inspection of food contact surfaces. In USDA plants, FSIS verifies pre-op sanitation; production cannot start on equipment that fails.
Operational sanitation is everything that keeps the plant sanitary while running: mid-shift cleanups, utensil and hand-dip maintenance, condensation control, waste removal, hygiene practices at changeovers and breaks. It is continuous, not a single event, and it needs its own monitoring records.

Most sanitation failures found by inspectors are operational, not pre-op, the plant that starts clean at 6 a.m. and degrades by hour six. Your SSOP set needs both clocks: the nightly cycle and the during-shift disciplines, each with frequencies and named owners. Allergen changeover cleans (see allergen management) are a third clock layered on top, triggered by the schedule rather than the shift.

What goes in an SSOP document?

An inspector-ready SSOP answers every question about one cleaning task without the author in the room:

The anatomy of an inspectable SSOP. If a section can't be verified from records, it isn't really in the program.

How does the verification loop work?

Regulation demands more than execution, it demands proof the program works and gets fixed when it doesn't. The loop has four moves: monitor (daily checks that procedures ran: pre-op inspections, sanitizer titrations, sign-offs), verify (periodic independent checks that monitoring is honest: ATP swabs, micro sampling tied to your environmental monitoring program record review), correct (documented corrective action when either fails, re-clean, hold product, retrain, and record it, per 9 CFR 416.15), and revise (update the SSOP when equipment, products, or results change, a static SSOP in a changing plant is a finding waiting to be written, per 416.14).

Monitoring proves the work happened; verification proves the monitoring is honest; correction and revision prove the program learns.

Facts worth pinning, from the rule itself:

Written Sanitation SOPs are required for every USDA official establishment describing daily pre-op and operational procedures (9 CFR 416.11–416.12).
Daily sanitation records must be kept and maintained at least 6 months (9 CFR 416.16).
FSIS verifies pre-op SSOPs per its directive on pre-operational SSOP verification production starts only on passed equipment.
FDA's seafood HACCP rule lists the eight key sanitation conditions plants must monitor (21 CFR 123.11), the de facto checklist across FDA-regulated food.

Paper is where this loop leaks: pre-op sheets filled at the end of the week, titration logs with suspiciously identical values, corrective actions that live in someone's memory. Moving sanitation checks onto tablets with timestamps and required fields makes records trustworthy by construction, the same digitize-the-paper move Harmony runs for production and quality logs (see how CLS did it), applied to the sanitation shift. It also connects sanitation to GMP compliance evidence, so audit prep is a query instead of a binder hunt.