When you need it
Open a change entry when an event, request or instruction may alter the agreed scope, schedule, cost or technical basis. Maintain the register throughout delivery until each event's decision and implementation status is evidenced.
XLSX /
AI tools and documents for engineering and project management.
Change Register
Track change event, notice, source, scope, schedule/cost/quality effects, authority and decision status.
How to use this templateThis Excel template contains prepared working sheets and completion notes on a separate sheet. Enter your project data and review the completed workbook before use.
This editable workbook helps you organise project information. Check any included formulas, assumptions and results before use; it does not replace professional review.
The form prepares a separate brief; it does not fill the Word or Excel file.
Read product descriptions in your language. The Word and Excel template files are in English.
Only selected pages are shown. This is not the complete template. The full editable Word or Excel file is supplied with purchase.
Learning
How to use this template
What it helps you decide
It preserves visibility of change exposure before every consequence is quantified. Managers can separate potential changes, assessed impacts and authorized decisions without losing the source and contractual context of each event.
How to complete it
- Identify the event and date, describe the proposed change and link its source or notice to the actual contract scope and document hierarchy.
- Record scope, schedule, cost and technical effects separately, stating assumptions and contractual position where assessment remains incomplete rather than forcing premature agreement.
- Name the decision owner and maintain status against actual records, then coordinate approved effects with the relevant baselines and package documentation through controlled processes.
Who prepares and reviews it
The change coordinator consolidates engineering, planning, cost and contract inputs. Package owners validate effects; the person authorized under the project and contract arrangements decides the change, not the register administrator.
A mistake to avoid
Do not mark a change approved merely because its design has been discussed; technical agreement and contractual authorization may follow different routes.
Illustrative example
Illustrative example: a client requests a larger standby generator after design development. The register links the request to technical, foundation and delivery implications. The team records unresolved cost and schedule effects so the authorized decision maker can evaluate the change before committing implementation.
Document contents
- Document control
- Change governance and authority
- Change register
- Schedule, cost, technical and contractual interfaces
- Review and approval route
Required inputs
- Project name, location, scope and responsible organization
- Project jurisdiction and confirmed regulatory applicability
- Contract document hierarchy and conflict resolution route
- Source titles, exact revisions and relevant sections
- Contract scope
- Change event
- Cost data
- Schedule baseline
- Decision data
Practical tools.
Professional judgment.
Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.
Prepare project brief