Normal Change Management Process

The normal change management process is the most frequently used change type. This type of change would be used when the business requires additional functionality to an application we support, that is not urgent in nature.

1. A Information Technology and Digital Services team determines a change is required to an IT System and raises a Request For Change (RFC). The requestor is responsible for ensuring that all fields are completed correctly and submits the change for assessment.
2. Once in ‘Assessing’, the requestors’ CAB representative(s) are responsible for technically assessing the quality and accuracy of the RFC and progressing it to the ‘Approval’ status. The assessment should be thorough to certify that the RFC is technically correct.
3. The Change Management Team will assess the accuracy and completeness of the RFC, then pass to the CAB. The Change Management team may ask for additional information in the RFC which will need to be completed prior to approval.
4. The CAB meets every Wednesday at 2pm to review RFCs and follow the CAB Procedure. If an RFC is approved by the CAB, the proposed change can be implemented with the details documented. The CAB can also deny the RFC or ask for action items to be completed prior to approval.
5. Once a change has been approved for implementation, the Implement Change Procedure is followed.
6. Upon completion of the ‘Implement Change Procedure’, the Change Management team will conduct a final review. This may require additional information from the implementer and/or can result in a Post Implementation Review (PIR).