How to Document a Sterilizer Load Log Correctly

A sterilization load log is the running record of how each cycle was monitored. The CDC is explicit that no single check is enough on its own: "The ability of a sterilizer to reach conditions necessary to achieve sterilization should be monitored using a combination of biological, mechanical, and chemical indicators." Your log is where those three streams of evidence come together, load by load.

The reason it matters isn't bureaucratic. As the CDC puts it, "Maintaining accurate records ensures cycle parameters have been met and establishes accountability." And there's a practical safety payoff: "if there is a problem with a sterilizer (e.g., unchanged chemical indicator, positive spore test), documentation helps to determine if an instrument recall is necessary." In other words, the log you keep today is exactly what tells you how far back to recall instruments if a spore test ever fails.

So the log does two jobs at once: it demonstrates compliance to an inspector, and it defines the boundary of any future recall. Both depend on it being complete.

Mechanical monitoring is the per-load layer, and the CDC advises doing it every time: "Mechanical monitoring should be conducted for every sterilizer load." The CDC describes it as "checking the sterilizer gauges, computer displays, or printouts, and documenting in your sterilization records that pressure, temperature, and exposure time have reached the levels recommended by the sterilizer manufacturer."

Translated into log fields, each load entry should capture at minimum:

• Date of the cycle
• Sterilizer identifier (by ID or location if you run more than one)
• Load or cycle number for that day
• Cycle type selected (e.g., wrapped, unwrapped, pouches)
• Temperature reached
• Pressure reached
• Exposure (cycle) time
• Chemical indicator result for the load (see the next section)
• Operator initials — who ran and verified the load

A printout or display that shows a short or cold cycle is your earliest warning of a problem; recording it every time is what makes that warning visible.

Chemical indicators are the second per-load layer, and their result should be recorded alongside the mechanical readings. The CDC's rule is that "a chemical indicator should be used inside every package to verify that the sterilizing agent has penetrated the package and reached the instruments inside." When that internal indicator can't be seen from outside, "an external indicator should also be used." The 2003 CDC guidelines put the same requirement plainly: "An internal chemical indicator should be placed in every package. In addition, an external chemical indicator (e.g., chemical indicator tape) should be used when the internal indicator cannot be seen from outside the package."

There's a step offices skip: reading the indicator at the right moment. The CDC says to "inspect the chemical indicator immediately when removing packages from the sterilizer; if the appropriate color change did not occur, do not use the instruments." A load log that notes the indicator result — pass or fail — for each load is how you prove that check happened.

Keep in mind what a chemical indicator does and does not tell you. It confirms the package was exposed to sterilizing conditions; it does not, on its own, prove the organisms were killed. That's the job of the weekly spore test.

The biological indicator — the spore test — is the only monitor that confirms lethality, and it's the entry inspectors most often check for by name. The CDC recommendation is that "a spore test should be used at least weekly to monitor sterilizers," and it "should use a matching control (i.e., biological indicator and control from same lot number)." There's also a per-load trigger: "a spore test should also be used for every load with an implantable device."

For each spore test, your log should record:

• Date of the test
• Sterilizer tested
• Indicator lot number
• Test result (negative/pass or positive/fail)
• Control result — which must be positive for the test to be valid
• Operator initials
• Any corrective action if the test failed

If a test ever comes back positive, that log line is the anchor for the CDC failure and recall protocol — it's how you identify the last negative test and therefore how far back to recall.

Most citations aren't about broken machines — they're about incomplete logs. The recurring problems are predictable:

• Missing weeks. A gap with no logged spore-test result reads, to an inspector, as a gap in sterilization assurance.
• Blank fields. A load row with no temperature, no operator initials, or no chemical-indicator result is treated as incomplete.
• Backfilling from memory. Filling in a week's worth of entries at month-end is where errors and gaps creep in. Log at the moment, not later.
• No corrective action recorded. A positive spore test or a failed chemical indicator with no documented response looks worse than the failure itself.

The fix for every one of these is the same: capture each load and each test as it happens, in a single consistent record, with no blank fields.

Paper logs are still legal, and the CDC does not mandate a medium — it advises you to "maintain your sterilization monitoring records (mechanical, chemical, and biological) long enough to comply with state and local regulations." Retention periods are set by your state, not by the CDC, so check your state's rule under state requirements and confirm it with your board.

What matters is that the record is complete, legible, and available on demand. Paper has real weaknesses here: thermal printout tape fades, fields get skipped, and a single lost binder erases years of proof. A continuous digital log timestamps every entry, makes missing weeks obvious before an inspector finds them, and lets you export a clean record for any date range in one step.

This is the exact problem ClaveLog was built around: QR-based load logging from a phone, spore-test tracking from any lab, and a one-click Inspector Packet — so your load log stays complete without anyone having to remember to backfill it. You can also start for free with the printable State Log tool.