Requesting Emergency IT Changes for Academic Services

In cases of urgent disruptions affecting academic services, emergency IT changes may be necessary to quickly restore functionality while minimizing impacts on education.

When to Request an Emergency Change

Submit an emergency change request for high-priority academic incidents when:

A critical system or application outage affects multiple classes or students
There's a security vulnerability posing significant risk
A temporary solution is needed to resume services while permanent changes are pending

Emergency changes should be rare. Always attempt to follow the standard change management process for non-critical changes.

How to Request an Emergency Change

Follow these steps to request an emergency IT change:

Submit a high-priority ticket to the IT Service Desk with details on:
- The issue or outage
- Justification for emergency change
- Details of proposed changes (implementation plan, expected downtime, etc.)
The IT Change Manager will prioritize and review the request
If approved, follow instructions to schedule and implement the change
An emergency Change Advisory Board (CAB) will convene for further evaluation

Emergency changes require approval from the IT Director and academic stakeholders based on the severity and risk assessment.

Rules for Emergency Changes

For approved emergency changes, adhere to these rules:

Assemble a qualified team for rapid execution
Prepare rollback plans in case of failures
Communicate impacts and downtime details effectively
Ensure standard procedures like peer reviews and testing are followed when possible
Document all actions and changes thoroughly

Emergency changes are subject to audit. Ensure proper documentation and don't hesitate to request a change in qualifying situations – the IT team is ready to assist.