Interesting Discussion Procedure vs. Work Instruction (WI) - What is the difference?

[abcauto]

in case where Who,What,When How is in one documents.



Regards
ANAND

 

[AndyN]

in case where Who,What,When How is in one documents.



Regards
ANAND

Anand - could you expand on your comment? What do you mean?

 

[David Hartman]

In the past I have developed ISO 9001-based documentation that consisted of a half-page to a page and a half flow chart depicting the Who, What, When and Where, accompanied by a page or two (sometimes more, but not often) of the How. Using one short document which has a greater chance of being looked at and followed. If you couple this with some documented training (class room or OJT) you can generally reduce the "How" info to simple bullet items and/or use pictures.

 

[katchani]

Thank you very much

I usually have a procedure to explain the Overall Process and Work Instructions explain the individual steps but in my 'Document Pyramid' it shows that WIs are the 'How'

 

[Stijloor]

Friends,

This topic can be discussed for ages, it will never end, and everyone has an opinion about it. That's great!

However, my take on this is that as long as everyone in the organization has access to information that will support them to perform the job safely, effectively and efficiently while at the same time retain this knowledge for times to come; and there are means to record evidence and "lessons learned", I do not realy care how you call these things or in what pyramid you put it in.

Happy Documenting!

Stijloor.

 

[SGquality]

Procedure - Requirements of Standard (Level 2)

WI - Supports procedure (Level 3)

 

[samsung]

Procedure - Requirements of Standard (Level 2)

WI - Supports procedure (Level 3)

Hi SGquality,

Welcome to the Cove.

Above differentiation is not correct. Infact there's hardly any difference between the two. Standards don't specify any 'levels' for the documents. What you call Level-2 can be Level-3 for another organization.

Have a look at the following quote paraphrased from ISO 9000:2005 (2.7.2 Types of document used in quality management systems)

documents that provide information about how to perform activities and processes consistently; such documents can include documented procedures, work instructions and drawings;

 

[Bill Goss]

Years ago when I was teaching document and data control, I always made sure the class remembered not to get hung up on the level of a document as long as the appropriate approvals were in place. If procedure contains "how to" information, so what? Just call it a procdure and if a procedure contains policy, just call it a policy.

 

[Jim Wynne]

Years ago when I was teaching documnt ad data control I always made sure the class remembered not to get hung up on the level of a document as long as the appropriate aprovals were in place. If procedure contains "how to" information, so what? Just call it a procdure ad f a procedure contains policy, just call it a policy.

I think the hierarchical difference between policies and everything else is worth establishing and preserving. There should be a path to the source from which requirements flow, and policies are the source. Once you get below the policy level, it makes no difference unless the difference is actually useful somehow.

 

[markatbapco]

I have always used this

Procedure: A "How to do it document" crossing organizational boundaries (significant work by more than one section). Typically a cross functional flow chart.

Work Instruction. a :how to do it document " for one section. Typically a simple flow chart.