Change Log

March 22, 2025
« Back to Glossary Index

What is a Change Log?

A change log is a record that documents all the modifications made to a project, product, or system over time. It provides a chronological list of updates, including details such as what was changed, when the change occurred, who made it, and why it was necessary. Project managers, team members, stakeholders, and auditors use this tool to track progress, maintain accountability, and understand the evolution of a project.

The change log supports transparency by helping teams manage expectations and control the impact of changes on scope, budget, and timelines. It is especially valuable in complex projects where frequent changes affect deliverables or introduce risk.

Key Points

  • A change log tracks every approved project scope, schedule, cost, or quality change.
  • It typically includes a unique ID, date, description of the change, reason for the change, author, and status.
  • It helps ensure that changes are documented and communicated to all relevant stakeholders.
  • Teams can maintain this record in spreadsheets, project management software, or formal change control systems.
  • It promotes consistency and supports risk management by enabling informed decision-making.

Related Terms

  • Before adding an entry to the change log, the team submits a formal proposal, a change request, for review.
  • The team establishes a change control process that outlines the steps for evaluating and approving project changes; they then record these changes in the log.
  • A project scope statement helps determine whether a proposed change is within the project’s boundaries.
  • A risk register can include potential risks associated with proposed or approved changes.
  • Project managers create a configuration management plan that outlines how they will track documentation and deliverables and log changes over time.

Change Log: Example

During a software development project, the client requested a new feature for the user dashboard. The project team submitted a change request, which the change control board reviewed and approved. The project manager then logged the change with an ID, description, approval date, responsible party, and updated timeline. This entry communicated and traced the change throughout the project.

Change Log: Best Practices

  • Keep the log up to date with accurate, precise, and complete information.
  • Assign responsibility for maintaining the change log to a specific team member.
  • Review entries regularly during status meetings to keep the team aligned.
  • Use consistent formatting and terminology to reduce confusion.
  • Limit access to editing rights while making the log viewable to all stakeholders.

Additional Resources

Guide to Change and Project Management     Enhancing and Unifying Project and Change Management

Preparing for a PMI certification?

« Back to Glossary Index