---
title: Change
slug: en/change
description: Learn about the Change Management process according to ITIL guidelines. Discover how changes are evaluated, prioritized, planned, tested, implemented, and documented to ensure control and minimize risk. Explore the categorization of changes as Standard, N
docTags:
createdAt: 2021-10-27T19:18:25.000Z
---
## Presentation
******Change Management** is the process responsible to evaluate, coordinating and
deciding about making change proposals to Configuration Items (CI).
According to ITIL, the main goal of this process is to ensure that changes are made in a
controlled way, and being evaluated, prioritized, planned, tested, implanted
, and documented.
Changes can be categorized as follows:
- **Standard Change**;
- **Normal Change**; and
- **Emergency
Change**.
| **Categories** | **Description** | **Example** |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| **Standard Change** | Authorized of low risk, it occurs with frequency.
It is initiated by a defined trigger that follows a procedure or works instruction
to make the activities - well known - have a pre-determined budget. | Install
a standard *desktop* application package. |
| **Normal Change** | Any change in services other than emergency or standard.
It follows the policies, deadlines, and procedures defined by the organization. | |
| **Emergency Change** | Changes that need to be done as soon as possible. The Change Management process usually has a specific procedure to handle
emergency changes. | Change to resolve a Major Incident or implement a security fix. |