Re: Where to define Authorities and Responsibilities in Documentation?
There is no limit to which document includes a description of who is responsible and/or has the authority to do XYZ. However, if it simplifies things a higher level document like the process procedure can contain the responsibilities and work instructions can serve the purpose of defining the work steps in greater detail.
Responsibility and authority should align: a person who is held responsible for something should have the authority to do it. But this can be difficult, if a responsible person (such as the "owner" of a process like SPC) has no, or thinks he has no ability to exert a consequence for failure to comply with the process requirements. The organization should establish a means for this person to enforce the requirement. What that looks like is up to the organization to decide.
Limits are the scope of the process and the extent of the responsibilities defined in the process document. There should be boundaries to ensure the inspector, for example, cannot be "punished" by the production manager for rejecting inspected parts.
Does this help clarify responsibility and authority?
"If you only have a hammer, you tend to see every problem as a nail." Abraham Maslow