RFC (Request For Change) Process
The RFC (Request For Change) Process is a formal procedure used in project management and IT service management to handle requests for changes to a system, project, or service. It ensures that all proposed changes are documented, evaluated, and managed systematically to minimize risks and disruptions. Here’s a breakdown of the typical RFC process:
1) Initiation:
A stakeholder identifies a need for change and submits an RFC (Request for Change) detailing the nature of the change, its purpose, and its potential impact. The RFC should include information such as the change description, business justification, benefits, risks, and any dependencies.
2) Assessment & Review:
The RFC will go through two phases of assessment and review. The first phase will start with a service desk request to the Workday Support Team (WST). This will include the appropriate functional or technical workstream SME(s) for discussion on need, feasibility, prioritization, planning, and testing. When this phase has been completed (and if the RFC is deemed viable), the second phase will include an official RFC submission to review and validate the change request’s feasibility, impact on operational or project strategy, scope, timeline, resources, and potential risks.
3) Approval or Rejection:
Based on the assessment, the Change Board decides whether to approve, reject, or request modifications to the RFC. Approved changes are prioritized and scheduled for implementation, while rejected requests are documented with reasons for denial.
4) Planning:
For approved changes, the detailed implementation plan is developed by WST, in coordination with the stakeholder, outlining the steps, resources, timeline, training, and responsibilities required to execute the change will be used. This plan includes risk management strategies and rollback procedures in case the change needs to be undone.
5) Implementation:
The change is implemented according to the approved plan. This phase may involve testing, deployment, training, and communication with all stakeholders to ensure everyone is informed and prepared for the change.
6) Review & Closure:
After implementation, the RFC is formally closed. Any lessons learned are recorded to improve future organizational change management processes.