Risk & Change
Change Log
MyPMP
QMS Template
| Ref | Change | Requested by | Impact | Status |
|---|---|---|---|---|
βοΈ
Free to try β your work auto-saves in this browser.
Saving to the cloud (sync across devices) is a paid feature. Unlock Change Log for $1/mo, or get everything with membership ($9/mo or $99/yr).
β οΈ Risk & Change
Auto-saved in your browser Β· β members can white-label & sync across devices
About the Change Log template
A Change Log is a centralised record of every change request raised on a project, tracking each from submission through assessment, approval or rejection, and implementation. It gives the project manager a single source of truth for what changed, who authorised it, and the impact on scope, schedule, and budget. Maintaining one protects the baseline and provides an audit trail when stakeholders question why a deliverable, date, or cost moved.
It's part of My QMS, MyPMP's Quality Management System: fill it in online, personalize it with your name and logo, then export a clean, branded PDF. Your work auto-saves in your browser.
When to use a Change Log
- βΈRunning formal change control on a project with a fixed scope, budget, or contract baseline
- βΈLogging requests raised in a Change Control Board (CCB) or steering committee for a decision
- βΈTracking scope creep so small tweaks don't accumulate unapproved
- βΈPreparing audit, governance, or client status reports that need a defensible change history
What a good Change Log includes
- βChange ID and date raised, plus who requested it
- βDescription of the change and its justification
- βImpact assessment across scope, schedule, cost, and risk
- βStatus (submitted, under review, approved, rejected, implemented)
- βApprover / decision authority and decision date
- βLinked risks, issues, or affected deliverables and revised baseline reference
What's inside this template
The interactive form above gives you:
A table of Ref, Change, Requested by, Impact, StatusNotes
Tips & common mistakes
- π‘Assess and record cost, schedule, and scope impact before the change goes to the approver, not after
- π‘Give every change a unique ID and never delete rejected entries, keep them for the audit trail
- π‘Distinguish a change request from an issue, a change alters an agreed baseline; an issue is a problem to resolve within it
How it works
- 1. Fill it in β type directly into the fields, tables and sections above.
- 2. Brand it β add your organization name and logo with the Branding button.
- 3. Export β print to PDF, or become a member to white-label and sync across devices.
FAQ
What is the difference between a change log and a change request form?οΌ
A change request form captures the detail of a single proposed change, while the change log is the running register that summarises and tracks the status of all requests across the project.
Who is responsible for maintaining the change log?οΌ
The project manager or a project support/PMO role owns the log, but the change authority or Change Control Board makes the approval decisions recorded in it.
How does a change log relate to the project baseline?οΌ
Only approved changes should update the scope, schedule, or cost baseline, and the log records which change authorised each baseline revision so variance can be traced back to a decision.
Make it yours β $9/mo or $99/yr
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membershipRelated free apps