Approval
Approval Task
- Overview
- During the Approval step, each Approver (if there are multiple Approvers assigned), shall have the opportunity to document their decision in relation to the Change information and the proposed Action Plan.
- The outcome of this step shall determine whether the Change shall proceed to Implementation, rejected (and hence closed) or returned for more changes/information (back to Initiate).
- Sections
- Optional sections: Impact Details, Approvals, Customers, Documents, Engineering Changes, Equipment, Processes, Product, Suppliers, Action Plan and Cost are not visible initially, users have to choose sections that are relevant to the Change and enable them in scope section.
Sections |
Visible |
Editable |
Basic Information |
✔ |
✔ |
Scope |
✔ |
✔ |
Impact Details |
✔ |
✔ |
Approvals |
✔ |
✔ |
Decision |
✔ |
✔ |
Customers |
✔ |
✔ |
Documents |
✔ |
✔ |
Engineering Changes |
✔ |
✔ |
Equipment |
✔ |
✔ |
Processes |
✔ |
✔ |
Products |
✔ |
✔ |
Suppliers |
✔ |
✔ |
Action Plan |
✔ |
✔ |
Cost |
✔ |
✔ |
Verification |
❌ |
❌ |
- Routing
- Please refer to the diagram in the Overview section to see an end-to-end workflow.
- Each Approver shall complete their respective Approval section by documenting their decision and comments.
- The last Approver shall have the responsibility for determining the next available step for the Change by selecting from the following options in the Approval Decision field of the Decision section:
- Proceed: The Change shall be routed to Implement.
- Rejected: The Change shall be routed to Closed.
- Return for more changes/information: The Change shall be routed to Initiate.
- Completing the Approval Task
- If there are multiple approvers, ALL approvers have to sign the change.
.