Five Kinds of Hand Hygiene Violation. Your Program Has One.

Your GMP checklist has one line for handwashing. The FDA model inspection form spreads the same ground across five numbered items: hands, bare-hand contact, sinks, fingernails, and gloves. Three sit in the risk factor half of the report. Two sit where the violation count never reaches them. That split can turn three separate findings into one corrective action, and leave the rest to be cited again under the same item numbers.

The inspector's form splits hands five ways

Five numbered items on the FDA model Food Establishment Inspection Report cover what your program files under handwashing. From the marking instructions in the 2022 Food Code, Annex 7, Guide 3-B:

• 8. Hands clean and properly washed

• 9. No bare hand contact with RTE foods or a pre-approved alternate properly followed

• 10. Adequate handwashing sinks, properly supplied and accessible

• 40. Personal cleanliness

• 46. Gloves used properly

Items 8, 9 and 10 sit together under "Control of Hands as a Vehicle of Contamination," inside items 1 through 29, the risk factor and public health intervention half of the form. Items 40 and 46 sit in the Good Retail Practices half, under "Prevention of Food Contamination," with a wiping-cloth item and a produce-washing item between them.

That split isn't cosmetic. The header field is labeled "Number of Risk Factor / Intervention Violations," and it counts only boxes marked OUT in items 1 through 29. The marking instructions say the Good Retail Practices "have been given less importance on the inspection form." For most of them the guide drops the risk factor IN, OUT, N.A. and N.O. differentiation. The inspector marks the item, documents each violation in "Observations and Corrective Actions," and records COS or R on items marked OUT. A fingernail finding and a glove-use finding are real citations that never touch that number.

Each item carries its own stack of code sections. Item 8 pulls in five: clean condition of hands and arms, the cleaning procedure (20 seconds, in a handwashing sink), when to wash, where to wash, and hand antiseptics. Item 10 pulls in eight, from sink numbers and placement to soap, hand drying, signage, and the requirement that the sink deliver water at a minimum of 85°F through a mixing valve or combination faucet. Item 10 for a blocked sink and item 10 for a cold-water-only sink are the same number against two problems with two different owners.

Gloves split as well. Item 46 reaches only §3-304.15(B)-(D), the slash-resistant and cloth glove limits. The single-use glove rule, one task and then discard, is §3-304.15(A), and the guide cites that one under item 15, "Food separated and protected."

Two adjacent items get mistaken for this group. Item 6 (proper eating, tasting, drinking, or tobacco products use) and item 7 (no discharge from eyes, nose, and mouth) are hygienic practice items, not hand items. They show up on the same report because §2-301.14(D) requires a handwash after coughing, sneezing, tissue use, tobacco use, eating, or drinking. Tasting is somewhere else again, under §3-301.12. Count them as triggers, not as hand hygiene citations.

Manufacturers get the same split with different numbers

Food manufacturers hit this taxonomy problem under a different citation scheme. 21 CFR 117.10(b) lists nine numbered methods for maintaining cleanliness in a single paragraph. Five of them are personnel-hygiene provisions covering the same ground:

• (b)(2) maintaining adequate personal cleanliness

• (b)(3) washing hands thoroughly "before starting work, after each absence from the work station, and at any other time when the hands may have become soiled or contaminated"

• (b)(4) removing unsecured jewelry and hand jewelry that can't be adequately sanitized

• (b)(5) maintaining gloves in an intact, clean, and sanitary condition

• (b)(8) confining eating food, chewing gum, drinking beverages, and using tobacco to areas other than where food may be exposed or where equipment or utensils are washed

Two observations on a Form 483, one against 117.10(b)(3) and one against 117.10(b)(5), are two problems: a wash-timing failure and a glove-condition failure. They get read as "personnel hygiene" and closed with a retraining roster.

Co-packers get a third version of it: several customer schemes, a state inspection, and a GFSI-benchmarked audit mapped against one program, each with its own terminology and numbering.

A 40-line report is not 40 problems

Raw granularity buries the action. The obvious lesson from the five-item split is "be more granular," and it's only half right.

Two failure modes show up, and they're opposites.

The first is collapse. The report has three hand findings, the QA manager reads the theme instead of the lines, opens one corrective action called "handwashing retraining," and closes it with a signed roster. The sink that couldn't reach 85°F is still cold. The cloth gloves are still touching RTE product. Both get cited again, and the sink comes back with the R box marked.

The second is explosion. A 40-line report becomes 40 corrective actions with their own owners and due dates, and by week three nobody can tell which of them share a cause. The log stops being something anyone reads.

The report gives you a list of line items. It does not give you the list of causes, and you need both to close it out.

The mapping step nobody writes down

Between the inspection report and your corrective action log there's a translation step, and in most facilities it lives in one person's head. Write it down: one row per cited item, mapping the inspector's line to the program element that owns it.

The mapping is where the ownership problem surfaces. On a plant program, all five hand items usually point at the same SOP and the same owner. On the inspector's form they belong to different functions:

Item 10 is a maintenance work order. Item 46 is a training and supply problem. Retraining the crew fixes neither, which is why the retraining corrective action keeps failing verification.

One mechanical rule for building it: use your last report's line items, not FDA item numbers. The Food Code is a model that jurisdictions may adopt and modify, so the wording on the report you actually received is the wording your crosswalk has to carry.

Open corrective actions per cited item, roll up per root cause

Open one corrective action per cited item, then group them by root cause. Doing it in the other order is what produces the repeat citation.

The reason is verification. The guide ties R to the same violation under a particular item number cited on the last report, so your closure evidence has to line up with each cited item and each violation under it.

The guide's own example is the cleanest version of this. Item 10 is marked out because the hand sink has no soap and no paper towels. The person in charge puts soap out and does not replace the towels, so COS is not marked, because "all violations under that item were not corrected." One item number, two violations, one of them closed.

Root cause grouping sits above the item log, not in place of it. Say three citations trace back to one cause: the only hand sink in the prep area runs cold because a mixing valve failed. You have one fix and still three item closures, each with its own evidence: the valve repair, the verification that the sink now delivers 85°F, and the observation record showing the crew washing there instead of at the prep sink. Group the rows by cause to decide what to fix, and keep the item log as the thing you close against.

Getting from an immediate correction to a real root cause is its own discipline, and it drives most repeat findings. We covered that depth problem in seven HACCP plan mistakes that lead to audit failures. This is the direction problem: item first, cause second.

Reconcile every cited line against its status before you call the report handled. An item can be open, corrected on site, or already closed, and an unexplained gap between cited lines and tracked items is worth chasing.

Build the crosswalk from your last report

Pull your most recent inspection report and build a one-page crosswalk. It works on a report from any authority.

One row per printed line item in the "Observations and Corrective Actions" section of the report, never per theme.

Four rules make it useful:

1. No merging. Two cited items never share a row, even when they share a cause. The root cause column is where they meet.

2. A blank program element is the finding. A cited item with nothing in column three means the inspector is measuring something your program doesn't track.

3. One accountable owner per row, by name. The same owner can legitimately hold several rows. Record why they hold each one.

4. Carry the repeats forward. Any item marked R gets flagged. R means the same violation under that item was cited on the last inspection, so find out whether the prior correction was incomplete, ineffective, or never made.

Build it on the last report and the gaps show up immediately. Do it again after the next inspection and you have a trend line on which program elements keep drawing citations, which gives an auditor a traceable record of what recurred.

Several of these items close on observed behavior rather than a document, so the training and competency side matters too, but the crosswalk comes first: it tells you what to train against.

Where the work actually goes

Most of the labor here is transcription: getting a scanned report into rows a corrective action system can track, and getting the facility items in front of maintenance instead of QA.

That transcription is what Beacon does with a regulatory inspection. The uploaded report gets extracted into coded violations, a person reviews and commits them, and only then do committed critical violations create CAPAs while non-critical ones create follow-up tasks. Owner assignment follows the facility's resolved responsibility settings.

Your program shouldn't make the inspector's item numbers its internal taxonomy. Use them as the crosswalk's traceability key and nothing more.

If you want to see how an inspection report turns into tracked corrective actions without the retyping, book a walkthrough.