Stub policies?

Comments

2 comments

  • We don't currently use these but would be interested in learning more!!! I would think you'd want to link back to the stub policy on each local policy as well so you know what is linked to what when it comes time to review.

    We are currently encountering scenarios where different facilities have different processes. For now, we decided to have one ministry-wide policy and attach just the different processes. In the approval workflow each "group" with a different process will be an approval step. We'll see how that goes!

    0
    Comment actions Permalink
  • Yes, this is how we have it set-up and there are a lot of steps to ensure we have the original the group approved and then making sure they clone the policy, make their edits, receive their local approval and then hyperlink it back on the step. Another group wants to do the stub policy because when we have the system-wide policy, the approvals seem to take longer and they believe it will be easier if we create local approvers to the policy only and link back to the stub. The managing piece of the policy is tough for some and I believe it would help if there was someone managing the process as a whole...but we will get there, just take time. Thanks for responding and I'll share more information as stubs as soon as we have a nice clean instructional sheet created.

    0
    Comment actions Permalink

Please sign in to leave a comment.