In service management, what is a key requirement for a Normal change?

A Normal change in IT Service Management refers to a change that is not classified as an emergency or standard change. A key requirement for a Normal change is that it must be reviewed and approved before implementation. This ensures that the change is assessed for risk, impact, and resources needed, allowing the organization to maintain control over its IT environment.

Review and approval are critical because they help prevent unnecessary disruptions that could arise from implementing changes without adequate consideration. By having a formal process where changes are evaluated and validated by the Change Advisory Board (CAB) or relevant authority, organizations can ensure that changes align with business objectives and operational constraints.

Immediate implementation without review would typically apply to an emergency change, where speed is crucial due to an urgent issue. Extensive logging of user activity may be beneficial for auditing but is not a primary requirement for what defines a Normal change. Similarly, minimal monitoring once implemented does not capture the need for ongoing assessment to ensure the change has met its intended goals and to identify any unforeseen issues. Therefore, the emphasis on review and approval is central to managing Normal changes effectively.