Inspections and corrective actions that close the loop

Most small businesses already inspect things. The warehouse checks a delivery before signing for it. The technician tests the unit before leaving the site. The kitchen checks the fridge temperature every morning. What is usually missing is not the inspection; it is what happens after a check fails.

A damaged carton gets put aside and forgotten. A reading out of range gets a shrug and a note on paper. A month later the same supplier sends the same damaged goods, and nobody can say how often it has happened. Quality management sounds like a big-company topic, but at its core it is a simple loop: check, record what failed, fix it, make sure the fix worked, and learn from the pattern.

This guide explains that loop in plain terms and shows how to run it without a quality department.

The loop in four steps

• Inspect against a checklist that says what passes.
• Record a non-conformance when something fails, with how serious it is and who owns it.
• Plan corrective and preventive actions: fix this case, and stop it happening again.
• Verify that the action really worked, by someone other than the person who did it.

Then look at the patterns every month: which checks fail most, on which products, with which suppliers.

Write checklists that say what passes

A checklist question that cannot fail is not a check. "Check the packaging" invites a tick; "Packaging intact?" with "no" as a failure is a check. Good inspection questions come in a few types:

• Yes or no, with the failing answer stated. "Damage found?" fails on yes; "Seal intact?" fails on no.
• A reading with limits. "Freezer temperature: between −18 °C and −15 °C." "Torque: at least 40 Nm." The limits are written on the question, so the inspector does not need to remember them.
• A choice with the passing options marked: "Label condition: good, worn, missing", where only "good" passes.
• A photo, when you need evidence: the pallet on arrival, the installed unit, the meter reading.
• A note for anything the inspector wants to add, which never fails by itself.

Keep each checklist short, ten questions or fewer for routine checks, and decide how serious a failure is: minor, major or critical. A critical failure, such as a safety issue, should be impossible to overlook.

Inspect where the work is

Inspections done at a desk afterwards are memories, not inspections. The receiver at the loading dock, the technician on site and the production lead on the floor should fill in the checklist on a phone, there and then, with photos. Warehouses, basements and sites often have poor signal, so the checklist must keep working offline and send itself once the connection comes back.

Link each inspection to what it checked: the goods receipt, the purchase order, the piece of equipment, the job. That link is what lets you see later that a supplier failed five deliveries out of twenty.

Turn a failure into a non-conformance

When a check fails, record a non-conformance. It is simply a record that something is not right, with:

• What failed, ideally filled in from the failed answers.
• Severity, which sets the deadline. Many teams use something like 3 days for critical, 14 for major and 30 for minor.
• An owner who is responsible for resolving it.
• The quantity concerned, for goods.
• A disposition: return to the supplier, rework, scrap, use as is, or hold until decided.

Non-conformances also come from outside inspections: a customer complaint, a defect noticed on the floor, a field return. Record those the same way, so all problems live in one list.

Find the root cause

The disposition deals with the goods in front of you. The root cause deals with why it happened. A simple method works well: ask "why?" until the answer is something you can change.

For example: the cartons arrived crushed. Why? They were stacked too high in the truck. Why? The supplier changed carrier. Why did we not notice? Our purchase order does not specify packaging or stacking. That last answer is something you can change.

Corrective and preventive actions, with a second pair of eyes

Each non-conformance gets one or more actions, each with an owner and a due date:

• A corrective action fixes this case: "Ask the supplier for a replacement batch."
• A preventive action stops it from happening again: "Add packaging and stacking requirements to the purchase order template."

The step most teams skip is verification. When the owner marks an action done, someone else should check that it really was done and that it worked. This is not about distrust; it is the same reason you do not approve your own expense claim. A second person catches the action that was "done" by sending an e-mail nobody answered. Our post on approvals that don't slow you down explains why the four-eyes rule pays off in other places too.

The non-conformance closes when its last action is verified, not before.

Share supplier quality with the supplier

Suppliers improve faster when they see the same numbers you do. Track for each supplier how many inspections passed, the reject rate over the last year, and their open non-conformances. A simple grade from A to D is easy to discuss in a supplier review. Showing it in a supplier portal turns a tense phone call into a shared fact.

Read the patterns every month

Once a month, look at three views:

• Open non-conformances by age and severity. Anything critical and overdue needs attention today.
• Repeat failures: which questions, products, assets or suppliers fail again and again. The top three items usually account for most of your problems.
• Pass rate by checklist. A checklist that always passes may be too easy; one that fails half the time may point at a process that needs redesign.

How to do it in Kluvan

Quality runs this loop from the inspection to the verified fix. Kluvan runs online with nothing to install, and inspectors use their phone's browser.

• Build inspection templates. Questions can be yes / no, a reading with lowest and highest values that pass, a choice, a note or a photo, with the severity of a failure. You can also start from a published Studio form. Templates are versioned, so past inspections keep their version. See build an inspection template.
• Inspect a delivery, equipment or a job. Start an inspection from a goods receipt, purchase order, equipment, field job or work order, and see it on the record's linked items. See inspect a delivery, equipment or a job.
• Inspect on the phone, even offline. Big yes / no buttons, photos and drafts; an inspection filled in without signal is sent once the connection returns. See inspect on your phone.
• Non-conformances. A failed inspection opens one with its severity, owner, due day (30, 14 and 3 days by default for minor, major and critical), the record and the rejected quantity. Record the root cause and the disposition. See handle a non-conformance.
• Corrective actions with verification. Plan corrective and preventive actions with an owner and a due day. Kluvan refuses a verification by the action's owner or by whoever marked it done: a second person must verify and close it. See plan and verify corrective actions.
• Supplier quality. Each supplier gets a quality score, a grade and a reject rate, shown on Procurement records, and you can share it read-only in the supplier portal.
• Reports. Pass rates, open non-conformances by age and severity, and repeat failures by template, record and supplier.

Overdue non-conformances and late actions are sent to their owners and managers once a day. Quality is sold on its own and comes with the Service Business and Trade Business bundles and Kluvan One; see pricing.

Some things are outside what Quality does today: statistical process control, calibration and audit programmes are not part of it, and suppliers can see their non-conformances in the portal but cannot answer them there yet.

Inspections at the door are the first half of good purchasing. The second half is paying only for what you accepted, which our post on three-way matching covers. If you send technicians to sites, field service job costing shows how inspections and rework feed the margin.

Pick one checklist this week, the one that fails most often on paper, and run the full loop on it for a month.