Overview
Audience: Technicians on TeamDynamix
This article explains how Technicians with the appropriate TeamDynamix (TDX) security role can access and submit a Change Request form using the Users Portal (TDNext). Change Requests are used to formally document, review, approve, schedule, and track changes that may impact systems, services, users, or infrastructure across the University of Arkansas. Using the Change Request form ensures changes are visible, coordinated, and implemented with minimal risk and service disruption.
Before you start
Before submitting a Change Request, make sure you have completed the planning stage of Change Enablement.
- You must have the Technician security role in TeamDynamix to access the Change Request form.
- You must use the Users Portal (TDNext) section of TeamDynamix. The form cannot be created from the Client Portal.
- Review the Change Calendar at change.uark.edu to identify scheduling conflicts and determine a proposed start and end time.
- Have your change planning documentation ready, including:
- Change type
- Title and description
- Proposed start and end time
- Upstream and downstream impacts
- Customers impacted
- Impact assessment
- Testing results
- Implementation plan
- Necessity
- Rollback plan
- Communication plan
Steps
- Go to change.uark.edu.
- Review the Change Calendar to identify approved and scheduled changes that may conflict with your planned work.
- Determine an appropriate Proposed Start Time and Proposed End Time for your change.
- Select the button on the top of the page, Create New Change Request, to access the Change Request Form from the Change Calendar. Note: Only Technicians can access this form.
- Complete the Change Type field:
- Standard / Preapproved – low-risk, repeatable changes already approved
- Normal – changes requiring Change Advisory Board (CAB) review and approval
- Emergency – urgent changes requiring rapid implementation and manager approval
- Complete the Title using the recommended naming convention:
[System/Service]: [Action] – [Specific Detail/Impact]
Example: Blackboard: Disable Guest Access – Improve Security
- Complete the Description by explaining:
- What is changing
- Why the change is needed
- Who requested it (Requestor)
- Any related incident or service ticket
- The business reason and urgency
- Complete all remaining required planning fields, including:
- Customers impacted
- Impact assessment
- Testing results
- Implementation plan
- Necessity
- Rollback plan
- Communication plan
- Add any supporting attachments or secure links if needed for vendor documentation, testing evidence, or implementation details.
- Select Save to submit the Change Request ticket.
Tip: The better your planning, the faster your change request moves through approval. CAB focuses most on clear necessity, realistic implementation steps, rollback planning, and stakeholder communication. A strong submission reduces delays and prevents the ticket from being sent back for revision.
What's next
After submission, your Change Request enters the TeamDynamix automated workflow for review and approval.
- Emergency Changes are first routed to your manager for approval.
- All Changes are reviewed by the Change Manager.
- Normal Changes are routed to the Change Advisory Board (CAB) for approval.
- Once approved, the Change Manager schedules the deployment window and the request appears on the Change Calendar.
- You will receive a task assignment to deploy the approved change during the scheduled window.
- After implementation, you must document the outcome and complete the deployment task to close the ticket.
A Change Request is not complete until the deployment results are recorded as Successful, Successful with Minor Issues, Unsuccessful/Rolled Back, or Cancelled.
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.