Submitting a change request through the form ensures your request is submitted with critical information from the beginning, enabling more accurate and faster resolution. Please review this page in full before submitting a request.
Who Can Submit a Change Request?
All users can submit a change request form, including:
Requests to optimize Workday and to eliminate work-arounds. These are prioritized in monthly Workday Governance meetings by functional area and are delivered throughout the year.
Eliminating workarounds
Optimizing and enhancing
Workday Change requests feed into our Workday adoption planning for evaluation.
Projects
Work that builds new functionality and capability within UVA HR.
When Not to Use the Change Request Form
Operational Support Requiring Immediate Attention
This type of support includes two categories:
1. Day-to-day break-fixes when someone is stuck and cannot complete their work or needs an immediate resolution. These issues should be directed to the UVA HR Solution Center rather than to the Workday team’s change request form.
Operational Issues for Change Request Form
Production support issues that are not immediately critical should be directed to the Workday team through the change request form where they will be vetted and prioritized. If a system change is required, these requests feed into Jira, our official source of IT audit.
What Happens After Change Request Submission?
After submitting a change request through the Workday Change Request form, a change control case is created. The Workday team partners with the requestor to further understand and outline the request. After the work is more defined and information is gathered, the Workday team creates an Adoption item in Workday to prepare for prioritization.
The Workday team meets with governance teams monthly by functional area to prioritize Adoption items and backlog items. If your change request is prioritized for resolution in an upcoming quarter, a Workday analyst will notify you.
The Workday team then proceeds to work on the changes and test solutions, and will stay in contact with you for questions and testing. Communications and training are considered for each change item prior to implementing the change in production.
Items are initially sourced from the Change Request Log.
Items are stored in Workday Adoption Planning, categorized by functional areas.
The Workday Team meets monthly with Governance teams (by functional areas) for their input on change request prioritization. Teams follow the Request Prioritization Model as a guide for evaluating what requests should be prioritized. (See image below.)
The Workday Team works on the resulting list of prioritized change requests for implementation in production.
The below methodology guides determining which requests will be developed as solutions in each quarter:
Request Prioritization Model
Quarterly Update Items and Backlog Items
QUARTERLY UPDATE ITEMS: Items prioritized in the governance meetings slated for the current quarter.
BACKLOG ITEMS: Requests not yet prioritized for a quarter. Items on this list may be worked on at a later date.
KEY OPERATIONAL ACTIVITIES: HR operational activities that occur each year. These may require configuration changes and testing. Example include Open Enrollment, Merit, Performance Review, etc.
PROJECTS: An effort with a fixed duration to introduce new capabilities. These typically take place outside of planned updates for each quarter.
Release Communications
As needed, individual teams and departments are informed in person or via email that their requests have been completed and are provided details pertaining to the change.
Changes that impact broader audiences are also communicated directly to those impacted or in newsletters across the University and UVA Health.
UVA_HR