What is a sanitizer concentration log?

A sanitizer concentration log is the written record a food-service team keeps to prove the chemical sanitizer in the three-compartment sink, wiping-cloth buckets, and warewashing machine was mixed to the correct strength and tested on a shift cadence. Each entry records the date and time, the sanitizer type, the measured concentration in ppm (parts per million, the amount of active sanitizer in the water) read off a test strip, the staff member who tested it, and any corrective action taken when the reading was out of range.

The log exists because sanitizer strength is not a set-it-and-forget-it number. Sanitizer that is too weak does not kill pathogens. Sanitizer that is too strong leaves chemical residue on food-contact surfaces and wastes product. The strength also drifts during a shift. As the sink water gets soiled and the solution sits, the active concentration drops. That is why a single open-of-shift test is not enough.

The log is the proof. When the health inspector asks "how do you know your sanitizer was in range at 2pm?", the log is the answer. A clipboard nobody verified until the inspector arrived is the exact pain this record solves.

A sanitizer test strip log applies anywhere a chemical sanitizer touches a food-contact surface:

• The sanitizing (third) compartment of the three-compartment sink for manual warewashing.
• Wiping-cloth buckets stored between uses (FDA Food Code 3-304.14).
• Sanitizer spray bottles for in-place food-contact surface sanitizing.
• The final rinse of a chemical-sanitizing warewashing machine.

This is the sanitation gap a temperature-only program leaves open. Sanitizer ppm is a chemical-strength check, not a temperature reading. It sits next to your walk-in cooler temperature log, not inside it. Both monitor TCS food hazards under HACCP Principle 4, but they measure two different things.

Regulatory framework

The FDA Food Code 2022 sets the chemical sanitizer concentration requirements in section 4-501.114 and requires food-contact surfaces to be cleaned and sanitized after every use and at least every four hours during continuous use of TCS food. The Food Code does not mandate a written sanitizer log by name. It does require operators to verify concentration with a test kit (4-501.116), and local health departments and HACCP-aligned programs routinely require the written record as the proof of that verification.

That nuance matters. Read FDA Food Code 4-501.116 carefully: the concentration of the sanitizing solution must be "accurately determined by using a test kit or other device." The verification is mandatory. The written log is the practical artifact that documents it, and most local jurisdictions and HACCP programs require it. The honest framing is this: the Food Code requires you to test and verify concentration. The log is how you prove you did.

The cadence anchor sits in FDA Food Code 4-602.11. Food-contact surfaces and utensils must be cleaned and sanitized after use and at least every four hours during continuous use.

Testing cadence for the three-compartment sink and wiping-cloth buckets:

1. Test at the start of each shift when the sink or bucket is first set up.
2. Test again every two to four hours during service, because soiled solution loses strength.
3. Test whenever the solution is remade or refreshed.
4. Test more often when soiling demands it. Heavy prep loads degrade the solution faster.

Record retention

Retention is set by state and local jurisdiction, not by a single federal number for sanitizer logs. Common requirements seen across health departments range from one year (Utah and Nebraska guidance) to two years (Kansas sanitizer test strip log guidance). The operator-safe rule: keep the log for at least one year, and check your local health department for the exact window. MSU Extension guidance on food safety paperwork retention is a useful starting point.

Cleaning vs. sanitizing vs. disinfecting

These three terms get used interchangeably on the line, and they are not the same thing:

• Cleaning removes visible food, soil, and grease from a surface with a detergent. It does not kill pathogens.
• Sanitizing reduces pathogens on a cleaned surface to safe levels, by chemical (the ppm-controlled solution this log measures) or by heat. This is what the concentration log tracks.
• Disinfecting eliminates or inactivates targeted pathogens. It is used on high-touch and non-food-contact surfaces and after contamination events like blood, vomit, or diarrheal incidents. The term "disinfection" was first defined in the Supplement to the 2022 FDA Food Code.

The order matters. You cannot sanitize a dirty surface. Sanitizer cannot penetrate organic soil, so clean first, then sanitize. For the full regulatory picture across temperature, sanitation, and date-labeling hazards, see our guide to FDA Food Code and food safety regulatory frameworks. The 2022 Food Code summary of changes documents the disinfection update.

PPM targets by sanitizer type

Chlorine sanitizer runs 50 to 100 ppm, quaternary ammonium (quats) runs at the EPA-registered label concentration commonly up to 400 ppm, and iodine runs 12.5 to 25 ppm, per FDA Food Code 4-501.114. Each sanitizer also has a minimum water temperature and a contact time the solution must meet to actually kill pathogens.

| Sanitizer | Target concentration (ppm) | Water temperature | pH / hardness | Minimum contact time |
|---|---|---|---|---|
| Chlorine | 50 to 100 ppm | 100°F at 50-99 ppm (pH up to 10) or 75°F (pH up to 8), 55°F at 100 ppm | Effectiveness drops as pH rises | About 10 seconds |
| Quaternary ammonium (quats) | Per EPA label, commonly 150-400 ppm, 200 ppm typical, not to exceed 400 ppm | Minimum 75°F | Water hardness 500 mg/L or less | About 30 seconds |
| Iodine | 12.5 to 25 ppm | Minimum 68°F | pH 5.0 or less | About 30 seconds |

The chlorine temperature and pH relationship is the most-missed detail. At 50 to 99 ppm the solution needs 100°F if pH is up to 10, or 75°F if pH is up to 8. At 100 ppm it can be as cool as 55°F. Quats vary by product, so always read the EPA-registered label for your specific product rather than assuming a single universal number. Contact time matters as much as ppm. A surface sanitized for two seconds is not sanitized. The numbers above come from the Virginia adoption of FDA Food Code 4-501.114, which reproduces the federal table verbatim, and from FoodSafePal's breakdown of approved foodservice sanitizers.

How to read a sanitizer test strip:

1. Use the strip that matches your sanitizer. Chlorine strips do not read quats, and vice versa. They are not interchangeable.
2. Dip the strip in the sanitizer solution (the third sink compartment or the bucket), not the wash or rinse water.
3. Hold it for the time printed on the strip vial, usually about 10 seconds.
4. Match the strip color to the chart on the vial.
5. Read it immediately and record the actual number. Do not estimate, and do not record a number you did not read.

For deeper test-strip guidance, the NC Division of Public Health guide to using sanitizer test strips walks through strip selection by sanitizer type.

How does Xenia handle sanitizer concentration logs?

Xenia turns the sanitizer concentration check into a recurring per-shift task on a tablet or phone. The store team enters the measured ppm, photographs the test strip as proof, and if the reading falls below the FDA Food Code target, a follow-up question and a corrective task fire automatically. The reading, the photo, the timestamp, and the corrective action all live in one audit trail the ops director can pull up across every location.

Here is how the workflow maps to the platform:

• Per-shift checklists. The sanitizer check runs as a recurring task. Opening, mid-shift, and the every-two-to-four-hour retest each become a scheduled line item with a timestamp and a completion record. The completion percentage becomes the store's pulse.
• Follow-up questions with required photo. When the cook enters a ppm below target, the form auto-presents "Sanitizer is below range. What did you do? Photo required." The photo of the test strip is captured at the moment of failure, not reconstructed after. The platform stores the photo as evidence. It does not interpret the strip color for you, so the read is still the staff member's job.
• Corrective action workflows. A below-target reading triggers an automatic corrective task ("re-mix the sanitizer, retest") assigned to the kitchen manager with a deadline, and escalates to the DM if it is not closed. The check and the fix become the same record. Most platforms collect the reading. Few drive it to closure.
• Conditional visibility and nullify scoring. A fuel-only C-store with no food service does not see the three-compartment sink questions, and is not penalized for items it does not have. A location running quats sees quat targets, a chlorine kitchen sees chlorine targets. Nullify scoring means a fuel-only store does not get marked down for missing food-service equipment.

The before-and-after is the whole point. Before: a ppm written in pencil on a clipboard at 4pm that nobody verifies until the health inspector arrives. After: a timestamped ppm reading with a photo of the strip, a corrective task if it failed, and an audit trail the DM can see across every location in real time.

| Approach | Paper clipboard log | Xenia digital sanitizer log |
|---|---|---|
| Proof of reading | A handwritten number, no verification | Timestamped ppm plus a photo of the test strip |
| Below-target response | Hope someone re-mixed it | Auto follow-up question and assigned corrective task |
| Escalation | None until the inspector arrives | DM escalation if the corrective task is not closed |
| Multi-unit visibility | Locked in a binder at each store | One issues-first dashboard across every location |

One note on scope: sanitizer ppm is a manual test-strip read, not a Bluetooth thermometer reading. This page is the sanitation gap that the Bluetooth thermometer setup items do not cover. Bluetooth thermometers handle temps. Chemical concentration stays a strip read. For how a failed reading becomes a tracked task, see our guide to the food safety corrective action workflow, and for why a sanitizer miss should score heavier than a cosmetic item, see critical vs minor food safety scoring and weighted audit scoring with critical-item thresholds.

Where do operators see results?

Operators see sanitizer concentration results in the issues-first dashboard: which locations logged an out-of-range reading, which corrective tasks are still open, and which sinks or stores are trending low across the week. The DM gets the problem view, not just a completion percentage.

The views surface what matters before the next failure forms:

• Open corrective actions from a below-target reading, sorted by store and deadline.
• Locations trending toward out-of-range sanitizer across multiple shifts. If sink #2 at four stores keeps reading low, that points to a dispenser or dilution-equipment problem, not a staff problem.
• The full audit trail per check: who tested, when, the ppm, the test-strip photo, and the corrective action, ready for the health inspector.
• AI-generated summaries that roll the week into a one-paragraph briefing per location or region.

The proof for the digital-log workflow this sanitizer check rides on comes from operators who already made the paper-to-digital move. Tempstop went paperless in 14 days, the exact clipboard-to-digital migration this log replaces. Mezeh cut manager phone calls 60% by moving frontline checks and accountability into the app. Power Market went live across 360 locations with QR deployment and 40% faster task resolution. None of these numbers are sanitizer-specific, and we will not pretend they are. They show the digital-log workflow holding up at scale.

For the bigger picture on how multi-unit restaurant teams run these checks, see Xenia for restaurant operations and the food safety compliance software overview. The dashboard is an operations-focused issues view, not a BI tool, and the summaries are descriptive, not predictive. They tell you what happened and what is still open.

How to set up a sanitizer concentration log in Xenia

You set up a sanitizer concentration log in Xenia by building a recurring per-shift checklist that captures the sanitizer type, the measured ppm, and a photo of the test strip, then adding a conditional follow-up and a corrective task that fire when the reading is below the FDA Food Code target.

1. Create a recurring checklist named "Sanitizer Concentration Check" and set it to repeat per shift (open, mid-shift, close) plus a two-to-four-hour interval during service.
2. Add a question for sanitizer type (chlorine, quats, iodine) so the right target shows.
3. Add a number field for the measured ppm reading, with a required photo of the test strip.
4. Set the pass thresholds to the FDA Food Code ranges: chlorine 50 to 100 ppm, quats per label up to 400 ppm, iodine 12.5 to 25 ppm.
5. Add a follow-up question that triggers when the reading is below target: "What corrective action did you take?" with a required photo.
6. Attach a corrective action that auto-assigns a re-mix-and-retest task to the kitchen manager with a deadline and a DM escalation.
7. Use conditional visibility so fuel-only or non-food-service locations do not see the sink questions.
8. Test the template at one location, then roll it out across all units.

Two notes for the franchise compliance officer. The AI Template Agent can convert an existing sanitizer-log SOP PDF into this digital checklist, so you do not rebuild it by hand. And offline mode matters for rural C-store kitchens with spotty connectivity: the check completes on the tablet and syncs when WiFi returns. If you want a paper starting point before you go digital, our temperature log template pairs with this sanitizer check inside the same HACCP checklist template.