Construction Change Order Management Guide
Construction change orders affect scope, price, schedule, and project risk. A clear workflow helps the project team move from field issue to written notice, pricing backup, approval, billing, and closeout.
This guide is general project workflow guidance, not legal advice. The contract controls notice, approval, markup, and documentation requirements.
Identify The Change
Start by connecting the change to a clear source.
Common sources include:
- Owner direction
- Design revision
- RFI response
- Addendum or bulletin
- Unforeseen condition
- Scope gap
- Specification conflict
- Field coordination issue
- Subcontractor change request
- Schedule impact
Document what changed, who requested it, when it was identified, and where it appears in the project documents.
Give Notice
Many contracts include notice requirements. The project team should review the contract before assuming a verbal direction is enough.
Track:
- Notice deadline
- Required recipient
- Delivery method
- Required content
- Related drawing or specification
- Cost or schedule reservation
- Follow-up owner
When requirements are unclear, escalate to the project manager, contract administrator, or qualified counsel.
Build Pricing Backup
Change order pricing should be transparent enough for review.
Break out:
- Labor hours and rates
- Material quantities and quotes
- Equipment
- Subcontractor costs
- Supervision or field overhead where allowed
- General overhead and profit where allowed
- Tax, freight, or fees where applicable
- Schedule impact
- Exclusions and assumptions
For pass-through costs, check the contract before applying markup. Overhead, profit, fee, and subcontractor markups are not universal.
Review Schedule Impact
Some changes affect time as well as price.
Review:
- Critical path impact
- Procurement lead time
- Crew resequencing
- Shutdowns or access windows
- Inspection timing
- Subcontractor coordination
- Weather or site constraints
- Owner decision timing
Document whether time is included, excluded, reserved, or not affected based on the project team's review.
Get Written Approval
Approval workflow should match the contract and owner process.
Track:
- Submitted date
- Reviewer
- Questions received
- Revisions
- Approval date
- Approved amount
- Approved time impact
- Billing status
- Change order number
Avoid treating a submitted change as approved unless the contract process supports that interpretation.
Maintain A Change Log
A change log gives the team a single view of open, submitted, approved, disputed, and billed changes.
Useful columns include:
- Change ID
- Title
- Source
- Owner
- Notice date
- Pricing status
- Submitted amount
- Approved amount
- Schedule impact
- Approval status
- Billing status
- Next action
Review the log during project meetings so open changes do not go stale.
Connect Change Orders To Bid Lessons
Change order patterns can improve future bids.
Review completed projects for:
- Repeated scope gaps
- Document conflicts
- Owner-specific review patterns
- Common subcontractor exclusions
- Underpriced logistics
- Missed escalation or wage assumptions
- Long approval cycles
Use those findings in future bid/no-bid reviews and estimate checklists.
Bottom Line
Change order management is a documentation and control workflow. Identify the change, give notice, build clear pricing backup, review contract-specific markup and pass-through treatment, get written approval, track status, and carry lessons into future bids.