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.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Change Log. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Change Log as a decision instrument rather than an administrative form. The subject terms—change, template, example, worked, management—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Change Log?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about change would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.