...
* Standard - Standard changes are changes for which the content of the change is already known to be good (e.g., installing Microsoft patches that have been released via MIT WAUS on a specific system), but the exact timing of the change is subject to approval. Changes of this type will generate an approval request as part of the implementation plan & schedule phase of the change process, specifically after the scheduled start and end times have been selected.
* Normal - Normal changes are changes for which both the content and the timing of the change are subject to review. Changes of this type will generate an approval request as part of both the initial request and the implementation plan & schedule phase of the change.
* Emergency - Emergency changes are those that are made in response to disruptions in production services and are required to restore service, or otherwise under duress. Given the need for expediency, these changes have no approval during implementation, but are subject to an approval as part of the close out process, to confirm that the change is sound and doesn't need to be revisited or revised once time is no longer of the essence.
...
3 (Moderate / Limited) - Changes of this impact will require approval at the Team Leader level. This would be an appropriate impact level for many day-to-day changes, and is a reasonable default if you're unsure of how to categorize a change. Team Leaders who select an impact of this level are able to self-approve their changes, however, this needs to be done explicitly. The self-approval is not automatic as it is for impact level 4 changes.
4 (Minor / Localized) - Changes of this impact will require no approval / explicit approval. Instead, they are automatically self-approvalapproved. This would be an appropriate change level for most departmental servers and/or development environments.
...