just completed a course on itsm fundmentals and implementation

[ikennaodo20]

We need to apply a small update to one of our core applications.
It’s already been tested, we’ve done it multiple times before, and it’s low risk — but it will happen during business hours.

From an ITSM change-management point of view, what type of change would you log, and why?

[M Iftikhar]

Hi @ikennaodo20,

This should be logged as a Standard Change because it is low risk, repeatable, and has been successfully implemented multiple times before. Standard Changes are pre-approved and follow a defined procedure, allowing them to be implemented during business hours without individual CAB approval.

While implementing changes during business hours can be sensitive, the Standard classification makes this acceptable. Because the change is pre-approved and low risk, it can be executed without waiting for a maintenance window, provided it complies with the organization’s defined standard change windows.

If my response helped, please mark it as the accepted solution so others can benefit as well.   

[Dr Atul G- LNG]

Hi @ikennaodo20 

It can be treated as a standard change since it’s low risk and already implemented in the environment. But do you have any evidence for this, or are you just saying it’s been implemented multiple times based on experience? If not, first create a standard change template and then implement it.