Creating, Approving, Implementing, and Closing RFCs
Take a tour of the standalone eChangeManager workflow and notifications.
Reporting on RFCs
Customizing RFC Layout
Hosted ITIL & SOX Compliant IT Change Management Software Change Rejection Reason Report
Easy-to-use Change Rejection Reason Report-Giva eChangeManager
The Change Manager rejects 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 RFCs. In addition, you can further define the search by Service Group(s), Priority(s), Scope(s), Change Category(s) and date range.

Request a Live Demo
Assess Your Needs
Try Giva's 30 Day Trial
All Tours
- RFCs-Intuitive Home Page Dashboards
- RFCs-Quick Navigation
- RFC Customization Fields
- RFC Approval & Notifications
- RFC Routine Approval & Notifications
- Urgent, Simple, Routine Quick Approval
- Urgent Change
- RFC Ready for Approval
- Incomplete RFC
- RFC Need Planning
- RFC Rejected
- Automated Notification Workflow
- RFC Status Workflow
- RFC Change Manager Approval
- RFC Team Approval
- RFC Change Summary
- RFC Change Detail
- Asset List
- RFC Attach Assets
- RFC Plans & History
- RFC Change Wrap-up & Induced Problems
- Forward Schedule Help Desk Integration
- RFC Integration with Help Desk
- RFC/Help Desk Service Request Integration
- Dashboard & Reporting
- Backed Out Changes Report
- Change Category Report
- Change Closed Code Report
- Change Rejection Reason Report
- Change Requester's Department Report
- Change Status Report
- Forward Schedule of Change Volume Report
- Forward Schedule of Changes Report
- Induced Problems Report
- My Requested Changes Report
- Schedule Changes by Group Report
- Schedule Changes by Scope Report
- Successful Changes Report
- Easy RFC Form Customization