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

[goodnede]

Thats funny. The employee is suppose to read the procedures associated to their job as part of their "new hire" training and reference it if they have a question after that. Any and all applicable procedures, work instructions and forms are linked. I am just the middle man here........

 

[Stijloor]

Thats funny. The employee is suppose to read the procedures associated to their job as part of their "new hire" training and reference it if they have a question after that. Any and all applicable procedures, work instructions and forms are linked. I am just the middle man here........

Solution:The employee is suppose to read the documentation associated to their job as part of their "new hire" training and reference it if they have a question after that.

See?

Stijloor.

 

[AndyN]

Thats funny. The employee is suppose to read the procedures associated to their job as part of their "new hire" training and reference it if they have a question after that. Any and all applicable procedures, work instructions and forms are linked. I am just the middle man here........

Ouch! I wonder what they think of that! I only remember 1 of my 'new hire' training sessions and nothing about any procedures! I'd imagine it's a great way to scare people off...

 

[QAMTY]

Bill

Good point.

In this case

let´s say we may have the general procedure for document control stating the general requirements from ISO

And to describe the details of control of department A, I may create a son/daughter WI with the name related to the general Procedure?

ANd having other type of control in department B, I´d create another son/daughter WI of the General procedure.

Is it like this?

Thanks for your feedback

 

[Jim Wynne]

Bill

Good point.

In this case

let´s say we may have the general procedure for document control stating the general requirements from ISO

And to describe the details of control of department A, I may create a son/daughter WI with the name related to the general Procedure?

ANd having other type of control in department B, I´d create another son/daughter WI of the General procedure.

Is it like this?

Thanks for your feedback

You can do it that way if you want to, but it's not necessary in most cases. If you create work instructions for document control it should be self-evident that they're for document control, and it should also be self-evident that document control requirements that you establish must be in conformance with the standard. Overt and explicit linkage probably won't help anything.

 

[DMS_Discuss]

I don't think I totally agree to that definition.
A good work instructions should also detail out who does what, when and how.
So, I would like to think WI and Procedure can be used interchangeably but I think WI is a better term.
Anybody disagree with me?

 

[Jim Wynne]

I don't think I totally agree to that definition.
A good work instructions should also detail out who does what, when and how.
So, I would like to think WI and Procedure can be used interchangeably but I think WI is a better term.
Anybody disagree with me?

We can't see what it is you're referring to and don't totally agree with. It's helpful if you quote at least part of the post you're responding to; you can use the "Quote" button in that post to do so.

 

[Jen C]

Jumping into the discussion late! Accepting the views above about the differences between SOPs and WIs (level of detail, single function vs. cross-function, etc.), what are your thoughts about the content/headings that would be in each document type? It seems to me that they really would contain the same kinds of information (e.g., Scope/Purpose, Responsibility, Safety, Materials/Reagents/Equipment, Procedure, Analysis Methods, Acceptance Criteria...). Do you think it's appropriate to use similar document outlines for the two types?

 

[Uriel Alejandro]

Jumping into the discussion late! Accepting the views above about the differences between SOPs and WIs (level of detail, single function vs. cross-function, etc.), what are your thoughts about the content/headings that would be in each document type? It seems to me that they really would contain the same kinds of information (e.g., Scope/Purpose, Responsibility, Safety, Materials/Reagents/Equipment, Procedure, Analysis Methods, Acceptance Criteria...). Do you think it's appropriate to use similar document outlines for the two types?

IMHO, I think it could work but it's not really necessary.

In our work instructions we only consider Scope, Purpose and the instructions (or steps). The instructions (or steps) ussually describe Who, How and With What the process will be performed. So, put separated headings or bullets for Responsibility, Safety, Materials/Reagents/Equipment, etc. could be redundant 'cause it was described in the instructions.

 

[ssz102]

procedure is describe the flow of all process, such as handling customer complaints flow and release ECN process, these documents marking responsibility and dept and purpose and scope
work instruction is describe the details contents for operation step