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

[Jen C]

Thanks to both of you - maybe I wasn't clear enough with my question, though.

I understand the difference between SOPs and WIs.

What I'd like to know is: what required information/headings do each of them have, in your experience?

For SOPs, I use the categories I listed above (Scope/Purpose, Responsibility, Safety, Materials/Reagents/Equipment, Procedure, Analysis Methods, Acceptance Criteria). Obviously, for different companies, more or fewer headings may be appropriate. But is there anything *different* that would be required for a WI?

In other words, if I'm providing templates for an SOP and a WI, would those templates basically look the same, but just contain different amounts of detail?

 

[Jim Wynne]

Everyone does it differently, and no one way is necessarily better than any other. There's a fine line between the right amount of information and unnecessary clutter. The latter state seems to be very popular. I prefer a minimalist approach, but that might not work for you.

 

[nealet01]

Procedures are usually higher level documents, SOP's are more detailed instructions on how to perform a task. I would usually reference SOP's within a procedure.

 

[AndyN]

Procedures are usually higher level documents, SOP's are more detailed instructions on how to perform a task. I would usually reference SOP's within a procedure.

"SOP" is an abbreviation for "Standard Operating Procedure". Are you suggesting a procedure should reference a procedure?

 

[Ajit Basrur]

Procedures are usually higher level documents, SOP's are more detailed instructions on how to perform a task. I would usually reference SOP's within a procedure.

These are typically called as "Work Instructions"

 

[nealet01]

Well spotted! I set my Business Management system up with 3 levels 1 - BMS Manual 2 - Higher level process maps 3 - SOP's or works instructions. Level 2 procedures usually reference level 3 SOP's or Works Instructions.

 

[manian512]

Procedure is what we follow and work instruction is a systematic and step by step operating procedure during the process. ie., from switch on to switich off

 

[Sean Kelley]

A Work Instruction (WI) as more of how to perform a task. Such as performing an inspection on a product often performed by one teammate.

Procedures are more process driven and complex involving muliple deptartments and processes. Procedures often have goals associated with them were as tasks or WI may or may not. An Inspection Procedure would likely include MSA studies on measuring equipment, training requirements, and more of a higher level view of all inspection practices rather than targeting one piece of inspection.

 

[sms4u]

Firstly I would like to thanks all for such a nice info.


I Have one query on the same subject.

Mine is a consulting Firm. Internally we do lots of activities such as taking approval for leaves, approval on loans, Alloting a Car for going on sites, Government related works.

1. My doubt is if we are having 30 - 40 different activities internally in our organization, do we have to create processes for all.

2. For instance, one activity is alloting a car for visiting Site location, How could we differeniate work instruction and procedure for this activity.

Thanks in advance to all.....

 

[John Broomfield]

sms4u,

You seem to be using the word process interchangably with procedure and work instruction.

This can confuse people.

Process is the work and comprise the activities of a cross-functional process team.

Procedures specify the way the work (process) is done and may be documented or not.

Procedures may refer to work instructions which are documented and specify how a task or activity is done.

Clause 4.2.1d specifies documentation where necessary for effective planning, operation and control. Many procedures need not be documented.

"Allotting a car" may need to be documented so the request is recorded. You and your colleagues are the best judge of this. It's a question of how best to help the users of your management system to prevent failures to fulfill requirements.

John