K
katschance
Thank you so much!!!
Kathy
Kathy
Interesting Discussion Procedure vs. Work Instruction (WI) - What is the difference?
Elsmar Forum Sponsor
L
LUTTO
Hi,
Agree with all of the above. Have a look at ISO10013 - Guidelines for Quality Management System Documentation is you can get your hands on it.
It explains the hierarchy of Policy, Procedure, Work Instruction and Support Docs. Work Instructions Level is typically quite broad as it tends to include many other documents types such as SOPs, PCPs etc.
Rgds,
Owen
Agree with all of the above. Have a look at ISO10013 - Guidelines for Quality Management System Documentation is you can get your hands on it.
It explains the hierarchy of Policy, Procedure, Work Instruction and Support Docs. Work Instructions Level is typically quite broad as it tends to include many other documents types such as SOPs, PCPs etc.
Rgds,
Owen
L
LUTTO
Apologies, I should have said AS ISO 10013:2003 or ISO TR 10013:2001 which provide more info on documents as well as the Quality Manual.
D
dnoah
Cari - I would agree. That pretty much sums up what I was taught in a certified auditor training course.
R
rhomman - 2012
Symantecs at best.......You can slice the differences 12 different ways and come back to, basically, the same conclusion. I think it is safe to say that both are designed to ensure process repeatability.
M
maroli_yogesh
The term procedure and Work instruction carry the same meaning. But as the general industry follows, Procedures are set or instructions specified to carry out an activity that could be administrative, Managerial or technical also.
Work instructions seems to be a technical term and is more of a shop floor document.
B
Bill Goss
In the "old" days we had procedures that covered the ISO standard's requirements in full but not in every detail. For example, document control required that documents be reviewed and approved by authorized functions who had access to pertinent background information on which to base their decisions. So the procedures, we called then level 2 because the manual was level 1, would pretty much echo what the standard required and would say something like "Documents are reviewed and approved by authorized functions who have access to pertinent information on which to base their decisions". The procedure might say that the Management Rep. for the QMS approves all level 2 procedures, departmental managers approve all level 3 work instructions, etc. But the details, like how they approve, electronically in a database with workflow capabilities, on paper with a serial routing, etc., the details, would be in the work instruction. So that is why work instructions change more frequently than do procedures and hat is also why they are used more ... they are where the "rubber hits the road".
The term procedure and Work instruction carry the same meaning. But as the general industry follows, Procedures are set or instructions specified to carry out an activity that could be administrative, Managerial or technical also.
Work instructions seems to be a technical term and is more of a shop floor document.
In my experience, there's an alternative viewpoint:-
Procedure and Work instruction are very different - the procedure is more about the process of part of the business - how to process a PO from receipt of a requisition to a finished PO to a supplier. A work instruction is very task specific, filling out a purchasing requisition.
Last edited:
