A construction change order process is the documented sequence that turns a scope, cost or schedule change into a signed contract amendment: identify the change, document it, price it, get it approved, execute the work and record the result. The moment a potential change surfaces on site, log it and assign an owner before any work proceeds on the new scope.
TL;DR:
- Confirm contractual entitlement before pricing a change, because entitlement is the most common failure point; support cost and delay claims with contemporaneous evidence.
- Do not start disputed extra work without a signed interim directive; otherwise, the contractor carries the cost and schedule risk until approval is settled.
- A defensible change order identifies the contract clause, revised scope, dates, schedule impact, separate cost components, authorized signatories, version number, and supporting attachments.
- Separate preparation, review, approval, and recordkeeping, and set spending limits for each approver; retain every version to preserve an auditable negotiation history.
Table of Contents
- What a change order actually is
- Common reasons change orders occur
- Step by step: from identification to a recorded change order
- What a change order document must include
- Pricing, entitlement and proving quantum
- Who approves what: roles and document control
- How a form-to-contract workflow maps to this process
- Where most change order disputes actually start
- A practical way to run change orders without the paperwork pileup
- FAQ
- Sources
What a change order actually is
A change order is a written amendment to the original contract that adjusts scope, price or schedule once both parties agree. From an owner’s perspective, it formalises approval to spend more or extend a deadline. From a contractor’s perspective, it is the mechanism that protects payment for work outside the original agreement. The Associated General Contractors describe a change order as work added or removed from the original contract to serve the finished product, and that definition holds across commercial and residential projects alike.
On site, you will hear several terms used almost interchangeably:
- Variation: common on contracts using standard forms outside North America.
- Change directive: an owner-issued instruction to proceed before price agreement is finalised.
- Contract modification: the broader legal term covering any amendment, including change orders.
Not every adjustment needs this formality. A colour swap within an existing allowance is administrative; a structural redesign is not.
Common reasons change orders occur
Most change orders trace back to a short list of recurring triggers, and recognising which one applies shapes how you document and price the request.
- Owner-directed additions: the client wants more than what the drawings show.
- Unforeseen site conditions: concealed utilities, rock, or contamination discovered after excavation begins.
- Design errors or omissions: drawings that conflict with code or with each other.
- Regulatory or code changes: a jurisdiction updates requirements mid-project.
- Material substitutions: supply shortages or lead times force an alternative product.
- Schedule-driven changes: compressing or extending a sequence to meet a new deadline.
Each of these carries different evidence requirements. A code change is easy to prove with a citation; a concealed condition needs photos and a dated site report.
Step by step: from identification to a recorded change order
The AACE recommended practice 100R-19 sets out a sequential control loop for change management: identification, preliminary submittal, formal submittal, approval or rejection, execution and, where needed, claims handling. Projects that follow this sequence consistently produce cleaner records and fewer disputes down the track.
- Identify and notify: log the potential change the day it’s spotted and notify the contract administrator or designer per the notice clause.
- Assess preliminarily: assign an owner (usually the project manager) to confirm the change is real and estimate its rough magnitude.
- Prepare the proposed change order: reference the original scope, drawings and specification sections affected, and attach supporting photos or markups.
- Price it properly: build a defensible estimate covering labour, materials, equipment and any supplier quotes, plus a time impact if the schedule is affected.
- Submit formally: route the priced change order to the owner or designer for entitlement review, not just a cost check.
- Negotiate and approve: resolve any disputed line items, then execute the signed document and update the contract baseline.
- Record and link: file the signed change order against the cost report and the next invoice cycle so nothing falls through the gap.
Pro Tip: Never let work on a disputed change proceed without at least a signed interim directive, otherwise you carry the cost and schedule risk alone.
A trade-focused breakdown of this same sequence, including negotiation tactics specific to subcontractors, is covered in this field guide for trade contractors.
What a change order document must include
A change order that skips any of these fields invites argument later, because every missing detail becomes a negotiating point.
- Project and contract identifiers: project name, contract number and reference to the original agreement clause.
- Scope description: a precise statement of the changed work, linked to revised drawings or specification sections.
- Dates and schedule impact: the date raised, the date required and any extension to the completion date.
- Price breakdown: labour, materials, equipment, overhead and any allowance adjustments shown separately.
- Approval block: named signatories for preparer, reviewer and approver, with a version number.
- Attachments: photos, manufacturer or supplier quotes, and a time-impact analysis where schedule is affected.
A ready-to-use change order template captures each of these fields so nothing gets left off the form before it reaches the approver.
Pricing, entitlement and proving quantum
Getting a change order approved without dispute comes down to three things: entitlement, causation and quantum. Entitlement is the contractual right to compensation or time, causation links the triggering event to the cost or delay claimed, and quantum is the dollar or day figure attached to it. Practitioners at ConstructConnect note that entitlement is the most common point of failure: contractors chase a price before confirming they actually have the right to be paid for the change at all.
Once entitlement is established, quantum needs real numbers behind it:
- Unit rates: pre-agreed rates from the original contract for common items.
- Time-and-materials logs: daily records of crew hours, equipment and materials used.
- Supplier quotes: current pricing for substituted or added materials.
- Provisional sums: pre-allocated budget lines drawn down as work proceeds, documented against actual cost.
Collecting supplier quotes and time-and-materials logs at the estimate stage makes quantum far easier to defend when a change order reaches negotiation or, worse, a formal claim, according to ConstructConnect’s guidance on the process. Daily logs, dated photos and a short delay narrative do the same job for schedule impacts.
Protecting margin on these figures matters as much as proving them. Practical pricing guidance for subcontractors covers how to avoid giving away margin during negotiation, which pairs directly with the quantum work above.
Who approves what: roles and document control
Change orders fail quietly when the same person prepares and approves the estimate, because there’s no independent check on the number. Assign four distinct roles on every project of meaningful size:
- Preparer: drafts the change order and gathers supporting evidence.
- Reviewer: checks entitlement, causation and the price breakdown before it goes further.
- Approver: signs off with authority tied to a delegated spending threshold.
- Recorder: files the executed document, links it to the cost report and updates the contract baseline.
Set a delegated authority threshold (for example, a site supervisor approves up to a set dollar figure, anything above goes to the project manager) so routing doesn’t stall on signatures. Keep every version of a change order, not just the final one, so the negotiation history is auditable if a dispute arises later.
Pro Tip: Standardise the template across every project so reviewers know exactly where to find entitlement, price and schedule information without hunting through a document.
How a form-to-contract workflow maps to this process
We built our form-to-contract workflow around exactly this sequence. A guided intake form captures scope description, attachments, dates and pricing in the same structured fields a change order document needs, then auto-generates the formal change order from those answers rather than leaving someone to retype them into a template.
- Structured intake: a site team logs a potential change order (PCO) through a mobile form the moment it’s spotted.
- Auto-generated document: the form answers populate a change order ready for review, with attachments already linked.
- E-signature and staged payment: approval and deposit collection happen in the same flow, so a signed change order and a paid deposit land together.
- Audit trail: every version, signature and payment is stored against the project, giving entitlement and quantum a documented paper trail if questioned later.
A site PCO can move from field note to signed, paid change order without ever leaving a single workflow, closing the gap between documentation and payment that most paper-based processes leave open.
Where most change order disputes actually start
Most disputes we see trace back to informal approval: a verbal “go ahead” from a site supervisor with no signature and no price agreed before work started. By the time the change order is written up, memories differ and the paperwork is reconstructed rather than contemporaneous.
A compact checklist avoids most of this: log the change the day it appears, assign a named owner, attach evidence immediately, quantify both cost and schedule before work proceeds, and require a signature before the new scope begins. Daily documentation and prompt invoicing close the loop faster than any negotiation ever will.
— Josh
A practical way to run change orders without the paperwork pileup
Chasing signatures and retyping site notes into a change order template costs time you don’t get back, and every day a change order sits unsigned is a day of margin risk. Our form-to-contract workflow turns a site form directly into a signed, priced change order, with deposit or payment collection built into the same step, so approval and payment happen together instead of weeks apart.
Our construction solutions page shows the templates built for this exact workflow, and our pricing page lists the Standard plan at a monthly fee charged per seat and the Professional plan at a higher monthly fee charged per seat if you want to compare what fits your team. Download the change order template and start a trial to see how quickly a logged site change becomes a signed, paid record.
FAQ
Who pays for change orders in construction?
The party responsible depends on what caused the change: owners typically pay for scope additions or design changes they request, while contractors absorb costs tied to their own errors. Unforeseen conditions or code changes are usually negotiated based on the contract’s change clause.
Who prepares change orders in construction?
A contractor, project manager or site supervisor typically prepares the initial change order, drawing on evidence gathered at the point the change was identified. The Associated General Contractors note that documentation standards for who raises and records a change order are usually set out in the original contract.
How do you negotiate a construction change order?
Effective negotiation starts with proving entitlement and causation before discussing price, since ConstructConnect’s analysis identifies entitlement as the most common point of failure. Supporting quantum with supplier quotes and time-and-materials logs collected at the estimate stage makes the final number far harder to dispute.
What is the process for issuing a change order?
The process follows a sequence: identify and notify, assess preliminarily, document and price the change, submit for formal review, negotiate and approve, then execute and record it against the contract baseline. The AACE 100R-19 recommended practice sets out this sequence along with templates projects can adapt.
Sources
- Contract change management (AACE 100R-19)
- Mastering change order process
- Change orders | Associated General Contractors