IT Change Management Process

The IT Change Advisory Board (CAB) exists to support the vetting and authorization of higher risk changes to IT systems and services.


The purpose of change management

  1. Ensure that standard methods and procedures are used for efficient and prompt handling of all changes.
  2. Ensure that we respond to the customers’ changing business requirements while maximizing value and reducing incidents, disruption and rework.
  3. Ensure that we respond to business and IT requests for change that will align the services with the business needs.
  4. Ensure that changes are recorded in Service Desk, Configuration Management System (CMS) and then evaluated, authorized, prioritized, planned, tested, implemented, documented and reviewed in a controlled manner and take necessary corrective action.


Benefits of the change management process

  1. Creates a culture of change management across the IT organization.
  2. Aligns the service change management process with business, project and business/organization change management processes.
  3. Allows us to prioritize changes.
  4. Establishes accountability/responsibilities for changes.
  5. Establishes a single focal point for changes to minimize conflicting changes and potential disruption.
  6. Prevents anyone who is not authorized to make changes from having access to the production environment.
  7. Establishes change windows.
  8. Allows us to do performance and risk evaluation of all changes.


Indicators of poor change management

  1. Unauthorized changes
  2. Unplanned outages
  3. A low change success rate
  4. A high number of emergency changes
  5. Delayed project implementations


Risk factors

While ‘Normal’ and ‘Standard’ sound like two ways to describe the same thing, there’s a big difference. A Standard change must have a documented process that’s been reviewed and approved by Change Management. A Normal change is a non-emergency proposed change that needs to be reviewed by Change Management.

Standard changes (pre-authorized)

A standard change is a change to a service or infrastructure for which the approach is pre- authorized by change management that has an accepted and established procedure to provide a specific change requirement.

  1. The elements of a standard change are
  2. There is a defined trigger to initiate the request for change
  3. The activities/tasks are well known, documented and proven
  4. Authority is given in advance (these changes are pre-authorized)
  5. The risk is usually low


Normal change

A normal change refers to changes that must follow the complete change management process. Normal changes are often categorized according to risk and impact to the organization/business. For example, minor change – low risk and impact, significant change – medium risk and impact and major change – high risk and impact. By definition a normal change will proceed through all steps of the change management process and all changes categorized as low, medium or high risk will be reviewed by the Change Advisory Board (CAB).

Activities of the normal change process

  1. Record requests for change
  2. Change logging
  3. Review the request for change
  4. Assess and evaluate the change
  5. Allocation of priorities
  6. Change planning and scheduling
  7. Authorizing the change
  8. Coordinating change implementation
  9. Review and close change record


Emergency changes

Emergency change is reserved for changes intended to repair an error in an IT service that is impacting the business to a high degree or to protect the organization from a threat.

Emergency Changes will be posted on the CAB agenda for the next change management meeting. Although already completed, a brief summary of the change is required.

The CAB submission

  1. Submission in UM Solutions Center by Monday end of day
  2. Change report sent to CAB members Tuesday morning at 7 a.m.
  3. CAB recurring meeting Tuesday 1:30 p.m. in Social Science 141
Was this helpful?
100% helpful - 1 review


Article ID: 47566
Thu 2/1/18 10:03 AM
Mon 11/5/18 2:39 PM