Change Log

Project managers need to be agile and able to adapt to changes in order to keep their projects on track. One way to help manage changes is by using a change log. This document allows project managers to track and communicate all changes that occur during the course of a project. By doing so, project managers can keep stakeholders informed and make sure that all changes are properly managed.

Change is an inevitable part of every project, and it is important for project managers to be prepared for it. A change log can help project managers stay organized and in control during times of change. By tracking all changes and communicating with stakeholders, project managers can ensure that their projects run smoothly.

Change log is a project management document that lists changes made during the project lifecycle. Change log is used to track transactions that involve reviewing, approving or rejecting, checking, and closing changes that will be applied to the project. 

A change in a project is done as in accordance with system thinking principle and should be seen as natural considering the adaptability and resiliency principles. Enable change to achieve the envisioned future state is not always easy. So many times it is difficult to make stakeholders embrace changes. So communication, as well as motivation, are important tools here. 

It is a very important tool to communicate with the stakeholders about changes. This communication enhances the stakeholder engagement in later stages.

Additionally change logs contain the history of the changes made and the impact it has on the project in terms of risk and cost. Change logs allow us to track accepted changes as well as rejected changes. In this aspect, it is used as an important input and control tool to prevent scope creep in predictive development approaches. It is also a document that is referenced in managing the engagement of stakeholders during the project.

The change register may include information about;

  • A brief description of the change
  • The category of the change, 
  • Information about the person or stakeholder who proposed it, 
  • History of the change request, 
  • The urgency of the change request, 
  • Its impact on the project, 
  • The decision about the change
  • Its current state.

Projects using a backlog show the adaptation of plans throughout the project. Projects that are using a predictive development approach and therefore using a change control process have change logs.

In PMBOK 7 there are 8 different project performance domains as we know. Change logs are among log and register artifacts and recommended to be used in,

Since project work performance domain has a main topic for monitoring new work and changes, it is recommended to be used in the project work performance domain. In delivery performance domain, managing the scope change and depicting the cost of changes can be done by using change logs.

Change logs are created in the process of 

It is used as an input to: