Change Management Instructions

Table of Contents


Illinois Tech's Change Management Process, managed by the Office of Technology Services (OTS), assesses any requested technology change that impacts any university system, application, or service that is currently in production or going into production. Requests must be submitted prior to Wednesday at noon in order to be considered for the Wednesday change control meeting. The submitter will give a very brief overview of their submitted request and answer any questions from the Change Control Board. Providing sign-offs from end-users for testing/configurations are required in order to move technology into a production environment. It will help to become familiar with the information listed on these OTS web pages—Change Management and Maintenance Window—and to submit your first change control request with the developer assigned to your project.

General Instructions

  1. Login to Footprints 11, from IIT Portal

Security note: You must confirm that you want to access the page by clicking “continue” when you see prompts about entering an unsafe environment.

  1. Change workspace to Change Management Control in the top right dropdown.

  1. Click New Change Request
  2. You need to complete two sections: Contact Information, and Change Request Information. These are in the left panel. You’ll also use the Attachments section to upload any approvals from the departments/individuals who need to sign off on the change. Make sure to click “save” after you complete a section, or before you step away from your computer. Copy information from the submitted business case or other project tracking documents as necessary.

Instructions by Form Section

New Change Request for Change Management

  1. Title: brief name that the community will understand
  2. Urgency: select relevant urgency — ask the developer for clarification
    1. Emergency
    2. High
    3. Medium
    4. Low
  3. Status: leave at Open
    1. Open
    2. Override Denied
    3. Deferred
    4. Expedited
    5. Pending INF Director
  4. Change Type: select one of the options below according to these guidelines. Most of changes will be “Normal.”
    1. Normal: changes that are performed less frequently and may or may not have a documented process.
    2. Common: pre-approved changes that are considered relatively low risk, are performed frequently, and follow a documented, Change-Management-approved process.  Examples include a scheduled reboot of a wireless access point or applying system patches.
    3. Emergency: the highest priority changes and need to be evaluated, assessed, and either rejected or approved within a short time span. Emergency changes must be approved by one of Illinois Tech's Associate Chief Information Officers (ACIOs).

Contact Information

  1. In Contact Information section, fill out your personal information
    1. For IIT Classification, select IIT Staff.

Change Request Information

  1. Requesting Team: Your team name.
  2. Change Duration: This refers to the time the whole change will take to complete, i.e., how many hours it will take to complete, in hh:mm format.
  3. Risk: The risk is dependent on the amount of our community that will be affected and the intricacy of the deployment.
    1. High
    2. Moderate
    3. Low
    4. None
  4. Implementation Date/Time: Select a specific day and time within the change control window when the deployment work will begin.
  5. Outage Length: This refers to when a specific system or systems will be offline during the change, in hh:mm format.
  6. Customer Impact: use best judgment based on conversations with the developer and project team members
    1. None
    2. Minor
    3. Significant
    4. Major
  7. Category: — Select one of the below.
    1. Documentation
    2. Facilities
    3. Hardware
    4. Human Resource
    5. Operating System Procedures
    6. Server Maintenance
    7. Software
    8. Storage
    9. Tactical Plans
    10. Telecommunications
    11. Training Courses
  8. Change Window: This is typically left at the default time (Friday at 9:15pm). See maintenance window information here.
  9. Select this option for Public Safety (PS) Escort: Generally, this will be left blank unless you need Public Safety on-site during your change to escort you to a location on campus to make the change.
  10. Escort Date/Time: Generally, this will be left blank. Sometimes deployments will require us to be on campus late at night or very early in the morning and we could request that Public Safety provide an escort to or from the building.
  11. “I updated the Confluence documentation” (checkbox) — If there is Confluence documentation on this system, you must update it.
  12. Effects of Change: This text will go out in the weekly email.  Describe in layman’s terms what impact this change, when completed, will have on the community.
  13. Reason for Change: Provide a brief explanation of why this is important.
  14. Change Description: Provide a brief explanation of what the change is.
  15. Systems/Applications Affected: List other systems that are impacted.
  16. IIT Teams Impacted: List or describe all teams impacted.
  17. Back-Out Plan: Indicate what will be done if the change does not work as intended and we need to “back out” of a solution. Make sure to discuss this with the developer and functional users within the project team.

Additional Comments

This section is for anything that would need to be provided that is not covered under the general questions above.


Upload any approvals from the departments/individuals who need to sign off on the change.

  • Attach —> Go —> Save

Assignees and Notifications

Ignore this section

Time Tracking

Ignore this section

Screenshots for Reference

Editing an Existing Request

To edit an already submitted request (eg. to attach sign-off documentation), log in, find your request, click the “...more” button, and then click “Edit.” Example below. Make sure to click “save” to save your changes within the system. If you can’t locate your request, click on “All Requests” in the dropdown, and sort by most recent.

Deleting an Existing Request

Only elevated permissions can delete Change Control requests.  Contact the Change Control Manager to have your request deleted.