A change requests log template is a project document used to record, track, and manage all change requests submitted during the project life cycle. According to the Project Management Institute (PMI), change requests are formally documented requests that may modify scope, schedule, cost, quality, or any other project baseline, and must be processed through the Assess and Implement Changes process (integrated change control) in PMBOK 8. A disciplined change requests log ensures that every change is traceable, that no change is implemented without authorization, and that the cumulative impact of changes on the project is always visible.

What is a Change Requests Log?

A change requests log template is a centralized register where every submitted change request is recorded from submission through evaluation, approval or rejection, and implementation. In PMBOK 8, the change requests log is updated as an output of numerous processes across all performance domains, reflecting the reality that change requests can originate from any part of the project at any time. The log provides a complete audit trail of all change activity and prevents scope creep by ensuring that informal or verbal change agreements are never implemented without formal documentation and authorization.

What's Included in This Change Requests Log Template?

• Change Request ID and Title - A unique identifier and short descriptive title for each change request, enabling quick reference across project documents, status reports, and governance reviews.
• Change Description - A clear statement of what is being requested, what triggered the request, and which project baseline or deliverable is affected.
• Change Category - Classification of the change type (scope addition, scope reduction, schedule change, cost change, quality change, corrective action, preventive action, defect repair) to support change pattern analysis.
• Requestor and Date Submitted - The name of the person or stakeholder who submitted the change request and the date of submission, establishing the official start of the change evaluation period.
• Impact Assessment - The analyzed impact of the change on project scope, schedule, cost, quality, risk, and stakeholder expectations, providing the evidence base for the authorization decision.
• Priority and Urgency - A rating of how critical the change is to project success and how urgently it must be decided, enabling the change control board to prioritize its review workload.
• Approval Status and Decision Date - The current disposition of the change request (pending, approved, rejected, deferred) and the date the decision was made, providing a clear authorization record.
• Implementation Status - For approved changes, the implementation status (not started, in progress, completed), the person responsible, and the actual completion date.

How to Use This Change Requests Log Template (PMBOK 8)

1. Log every change request at the moment it is raised - Even requests that seem minor must be logged before any analysis or approval occurs. A verbal agreement to change scope that is not logged is scope creep, not change management.
2. Complete the impact assessment before routing for approval - Change requests must be analyzed for their full impact on scope, schedule, cost, quality, and risk before being presented to the change control board. Approving changes without impact analysis is a governance failure.
3. Communicate decisions to all affected stakeholders promptly - Both approvals and rejections must be communicated. Stakeholders who submitted a change request and hear nothing tend to assume approval and proceed, creating unauthorized scope changes.
4. Track cumulative change impact on the project baselines - Individual changes may each seem small but collectively represent significant scope growth, cost overrun, or schedule extension. The log enables the project manager to report the total change impact at any point.
5. Close change requests formally when implementation is verified - Mark changes as closed only after the implementation has been verified and the affected baselines have been formally updated. A change that is approved but not tracked to completion can be lost in execution.
6. Use the log data in lessons learned - The change log provides valuable data for post-project review: volume of changes, source patterns, approval rates, and the accuracy of impact estimates versus actual impact.

When to Create This Document (PMBOK 8)

The change requests log is established at project start as part of the integrated change control process setup and is maintained throughout the entire project life cycle. In PMBOK 8, change requests are generated as outputs of many processes and must flow through the Assess and Implement Changes process for formal disposition. The log remains active until project close, at which point it becomes part of the project archive and feeds the organizational process assets.

Related Templates

• Change Request Template
• Issue Log Template
• Risk Register Template
• Project Management Plan Template
• Lessons Learned Template

Complete Guide & Filled-In Example

Get the most out of this template with the two companion resources below:

• Change Requests Log in PMBOK 8 - Complete Guide - Understand the purpose, key elements, and best practices before filling in the template.
• Download the Filled-In Example - Project Phoenix - See exactly how this document was completed for a real $72K website launch project.