Change Calendar

The Change Management process establishes an orderly and effective procedure for tracking the submission, coordination, review, evaluation, categorization, and approval for release of all changes to the project’s baselines.

Standard Change

A low risk (in this case, “low risk” is being used as a general term, as opposed to the formal definition calculated by the Risk Questionnaire you can download here), frequently occurring, routing change that has a pre-approved Standard Operating Procedure (SOP).

Non-Production — a change that is being performed against development, test or pre-production IT infrastructure. All non-production changes will go in as a Standard change.

Normal Change

A change that follows the normal process flow that may require approval by the Change Manager or the Change Advisory Board (CAB). Normal Changes are further categorized into high, medium or low risk.

Fast-Track Change

A change that is submitted as a Normal Change but must be expedited with the following justification 1) for Financial or Legal reasons and 2) Organization’s Reputation or a Critical Vulnerability.

Emergency Change

A change to resolve an outage or a pending outage, or to address a regulatory or security issue. Emergency changes must be approved by the Director verbally or by email or by text. The change is recorded after the Incident has been resolved.

Informational Change

A change that is driven by a vendor or third-party that is being recorded to aid with communication, e.g. Change Calendar, Informational Change

Type of Change
Lead Time from Submission to Approval
Approval process
Standard Change Same day
Normal – Low Risk 1 business day
  • Change Owner Manager approves online.
  • For Low Risk changes only, approval by the Change Owner Manager will allow the Change to move forward to be built.
  • Once tested the Change will go the Change Manager for Deployment approval.
Normal – Medium Risk 1 week (calendar days)
  • Technical Review Board (TRB) approval is necessary. The need for an Architectural Review process will be determined and flagged within the TRB process activity. Approval to move forward is done online.
  • The Change Owner Manager approves online to build the change.
  • Once tested the Change Manager provides Deployment approval.
Normal – High Risk 2 weeks (calendar days)
  • TRB approval is tracked online (as described for Normal-Medium Risk)
  • The Change must be discussed at a CAB meeting at least 2 weeks before implementation.
  • The Change Owner Manager will approve to build the change.
  • Once built, the Change will go to CAB for Deployment approval.
Normal – Fast Track Less than required lead time based on risk level
  • Less than required lead time based on risk level TRB approval required above for Medium or High risk changes.
  • Have a High or Urgent Priority
  • Must go to eCAB for Deployment approval
Emergency Change N/A
  • Verbal/email/text approval by the Director.
  • The Director will consult/inform other stakeholders as they deem necessary.
  • The Change record is created after the fact.

It is important to observe the minimum lead time for submitting the change and the approval process. The change should be submitted as soon as the business approves the change which typically should be well in advance of the minimum lead time.

Pre-register now!

GroupLink ITSM Change Management’s beta release is scheduled for Q3 of 2021. Fill out the form below and we’ll you know when it becomes available.