Corrective Actions

Finding a problem is the easy half

Inspection is the part of quality management everyone does. Somebody walks the account, notices what’s wrong, writes it down. The report is filed, and often that is where it ends — not through negligence, but because a finding without an owner belongs to nobody.

The failure mode is predictable. The report says the same thing next month. And the month after that, everyone stops reading it, because a document that describes problems without resolving them trains people to ignore it.

Findings become tasks, not entries

When a supervisor scores an inspection, anything below standard is converted directly into a corrective task — with a named owner and a deadline. It appears in that person’s queue alongside their scheduled work. It does not close on its own, and it cannot be closed by silence: someone closes it, at a recorded time.

Issues raised by your team enter the same queue, on the same terms. That symmetry matters more than it sounds. If a client complaint travels down a different path than an internal finding, the client’s issue is handled as a relationship problem rather than an operational one — which is exactly how vendors end up managing perception instead of buildings.

The second time is a different problem

The most useful thing this system does is notice repetition.

A finding that appears once is an incident. The same finding three times is a symptom, and treating it as three incidents means cleaning the same thing three times while the actual cause stays untouched. A restroom running out of supplies repeatedly is not a cleaning failure — it’s a stock level set wrong, or a dispenser wasting product, or traffic the scope never accounted for.

Recurring issues are flagged as recurring and trigger a root-cause review rather than another correction. The output is usually a change to the scope, the frequency or the stock levels — and then the finding stops appearing at all, which is the only real fix.

Where it connects

Corrective actions are what make the rest of this section honest. Inspections produce the findings, client feedback adds what your team sees, and the closure record feeds the account’s Protex Verified score. Critical incidents left open can block certification entirely — which is the point. A certificate awarded over an unresolved problem would be evidence of nothing.