This section may describe why the change request was rejected, deferred or provide any other useful information. Is the change request open, closed or pending? Has it been approved, denied or deferred? This may be a design, scope, schedule or other type of change. The change request should be described in detail.When was the request submitted?When was the request approved? Change LogĮach change request is assigned a reference number.

The following table in this template shows a common project change log format: Change Log Template: As the change request follows the change request process and is reviewed and approved/denied/deferred, the status will be updated in the change log. The project team will use the data from the change request form to populate the change log. The change management process should be clearly communicated to all stakeholders and if a change is requested it should be submitted on the change request form. Most of the information on the change log will come directly from the change request form that the project team uses. This change register (change log template) should be updated as new change requests are submitted or as existing change requests are approved, rejected, or deferred. These may be changes in scope, deliverables, design, or other changes which can easily cause a project to fail without a deliberate change management effort. Many projects involve highly influential people with varying interests and often times there are many attempts to impart these interests on the project.

Change management is one area of project management which will cause serious problems if it is not carefully managed. The change log is a document that is used by the project team to log and track change requests throughout the life of the project.

Liquidbounce change log taco