Those of you that operate to Jar-ops will probably relate to this more than the ano operators.
Question: Under jar-ops as a department head I can no longer audit my own records?
Apparantly quality systems get in the way!
If I have undetstood the concept, and I admit I may have been mislead
if there is an error made that affects your work then you raise a non-formity report against that department. This is all duly recorded in your reference you maintain (for auditing). They are then supposedly going to investigate this problem, find out why it happened, and what measures will be put in place to prevent it happening again. Thats all well and good, but after waiting weeks for that response, when nothing is forthcoming do I raise any non-conformity on the non-conformity?
My preference is for how I have always done it - gone straight to the source of the problem, discussed what went wrong and sort it.
Another part I have a problem with, is if an outside person is going audit my department how much time I am going to have to spend explaining things either to them or going over pages of findings, most of which only highlight the fact that that person doesn't know what to look for when undertaking the audit. This is especially true when it comes to loadsheets.
Your experiences of how this works invited.
------------------
say it with icons!