Why "clean food-contact surfaces daily" fails an auditor, the five things every procedure must actually name, and how to keep the paper matched to what your floor really does.
Do these first
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
After this lesson you can take a procedure that reads fine on the page and rewrite it so an auditor reading it against your floor finds nothing to write up. The gap between a procedure that sounds reasonable and one that survives an audit is smaller and more mechanical than it looks — and closing it is mostly a matter of naming five things.
Write "clean food-contact surfaces daily" in your sanitation binder and it reads like a rule. It is not. It names no person, no specific surface, no method, and no way to prove any of it happened. An auditor does not grade whether the sentence sounds reasonable. They grade whether the procedure is, in the SQF code's recurring phrase, documented and implemented — and a sentence that vague cannot be implemented the same way twice, let alone shown to have been.
That is the mechanism behind one of the most common ways a first-timer's audit fills up with findings. A at the minor level is defined in the SQF Food Safety Code (Edition 9) as evidence of "an incomplete or inappropriate implementation" of a requirement. A procedure too loose to carry out consistently is that, by definition. It is not that the auditor is being pedantic — it is that a vague procedure is genuinely unprovable, and an audit runs on evidence.
Notice something about the code itself: it never uses the term . Across the whole SQF code the requirement is phrased the same way, clause after clause: "the methods and responsibility for [some task] shall be documented and implemented." That sentence is the entire test. Your SOP passes when it makes the method and the responsibility concrete enough that someone else could do the task from it, and you can show it was done. Everything below is how to get there.
The clearest place the code spells out the anatomy of a strong procedure is the cleaning clause, 11.2.5.1. Written for sanitation, it lays out a template that works for any SOP you write. Reduced to what an operator actually writes down, it is five questions, and the fix for "clean food-contact surfaces daily" is to answer all five.
What — the specific thing, not the category
Not "surfaces." The filler nozzle, the depositor hopper, the slicer blade and its guard, the tote interiors. The code asks what is to be cleaned; your procedure names each item, because different surfaces need different methods.
How — the method, in steps a new hire could follow
The chemical and its concentration, the tools, the sequence, the contact time, the rinse. "Foam with the alkaline detergent at label strength, ten-minute dwell, potable rinse, no-rinse sanitizer at 200 ppm" is a method. "Clean it" is not. The code also asks how you confirm the concentration is right — a titration strip reading, not a guess.
How often — a stated frequency, not 'as needed'
The code asks when it is to be cleaned. "Daily" can pass if daily is genuinely right, but say what daily means: after each production run, at every allergen changeover, before the first fill of the shift. "As needed" is not a frequency — it is a way to have no frequency.
Who — a role that carries the responsibility
The code asks who is responsible. Name the role — the line sanitor, the shift lead — so the task has an owner and the training record has a target. A procedure that belongs to everyone belongs to no one.
How verified — the proof it worked, and where it is recorded
This is the step vague SOPs skip entirely, and it is the one the code is most insistent on. Clause 11.2.5.9 requires that the responsibility and methods used to verify the cleaning was effective be documented, that a verification schedule exist, and that a record be kept. Naming the check — an ATP swab of the food-contact surface, a pre-start visual, a periodic environmental result — and the log it lands in is what turns your procedure from a claim into evidence.
That last step deserves its own word, because operators and auditors both lean on it. is the difference between "we clean daily" and "we clean daily and here are twenty days of swab results that show it worked." An auditor can dispute the first. The second closes the question.
A procedure that answers all five reads longer than "clean food-contact surfaces daily." That length is the point. It is the difference between a sentence and something a new sanitor could execute and a stranger could audit.
Sanitation is where the whole plant's food safety rides on procedures being followed exactly, so it gets its own name. A is not a different kind of document; it is an SOP for cleaning, written to the five-question bar above and then held to a daily rhythm.
Two things make sanitation stricter than a generic procedure. First, the pre-operational inspection: under SQF clause 11.2.5.7, after cleaning and before production starts, qualified personnel inspect food-contact surfaces and the processing areas to confirm they are actually clean. That is a verification step that happens every single production day, not once a year. Second, the record: clause 11.2.5.9 requires that the pre-op inspections, the cleaning activities, and the verification all be recorded and kept.
Where you are regulated changes how formal this gets. For an FDA-regulated facility, sanitation lives inside the current good manufacturing practices of 21 CFR Part 117 — the requirement is real, but the code does not mandate a document literally called an SSOP. For a USDA-inspected meat or poultry plant, the SSOP is a named federal requirement. Under 9 CFR Part 416, the establishment must develop, implement, and maintain written sanitation SOPs (416.11); each procedure must specify its frequency and identify the employee responsible, and the SSOP must be signed and dated by the person with overall on-site authority (416.12); and the plant must monitor the implementation daily (416.13), keeping the daily records — including any corrective action — on file. If you sell into USDA-inspected channels, confirm the current text at 9 CFR Part 416 and write to it. Whichever regime you are under, the five questions are the same; the paperwork formality is what shifts.
Here is the failure that catches good operators who have already done the hard writing. The code's phrase is "documented and implemented" — two conditions, not one. A binder full of beautifully specific SOPs that describe a process the floor stopped using six months ago fails just as surely as a vague one, because the paper no longer matches the practice. The auditor's move is simple and hard to argue with: they read your SOP, they walk to where the work happens, and they write a finding wherever the two diverge.
Divergence is normal. Lines get re-tooled, a faster sequence gets discovered, a chemical gets swapped, a step gets quietly dropped because it seemed unnecessary. None of that is misconduct — it is a plant improving itself. The problem is only that the document did not move with the floor. So the discipline is to close the gap on purpose, in one direction or the other: sometimes the paper is right and the floor drifted, and you retrain; sometimes the floor found a better way and the paper is stale, and you rewrite. Either way, the SOP and the practice have to end up saying the same thing.
The way you catch this before the auditor does is the internal audit — the review your own site runs against the code to find its own gaps first. The SQF Practitioner lesson covers who runs those and why independence matters; the point here is that walking each SOP against the actual task is the single most useful thing an internal audit does. It is also the cheapest to do yourself, any day of the week, long before an audit is scheduled.
Once your procedures name who does what, how, how often, and how it is proven — and once the paper matches the floor — you have taken the sting out of the finding first-timers most often walk into. What remains is the audit day itself: how the visit actually runs, and the other places first-timers stumble.
Do this in your operation