Overview
Audience: TeamDynamix Technicians
The Change Enablement Process provides a structured, risk‑based approach for managing changes to production systems, services, and applications supported by IT Services. A change is defined as the addition, modification, or removal of anything that could have a direct or indirect effect on services.
The purpose of Change Enablement is to reduce risk, minimize service disruption, and ensure that changes are reviewed, approved, scheduled, implemented, and documented in a consistent and transparent manner. This process supports service quality, availability, and alignment with university priorities.
The purpose of Change Enablement is to:
- Reduce risk to IT services and campus operations
- Maintain service stability and availability
- Ensure appropriate authorization and oversight
- Improve communication and coordination across teams
- Align changes with university priorities and compliance requirements
All production changes managed by IT Services are documented and tracked in TeamDynamix (TDX) and reflected on the Change Calendar to provide visibility across the organization.
When to Submit a Change Request
A Change Request must be submitted before performing any work that could impact a service, system, or user experience.
Submit a Change Request when your work involves:
Service or System Changes
- Implementing new systems, services, or features
- Modifying existing applications, infrastructure, or configurations
- Applying patches, upgrades, or updates (outside of pre-approved standards)
User or Business Impact
- Changes that may affect students, faculty, staff, or campus operations
- Scheduled maintenance that could result in downtime or degraded performance
- Changes requiring communications to stakeholders
Risk or Dependency Considerations
- Change that impact multiple systems (upstream or downstream dependencies)
- Change with potential for service interruption, data loss, or security risk
- Changes requiring coordination across teams
Planned and Emergency Work
- Planned work requiring scheduling and approval
- Emergency fixes needed to restore service (submitted as emergency changes)
When a Change Request May NOT Be Required
A Change Request is typically not required for:
- Routine, low-risk tasks that follow a pre-approved standard change
- Work that does not impact services, users, or system functionality
- Informational or administrative updates with no service impact
Tip: If you are unsure, submit a Change Request or consult your supervisor or the Change Manager.
IT Staff Responsibility
All IT Staff are responsible for:
- Identifying when their work qualifies as a change.
- Submitting accurate and complete Change Requests
- Assessing risk, impact, and affected services
- Following the approved schedule and implementation plan
- Communicating with stakeholders as needed
- Documenting outcomes and completing the change record
IMPORTANT:
Failure to follow the Change Enablement process may result in service disruptions, increased risk to systems and data, and lack of visibility and coordination across IT Teams.
Access
The Change Request process is on TeamDynamix. Only staff with Technician security role on TeamDynamix are able to submit a Change Request on the technician-facing side (TDNext) of TeamDynamix.
Need Help?
Need more information? Check the Related Articles or Related Services sections on this page (side or at the bottom) for additional resources that might help.
If this article needs to be updated, please leave feedback on this article and it will notify the owner of the article.