Best Approach for Bypassing CAB for a Standard Change

[DevtoSME]

What is the best approach to ensure a standard change bypasses the CAB approval? Should the focus be on  configuring the standard change model to automatically skip CAB approvals, or would it be more effective to create a normal change with an expedited approval process where as instead of going to CAB it would go to the approving managers of the t

team?

[Sreeram Nair]

✅ Use the Standard Change Model with pre-approved workflow.
✅ Define clear entry criteria for standard changes.
✅ Automate assignment and validation steps to reduce manual approvals.

Why Not Use a Normal Change with an Expedited Approval?

• Normal changes require risk assessment and CAB review.
• Even if approvals are streamlined, normal changes still involve unnecessary governance.
• This approach does not align with ITIL best practices, as standard changes are meant to be pre-approved.

[DevtoSME]

Hi, so the requirement is to by pass CAB but the department that is doin the change would like to asses/approve it first themselves before it is implemented. Is there an alternative to the standard change template that we can work an approval in but not for CAB. 

[Sreeram Nair]

@DevtoSME You can achieve this by using a Standard Change Model with Internal Approval.

1️⃣ Create a Standard Change Model

• Navigate to Change > Administration > Standard Change Models
• Create a new model that pre-defines key fields like implementation steps, risk assessment, etc.
• Ensure the workflow bypasses CAB entirely.

2️⃣ Modify the Workflow to Include Internal Approval

• Open Flow Designer (or Workflow Editor if using legacy workflows).
• Add an Approval Action after the "Assess" phase.
• Set the approval group to the department managers or team leads (not CAB).
• Once approved, the change moves directly to implementation.