A finding is read by people who were not in the room. It has to carry its own proof. If it does not, the closing meeting turns into a discussion about wording, and the thing that was actually seen disappears.
Three grades, one rule
| Grade | When | What it triggers |
|---|---|---|
| Nonconformity | A requirement of the criteria is not met, and the evidence shows it | Cause, action, owner, date and an effectiveness check |
| Observation | The requirement is met, but the way it is met depends on luck, memory or one person | Action with an owner and a date, no formal cause analysis |
| Opportunity | Nothing is wrong, something could be simpler, faster or safer | Handed to the process owner, who decides freely |
The grades only work if every auditor uses them the same way. The fastest way to get there is to grade five real findings together twice a year and argue about those, not about definitions.
Splitting nonconformities into major and minor is worth doing only if the split changes something, for example containment and a report to the plant manager within one working day. If nothing changes, the split creates arguments and no action.
The four parts
Every finding has a requirement, evidence, a place and time, and a grade.
- Requirement: only the released revision of a work instruction is used at the workplace.
- Evidence: three of eight assembly orders sampled at station 3 were built against revision 4.
- Place and time: station 3, early shift, orders of 14 to 22 October.
- Grade: nonconformity. Revision 6 is released since 12 March.
The requirement comes first for a reason. An auditor who cannot name the requirement has found something interesting, not something that has to change.
Wording
| Do not write | Write |
|---|---|
| “Document control is not working in assembly.” | “Three of eight orders sampled at station 3 were built against revision 4; revision 6 is released.” |
| “The team leader did not withdraw the old copy.” | “The station folder contained revision 4, dated 2 February.” |
| “Training is insufficient.” | “Two of eleven operators at station 2 have no release entry; both work at the station.” |
| “Probably nobody checks this.” | Nothing. An assumption is not a finding. Draw a sample instead. |
There is one test for every sentence. Could the process owner show it to their team without having to defend themselves against an accusation? A finding describes a process, names a requirement and shows evidence. It never names a person, and it never guesses why.
Three findings from one audit
Audit A-16 in assembly produced one of each grade.
The nonconformity was the revision at station 3. The observation was the first piece record of order 41-2290, signed at 09:12 while the gauge printout is timed 09:35: the sequence of result and signature is not defined for the line. The opportunity was that two of four torque tools at station 2 are checked on different intervals, where one interval would simplify planning.
Three findings from four and a half hours is not a weak audit. The two audits that followed in the same week produced five and four. Twelve findings across three audits, four of them nonconformities, is the normal shape of an audit program that asks about the process rather than about the filing.
Heard before you leave
Every finding is read out in the closing meeting, with its evidence, before the auditors leave the area. Two things follow from that.
The process owner can correct a fact on the spot, which is better for everyone than correcting it in writing three weeks later. And a disagreement that remains is recorded as a disagreement, with both positions, instead of being argued away by whoever has more time.
A finding nobody heard about is a finding nobody owns.