> For the complete documentation index, see [llms.txt](https://docs.7ft10.com/flow-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.7ft10.com/flow-system/change-management-3c-change-model/intro-to-3c-change/what-is-change.md).

# What is Change?

In **ITIL v4.0**, a change is defined as any addition, modification, or removal that could directly or indirectly impact services. At 7ft10, we expand this definition to encompass several critical areas that may require change management:

* **Processes**: Adjustments or improvements to existing workflows.
* **Technological/System Changes**: Implementing new technologies or updating current systems.
* **Equipment, Hardware, and Software**: Any modifications to physical or digital assets.
* **Staff Changes**: Alterations in personnel roles or responsibilities.
* **Legal and Legislative**: Compliance-related adjustments driven by changes in laws or regulations.
* **Personnel Training**: Initiatives aimed at equipping staff with new skills or knowledge.
* **Supplier Selection and Management**: Changes in vendor relationships or management strategies.

Additionally, other change types can be linked to various process elements, including inputs, resources, activities, controls, measurements, and outputs.

It’s important to note that specific changes are exempt from this procedure. Specifically, changes that are part of the system's routine operations and administration and do not fundamentally alter its functioning are not subject to this framework.

By establishing clear definitions and boundaries around what constitutes a change, organisations can better manage the complexities associated with transformation and ensure a smoother transition to new ways of operating.

For more detailed insights, we recommend exploring ITIL v4.0 guidelines and their approach to change management in further detail.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.7ft10.com/flow-system/change-management-3c-change-model/intro-to-3c-change/what-is-change.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.