Rejecting an RFC That "Needs More Work"

See how Giva helps Change Managers handle incomplete work.

What happens when a change request is incomplete?
  1. The Change Manager moves the status to "PENDING" and sets Pending Actions to a waiting reason, such as Implementation Plan, Backout Plan and/or Test Plan.
  2. Giva automatically notifies the Implementer.
  3. The Implementer reviews notes in the Change History field, which indicate that the RFC needs more work before sending it back to the Change Advisory Board (CAB) for discussion and approval.
What if an RFC is not only incomplete, but needs to go back to the drawing board because it was submitted too early? See how Giva lets Change Managers send work back to the planning stage.
Sign up for a Giva trial for 30 days.
Giva's cloud-based solution is ITIL® aligned, HIPAA compliant and SOX compliant.
Change Management Pending RFC
(Swipe to continue)
Request a Live Demo
See It In Action
Assess Your Needs
Get the Tool
Try Giva's 30 Day Trial
Sign Up Today