Change Order

Master this essential documentation concept

Quick Definition

A formal document that authorizes a modification to the original construction contract, detailing changes in scope, cost, or schedule that all parties must approve.

How Change Order Works

stateDiagram-v2 [*] --> ChangeIdentified : Scope/Cost/Schedule deviation detected ChangeIdentified --> DraftPrepared : Contractor prepares CO draft DraftPrepared --> OwnerReview : Submitted for owner review OwnerReview --> Negotiation : Owner requests revisions Negotiation --> DraftPrepared : Revised CO resubmitted OwnerReview --> ArchitectReview : Owner approves terms ArchitectReview --> Rejected : Architect finds contract conflict Rejected --> DraftPrepared : Contractor revises ArchitectReview --> PendingSignatures : Architect certifies CO PendingSignatures --> Executed : All parties sign Executed --> ContractUpdated : Contract sum and schedule amended ContractUpdated --> [*] : CO logged in project record

Understanding Change Order

A formal document that authorizes a modification to the original construction contract, detailing changes in scope, cost, or schedule that all parties must approve.

Key Features

  • Centralized information management
  • Improved documentation workflows
  • Better team collaboration
  • Enhanced user experience

Benefits for Documentation Teams

  • Reduces repetitive documentation tasks
  • Improves content consistency
  • Enables better content reuse
  • Streamlines review processes

Keeping Change Order Decisions Searchable and Traceable

When a change order comes up during a project, the discussion rarely happens in a document first. It happens in a site walkthrough recording, a stakeholder meeting, or a recorded call where someone explains why the scope shifted and what the cost implications are. That context is valuable — but it's buried in a video file that nobody can search through at 11pm when an auditor or project manager needs to verify what was approved and when.

The core problem with video-only records for change orders is traceability. A change order requires documented approval from all parties, and if your team's institutional knowledge about why a particular change was authorized lives only in a recording, you're one personnel change away from losing that context entirely. When disputes arise — and in construction contracts, they do — timestamps in a video are not the same as structured, searchable documentation.

Converting those recordings into written documentation means your team can search for a specific change order by project, date, or scope description. You can pull the exact language used during approval discussions, cross-reference it with contract terms, and build a reliable audit trail without manually transcribing hours of footage.

Real-World Documentation Use Cases

Unforeseen Underground Utility Conflict During Foundation Excavation

Problem

A contractor discovers unmarked gas lines during excavation, halting work and requiring rerouting. Without a formal change order, the contractor risks absorbing the extra cost and schedule delay, while the owner has no documented authorization for the added expense.

Solution

A Change Order formally documents the scope addition (utility rerouting), the cost impact (labor, materials, equipment standby), and the schedule extension, ensuring all parties agree before work resumes and the contract is legally updated.

Implementation

['Contractor issues a Request for Information (RFI) and photographs the conflict, then submits a detailed cost breakdown for rerouting labor and materials to the architect.', 'Architect reviews the cost against unit prices in the original contract and issues a Change Order draft specifying the revised contract sum and a 5-day schedule extension.', 'Owner reviews, negotiates the standby equipment cost, and approves the revised Change Order amount.', 'All three parties sign the Change Order; the project manager updates the schedule baseline and logs the CO in the contract amendment register.']

Expected Outcome

Work resumes within 48 hours of discovery with a fully executed Change Order, preventing a $42,000 dispute and maintaining a clear audit trail for the owner's lender and insurer.

Owner-Directed Design Upgrade to Mechanical Systems Mid-Construction

Problem

An owner decides to upgrade HVAC units to higher-efficiency models after the mechanical subcontractor has already ordered standard units. The project team lacks a structured process to capture the cost delta, restocking fees, and lead-time impact, leading to verbal agreements that later cause billing disputes.

Solution

A Change Order captures the deductive cost of the original equipment, the additive cost of the upgraded units and extended lead time, and the schedule impact, replacing informal verbal agreements with a binding contract amendment.

Implementation

["Project manager documents the owner's upgrade request in writing and requests a quote from the mechanical subcontractor covering restocking fees, price differential, and revised delivery dates.", 'General contractor compiles a Change Order proposal with a net cost increase and a 12-day schedule impact, attaching the subcontractor quote and equipment cut sheets as supporting documentation.', 'Architect reviews the proposal for compliance with the updated mechanical specifications and certifies the Change Order.', 'Owner signs the executed Change Order before the subcontractor cancels the original equipment order, locking in the new contract sum and revised substantial completion date.']

Expected Outcome

The project avoids a $15,000 billing dispute; the Change Order serves as the authorizing document for the owner's budget reallocation and is referenced in the final certificate of payment.

Differing Site Conditions Discovered in Historic Building Renovation

Problem

During a historic building gut renovation, workers uncover asbestos-containing floor tiles not identified in the pre-construction survey. Remediation is required before work can continue, but the scope, cost, and required licensed subcontractor were never part of the original contract, creating a legal and financial gap.

Solution

A Change Order authorizes the emergency engagement of a licensed asbestos abatement subcontractor, documents the hazardous material removal scope, and formally extends the contract schedule to account for mandatory clearance testing periods.

Implementation

["Contractor immediately stops work in the affected area, notifies the owner and architect in writing per the contract's differing site conditions clause, and obtains three abatement bids.", "Owner's environmental consultant confirms the scope; the architect prepares a Change Order incorporating the lowest qualified abatement bid, a 10-day schedule extension, and updated insurance requirements for the abatement subcontractor.", "Owner's legal team reviews the Change Order to confirm it preserves the owner's right to seek recovery from the original environmental survey firm.", 'All parties execute the Change Order; the abatement subcontractor is formally added to the project roster and work resumes after air clearance certification.']

Expected Outcome

The project maintains regulatory compliance, avoids stop-work orders from the EPA, and the executed Change Order provides the documented basis for the owner's insurance claim against the original site survey firm.

Value Engineering Substitution Proposed by Contractor to Recover Schedule

Problem

A structural steel fabricator is 6 weeks behind schedule, threatening the project's substantial completion date and triggering liquidated damages. The contractor proposes a value engineering substitution using a local supplier with faster delivery, but the substitution requires a specification change and a modest cost reduction that must be formally captured.

Solution

A Change Order documents the approved specification substitution, the deductive cost credit passed to the owner, the revised steel delivery schedule, and the updated substantial completion milestone, protecting all parties from future claims about unauthorized substitutions.

Implementation

["Contractor submits a Value Engineering Proposal with the alternate steel supplier's shop drawings, mill certifications, and a delivery schedule showing a 4-week recovery.", 'Structural engineer of record reviews and approves the substitution; the architect issues a Change Order draft reflecting a $28,000 credit to the owner and the revised schedule milestone.', 'Owner reviews the net benefit, confirms the credit calculation, and signs the Change Order, formally releasing the original fabricator from the steel scope.', 'Project manager updates the master schedule, resets the liquidated damages exposure date, and distributes the executed Change Order to the surety and lender as required by the loan agreement.']

Expected Outcome

The project recovers 4 weeks of schedule, the owner receives a documented $28,000 credit, and the contractor avoids $56,000 in potential liquidated damages, with the Change Order serving as the binding record of the approved substitution.

Best Practices

Establish a Numbered Change Order Log Before Construction Begins

A sequential, numbered log maintained by the project manager ensures every Change Order is tracked from initial request through execution, preventing duplicate numbering, lost documents, and confusion during audits or disputes. The log should capture CO number, description, cost impact, schedule impact, submission date, and execution date in a single source of truth shared with all parties.

✓ Do: Create a shared Change Order log (e.g., in Procore, Autodesk Build, or a shared Excel tracker) at project kickoff, assign sequential CO numbers starting at CO-001, and require all parties to reference the log number in all correspondence related to that change.
✗ Don't: Do not allow verbal change authorizations or informal emails to substitute for a numbered Change Order entry; undocumented changes become unenforceable and create disputes during final payment reconciliation.

Include Detailed Scope Descriptions with Supporting Attachments

A Change Order that references only a dollar amount without describing the specific work added or deleted is legally vulnerable and operationally useless in the field. Every Change Order should reference the affected specification section, drawing number, or RFI, and attach supporting documents such as subcontractor quotes, material cut sheets, or revised drawings.

✓ Do: Write scope descriptions that answer who performs the work, what materials or systems are affected, where on the project the change occurs, and attach all supporting documentation as numbered exhibits referenced within the Change Order body.
✗ Don't: Do not use vague scope language such as 'additional work as directed by owner' or 'miscellaneous changes per field conditions,' as this language is routinely challenged during payment disputes and litigation.

Capture Both Cost and Schedule Impact in Every Change Order

Many project teams diligently document cost changes but neglect to formally record schedule impacts in the Change Order, leading to disputes at project closeout when the contractor claims delay damages that the owner believes were waived. Even a zero-cost Change Order for a pure schedule extension must be executed to amend the contract's substantial completion date.

✓ Do: Include a dedicated schedule impact field in every Change Order template that states either the number of calendar days added or removed, or explicitly states 'No schedule impact,' and update the project baseline schedule within 5 business days of CO execution.
✗ Don't: Do not execute a Change Order that modifies cost without simultaneously addressing whether the work can be performed within the existing schedule; separating these two elements creates a reservation-of-rights dispute at closeout.

Set and Enforce a Change Order Submission Deadline in the Contract

Without a contractual deadline for submitting Change Order requests, contractors may present large cumulative change claims weeks or months after the triggering event, when cost reconstruction is difficult and the owner's budget flexibility is exhausted. Specifying a 10- to 14-day notice requirement in the contract conditions and enforcing it consistently protects both parties.

✓ Do: Reference the contract's notice clause in every Change Order request, include the date the change was identified, and submit the formal Change Order proposal within the contractually specified window, attaching time-stamped field reports or RFIs as evidence of the discovery date.
✗ Don't: Do not accept or issue Change Orders for work that was completed weeks earlier without documented justification for the late submission; retroactive change orders undermine budget controls and signal poor project administration to auditors and lenders.

Require All Authorized Signatories to Execute the Change Order Before Work Proceeds

A Change Order signed by only the contractor and architect but not the owner, or signed by a field superintendent without written authorization authority, is not a fully executed contract amendment and may not be enforceable. Confirm each party's designated signatory and their authorization limits at project kickoff and document them in the project directory.

✓ Do: Maintain a Change Order signature authority matrix listing the name, title, and dollar threshold for each authorized signatory for the owner, contractor, and design team, and verify that the correct signatories have executed the document before authorizing work to proceed.
✗ Don't: Do not begin changed work based on a verbal approval, an email from an unauthorized field representative, or a partially signed Change Order; proceeding without full execution exposes the contractor to non-payment and the owner to unauthorized contract modifications.

How Docsie Helps with Change Order

Build Better Documentation with Docsie

Join thousands of teams creating outstanding documentation

Start Free Trial