Blog / Downtime
Downtime · Guide

Sanitation Downtime: Count It, Shorten It Safely

OL By OEE Lab Editorial |Updated 2 November 2026 |6 min read
Short answer

Sanitation downtime is time a food line stops for cleaning during planned production, and it counts as an availability loss even though it is scheduled. Shorten it by timing each phase and removing the waiting between them, and never by cutting a validated step, a contact time or a release check.

Start with food safety

Your food safety plan owns the cleaning steps, chemicals, temperatures and contact times. Everything below targets the time around those steps, and any change to a validated procedure goes through your food safety or quality team first.

A faster clean that fails a check costs far more than the minutes saved. Treat release checks as part of production, and keep them in the plan.

What to count, and where

Sanitation is planned downtime, and planned stops inside planned production time still lower availability. That matches how changeovers work, as planned vs unplanned downtime explains.

Decide once, per line, what is inside the schedule. Then keep the rule, because moving cleaning out of planned time later will raise OEE with no real change.

Type of cleanUsual treatmentReason code
Mid-shift dry cleanInside planned timeSanitation: dry
Allergen clean between productsInside planned time, tied to the changeoverSanitation: allergen
CIP between batchesInside planned timeSanitation: CIP
End-of-day wet cleanInside if another shift could otherwise run, outside if the plant is closedSanitation: wet
Deep clean with no production plannedOutside OEENot an OEE stop
A common way to set the rule, though practice varies by plant. What matters most is that it stays the same over time.

If an allergen clean is part of a product change, split the log into two lines. How to count changeovers in OEE covers the changeover side, and the split shows which one drives the time.

What 30 minutes does to availability

Example: a two-shift line has 960 planned minutes, 70 minutes of other stops, and one 90-minute wet clean inside planned time. Over a five-day week, 30 minutes saved per clean returns 150 minutes of planned time.

Availability = run time / planned production time
90 min clean: (960 - 70 - 90) / 960 = 83.3%
60 min clean: (960 - 70 - 60) / 960 = 86.5%
Hypothetical line. 30 minutes off the clean adds 3.1 points of availability on every day it runs.

Time the phases

"Sanitation: 90 minutes" gives you nothing to work on, so split it. Have one person walk the clean with a clipboard, noting the time each phase starts and ends, and whether people or chemicals are working in that time.

Wait: run-out and crew18 min
Dry clean15 min
First rinse10 min
Detergent and contact17 min
Second rinse8 min
Wait: inspector12 min
Sanitize and release10 min
Hypothetical 90-minute wet clean. The red bars are the two waits, 30 minutes in total.

A third of this clean is waiting, and removing it touches no chemistry. Grey phases hold contact times and release steps, and those stay as validated unless your food safety team changes them.

Time two or three cleans with different crews before you act. One clean can mislead you, since a bad run-out or a late inspector may be a one-off.

Include a clean after your hardest product as well. A heavy soil load can change how long the dry clean takes.

Six ways to shorten it safely

1. Start on time

Plan the product run-out, so the last product leaves as the crew arrives. In the example, this is the biggest single bar.

2. Prepare before the stop

Move anything that can happen outside the stop to before it: chemicals mixed and checked, tools laid out, hoses connected. That idea comes from SMED, and it applies here with no change to the cleaning itself.

3. Book the inspector

Give QA a time for the release check, based on the plan, and tell them early when the clean is running late. A short message can often remove the 12-minute wait.

4. Make more dry clean possible

Good dry removal leaves less for the wet steps. Check that your procedure allows it, and use dedicated tools, stored at the line.

5. Make machines easier to open

Tool-free guards, removable parts and spare change parts ready to swap can reduce the most time-consuming teardown. Any design change still has to pass your hygiene rules.

6. Clean less often, if your plan permits

Run allergen-free products first and allergen-containing products last, so fewer full cleans are needed. Sequence changes need sign-off from your food safety team, and changeover frequency covers the planning trade-off.

CIP: time the gaps around the cycle

A CIP cycle is run by the system, so its rinse, caustic and sanitize phases are usually fixed by validation. The time you can work on tends to sit before and after them.

  • Waiting for the skid. If lines share one CIP set, log the wait as its own code, and look at how cleans are sequenced across lines.
  • Connecting and disconnecting. Swing panels, hoses and gaskets are manual work, so time them like a changeover.
  • Waiting for the result. A cycle that finishes while nobody is free to check it adds minutes with no cleaning in them.

Rerun cycles deserve their own count. Each one doubles the stop, so a repeat fault on a valve or a conductivity reading can matter more than any step you shorten.

Measure the restart too

A clean does not end at release, since a wet or cold line often runs slowly or makes rejects for a while. Those minutes are startup losses, and they belong in the total cost of the clean.

Track minutes from release to the first good product at target speed. The clean that looks fast may be the one causing the slow restart.

Keep these numbers each week

  • Total sanitation minutes, by line and by type of clean.
  • Cleans per week, because frequency can matter more than length.
  • Waiting minutes inside each clean, from a timed sample.
  • Failed checks and re-cleans. This must stay at or below today's level while time falls.
  • Release to first good product, in minutes.

A rising re-clean count alongside falling times means you are cutting the wrong thing. Stop and review it before going further.

Use the downtime Pareto to see how sanitation compares with other losses on the line, and read OEE and downtime in food and beverage for the sector picture.

Habits that keep cleans long

  • Calling cleaning "not a loss". Moving it out of planned time hides the cost, and then nobody works on the waits.
  • One code for all cleans. A 10-minute dry clean and a 90-minute wet clean need different projects.
  • Rushing the crew. Set the plan and remove the delays, and leave the pace of the validated work alone.
  • Ignoring handover. Production and sanitation often blame each other for the gap, so give one person the start and finish of the clean.
See it live in Fabrico

Sanitation time gets clearer once each clean is its own coded stop. Fabrico takes stops live from the machines, operators tag the type of clean at the line, and the minutes show in OEE per line and shift. See how Fabrico tracks stops.

What people ask next

Does cleaning count as downtime in OEE?

Yes, if it falls inside planned production time, because it reduces availability. If no production was planned, as with a deep clean in a closed plant, it sits outside OEE. Keep the rule steady, or your trend will mislead you.

Is CIP time an availability loss?

Yes, when it happens within planned production time. Log it under its own code, so you can follow length and frequency. OEE for batch processes covers how time between batches is treated.

How do you reduce sanitation time without risking food safety?

Remove the waits and prepare before the stop, and leave contact times, chemicals and release checks to your food safety plan. Have the food safety team approve any change to procedures. Track re-cleans to check that nothing has slipped.

Should sanitation be measured with changeovers?

Log them separately even when they happen together, as they have different owners and fixes. How to measure changeover time applies well to timing each phase.

Why does the line run badly just after cleaning?

Wet belts, cold equipment and re-fitted parts are common causes. Those minutes are startup losses, so measure them apart from the clean. See startup losses for how to count them.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

Related guides: End of Shift Losses: The Last Hour Pattern

← More OEE Lab guides · OEE for bakery lines →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES