What Is a Change Order in Construction?
A construction change order is a formal project record used to document an approved or formally processed modification to the work, contract value, project time, or other contract requirements according to the project's applicable procedures.
A good change-order process preserves the full decision trail: what changed, why it changed, where the change originated, what it costs, whether it affects the schedule, who reviewed it, and how the approved change updates the project record.
Change order at a glance
- Used to document
- A formal change to project scope, cost, time, or another contractual requirement
- Common origins
- Owner decisions, design revisions, field conditions, RFIs, coordination issues, substitutions, scope clarifications, and schedule decisions
- Common precursor records
- RFI, change event, PCO, change request, proposal, design bulletin, field documentation, or owner direction — depending on the project
- Financial impact
- May add cost, deduct cost, or result in no cost change
- Schedule impact
- May add time, deduct time, revise sequencing, affect milestones, or result in no time change
- Final result
- A documented change processed through the approval and execution requirements established for the project
Terminology and approval requirements vary by contract and organization.
What is a construction change order?
Construction projects rarely finish with every assumption unchanged from the original contract documents. As design develops and construction progresses, teams encounter owner decisions, design revisions, coordination conditions, unforeseen field conditions, scope clarifications, substitutions, procurement issues, schedule decisions, RFI responses, and work that has to be added or deleted.
A formal change-management process creates a documented path from issue, to evaluation, to pricing and time review, to approval, to an executed change, to updated project records. The change order is the record at the end of that path.
A change order is not simply "extra work." Depending on the situation, it may add scope, delete scope, revise scope, change contract value, modify contract time, document a no-cost change, document a no-time change, or combine cost and time adjustments.
The key idea. A change order records the authorized change. The issue that created it may have started much earlier.
Why are change orders used in construction?
The practical reason is to preserve agreement and traceability. A structured change record helps the project answer a specific set of questions later, without relying on memory or an email thread:
- What changed?
- Why did it change?
- What documents triggered it?
- Who requested it?
- What work is affected?
- What does it cost?
- Does it affect time?
- Who reviewed it?
- Who approved it?
- What project records need updating?
The value is not paperwork for its own sake. It is keeping scope, cost, schedule, and authorization aligned as the project moves.
What causes a construction change order?
Most changes trace back to a small set of recurring project conditions. Recognizing the source early is what makes pricing, review, and approval move quickly later.
Owner-requested change
An owner changes scope, finish, functionality, sequencing, or another project requirement.
Design revision
Architectural or engineering information is revised after the original work was priced or planned.
RFI response
A clarification reveals work different from what the team previously understood.
Unforeseen or field condition
Existing or concealed conditions differ from assumptions or available documents.
Coordination issue
Two disciplines, trades, or assemblies require revised work to resolve a conflict.
Substitution or material change
A product, material, equipment item, or system changes.
Scope clarification
The parties determine that work needs to be added, removed, or redefined.
Schedule or sequencing change
A project decision changes timing, sequencing, access, phasing, or milestone requirements.
Value engineering
An approved alternative changes the planned scope or cost.
Allowance or contingency adjustment
A project-specific allowance or other budget item is reconciled through the applicable process.
Not every event above automatically creates entitlement or requires a change order. Project-specific contract documents and procedures govern the actual treatment.
Who initiates and approves construction change orders?
There is no single universal workflow. Project structure, contract type, and organizational governance all change who does what. On most projects the pattern looks like this:
Potential initiators
- Owner
- Developer
- General contractor
- Construction manager
- Architect
- Engineer
- Subcontractor, routed through the GC
- Owner's representative
- Project manager
Potential reviewers
- Project management
- Estimating
- Design team
- Owner representative
- Finance / accounting
- Project controls
- Scheduler
- Legal / contract administration where appropriate
Approval authority depends on the contract, the organization, project governance, approval limits, dollar thresholds, and the type of change involved.
At any point in the process, the team should be able to answer:
- Who owns the next action?
- What is being reviewed?
- What information is missing?
- What decision is required?
The construction change-order process, step by step.
The specific procedure is set by the project's contract documents, but the sequence below reflects how a well-run change moves from identified issue to updated project record.
- 01
Change identified
A project condition, decision, document revision, RFI response, or scope issue creates a potential change.
- 02
Source records connected
Link the drawings, specifications, RFI, submittal, owner direction, meeting decision, photos, or other records behind the change.
- 03
Scope defined
Clarify exactly what work is added, removed, or revised.
- 04
Responsibility / routing assigned
Send the potential change to the party responsible for estimating, reviewing, or deciding it.
- 05
Cost evaluated
Pricing, credits, allowances, subcontractor impacts, or other cost effects are documented according to project procedures.
- 06
Time impact evaluated
Identify schedule activities, milestones, procurement items, or sequencing potentially affected.
- 07
Review / negotiation
The parties review scope, pricing, time, responsibility, backup, and required revisions.
- 08
Approval / execution
The change reaches the formal approval stage required by the contract and project procedures.
- 09
Project record updated
Update budgets, contracts, commitments, forecasts, schedules, documents, and reporting as appropriate.
The exact sequence, terminology, required notices, and approval authority are project-specific.
Potential change vs. executed change order
The issue that creates a potential change often appears well before the final change order exists — frequently first surfacing in an RFI or during the construction submittal process. Many organizations use an intermediate record to evaluate the issue first. Depending on the organization, that record may be called a change event, potential change order, PCO, change request, change proposal, proposed change, or change notice. These terms are not universally interchangeable.
Potential change
Evaluate whether something affects scope, price, time, responsibility, or downstream work.
- Source
- Description
- Responsible party
- Pricing request
- Supporting documents
- Estimated cost
- Estimated time
- Review status
Executed / approved change order
Record the change once it reaches the formal approval or execution point required by the project.
- Approved scope
- Agreed cost adjustment
- Agreed time adjustment
- Supporting documents
- Approvals
- Revised contract information
The important control is preserving the connection from the original issue to the final approved record.
What should a construction change order include?
A practical construction change-order record usually needs enough information to answer what changed, why, what supports it, what it costs, and what it does to time. Start from our free construction change order template, which already includes the fields below.
- Project name
- Project number
- Contract number
- Change order number
- Date
- Title / subject
- Source or reason for the change
- Description of the changed scope
- Drawings and specifications referenced
- Related RFI
- Related submittal
- Related change event or PCO
- Affected trades
- Original contract value
- Prior approved changes
- Current contract value
- Amount of this change
- Revised contract value
- Cost breakdown where applicable
- Affected schedule activity
- Time adjustment
- Revised milestone or completion date where applicable
- Supporting documents
- Approval / execution information
- Notes and conditions
This is a practical field list, not a legally required universal one. Contract documents and project procedures govern what a given project actually requires.
Construction change order example
The fictional example below shows how the fields work together on a change that originated from an RFI response.
- Project
- Harbor Point Office Renovation
- Change order
- CO-017
- Title
- Loading Dock Slab Drainage Revision
- Origin
- RFI-041
- Reason
- Revised drainage configuration after coordination between architectural, structural, and plumbing documents.
- Scope
- Revise the loading dock slab depression and drain configuration based on the coordinated detail issued in response to RFI-041.
- Supporting records
- RFI-041, A-504 markup, P-202 markup, contractor proposal
- Cost
- +$12,500
- Time
- 0 calendar days
- Status
- Approved
The amount shown does not represent a benchmark or typical project value. Project-specific contracts and procedures govern actual change-order requirements, including numbering, routing, pricing, time adjustments, and approval authority.
RFI vs. change order — what is the difference?
These records are often mentioned in the same conversation, but they sit at different points in the same chain and produce different outcomes.
| Document | Purpose | Typical trigger | Typical result |
|---|---|---|---|
| RFI | Clarify missing, conflicting, or ambiguous project information | A question discovered in drawings, specifications, scope, coordination, or field conditions | A documented response or clarification |
| Change event / potential change | Evaluate whether an issue affects scope, cost, time, responsibility, or downstream work | An RFI response, field condition, owner request, design revision, or other potential change | Scope, pricing, and time evaluation, plus a decision on how to proceed |
| Change order | Document a formally approved or processed modification according to project procedures | A potential change reaches the required approval or execution stage | A documented modification to the project and contract records |
RFI
- Purpose
- Clarify missing, conflicting, or ambiguous project information
- Typical trigger
- A question discovered in drawings, specifications, scope, coordination, or field conditions
- Typical result
- A documented response or clarification
Change event / potential change
- Purpose
- Evaluate whether an issue affects scope, cost, time, responsibility, or downstream work
- Typical trigger
- An RFI response, field condition, owner request, design revision, or other potential change
- Typical result
- Scope, pricing, and time evaluation, plus a decision on how to proceed
Change order
- Purpose
- Document a formally approved or processed modification according to project procedures
- Typical trigger
- A potential change reaches the required approval or execution stage
- Typical result
- A documented modification to the project and contract records
An RFI may reveal the need for a change, but an RFI itself is not the change order. For the question side of that chain, see our guide to RFIs in construction. To document the resulting change, use the free construction change order template.
Change order vs. change request, PCO, or change event
These terms are often used at different stages of the same broader change-management workflow, but their exact meaning varies by organization and contract. A practical way to think about the stages:
Issue / change event
Something potentially affects the project.
Change request / PCO / proposal
The team defines, prices, evaluates, or negotiates the potential change.
Change order
The change reaches the formal approval or execution point required by the project.
Some organizations use entirely different terminology, or combine these stages into fewer records. What matters operationally is that the connection between the original issue and the final approved record survives.
What if work needs to proceed before the final change order is executed?
Construction projects sometimes encounter conditions where the team needs direction before pricing or formal documentation is complete. Depending on the contract and organization, projects may use records such as a written directive, construction change directive, field directive, owner directive, change notice, time-and-material ticket, or another form of interim authorization. These are not universally equivalent.
Whatever the mechanism, the project should preserve:
- Who directed the work
- What work was directed
- When it was directed
- Supporting records
- Cost tracking
- Time tracking
- What formal change process follows
The contract governs authorization, notice, compensation, time entitlement, and required documentation.
How change orders affect project cost
There is a meaningful difference between potential exposure and approved financial impact. A potential change may be unpriced, estimated, submitted, under review, negotiated, approved, rejected, withdrawn, or superseded. The financial record should distinguish those stages rather than treating every open item as a committed number.
Relevant financial effects may include:
- Labor
- Material
- Equipment
- Subcontractor cost
- Allowance adjustments
- Credits
- Overhead or fee where applicable
- Insurance and bond impacts where applicable
- Tax where applicable
- Contingency use
- Revised commitment
- Revised owner contract
- Forecast impact
A project can carry significant pending exposure before any approved change reaches the contract value. That is the gap most teams are trying to close when they move change tracking into construction cost management alongside construction financial management.
Change orders affect more than the contract value
One approved change can move several different financial views of the same project. Teams should know where a change shows up in each of them.
Budget
What was planned or allocated for the work.
Commitment
What is contracted or committed to vendors and trades.
Owner contract
What the owner-facing contract value reflects, where applicable.
Forecast
What the team currently expects the final project cost to become.
Pending change exposure
Potential financial impact that has not reached final approval.
Approved change
Financial impact that has completed the required approval process.
If change information is tracked separately from budgets and forecasts, leadership can be looking at an outdated financial picture even when the project team already knows the exposure exists.
How change orders affect the project schedule
A change can affect the schedule even when its cost impact is modest. The schedule effect usually shows up somewhere other than the change itself:
- A redesign delays a procurement package
- A long-lead item changes and the order has to be reissued
- A fabrication release moves out
- Trade work has to be resequenced
- Site or floor access changes
- Inspection scope or timing changes
- Rework is required on work already in place
- Added work affects a contractual milestone
- An owner decision delays a release
- A design response affects field installation
A cost change does not automatically create a time extension. Where time is at issue, the record should document:
- Affected activity
- Affected milestone
- Days potentially added or deducted
- Procurement impact
- Sequencing impact
- Mitigation decision
- Approved time adjustment
That is also why teams increasingly review pending changes inside construction scheduling software rather than as a separate financial list.
Why change-order status needs to be specific
A generic "open" status is not enough for complex change management. Teams commonly use stages such as the following — as examples, not universal requirements:
- Identified
- Pricing requested
- Pricing received
- Under review
- Revision requested
- Owner review
- Approved
- Rejected
- Withdrawn
- Superseded
- Executed / closed
The important thing is that each status represents a real next action. At any moment, the team should be able to see what is waiting, who owns it, how long it has been waiting, what financial exposure exists, and what schedule exposure exists.
What should you track in a change-order log?
One change-order form documents one change. A change-order log gives the project-wide view — what is pending, what is priced, what is waiting on a decision, and how much exposure sits behind all of it. If you need a register to start from, use our free construction change-order log template. Useful fields include:
- Change number
- Subject
- Source
- Change type
- Related RFI
- Related submittal
- Responsible party
- Date identified
- Pricing requested date
- Pricing received date
- Required decision date
- Current status
- Days open
- Estimated cost
- Submitted cost
- Approved cost
- Cost exposure
- Estimated time impact
- Approved time impact
- Affected activity
- Owner decision
- Design decision
- Related commitment
- Related contract
- Approval date
- Execution date
- Attachments and links
| Change | Subject | Source | Status | Cost exposure | Time |
|---|---|---|---|---|---|
| CE-014 | Loading dock drainage revision | RFI-041 | Approved | $12,500 | 0 days |
| CE-015 | Electrical gear substitution | Procurement | Under review | Pending | Equipment release at risk |
| CE-016 | Level 3 finish revision | Owner request | Pricing received | $8,400 | No identified impact |
| CE-017 | Existing utility conflict | Field condition | Pricing requested | Pending | Sitework sequence |
| CE-018 | Roof screen modification | Design revision | Withdrawn | $0 | None identified |
CE-014 — Loading dock drainage revision
- Source
- RFI-041
- Status
- Approved
- Cost exposure
- $12,500
- Time
- 0 days
CE-015 — Electrical gear substitution
- Source
- Procurement
- Status
- Under review
- Cost exposure
- Pending
- Time
- Equipment release at risk
CE-016 — Level 3 finish revision
- Source
- Owner request
- Status
- Pricing received
- Cost exposure
- $8,400
- Time
- No identified impact
CE-017 — Existing utility conflict
- Source
- Field condition
- Status
- Pricing requested
- Cost exposure
- Pending
- Time
- Sitework sequence
CE-018 — Roof screen modification
- Source
- Design revision
- Status
- Withdrawn
- Cost exposure
- $0
- Time
- None identified
Values shown are illustrative only and carry no benchmark implication.
Change-order metrics worth reviewing
Useful change reporting is less about industry benchmarks and more about live exposure. The measures below tend to change how a project actually behaves:
- Open potential changes
- Pending cost exposure
- Approved changes
- Rejected and withdrawn changes
- Average time from identification to decision
- Median time from identification to decision
- Changes awaiting pricing
- Changes awaiting an owner decision
- Changes awaiting a design decision
- Changes by source
- Changes by responsible party
- Changes by project area
- Changes by discipline
- Changes affecting upcoming schedule activities
- Pending time impact
- Approved time impact
- Committed vs. owner-approved change exposure
- Forecast impact
- Changes aging beyond project-defined thresholds
The number of changes alone does not tell leadership the amount of exposure. Twenty small closed items and three unpriced changes against a milestone are very different situations.
Common change-order mistakes that create project risk
Vague scope
The team cannot tell exactly what work is included, so reviewers price and approve different things.
No source record
The change is disconnected from the RFI, drawing, owner decision, field condition, or other trigger that created it.
Cost without time review
Pricing is evaluated and approved without anyone checking what the change does to the schedule.
Time without an affected activity
A request for time does not identify the work, procurement item, or milestone actually affected.
Pricing without backup
Reviewers cannot understand what the requested value represents, so the review turns into a negotiation about missing information.
Unclear responsibility
Nobody knows whose action is next, and the change sits between two parties who each believe the other has it.
Approved change not reflected downstream
The change is executed, but budgets, commitments, forecasts, schedules, or reporting stay outdated.
Email as the only record
The decision exists in threads rather than in the controlled project record, and it disappears when people move on.
Bundling unrelated changes
Multiple unrelated issues in one record become difficult to evaluate, approve, and audit later.
Not every open change deserves the same priority
Change registers are usually sorted by number or dollar value. Neither reflects operational urgency. Priority should reflect:
- Schedule activity affected
- Procurement urgency
- Current cost exposure
- Milestone impact
- Work already proceeding
- Decision dependency
- Owner or design decision required
- Potential rework
- Contractual notice requirements as governed by the contract
Illustrative example. A $100,000 change affecting work six months away may require less immediate operational attention than a $5,000 unresolved change blocking tomorrow's inspection or material release. The dollar values shown are examples only.
Change control is bigger than the change order
The change order is one document. Change control is the broader operating process around identifying potential changes, assigning responsibility, documenting source records, estimating cost, evaluating schedule impact, reviewing and negotiating, obtaining decisions, managing approvals, updating project financials and commitments, updating schedules, maintaining forecast visibility, reporting exposure, and preserving history.
A project can have strong change-order forms and weak change control. The form proves a decision happened. Change control is what keeps that decision connected to cost, schedule, and the work in the field.
How construction teams manage changes at scale
On a small project, documents, a spreadsheet, and a weekly meeting may be enough. As volume grows, that breaks down — because the issue, the pricing, the approval, and the financial impact end up in four different places. Teams running structured change control are generally solving for:
- One change register for the project
- Clear ball-in-court on every item
- Related RFIs
- Related documents
- Related submittals
- Pricing backup
- Budget context
- Contract context
- Commitment context
- Forecast context
- Schedule context
- Approval history
- Notifications when action is required
- Owner decisions
- Design decisions
- Portfolio reporting
- Audit trail
None of this requires a specific vendor. It requires that potential changes, financial exposure, project records, and approvals do not live in disconnected places.
Keep the issue, pricing, approval, financial impact, and project record connected.
Jet.Build connects project changes to the information behind them — budgets, commitments, RFIs, documents, approvals, schedules, and reporting — so teams can see both the individual change and the project-wide exposure.
Centralized change register
Potential, pending, approved, rejected, and executed changes stay visible in one project workflow.
Connected project records
RFIs, drawings, submittals, proposals, and attachments remain connected to the change they support.
Cost visibility
Changes can be reviewed alongside budgets, commitments, contract values, and forecast information.
Clear responsibility
Each item shows status, responsibility, and the next action required.
Approval workflows
Reviews and decisions follow the project's configured workflow and preserve history.
Project and portfolio reporting
Teams can review active change exposure instead of reconstructing it from separate spreadsheets.
Teams can use Jenny, Jet.Build's built-in assistant, to surface underlying project records and summarize project information. Pricing, contractual decisions, and approvals remain the responsibility of the project team. Changes also stay connected to the wider construction project management record.
Frequently asked questions
Good change control protects the financial and decision trail.
At the end of the process, the project should be able to answer every one of these questions without reopening an email thread:
- What changed?
- What caused it?
- What documents support it?
- Who reviewed it?
- What did it cost?
- Did it affect time?
- Who approved it?
- When?
- What project records were updated?
- What unresolved exposure remains?
The change order is the final record of one decision. The change-control process is how the project keeps hundreds of those decisions from becoming disconnected from cost, schedule, and execution.
Related construction change resources.
Where change orders connect to project controls, financials, RFIs, schedules, and approvals.
- Construction Change Order Log TemplateTrack potential changes, pricing, pending cost exposure, approvals, schedule impact, and executed changes in one free spreadsheet-ready register.Read more
- Construction Change Order TemplateA free printable and copy-ready form for documenting scope, cost, time, supporting records, and approvals.Read more
- Construction Cost ManagementTrack budgets, commitments, forecasts, and change exposure across active projects.Read more
- Construction Financial ManagementKeep changing contract values, commitments, invoices, and project financial information aligned.Read more
- What Is an RFI in Construction?Understand the project questions that can surface conditions requiring downstream change management.Read more
- Construction Project ManagementConnect RFIs, submittals, documents, approvals, tasks, and changes to the project record.Read more
- Construction Scheduling SoftwareConnect change decisions to activities, milestones, sequencing, and schedule exposure.Read more
- Workflow AutomationRoute project reviews and decisions with clearer responsibility and history.Read more
- Construction Project Controls SoftwareHow cost, schedule, documents, and issue management work together as one control system.Read more
See how Jet.Build connects project changes to cost, schedule, and execution.
Take about 30 minutes with our team to see how Jet.Build connects potential changes, RFIs, budgets, commitments, approvals, schedules, documents, and reporting across active projects.
Schedule a Demo