Change Managers reject RFCs based on many reasons. For example, the request may be a duplicate. Typically, rejections should be the exception. The purpose of the Change Rejection Reason Report is to provide information about the various reasons for rejections so that process improvements will reduce the rejection volume and reducing the Change Manager workload. This report queries all rejected reason codes. In addition, you can further define the search by Service Group, Priority, Scope, Change Category and date range. Below is a rejection report sample.
The following reports will assist the Change Manager and the Change Advisory Board (CAB) in increasing the number of successful changes. A root cause analysis of why any changes were backed out and why some changes induced problems will help increase the number of successful changes in the future. The change team should review any induced service requests that are attached to RFCs. It is also helpful to understand why changes were rejected.
When Giva customers focused on root cause analysis with just these reports, they experienced a very significant increase in satisfaction from the business teams and customers that they serve. With Giva you can achieve the same!
- Successful RFCs Report
- Backed Out RFCs Report
- RFCs by Induced Problems Report
- Change Rejection Reason Report
- RFC Closed Code Report