Change Request Lifecycle

A change request (CR) analyzes and assesses the scope of the required change from a financial and risk perspective.

The Change Request lifecycle includes these states:

This page discusses:

Draft

A user who creates a CR becomes its owner. The owner assigns a Change Coordinator and responsible technical organization. If only one fast track change template exists, it is automatically connected to the CR when it is created. If a fast track change template was not connected to the CR when it was created, the CR owner can add one while the CR is in the Draft state.

The owner can:

  • Edit the CR.
  • Delete the CR.
  • Transfer ownership to another user or to the Change Coordinator. Notifications are sent to the new owner.
  • Assign Assignees for the CAs.
  • Promote the CR to the In Work state.

In Work

The Assignee, and the Change Coordinator evaluate the requested change. The Change Coordinator owns the CR while it is in the In Work state. The Assignee performs the impact analysis associated with the CA. The CR owner must respond to Change Questionnaires and mandatory Impact Questionnaires associated with the CR when it is in the In Work state. The CR owner can add and respond to Impact Questionnaires to the CR when it is in the In Work state.

The owner can:

  • Edit the CR.
  • Promote the CR to the In Approval state if these requirements are met:
    • At least one impact analysis is complete.
    • The Reviewer list is assigned.
    • All Change Questionnaires and mandatory Impact Questionnaires associated with the CR are submitted.

In Approval

The CR is reviewed and approved before planning implementation. Notification is sent to users on the review route, which is automatically created when the CR is promoted to In Approval.

Note: You can use only an approval-based route as an approver list. Change Management creates an approval route for routes that the change process creates regardless of whether you create a review route template or approval route template.

All related objects assigned to attributes in a Conditional Questionnaire that match the CR's attributes are automatically added to the CR when it is promoted to In Approval.

You can edit the properties of the CR when it is in In Approval. This is in compliance with baseline behavior. When the review route is approved, the CR is promoted to the next state.

Approved

Implementation of the CR begins in the Approved state. A change order (CO) is automatically created with attributes copied from the CR. The Change Coordinator is the owner of the CR in this state.

COs created from the CR contain any Related Objects (such as routes, member lists, people (approvers), or Impact Questionnaires) attached to the CR as a result of responses to questions in the Change Questionnaire. Any routes attached to the CR as a result of responses to questions in the Change Questionnaire are copied to the CO in the Implementation Review state.

You can edit the properties of the CR when it is in Approved. This is in compliance with baseline behavior. When all related COs are completed, the CR is auto-promoted to the Completed state.

Completed

The CR and related COs are completed and no modifications are allowed. A CR in Completed state cannot be added as an agenda Item under a meeting nor can it be added as an applicable item under a decision.