Request for Change Setup/ Customization
Take a tour of quick and easy eChangeManager setup process.
Customize RFC Fields
ITIL Cloud Change Management Software Setup Close Codes
Define Root Reasons a RFC is Closed
A close code is required when a RFC is closed. Examples of codes are: Successful, Successful with Problems, Unsuccessful, Backed Out and Cancelled. For reporting purposes, you must designate one close code as "Successful" and one code as "Backed Out." Selecting the appropriate radio buttons on this screen will set these designations.
ITIL definition: All changes should have a Post Implementation Review to determine if there are any long-term unwanted or undesirable side effects associated with the change. This review also looks at the effectiveness of the change, and checks to see if the user is satisfied with the results of the change. In other words, did we achieve the benefits at the stated cost as documented in the RFC? Upon the completion of a satisfactory review, the change record is closed. Each organization decides the timing to conduct the review, but at least one review must take place.
Request a Live Demo
Assess Your Needs
Try Giva's 30 Day Trial