Skip to content
PMPCAPM

Change Log

A change log is a comprehensive list of all change requests submitted during the project, along with their current status (approved, rejected, or deferred) and key details.

Share:

Explanation

The change log serves as the project's official record of all change activity. Each entry typically includes a unique identifier, a description of the change, the requester, the date submitted, the impact assessment results, the decision (approved, rejected, or deferred), the decision date, and the implementation status. The change log is a project document, not part of the project management plan.

Maintaining the change log is critical for project transparency, audit trails, and stakeholder communication. When stakeholders ask about the status of a requested change, the change log provides the answer. It also helps the project manager track whether approved changes have been fully implemented and validated.

The change log is updated throughout the project whenever a change request is submitted or its status changes. It works alongside the change management plan (which describes the change control process) and the configuration management plan (which tracks the state of deliverables). Together, these components ensure that all changes are systematically managed and traceable.

Key Points

  • Records all change requests and their dispositions throughout the project
  • Includes unique ID, description, requester, impact assessment, decision, and status
  • A project document, not part of the project management plan
  • Essential for audit trails, stakeholder communication, and implementation tracking

Exam Tip

The change log captures the status of every change request. The change management plan describes the process for handling changes. Know the difference — the log is a record, the plan is a process description.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Change Control Board (CCB)

A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Integration Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.