CHANGE READINESS CHECKLIST:

1. Are back out procedures in place? Do we have appropriate, pre-tested, recovery procedures ready?

2. Do all units have the necessary training and documentation to support the change?

3. If appropriate, does the Support Center have the proper training, documentation to support the change?

4. If appropriate, does the Help Desk have the needed training and/or documentation to
support the change?


5. Do we know exactly when the change will be implemented, and has that been
communicated to users?


6. In regards to new server installations: Have all unnecessary software been removed and unneeded services turned off? Applicable patches applied?

7. Does a security scan show NO medium or high-risk vulnerabilities?

8. Has the change been scheduled to minimize the user impact, in relation to the cost?
Is the scheduled time the best time for the change, is it scheduled in the established
change window? Have we scheduled with the user in mind, rather than for staff convenience?


9. Have the users been properly notified, with adequate lead-time, are banners necessary and posted? (A discussion on how the users have been notified may be relevant) Have users, who operate as "clients" to central systems, rather than "login" users, been notified? The Help Desk, the CSC, and the Publications group offer to participate in relevant user notifications. If you need assistance from these areas, ask.

10. Have users been trained, provided with documentation, or otherwise informed of anything different than they need to be aware of or to do? (From a user point of view, what is the result or impact of this change?)

11. Has the change been communicated to all appropriate areas within UITS with adequate lead-time?

12. Are all other appropriate UITS areas ok with implementing the change?

13. Will we know if the change is a success? Will we know if the change was not a success? If not a success, are measures in place for appropriate action, and additional user notification as required?

14. Do we know whom the person is who is overall responsible for implementing this change?

15. Do staff members and users know whom to contact if there are further questions, either before or after the implementation?

16. Have you informed your manager, sent them a copy of the SCR, do they know of the change and approve?

17. As a general rule, if the answer to any question is NO, then the change should not be implemented until all questions result in a YES answer.


Return To Change Management Page