Changes & CAB

Last updated:

What it is

Change Management lets you raise formal change requests, assess their risk and impact, take them through approval at a Change Advisory Board, schedule the work into a window, and record the result. Each change carries a reference in the form CHG-0001.

Raising a change

  1. Create a change with a title and a type: Standard (pre approved and low risk, for example a routine patch), Normal (needs full CAB review), or Emergency (expedited, with a mandatory review afterwards).
  2. Fill in the ITIL plans. The justification, implementation plan and rollback plan are required, and a test plan and communication plan are optional.
  3. Set the risk and the impact. Chorum computes a priority score from the risk by impact matrix.
  4. Attach the affected services and link any related tickets.

Approval at the CAB

Submitting a change runs it through the approval chain resolved from your Approval Policy. Each approver reviews and either approves or rejects, and the full approval trail is kept on the change as a snapshot of the policy at the time. You can group changes into a CAB meeting for review together, and each meeting carries a reference in the form CAB-0001.

Scheduling and outcome

Once approved, a change is scheduled with a planned start and end and an optional maintenance window. As the work happens it moves through Scheduled, In progress and Implemented, with the actual start and end recorded. Emergency changes require a post implementation review so lessons are captured.

Statuses

A change moves through Draft, Submitted, Assessment, Awaiting approval, Approved (or Rejected), Scheduled, In progress, Implemented, Review, and finally Closed. A change whose rollback was executed is marked Failed.