This discussion continues to amaze me!
Does anyone
seriously believe that any manager really factors any understanding of 'clause numbers' into their tactical or strategic thinking and operation of a business process? If you know someone who does, I'd like their names and telephone numbers!
I certainly don't dispute that a well written nc is totally important to resolving a quality system problem. Identifying an ISO clause to 'hang it on' isn't, although surely, to assign some indication of which process (internal requirement) is the issue should be. I think you guys have fallen into the normal view of reporting is 'one size fits all', for an IA as well as for a CB auditor.
Do we truely believe putting an ISO clause on an nc is going to stop management "wriggling out" of a corrective action? I feel like John McEnroe (you cannot be serious, man!) and I'm surprised at that comment! '7.1' '7.6' or '6.2.2', certainly doesn't feel like a 'big stick' to me!
True, a 'perfect clause' may not be totally necessary, but wouldn't the MR like to know where the 'leaks in the hull' are with some accuracy? Management Reviews going to be lively if they're off base with their report!
Surely, if an internal audit program is to be properly managed, it should be directing audits to look at what we've learned from past audits (see ISO 9004 on this). Based on what I'm reading here, I'd like to see the look on the Quality Planning (
APQP) Process Owner's face, when an audit is scheduled of that process because someone moved some gauges in manufacturing!!!
If you are the Audit Program Manager, better start pulling your resume together!