Change Log
Track every project change request from submission through disposition with this master log template and worked case study example.
In this resource
§1 Purpose of the Change Log
The Change Log serves as the master record of all change requests received on a project, tracking each from its initial submission through to final disposition.
As a critical project control artefact, the Change Log provides a single source of truth for the project team, sponsors, and stakeholders. It documents what changes were proposed, who proposed them, when they were assessed, and the final decision rendered by the Change Control Board (CCB) or designated authority.
§2 Blank Template
A standardised, unpopulated framework ready for deployment on new engagements.
The structure below maps exactly to standard project management governance requirements. Ensure the status of all logged items is updated continuously as requests progress from Submitted to Under Review, and finally to a closed disposition (Approved, Rejected, or Deferred).
| Project Title: [Insert Project Name] | Date Prepared: [YYYY-MM-DD] | ||||||
|---|---|---|---|---|---|---|---|
| ID | Category | Description of Change | Requestor | Submission Date | Status | Disposition | Disp. Date |
| [CR-###] | [Scope/Schedule/Cost] | [Brief summary of the proposed change] | [Name] | [Date] | [Open/Closed] | [Pending/Approved/etc] | [Date] |
§3 Worked Example: Mary's Consulting
A fully populated snapshot demonstrating standard usage for a mid-sized digital implementation project.
In this scenario, we observe an active change control process for a "New Company Website" project. Notice how scope requests are categorised, tracked against specific requestors, and resolved with clear dispositions and dates.
| Project Title: Mary's Consulting - New Company Website | Date Prepared: snapshot Oct 17, 2026 | ||||||
|---|---|---|---|---|---|---|---|
| ID | Category | Description of Change | Requestor | Submission Date | Status | Disposition | Disp. Date |
| CR-001 | Schedule | Move kickoff meeting from Apr 28 to May 8 to accommodate sponsor calendar. | Andrew (PM) | Apr 25, 2026 | Closed | Approved | Apr 25, 2026 |
| CR-002 | Documents | Update Project Charter to reflect revised kickoff date. | Andrew (PM) | Apr 26, 2026 | Closed | Approved | Apr 26, 2026 |
| CR-003 | Scope | Add real-time chat widget to website (third-party integration). | Sales Lead | Jul 12, 2026 | Closed | Rejected | Jul 18, 2026 |
| CR-004 | Scope | Add LinkedIn-link field to consultant directory. | Sales Lead | Aug 28, 2026 | Closed | Deferred (Phase 2) | Aug 28, 2026 |
| CR-005 | Cost | Negotiate 5-seat legacy CMS pricing in year 1; 10-seat from year 2. | Bob (Tech Lead) | Aug 22, 2026 | Closed | Approved | Aug 22, 2026 |
| CR-006 | Quality | Update brand color tokens to fix WCAG contrast issues found in pre-audit. | Bill (UX) | Sep 4, 2026 | Closed | Approved | Sep 4, 2026 |
| CR-007 | Scope, Cost, Schedule | Add Press / Media section to website (2 pages, 15 items at launch). | Mary (Sponsor) | Sep 13, 2026 | Closed | Approved | Sep 16, 2026 |
| CR-008 | Scope, Requirements, Cost | Add LinkedIn icons linking to consultant profiles on each bio card. | Marketing Lead | Oct 15, 2026 | Closed | Approved | Oct 17, 2026 |
Sequential Logging
Every logged item receives a unique, sequential identifier (e.g. CR-001, CR-002) to ensure traceability across meeting minutes and requirement documents.
Timely Resolution
As demonstrated by CR-003, tracking both the submission and disposition dates provides oversight on CCB turnaround times and bottlenecks.
Categorisation
Tagging the core impact area (Scope, Cost, Quality, Schedule) allows project managers to quickly filter and audit specific areas of project expansion.