By Igor Published · Updated

Conducting Quality Inspections: From Planning to Action

A quality audit is a planned system, process, or product audit that flags deviations before they reach the customer — and demonstrates that processes are under control. An effective quality inspection program comes down to four things: a risk-based inspection frequency, audit checklists that actually work on the floor, a well-trained audit team, and tight action follow-up. This article shows how to set up, run, and maintain all four together — whether you work under ISO 9001, IATF 16949, or from a Lean and 5S foundation.

Why structured quality audits make a difference

Structured quality audits make a difference because they don't just log deviations — they make it demonstrable that those deviations get resolved, keeping your product quality on track and your system operationally reliable. Every company with a quality management system runs checks: quality rounds, process indicators, product inspections. The difference isn't whether you check, but how you check.

Poorly structured quality checks produce three symptoms we see time and again in audits:

  • The same deviations keep recurring, because the corrective action was never implemented or verified.
  • Checklists that haven't been updated in years, while processes, drawings, and customer specifications have since changed.
  • Checking for the sake of checking — as long as the rounds get done, the requirement is met, without quality performance actually improving.

Good quality checks close those gaps — and in doing so, feed directly into periodic management reviews.

The framework determines the reporting, not the execution

Whichever standard you fall under — ISO 9001, IATF 16949, AS9100 — or whether you work from a Lean and 5S foundation: the execution logic of an audit/inspection/check is nearly identical. You control quality aspects, safeguard customer and legal requirements, and verify according to the set frequency. What differs per system are the reporting and scope requirements; you take that interpretation from the standard itself. We focus on the part that's the same everywhere: how to run audits efficiently and make them add value.

Designing your audit program

A workable audit program is built around six elements — scope, frequency, role division, time investment, training, and action management — plus after-the-fact analysis.

1. Scope — what do you check, and at what level? The biggest challenge lies in getting the checklist right: the audit's objective and the inspection points must be sharp and clear to the person carrying it out. The starting point is always process documentation and customer requirements. Typical scope categories:

  • Quality checks (incoming, in-process, final) — dimensions, surface quality, functionality, material certificates, measuring equipment calibration
  • Start-up inspections — process settings, materials present, line clear of materials from the previous run, cleanliness or flush programs
  • Assembly checks — correctness and sequence of components, torque values, visual final inspection, traceability of serial and batch numbers
  • 5S rounds and process or system audits — compliance with requirements and effectiveness of controls, assessed against legal, customer, or other stakeholder and standard requirements.

2. Check on risk, not on the calendar. Processes with a different risk profile call for a different frequency and intensity. Split your scope along two questions: how likely is this process to produce a deviation (quality risk), and how severe is the consequence if that deviation goes undetected (criticality)? Together, these two determine how heavily you inspect:

  • High risk + high criticality (product safety or liability consequences): 100% inspection or high-frequency sampling, multiple verification, full traceability.
  • High risk + low criticality (cosmetic deviations): increased sampling frequency, visual inspection against a reference standard.
  • Low risk + high criticality (routine maintenance on critical systems): standardized checks with independent verification.
  • Low risk + low criticality (5S compliance and internal process and system audits): weekly or monthly rounds with trend monitoring, or even lower frequencies depending on the importance of process control and findings from previous audits.

3. Role division. On the line, the operator is your first line of inspection — deviations get stopped at the source. Quality is built in at the source, not caught at final inspection. Product quality checks belong with QC; general rounds such as 5S go through the operational supervisor or QA. Build in independence: don't have process and system audits carried out by the person responsible for day-to-day execution.

4. Time investment. Too many checkpoints at too high a frequency means checks get rushed. Plan no more than can realistically be assessed — proper observation requires standing still. A good audit requires checking and comparing, consulting requirements, reviewing records, and logging findings.

5. Training and instruction. We repeatedly see a questionnaire drawn up and handed off without explanation. How is that person supposed to know what a question actually means? That requires explanation — especially where customer specifications or legal requirements are involved. Some checks, moreover, may only be carried out by authorized, qualified personnel. There's no point putting someone on an audit if they don't understand the process. Select for competence, not availability.

6. Action management. A good check is followed by a proper action: feedback, assignment, deadline, and follow-up. If you keep flagging the same points without anything being done about them, your inspection program becomes make-work. But stay critical. "Nice to have" is not the same as necessary. Set priorioties with different deadlines. Be willing to decide that some proposed improvements won't be picked up — and communicate that decision too.

Analysis. Improvement requires trend analysis: where does the organization structurally underperform, which deviations keep recurring on the same machine or assembly step? Track a handful of hard indicators — first-pass yield, rejects, rework — and adjust based on them.

Carrying out the check on the shop floor

A quality audit is carried out in seven steps: prepare, observe, capture evidence, classify, assign action, close out with the person involved, and report immediately:

  1. Preparation. Read the previous report and check which actions are still open. Study the checklist before you start and determine the sequence. Bring the checklist app on phone or tablet, and check that current drawings, work instructions, and specifications are available on site.
  2. On the shop floor, stand still. Observe, check against the checklist, and evaluate. For 5S rounds: assess each S individually — not the overall impression, but compliance with the standard per element.
  3. Capture evidence on the spot. Take photos — always of negative findings. Log measurement results immediately, not afterward. For assembly checks, serial, batch, and revision numbers belong with the evidence.
  4. Classify immediately. OK / Not OK / N/A, a percentage score (e.g., 5S), or a measurement score for product checks. A measurement outside tolerance is grounds for rejection or re-assessment of the entire sample. For system audits, sometimes critical/major/minor.
  5. Assign the action. Discuss with those responsible and determine, where possible, what action is needed on the spot — then assign it, usually to the person responsible for the process or machine.
  6. Close out with the person involved, on the spot. Read out loud what you've recorded to the operational owner. They correct anything inaccurate and confirm the rest. That prevents the classic "that's not right" weeks later, and reinforces ownership.
  7. Generate the report immediately, not next week. With a digital app, the check is done as soon as findings and photos are in it: the report is available right away and goes out by email.

From practice

During a line start-up check at a food packaging company, we found packaging materials, labels, and even production orders from previous runs still sitting at multiple stations. Yet the checkpoint "line clear of materials from previous orders" was always marked "OK": the inspector had never been told what this meant and didn't recognize packaging components and labels as "materials." The fix wasn't an extra checkpoint — it was training on what "free of contamination" means and what risk it poses for a new run. The checklist was also revised: broken into sections, with more explicit questions, explanations, and reference images of the ideal situation.

A finding only becomes valuable once it's immediately followed by an assigned action with a deadline and verification. A check without action management is make-work. This is exactly where many quality audit programs fall short: findings get logged and only reach the person who needs to turn them into actions weeks later — by then the context is gone and actions stay half-hearted. Three rules to prevent this:

  • Strike while the iron is hot. Decide right after the check who needs to take which action, and by when. For high criticality: act immediately, no waiting.
  • Verification is part of the action, not an afterthought. The action isn't "fix problem X" but "fix it, and demonstrate that it's fixed" — typically through a measurement, photo, or recheck.
  • Recurring findings are a system signal. The same deviation showing up repeatedly on the same machine or in the same process? Then the control measure, work instruction, or maintenance program isn't effective. Fix the system, not the incident.

Six pitfalls we see in teams

The six most common pitfalls in quality audit programs are a generic checklist, calendar-driven frequency, missing measurement evidence, checking as a ritual, and actions without verification.

  • Checklist as a form, not a tool. Sample checklists get copied without being adapted to a company's own processes, machines, and specifications. Result: half the questions are "N/A," the other half routinely "OK" — without observation or measurement.
  • Frequency by calendar, not by risk. Department A every Tuesday and department B every Wednesday isn't the same as risk-based checking. High risk or high criticality deserves more intensive inspection.
  • No measurement evidence for a deviation. "Workbench damage with a risk of scratches on components to be assembled," without a location and photo, is unrecognizable within a week. Location notes and photo evidence are a must; where traceability matters, record batch and serial numbers.
  • Incompetent auditors/inspectors. You're not competent if you lack knowledge of the process and the requirements you're checking against, if you haven't been briefed on the objective of the audit or inspection system and how to report, or if you don't ask probing questions and don't verify that what you're told is actually being done. You're not competent if you're unwilling to raise findings — but you're equally not competent if you record personal preferences as improvement points in audit and inspection reports. In short, auditors need to be selected on competence and trained.
  • Checking because it's required. The goal is to demonstrate that quality aspects are under control and deviations get flagged — not to demonstrably follow the schedule. A 5S score of 100% on every round is unlikely in an active environment; the eye needs to stay critical.
  • Action without a verification moment. "Resolved" is not the same as "checked that it works." Without effectiveness verification, you run the same risk again.

Frequently asked questions

How often should I schedule internal quality audits and checks?

Set the frequency based on the risk and criticality profile of each process: critical or high-risk processes call for higher frequency or 100% inspection, low-risk processes can be covered with sampling. Factor your complaint history into the frequency as well.

Who within a team should carry out quality checks?

On the line, the operator is the first inspector: deviations get stopped at the source. Independent checks by quality staff, preferably cross-functional, come on top of that. Some checks require authorized, qualified personnel.

How do I distinguish quality risk from criticality risk?

Quality risk is the likelihood that this process produces a deviation. Criticality is the severity of the consequence if that deviation goes undetected. A process can often go wrong without serious consequences, or rarely — but then fatally. Together, these two dimensions determine frequency and intensity.

How do I stop checklists from going out of date?

Schedule fixed review moments (annually, for example) and include an "improvement opportunities" field in the checklist itself. Link the inspection system to your MOC process for interim changes. Tie reviews to changes in customer specifications or drawings, to incidents and complaints, and to rounds that expose structural problems.

How do I handle recurring quality deviations?

Treat them as a system signal, not an incident. If the same deviation keeps coming back, run a root-cause analysis and address the cause, not the symptom. Record the effectiveness verification so you can show it's genuinely resolved this time.

Can I use digital photos as evidence in an audit?

Absolutely. Photo evidence shows the conclusion is grounded in an actual finding. Add measurement values to the inspection record and ensure unique photos per check — reusing photos is a hard no. As long as they're dated and traceable in a controlled system, they hold up.

How do I combine quality audits and inspections with safety and environment, hygiene, or security?

Through a single inspection platform: separate checklists per domain, a shared action module, and joint trend analysis. Overlap between quality and safety (machine safety, 5S) delivers a benefit, and having all findings in one place saves work.

How do I measure whether my quality audit/inspection program is working?

Five indicators: (1) first-pass yield or internal reject rates — the trend figures alone confirm the inspection system is working; (2) the share of checks that run on schedule; (3) the share of deviations resolved within deadline; (4) the frequency of recurring findings on the same process; (5) results from external audits and customer satisfaction over 2–3 years.

About the author

Igor Bots — ISO Lead Auditor 9001. More than 30 years of experience in QHSE implementation, training, and auditing across industry, logistics, and manufacturing companies. LinkedIn

Get started today

Start your 30-day free trial with Easy to Inspect — including ready-made templates for quality checks, assembly checks, maintenance rounds, and 5S audits. Works for ISO 9001, IATF 16949, and AS9100. Your first check runs within the hour. Start your free trial.