When to have top level procedure in order to have a work instruction for a process

[goodnede]

I have a simple question, do you have to have a top level procedure in order to have a work instruction for a process?

My example, if you have a procedure for Production Planning, this states planners have to do this, that and the other thing. If you reference a WI for say "Outside Services" that defines the steps and requirements do you still have to have a top level procedure for "Outside Services"?

While I am on the subject, is it incorrect to have a WI for a process that defines the steps for more than one department to follow in the same WI or does each department have to have their own separate WI?

I did do a search and didn't find anything that seemed to answer my question. Maybe I didn't enter the most appropriate search words. Thanks in advance for any of your expert knowledge or opinions.

 

[Jim Wynne]

Re: When to have top level procedure

I have a simple question, do you have to have a top level procedure in order to have a work instruction for a process?

My example, if you have a procedure for Production Planning, this states planners have to do this, that and the other thing. If you reference a WI for say "Outside Services" that defines the steps and requirements do you still have to have a top level procedure for "Outside Services"?

While I am on the subject, is it incorrect to have a WI for a process that defines the steps for more than one department to follow in the same WI or does each department have to have their own separate WI?

I did do a search and didn't find anything that seemed to answer my question. Maybe I didn't enter the most appropriate search words. Thanks in advance for any of your expert knowledge or opinions.

There is no requirement for there to be a hierarchical documentation structure, so a work instruction doesn't have to have an antecedent at a "higher" level. The idea of the documentation "pyramid" with multiple tiers is outdated.

 

[goodnede]

Re: When to have top level procedure

Thanks Jim, I see it this way also. Too bad all of my co workers do not.

 

[Jim Wynne]

Re: When to have top level procedure

Thanks Jim, I see it this way also. Too bad all of my co workers do not.

Ask your coworkers to read the standard and find the "shall" that supports their opinion.

 

[noboxwine]

Re: When to have top level procedure

Ask your coworkers to read the standard and find the "shall" that supports their opinion.

You go Jim ! Logic and Common Sense are still Alive

 

[fattyfish]

Re: When to have top level procedure

There is no requirement for there to be a hierarchical documentation structure, so a work instruction doesn't have to have an antecedent at a "higher" level. The idea of the documentation "pyramid" with multiple tiers is outdated.

The documentation "pyramid" is outdated...and what is the current best practice?

 

[Jim Wynne]

Re: When to have top level procedure

The documentation "pyramid" is outdated...and what is the current best practice?

The "best practice" (in my opinion, mind you) is to have a quality manual, the documented procedures required by the standard, and other documentation needed for the efficient operation of processes.