Everything an auditor writes down later, they saw here. An audit that stays in the meeting room hears the process as it is described, and the description is usually correct and usually incomplete: nobody describes the workaround they invented last spring. In audit A-16 of the valve plant, three of the four and a half hours were spent at the line.
The six moves
Open the audit properly. Objective, scope, criteria, and how findings will be handled. Five minutes of this saves an hour of defense later.
Walk the process in the direction of the material, with the supervisor, and let the line explain itself before asking anything.
Ask open questions and then be quiet. The second half of an answer is usually the useful half.
Ask to be shown, not told. A screen, a record, a part, a step at the workplace.
Draw the sample by the rule written in preparation, and note what was drawn: which orders, which stations, how many.
Close in the area. Read every finding out loud with its evidence before leaving.
Sampling without statistics
An audit sample does not prove a defect rate. It shows whether a process can hold its own rule. Five rules make it defensible.
Write the rule before you draw: five to ten cases per question, chosen in a way you can repeat. Spread the sample across days, shifts, operators and products. Include the awkward cases: the rush order, the reworked unit, the new operator. Record what you drew in the finding itself. And follow a hit: one deviation is a reason to draw more, not to close the question.
At station 3 the auditor asked for eight assembly orders of the last two weeks. Three of them had been built against revision 4 of the work instruction. Revision 6 had been released in March. The number that matters is three, and the finding says eight.
When the answer avoids the question
| What you hear | What to do |
|---|---|
| “We always do that.” | Ask for the last three times. Then look at them. |
| “That is handled in the system.” | Ask the person at the station to show you, on the screen they use. |
| “That was a one-off.” | Accept it and ask for the next case of the same kind. |
| A long story about another department | Note the hint, finish your question, raise it in the audit it belongs to. |
| “Who told you that?” | Name the evidence, never the person. |
None of these is a trick. They turn a general statement into something both sides can look at together, which is also the fastest way out of an argument.
Two levels of audit
A process audit of three to five hours and a shift audit of fifteen minutes find different things, and a program needs both.
| Process audit | Shift audit | |
|---|---|---|
| Who | Trained auditors from another area | Supervisors and managers of the area |
| Questions | Six to ten, written for this audit | The same five to eight points every time |
| Result | Graded findings with causes and effectiveness checks | Corrected on the spot or one action on the board |
| Frequency | Once or twice a year by risk class | Weekly or per shift |
The shift audit keeps known rules alive and corrects small drift immediately. The process audit asks whether the rules themselves still fit the process and its risks. A point that keeps failing in the shift audit is an input for the next process audit, and a nonconformity from a process audit often becomes a new fixed point on the shift route.
The rule of evidence
If you cannot name what you saw, where, and how much of it, you have an impression and not a finding. Impressions belong in the closing conversation, not in the report, which is read by people who were not there.