Change Order Log Template: Free Construction Tracker

Example construction change-order log showing change number, subject, source, responsible party, date identified, workflow status, days open, pending cost exposure, approved cost, and schedule impact.
Change	Subject	Source	Responsible Party	Date Identified	Status	Days Open	Pending Exposure	Approved Cost	Schedule Impact
CE-014	Loading dock drainage revision	RFI-041	Project Manager	Mar 02	Executed / Closed	18	$0	$12,500	0 days
CE-015	Electrical gear substitution	Procurement	MEP / Electrical	Mar 11	Under ReviewOverdue	9	$48,000	—	Equipment release at risk
CE-016	Level 3 finish revision	Owner Request	Owner Representative	Mar 14	Pricing Received	6	$8,400	—	No identified impact
CE-017	Existing utility conflict	Field Condition	Civil / GC	Mar 16	Pricing Requested	4	Pending	—	Sitework sequence at risk
CE-018	Roof screen modification	Design Revision	Architect	Mar 09	Withdrawn	11	$0	—	No identified impact

What should a construction change-order log track?

A register earns its place when it answers seven questions without a phone call: what changed, why, who owns it, what it is worth, what decision is needed, what work is affected, and what has already been approved.

The 36 columns in the template group into eight practical categories.

Identification

Enough detail that anyone reviewing the register can tell what changed and where, without asking the originator.

Change Number
Subject
Source
Change Type
Project Area / Location
Related Drawing / Specification

Source records

A change is easier to price, defend, and close when the record it came from is one click away.

Related RFI
Related Submittal
Attachments / Link

Ownership

The most common reason a change sits unresolved: nobody can say whose action is next.

Responsible Party
Responsible Company
Owner Decision
Design Decision

Timing

Dates turn the register into a control. Without them the log is a list of things that happened.

Date Identified
Pricing Requested Date
Pricing Received Date
Required Decision Date
Approval Date
Execution Date
Days Open
Last Updated

Workflow

One agreed status model, applied the same way by everyone who contributes to the register.

Status
Priority

Financial exposure

Potential, submitted, and approved values kept apart so leadership can see risk before approval.

Estimated Cost
Submitted Cost
Approved Cost
Pending Cost Exposure
Budget Impact
Forecast Impact
Commitment Impact
Owner Contract Impact

Schedule

Time impact recorded against the activity it actually affects, not as an unqualified number.

Estimated Time Impact (Days)
Approved Time Impact (Days)
Affected Schedule Activity / Milestone

Record

What the project can point to later when someone asks what was decided, by whom, and on what basis.

Approval / Execution Notes
Notes

A useful change log tells leadership what financial and schedule exposure exists before every item reaches final approval.

Recommended change-order status values

One agreed status model, applied consistently, is what makes the register readable at a glance. These are practical example statuses only. Project-specific contracts and procedures may use different terminology and stages.

Identified: A potential change has been recognized but has not yet entered pricing or review.
Pricing requested: Pricing has been requested from the responsible party.
Pricing received: Pricing has been received and is ready for review.
Under review: Scope, pricing, schedule impact, responsibility, or supporting backup is being evaluated.
Revision requested: The submitted change requires revised scope, pricing, or supporting information.
Owner review: The item is awaiting an owner or otherwise authorized decision, where applicable.
Approved: The change has received the required approval but may still require final execution and downstream record updates.
Rejected: The proposed change was not approved.
Withdrawn: The potential change is no longer being pursued.
Superseded: Another change record has replaced this item.
Executed / closed: Required approval or execution and the downstream record updates are complete according to project procedures.

Status should represent the next action

The purpose of status is not labeling. Each status should tell the team what happens next. For every open change, the team should be able to answer:

What is waiting?
Who owns it?
What information is missing?
What decision is required?
What exposure exists while it waits?

Overdue is a timing condition, not a workflow status. Keep it in its own indicator so an item can be both “Under Review” and past its required decision date.

How to prioritize changes in the log

Do not prioritize by change number, age, or dollar value alone. Priority should reflect what the unresolved decision is holding:

Schedule activity affected
Procurement urgency
Current cost exposure
Milestone impact
Work already proceeding
Owner decision dependency
Design decision dependency
Potential rework
Contractual notice requirements where governed by the contract

Critical: An immediate decision is needed to avoid affecting current work, procurement, fabrication, inspection, or a critical milestone.
High: Near-term work, a procurement item, or a financial decision is exposed.
Normal: The change requires action, but the affected work has sufficient lead time.
Low: Administrative or non-time-sensitive item.

These are internal prioritization labels, not contractual entitlement or legal classifications. Project-specific contract documents and procedures govern notice, authorization, entitlement, pricing, time adjustments, approval authority, and execution.

Why “days open” matters — and why exposure matters more

Days Open is the fastest way to surface aging changes. On its own it is a weak signal, because age says nothing about what the unresolved item is holding. A useful change-control review reads six fields together:

Days Open
Required Decision Date
Pending Cost Exposure
Affected Schedule Activity
Responsible Party
Current Status

A change open for 30 days against future work may be less operationally urgent than one opened yesterday that is blocking a major procurement release. Age ranks the register. Exposure and the affected activity decide what gets chased this week.

Pending exposure is not the same as approved cost

This is the field group most often collapsed into a single “cost” column, and it is the one that costs the most to lose. Four values, kept apart:

Estimated cost: An early internal estimate of potential impact.
Submitted cost: The amount formally submitted for review, where applicable.
Approved cost: The amount that has completed the required approval process.
Pending cost exposure: The amount of potential financial exposure that remains unresolved.

Leadership can have real project exposure before the owner contract or a commitment has formally changed. A register that only reports approved values will always report it late.

Your organization may define these fields differently. The key is to keep potential, submitted, and approved values from collapsing into one number. Nothing here is intended to override organizational accounting rules or prescribe accounting treatment.

A change can hit more than one financial view

One change may affect different financial views at different times — and rarely all at once. Recording them separately is what lets a project team explain the sequence.

Budget impact: Does the change affect the planned project allocation?
Forecast impact: Does it change the team's current expectation of final cost?
Commitment impact: Does a vendor or subcontractor commitment need to change?
Owner contract impact: Does the owner-facing contract value change, where applicable?
Pending exposure: What unresolved financial risk is already known to the team?

For how these views stay connected once a change is approved, see construction cost management.

How to use this change-order log on an active project

1
Log the change early
Create the record when the potential issue becomes meaningful enough to track — not only after final approval.
2
Connect the source
Link the RFI, owner request, design revision, field condition, submittal, drawing, proposal, or other originating record.
3
Assign the next action
Identify one responsible party. Shared ownership of a pending change is how items stall.
4
Set a decision date
Tie it to the work, procurement item, budget decision, or milestone the change actually affects.
5
Track financial stages separately
Keep estimated, submitted, pending, and approved values distinct rather than overwriting one cost field.
6
Document schedule impact
Connect the change to the affected activity or milestone, and keep estimated time apart from approved time.
7
Update status consistently
Use one agreed status model so the register can be read the same way by everyone.
8
Review open exposure regularly
Project reviews should focus on what is waiting, what it may cost, and what work it affects.
9
Update downstream records
After approval or execution, update budgets, commitments, contracts, forecasts, schedules, and reports as appropriate.
10
Close the record
Close only when the required approval or execution and the downstream record updates are complete.

Example of a construction change-order log

The same five fictional changes, expanded to show how the fields work together across an item under review, one with pricing received, one still awaiting pricing, an approved and executed change, and a withdrawn record.

CE-015Under ReviewOverduePriority: Critical

Electrical gear substitution

The specified gear carries a lead time that no longer supports the current sequence, and a substitution has been submitted for review. Pricing has been received but scope and warranty terms are still being evaluated, so the amount remains pending exposure rather than approved cost. The required decision date has passed, which is tracked separately from the workflow status.

Source: Procurement
Responsible party: MEP / Electrical
Identified / decision due: Mar 11 / Mar 18
Days open: 9
Estimated cost: $44,000
Submitted cost: $48,000
Approved cost: —
Pending exposure: $48,000
Forecast impact: Forecast updated for potential exposure
Schedule impact: Equipment release at risk
Affected activity: Switchgear release / electrical rough-in
Related records: Procurement package · Submittal: switchgear (in review)
Decision / notes: Awaiting review of submitted pricing and equipment substitution backup. No approval has been issued.

CE-016Pricing ReceivedPriority: High

Level 3 finish revision

The owner requested a finish revision on Level 3. Pricing has been received and is ready for review. The affected work has lead time, so the item is high rather than critical, but the pending exposure is already visible to the project team.

Source: Owner Request
Responsible party: Owner Representative
Identified / decision due: Mar 14 / Mar 27
Days open: 6
Estimated cost: $8,400
Submitted cost: $8,400
Approved cost: —
Pending exposure: $8,400
Forecast impact: Carried as pending exposure
Schedule impact: No identified impact
Affected activity: Level 3 interior finishes
Related records: Owner request memo · Finish schedule revision
Decision / notes: Pricing received. Owner decision pending.

CE-017Pricing RequestedPriority: Critical

Existing utility conflict

An existing utility was encountered in a location that conflicts with the planned routing. Pricing has been requested. Until it is received the register carries the item as pending with no quantified amount, which is more honest than entering a placeholder value.

Source: Field Condition
Responsible party: Civil / GC
Identified / decision due: Mar 16 / Mar 24
Days open: 4
Estimated cost: Not yet estimated
Submitted cost: —
Approved cost: —
Pending exposure: Pending
Forecast impact: Exposure not yet quantified
Schedule impact: Sitework sequence at risk
Affected activity: Underground utility rough-in / sitework sequence
Related records: Field condition report · Civil drawings
Decision / notes: Pricing requested from the civil subcontractor.

CE-014Executed / ClosedPriority: Normal

Loading dock drainage revision

A drainage revision at the loading dock followed the response to RFI-041. The change completed the required approval and was executed, so the submitted amount moved to approved cost and no pending exposure remains against this record.

Source: RFI-041
Responsible party: Project Manager
Identified / decision due: Mar 02 / Mar 14
Days open: 18
Estimated cost: $11,800
Submitted cost: $12,500
Approved cost: $12,500
Pending exposure: $0
Forecast impact: Forecast and budget updated at approval
Schedule impact: 0 days
Affected activity: Loading dock slab and drainage
Related records: RFI-041 · Revised civil detail
Decision / notes: Approved and executed. Budget, commitment, and forecast records updated.

CE-018WithdrawnPriority: Low

Roof screen modification

A proposed roof screen modification was reviewed and then withdrawn before pricing was submitted. The record stays in the log with no approved cost and no remaining exposure so the history of the decision is preserved.

Source: Design Revision
Responsible party: Architect
Identified / decision due: Mar 09 / Mar 20
Days open: 11
Estimated cost: $6,200
Submitted cost: —
Approved cost: —
Pending exposure: $0
Forecast impact: No forecast impact
Schedule impact: No identified impact
Affected activity: Roof screen installation
Related records: Design revision narrative
Decision / notes: Withdrawn before pricing submission. No approved cost.

Example data only. Values shown are illustrative and do not represent benchmarks or typical project values.

Change order form vs. change-order log — what is the difference?

Change order form

Documents one individual change.

Scope
Reason
Supporting records
Cost adjustment
Time adjustment
Approvals
Revised contract information

construction change order template

Change-order log

Tracks all potential and approved changes across the project.

Ownership
Status
Aging
Pending exposure
Approved cost
Schedule impact
Approval progress
Overall project exposure

For the process behind both — how a potential change is priced, reviewed, approved, and executed — see the construction change-order process.

Should the log include potential changes or only approved change orders?

For project controls, the log is most useful when it includes potential changes before approval.

If the register only shows executed change orders, it describes what already happened. It does not show:

Pricing still outstanding
Pending owner decisions
Design decisions
Unresolved financial exposure
Schedule exposure
Items being negotiated
Potential changes still under review

Terminology varies. Organizations may call these records a change event, a PCO, a change request, a proposed change, or a potential change. For the broader distinction, see what a change order is in construction.

Why keep a formal change log if the team already uses email and meetings?

Email and meetings remain useful for communication and decisions, and most projects will keep using both. What they do not create automatically is one controlled register of:

Every change record
The source of the change
The responsible party
Pricing status
The required decision date
Current status
Pending cost exposure
Approved cost
Schedule impact
Approval history
Supporting documents
Final execution

Communication and project control are different jobs.

Change-order metrics worth reviewing

Useful change reporting is operational, not benchmarked. These are the measures that tend to change what a project team does next:

Open potential changes
Pending cost exposure
Approved change value
Changes awaiting pricing
Changes awaiting owner decision
Changes awaiting design decision
Average time from identification to decision
Median time from identification to decision
Changes by source
Changes by responsible party
Changes by discipline
Changes by project area
Changes affecting upcoming schedule activities
Pending time impact
Approved time impact
Withdrawn and rejected changes
Forecast impact
Changes aging beyond project-defined thresholds

Change count alone does not tell leadership the amount or the urgency of the exposure.

Common change-order log mistakes

Logging only approved change orders and ignoring the potential exposure still in review.
Collapsing estimated, submitted, and approved cost into one number.
No clear responsible party, so the item belongs to everyone and nobody.
No required decision date, which makes aging impossible to interpret.
Status labels used inconsistently between contributors.
Pricing received but the log never updated.
No link to the source RFI, drawing, field condition, or owner request.
Time impact recorded without naming the affected activity.
An approved change never reflected in budget, commitment, or forecast records.
One person owns the spreadsheet and nobody else can see it.
Closing the record before the downstream updates are complete.

When is a change-order spreadsheet enough?

Often. A spreadsheet register is a legitimate project control, and plenty of well-run projects never need anything else. It works well when:

Change volume is manageable
One person owns the register
The pricing flow is straightforward
Approval responsibility is clear
Cost fields are maintained consistently
Schedule connections are limited
Supporting documents are easy to reference
The team reviews the log consistently
Portfolio rollups are not required

If that describes the project, use the CSV. The discipline of maintaining the register matters more than the software holding it.

When the log stops scaling

The spreadsheet shows the exposure. The workflow has to move it.

Larger projects and portfolios need more than a place to store the row. They need:

Multiple submitters
Multiple reviewers
Automated notifications
Approval workflows
Role-based access
Pricing backup
Document links
RFI links
Budget context
Commitment context
Contract context
Forecast context
Schedule connections
Owner decisions
Design decisions
Project-wide visibility
Cross-project rollups
A complete audit trail

The spreadsheet usually does not fail because it cannot store another row. It fails when every handoff around the row has to be managed manually.

Change management in Jet.Build

Move from a change log to a live project-control workflow.

Jet.Build keeps project changes connected to the financial and operational information behind them — including budgets, commitments, contracts, RFIs, documents, approvals, schedules, and reporting — so teams can see both the individual change and the project-wide exposure. The register holds status and ownership, approval routing moves the item, and project management keeps the source records attached to it.

Teams can use Jenny to surface underlying project records and summarize project information, while pricing, contractual decisions, and approvals remain with the project team.

Explore Cost Management Explore Financial Management

Related change-order resources

What Is a Change Order in Construction?Understand the full change-control process from issue identification through pricing, schedule review, approval, and execution.Construction Change Order TemplateUse a free printable and copy-ready form to document one individual project change.Construction Cost ManagementConnect potential and approved changes to budgets, commitments, forecasts, and cost visibility.Construction Financial ManagementKeep contract values, commitments, invoices, forecasts, and changing project financials aligned.Construction Project ManagementKeep RFIs, submittals, documents, approvals, and project changes connected.Construction Scheduling SoftwareConnect open changes and decisions to activities, milestones, procurement, and sequencing.Workflow AutomationRoute project reviews and approvals with clearer responsibility and history.

See how Jet.Build tracks change exposure across active projects.

Take about 30 minutes with our team to see how Jet.Build connects potential changes, pricing, approvals, budgets, commitments, forecasts, schedules, documents, and reporting across active projects.

Schedule a Demo

What the change-order log looks like