How to Build a Per-Unit Reprocessing Log

When a surveyor asks how you know a returned hospital bed was cleaned before it went back out, "we always clean everything" is not an answer. They want to see the record. Specifically, they want to see the record for that unit, on that day, by that person, with that process.

Most DME providers do clean their equipment. The problem at survey is rarely the cleaning. It is the documentation. A defensible reprocessing log is what turns a routine practice into something a surveyor can verify, and building one is more about structure than effort.

What a defensible reprocessing record contains

A useful per-unit cleaning log should answer five questions. The accreditor will assess whether the record and the supplier's process meet its standards.

• Which unit, by serial. Not "a wheelchair" but the specific serialized asset. This is the difference between a general claim and verifiable evidence. Per-unit identity through serialized-asset-tracking is the foundation everything else sits on.
• Who did it. A named person accountable for the work, not an anonymous initial that could belong to anyone.
• When. A real timestamp, not a date written in later from memory.
• What process. The cleaning or disinfection method used, tied to the manufacturer instructions and your infection-control policy for that equipment type.
• Outcome. The result of the work, ending in a clear status that the unit is patient-ready or, if it failed inspection, that it was pulled from service.

That last field matters more than people expect. A record that shows cleaning started but never confirms the unit passed and was released is an incomplete chain. Surveyors read incomplete chains as gaps.

Why paper logs fail at survey

Paper reprocessing logs feel thorough because they fill up with entries. Under survey scrutiny they fall apart in predictable ways.

They are not per-unit. A clipboard log usually records "cleaned 6 beds today" rather than which six serials. When a surveyor pulls a specific bed and asks for its cleaning history, you cannot find it, because the paper was never organized around the individual asset.

Timestamps are soft. A handwritten date can be filled in at the end of a shift, or the end of a week. There is no way to prove the entry was made when the work happened, which is exactly what a surveyor is testing for.

They break the link to the patient timeline. The whole point is to show that a unit was cleaned after it came back and before it went out again. Paper logs live in a binder, separate from your dispatch and delivery records, so reconstructing that sequence means cross-referencing three different documents and hoping the dates line up.

They go missing. Binders get lost, coffee-stained, and stored off-site. A record you cannot produce on the day of survey is a record that does not exist.

The underlying issue is that paper organizes by day and by person, while a surveyor investigates by unit. You are answering a question the document was never built to answer.

How per-unit records support a survey

The fix is to link the actual cleaning and inspection log to the specific unit. TrackDME can timestamp when staff mark that unit ready, but its readiness history does not capture the cleaning method or inspection result. The separate log must answer those questions.

Think of it as a per-unit operational history alongside a separate cleaning and inspection log. Together, those records should show:

1. It came back from a patient on this date (check-in).
2. It was reprocessed by this person, using this method, on this date and time.
3. It was marked patient-ready as a result.
4. It went back out to the next patient only after that.

That sequence can support a survey when the physical cleaning and inspection details are documented in the separate log. A readiness timestamp alone cannot prove the work occurred or guarantee that an accreditor will accept the evidence.

The most reliable version of this is a hard gate. A returned unit stays locked from re-rental until staff mark it ready after completing the required work. That is the idea behind the reprocessing gate, and it does two jobs at once: it holds the unit from checkout until someone marks it ready, creating an attributed readiness entry. Staff still need to perform and document the physical cleaning and inspection.

The per-unit readiness event helps put the cleaning process in sequence with recorded unit history. The separate cleaning log supplies the evidence of what was physically done.

Fit it into your accreditation prep

Reprocessing documentation is one line item in a larger survey readiness effort. It connects to your standards on infection control, equipment maintenance, and patient safety, all of which a surveyor reviews together. Treat the cleaning log as part of that whole, and use a DMEPOS accreditation checklist to make sure it lines up with the rest of your evidence rather than standing alone.

The goal is not a fatter binder. It is a record that answers the surveyor's actual question, per unit, on demand.

Make the record build itself

In TrackDME, choose Clean before renting again for the equipment types that need a cleaning hold, or require cleaning company-wide. Staff confirm the return, perform the work, then select Mark ready. The unit history records the readiness transition. Keep detailed cleaning, inspection, and other records required by your own procedures alongside it.