Hi Anthony,
There is a very good article about understanding change types. I will post the link below
Standard Changes
Standard Changes are pre-approved changes that are considered relatively low risk, are performed frequently, and follow a documented (and Change Management approved) process. Think standard, as in, ‘done according to the approved, standard process’. Not standard, as in run-of-the-mill.
Standard Changes are not tracked as a Request for Change (RFC), but are tracked elsewhere, often as Service Request records.
The process for a proposed Standard Change is presented to Change Management to review/approve. The proposed Standard change describes how the change and associated risks will be managed. Once Change Management has approved the Standard Change, it can be carried out in production as needed (per the defined process.)
It’s worth noting that Standard Changes, even after approval, are still under the jurisdiction of Change Management. If Standard Changes start causing Incidents, Change Management can bring the Standard Change back for review and request changes as needed.
Standard Changes are the antidote to the complaint that “every little change has to wait for CAB approval”, and “Change Management just slows everything down”.
Far from bureaucratic, Standard Changes enables rapid implementation of frequent changes while managing the risk
Normal Changes
Normal Changes, on the other hand are just that – the normal, run of the mill not ‘Standard’ and non-emergency Changes that require full Change Management review. They are raised as Request for Change (RFC), reviewed by CAB, and approved or rejected by the Change Manager.
Reference : The Difference Between Standard and Normal Changes in ITIL
Mark Correct or Helpful if it helps.
***Mark Correct or Helpful if it helps.***
