Standard Change Request

What is a Standard Change?

ITIL defines a Standard Change as a low-risk, pre-authorized change that is well understood and fully documented, and which can be implemented without needing additional authorization.


A Change Request includes the time to complete the task AND the time for functional testing by stakeholders to validate the change success.  Timely functional testing reduces risk and impact from possible necessary rollbacks.


Standard Change Data Flow


How to Create a New Standard Change

  1. In the filter navigator, search for Change and click Create New.

  2. On the "What type of change is required?" screen, click Standard: Select from available pre-approved change templates. These changes do not require approval.

  3. On the "Standard Changes" screen, select the category for your change.  For example, "Server Standard Changes".

  4. Select the standard change template from the list in the category. For example, "SharePoint Server Patches (PROD)".

  5. Complete the change request form, documenting all required fields (look for the red * next to fields and the * on the tabs).  When you are complete, press Save

    Upon submission, a notification will be sent to the individual who requested the change (Requested By) and the Assignment Group.

    Standard Change Templates allow the creator to pre-populate most or as few fields as they wish, so when it comes to filling out a Standard Change Request it really depends on how much was specified in the template already.

    Even though fields are prepopulated with the template it is a good idea to review the information to make sure it is correct for your change.

    Your change request has been created. [Current State: New]

  6.  It's time to schedule your change.  Enter the Planned start date and Planned end date and then press Schedule.

    Your change has been scheduled.  [Current State: Scheduled]

  7. When you are ready to start implementing the change, press the Implement button. 

    [Current State: Implement]

    Entering the implementation phase automatically fills in the Actual start field and creates a Change Task (CTASK#######) to complete this Change Request.

    If you are not in the Assignment Group, the Change Task will not get assigned to you. If you are doing the work, make sure the Task gets Assigned to a group that you are a member and then to yourself.  A notification will be sent to the "Assigned to" individual to complete the work.

  8. The individual assigned the Change Task now completes the actual change work and closes the task.  This action automatically closes the Change Request and the Requested by individual will receive a notification that the Change has been completed.

    [Current State: Closed]

    Notice that the parent Change is now closed and the Actual end was filled in.

Video Resources

How to Propose a Standard Template

Related Articles

Change Management Overview Normal Change Request Emergency Change Request How to Cancel a Change