Looking Clean Is Not Being Clean: Why Food Factories Must Verify Sanitation, Not Just Do It

By Isaac Muthui, CEO, Tamalaki Business Network Ltd. Originally published at factoraerp.com.

Every food factory cleans. The night shift hoses the floor, someone scrubs the mixing tank, the pasteuriser runs its wash cycle, and by morning the stainless steel shines.

Now ask the question an auditor, a buyer or a county public health officer will eventually ask: "How do you know it is clean?"

"It looks clean" is not an answer. Bacteria, allergen residues and milk film in a pipe bend are not visible from the doorway. A detergent can be dosed at half strength for weeks because the dosing pump drifted and nobody measured it. A brush used on the drain on Monday can end up on the filler on Tuesday. None of that shows until a product fails a test or a customer complains.

This article is for production leads, QA officers, hygiene supervisors, engineers and owners of small and mid-sized food and agro factories in Kenya and East Africa: dairies, millers, bakeries, juice and beverage makers, edible-oil processors, meat and poultry plants, and spice and snack packers. It gives you an eight-step cleaning and sanitation checklist for food factories that you can run with your own team, whether you clean by hand, by foam, or with clean-in-place (CIP) systems. It is operations guidance, not legal advice; confirm the specifics with your county public health office, KEBS and your customers' specifications.

What the standards and the law actually say

Codex, the international baseline. The General Principles of Food Hygiene (CXC 1-1969) separates two things that factories often blur. Cleaning is "the removal of soil, food residues, dirt, grease, or other objectionable matter". Disinfection is the reduction of viable micro-organisms on surfaces, in water or in air to a level that does not compromise food safety or suitability. You need the first before the second works: Codex warns that if cleaning does not remove soil so the disinfectant can reach the micro-organisms, or if sub-lethal concentrations are used, the micro-organisms may persist.

Section 11 says written procedures should specify the areas, equipment and utensils to be cleaned, who is responsible, the method and frequency, and the monitoring and verification activities. Chemicals should follow the manufacturer's instructions, "using the correct dilutions and contact times", and be stored separately from food, and separate cleaning equipment should be used for different hygiene zones. Monitoring could include pH, water temperature, conductivity and chemical concentration; verification could include "protein and allergen test swabs, or microbiological testing for indicator organisms". Codex also says food contact surfaces for ready-to-eat food deserve more attention than walls and ceilings.

The East African hygiene code. EAS 39:2001, the hygiene code of practice for the food and drink manufacturing industry, gives cleaning its own chapter. It asks for a documented cleaning and disinfection schedule, and for one person, preferably a manager whose duties are independent of production, to be responsible for cleanliness (clause 6.2). Each area's programme should state the frequency, contact time, temperature and strength of cleaning solutions, with records and "evidence that the cleaning programme has been adhered to" (6.3.2). It requires a documented procedure to check how effective cleaning is, "by microbiological analysis of rinse water, swabbing of surfaces, or other appropriate means" (6.3.3), and plant and equipment to be cleaned at least daily unless it can be shown that daily cleaning is not needed (6.3.4).

It also covers the details that trip plants up: chemicals stored away from food and labelled (6.3.6), non-wooden, coloured nylon brushes, with floor brushes never used on equipment (6.3.9), and wet-cleaned equipment kept out of use until dry where dampness could contaminate product (6.3.13). It recommends a total viable count below one colony per square centimetre on food contact surfaces after cleaning (6.4.5), and lists cleaning procedures, the strength of active ingredients and the temperature of each washing cycle among critical parameters to monitor and record (4.3.5).

Kenyan law. The Food, Drugs and Chemical Substances (Food Hygiene) Regulations, 1978, made under the Food, Drugs and Chemical Substances Act (Cap. 254), put cleaning duties on whoever owns, operates or is in charge of a food plant. Regulation 12 requires cleaning to minimise the danger of contaminating food, and cleaning supplies to be safe and effective. Regulation 13 requires equipment to be cleaned and sanitised before use (or, in continuous operations, on a predetermined schedule) with effective, safe sanitising agents. Regulation 14 requires overall sanitation of the plant to be supervised by a person specially assigned to it. Regulation 16 lets an authorised officer serve a written notice requiring a plant to be cleaned, reconstructed or repaired, or not to be used until the conditions in the notice are met.

Put together, the floor rule is simple: write down what gets cleaned, how and by whom; control the chemicals and tools; check each clean before production starts; prove it works with tests; and act on the product when it does not.

Why "it looks clean" is not a sanitation programme

Consumers are paying attention. On 16 October 2026, CityNews Kenya reported health concerns after a video showed yoghurt being prepared and packaged in what appeared to be a residential house, and noted that the video renewed calls for authorities to intensify inspections of yoghurt producers. That case is at the extreme end, but hygiene is now judged on video, not just on paper.

The harder problem in a real factory is not dirt you can see. It is cleaning that looks complete and is not.

Illustration (not real customer data): a small juice plant runs CIP on its filler every evening, and the operator signs the sheet. Over several weeks the caustic dosing pump weakens and a sticking steam valve keeps the wash below target temperature. Nobody records concentration or temperature, only that the cycle "ran". When shelf-life complaints arrive, the plant cannot say which nights' cleans worked, so it cannot say which batches are at risk. A concentration check and a temperature reading on each cycle would have shown the drift within days.

That is the gap this checklist closes: from "we clean" to "we can show that this line was clean before this batch".

The 8-step cleaning and sanitation checklist

1. Build a master sanitation schedule

• List every area and item that must be cleaned: each room or production area, each piece of equipment, food contact surfaces, non-contact surfaces, overhead structures, walls, floors, drains and gullies, cold rooms, vehicles and tankers, and the outside of the plant. EAS 39 asks for a programme for each room or area and for the exterior.
• For each item, record the frequency (after each batch, each shift, daily, weekly, monthly), the method (manual, foam, soak tank, CIP), and who is responsible.
• Mark the high-risk items: food contact surfaces, especially those touching ready-to-eat food after the last heat step, fillers, slicers, mixers, and anything shared between allergen and non-allergen products. Codex says these deserve more attention than walls and ceilings.
• Treat daily as the default for plant and equipment, as EAS 39 does, unless you have evidence that a longer interval is safe.
• Put deep cleans into your preventive maintenance calendar.

2. Write a sanitation standard operating procedure (SSOP) for each item

• For each item on the schedule, write a short, step-by-step procedure: what to dismantle, the chemical, the concentration, the water temperature, the contact time, the rinse, the disinfection step, the final rinse if the disinfectant label requires one, how to dry, and how to reassemble.
• Include lock-out of moving parts and chemical protection. Keep it short, in your team's language, with photos, posted where the cleaning happens.
• Get the chemical supplier to confirm concentrations and contact times in writing.
• For CIP circuits, write the cycle itself: pre-rinse, caustic wash, intermediate rinse, acid wash where used, disinfection and final rinse, with a target concentration, temperature, time and flow for each step.

3. Control cleaning chemicals

• Keep an approved list of cleaning and disinfection chemicals, suitable for food contact surfaces where they will touch them, with safety data sheets on file.
• Store them in a separate, locked, labelled area away from food, ingredients and packaging, in their original or clearly labelled containers. EAS 39 and Codex both ask for separate, clearly identified storage, and the Food Hygiene Regulations limit toxic materials in the plant to those actually needed.
• Make up solutions with measured doses, not "one cup per bucket". Check the concentration of working solutions with test strips, titration kits or conductivity, as the supplier recommends, and record the result.
• Provide gloves, goggles or face shields, and an eye-wash point near where chemicals are mixed or dispensed, as EAS 39 sets out.
• Check label, batch and expiry at intake; our supplier intake checklist works for chemicals too.

4. Control cleaning tools and zones

• Colour-code brushes, squeegees, buckets and cloths by zone: one colour for food contact surfaces, another for floors, another for drains and toilets, and a separate set for raw and cooked or high-care areas where you have them. Codex asks for separate, suitably designated cleaning equipment for different hygiene zones.
• Never use floor brushes on equipment. EAS 39 says so directly and notes that brushes can carry Listeria from footwear onto the plant.
• Use non-wooden brushes with nylon bristles that are coloured so a lost bristle is easy to see. Hang them bristles down to dry, and replace them when worn.
• Clean the cleaning equipment. A dirty mop spreads contamination instead of removing it.

5. Clean in the right order, and record the parameters that matter

• Follow a fixed order: dry clean and remove gross debris; pre-rinse; apply detergent and scrub or circulate; rinse; disinfect for the required contact time; final rinse where the label requires it; dry. Codex sets out this sequence for wet cleaning.
• Work top to bottom and from clean areas towards drains. Use high-pressure hoses early, keep spray away from surfaces already cleaned, and do not wash floors next to open product or exposed lines.
• In dry plants, such as flour mills and spice packers, prefer dry cleaning and vacuuming, keep wet cleaning physically separate, and do not restart a line until wet-cleaned parts are completely dry. EAS 39 gives powder conveying lines as an example.
• Record what proves the clean was done properly, not just that it happened: for manual cleans, the chemical, the measured concentration, the time and who did it; for CIP, each step's concentration, temperature and duration, and, where you can, the final rinse conductivity or pH to show no chemical is left behind. These are the parameters Codex lists for monitoring.
• Allow enough time. A crew given half the time a job needs will cut steps, and the sheet will still say "done".

6. Inspect before production and release the line

• Before any production starts, a person other than the cleaner, such as the shift supervisor or a QA officer, inspects the line against a short pre-operational checklist: no visible residue on food contact surfaces, no standing water where the product is dry, guards and parts reassembled correctly, no tools or cloths left behind, chemicals removed, and drains clear.
• Use a torch: under belts, inside nozzles, behind guards, in gaskets and dead legs. Where a disinfectant must be rinsed off, confirm it with a pH or residue strip.
• If the line fails, it is re-cleaned and re-inspected. Production does not start until the line is released and signed. It is the same discipline as line clearance, often done in the same walk.
• Record the release time, so "was the line released before this batch?" takes seconds to answer.

7. Verify that cleaning works, and trend the results

• Choose verification methods that fit your risk and budget: rapid hygiene swabs (ATP or protein tests) on food contact surfaces after cleaning, allergen swabs after changeovers from allergen products, microbiological swabs for indicator organisms sent to a laboratory, and analysis of final rinse water from CIP circuits. EAS 39 names rinse water analysis and surface swabbing; Codex names protein, allergen and indicator-organism testing.
• Write a sampling plan (surfaces, frequency, pass criteria) and rotate sites so hard-to-clean spots get tested. Include drains and floors near open product; EAS 39 (4.3.4) asks for environmental sampling matched to risk.
• Rinse water must be fit for use (see our water quality checklist), and CIP thermometers and conductivity meters need calibration.
• Trend the results by line, by surface and by shift. One failed swab is an event. The same filler nozzle failing every few weeks is a design, procedure or training problem.

8. When cleaning fails, act on the product, then fix the cause

• If a pre-operational inspection fails, re-clean and re-inspect before production. If a swab result, a rinse water result or a CIP record shows that a clean was not effective after production has already run, identify every batch produced on that line since the last verified good clean.
• Put those batches on QA hold until QA assesses them. If product has already been dispatched, you need to find it quickly, which is what a mock recall tests.
• Log a non-conformance with the cause, corrective action, owner and closing date. Typical causes: rushed cleaning windows, wrong dilution, worn equipment, untrained staff.
• Review cleaning records every day. EAS 39 (clause 4.3.6) asks for records of processes that assure food safety to be inspected at least daily by a qualified person and signed.
• Review the programme every few months and whenever equipment, products or allergens change. Codex also suggests reviewing disinfectant effectiveness with suppliers and considering rotation.
• Use customer complaints about spoilage, off-flavours or short shelf life as a signal to check cleaning records for the lines and dates involved.

Habits that make sanitation stick

• No release, no run. A line starts only when someone other than the cleaner has inspected and signed it off.
• Measure the chemical, not the bucket. Concentration and temperature are recorded, not assumed.
• Colours mean zones. A floor brush never touches a food contact surface.
• Swabs go where cleaning is hardest. Test the gaskets, nozzles and belt undersides, not just the shiny tank wall.
• A failed clean is a batch problem. Products made after a failed clean are held until QA decides.

Sanitation ties into the rest of your quality system: pest control depends on removing food residues pests feed on, allergen control depends on validated changeover cleans, and the dairy milk intake checklist depends on clean cans, tankers and reception equipment.

Where an ERP helps

A clipboard and a disciplined hygiene supervisor can run this checklist in one small plant. It gets harder with several lines, shifts and changeovers, because the question after a failed swab is "which batches were made on that line since the last good clean?"

FactoraERP tracks production batches and lots, stock status including QA holds, non-conformance records, stock adjustments with reason codes, and batch costs and yields. That means a failed pre-operational check, swab or CIP record can be logged as a non-conformance with an owner, linked to the batches produced on that line since the last verified clean, those lots can be put on hold until QA decides, and any product written off gets a reason code instead of disappearing into an unexplained stock count difference or a strange batch yield. See factoraerp.com.

Free download: eTIMS readiness checklist for factories

Quality records, stock records and invoices increasingly have to tell the same story for Kenyan manufacturers, and a batch written off after a failed clean touches all three. If you want a free eTIMS readiness checklist for factories, sign up for the FactoraERP Insights newsletter at https://isaacmuthui.substack.com. You will get practical operations notes for food and agro manufacturers. No spam; unsubscribe anytime. For background, see our guide to eTIMS for food and agro manufacturers.

FAQ

What should a cleaning and sanitation checklist for a food factory include?
A master sanitation schedule covering every area and item, a written sanitation standard operating procedure (SSOP) for each, control of cleaning chemicals and tools, a fixed cleaning sequence with recorded parameters such as concentration and temperature, a pre-operational inspection and line release before production, verification by swabs or rinse water tests, and a procedure for failed cleans that includes holding affected product and logging a non-conformance.

What is the difference between cleaning, disinfection and sanitising?
Codex defines cleaning as removing soil, food residues, dirt, grease and other objectionable matter, and disinfection as reducing viable micro-organisms to a level that does not compromise food safety or suitability. "Sanitising" is commonly used for that step on food contact surfaces. Cleaning comes first: a disinfectant cannot work properly on soiled surfaces.

How often should food processing equipment be cleaned?
EAS 39 says plant and equipment should be cleaned at least daily, or more often if needed, unless it can be shown that daily cleaning is not required. Kenya's Food Hygiene Regulations require equipment to be cleaned and sanitised before use, or on a predetermined schedule in continuous operations. Set frequencies by risk, giving food contact surfaces for ready-to-eat food the most attention.

What is an SSOP?
A sanitation standard operating procedure: a written, step-by-step instruction for cleaning one area or machine, covering dismantling, chemical, concentration, temperature, contact time, rinse, disinfection, drying, reassembly, who does it and how it is checked.

How do we verify that cleaning is effective?
Combine a pre-operational inspection with tests: ATP or protein swabs, allergen swabs after allergen changeovers, microbiological swabs for indicator organisms, and final rinse water analysis for CIP. Trend results by line and surface.

What records should we keep for CIP?
For each cycle: the circuit or line, the date and time, each step's chemical concentration, temperature and duration, and, where possible, flow and final rinse conductivity or pH, plus who ran and checked it. These match the parameters Codex and EAS 39 name for monitoring.

---

Isaac Muthui, CEO, Tamalaki Business Network Ltd