Chapter 26: Conducting Process-Based Audits: A Step-by-Step Field Guide

The difference between an audit that ticks boxes and an audit that reveals system gaps comes down to methodology. Most plants default to a procedure-based audit: auditor opens your procedure manual and verifies that people are following what's written. This is necessary, but insufficient.
A process-based audit starts from a customer requirement and traces it through your operation to verify that each step is adding value and that controls are actually working. This approach surfaces gaps that procedure-checking misses.
Here's the flow:
1. Start with the customer outcome. Your audit brief asks: What does the customer need? For a machined component, it might be a dimensional tolerance and surface finish. For a service, it might be delivery on schedule. Write that requirement on your audit plan.
2. Map the process using a turtle diagram. Who (resources) carries out what activities (process), following which procedures and using which inputs to produce which outputs? The turtle diagram forces you to consider the entire context, not just isolated steps. If you're auditing the finishing process, you map backward to the assembly process that feeds it and forward to the packaging process that protects the finished product.
3. Identify the critical controls. Which steps in the process directly affect whether the customer requirement is met? At finishing, the critical control is the inspection and rework procedure. Secondary controls might include equipment capability, operator training on the new alloy, and preventive maintenance of the finish-line equipment. All matter, but critical controls get deeper audit focus.
4. Test controls through observation and evidence. You don't audit by interviews alone. Walk the floor. Watch an operator finish a part. Ask them to show you how they verify a dimension or a surface. Look at the inspection records for the past 30 days.
If a critical control is documented as in place but you can't find evidence it's actually being executed, you've found your finding.
5. Trace at least one complete part or service record. Pick a customer order from the past 60 days. Follow the documentation from order entry through design (if applicable), procurement, production, inspection, and shipment. This reveals integration gaps that isolated process audits miss. You might discover that the design team approved a material change, but the procurement team didn't, and production is using the old material specification.
The questioning techniques matter as much as the methodology. Ineffective auditors ask yes/no questions ("Are you following the inspection procedure?") and leading questions ("You're doing X, right?"). Effective auditors ask open-ended questions that invite the auditee to explain: "Walk me through how you verified this dimension." "What did you do when this gauge failed calibration last month?" "How do you know if you've applied the finish correctly?" These questions reveal whether the control is a ritual or a genuine protection.
When you find a gap—say, an operator can't articulate the acceptance criteria for surface finish, even though it's in the procedure—don't immediately write a nonconformance. Ask more questions. Is this a knowledge gap, a communication gap, or a procedure that's unclear? That diagnosis is the beginning of an effective corrective action, not the end of the audit.
Chapter 25: Training Effective Internal Auditors From Your Existing Team
You have two paths to building internal audit capability: send people to an external ISO 9001 lead auditor course (typically 40–60 hours over 5 days), or develo
Chapter 27: Audit Findings to Corrective Action: The Handoff That Most Plants Break
This is where most internal audit programs collapse. The audit is done, the report is filed, and then... nothing happens with urgency. Findings sit in a queue.
Request a Consultation
Fill in your details and we'll get back to you.

