Datagrid, a Procore Company
Pricing
Request a Demo
LoginCreate Account
Datagrid, a Procore Company

Subscribe to our newsletter

By subscribing, you agree to our Privacy Policy.

Product

  • Product
  • Agents
  • Integrations
  • Pricing
  • Download

Resources

  • Guides
  • Blog
  • Events
  • Release Notes
  • FAQ
  • Brand Assets

Get Help

  • Help Center
  • API Quickstart
  • Contact Us

Follow Us

  • LinkedIn
  • YouTube

Company

  • Careers
  • Privacy Policy
  • Terms of Use
  • Legal Terms
  • Credit Usage Policy and Pricing Terms
  • Report a Vulnerability

© 2026 Datagrid, a Procore company. All rights reserved.

On this page

Change Order Definition and Contract FunctionWho Initiates a Change OrderCommon Types of Change OrdersWhat Causes a Change OrderThe Change Order Process: From Request Through ExecutionHow Change Orders Impact Cost and ScheduleDetecting Scope Changes in Drawing Revisions with AI AgentsBest Practices for Managing Change Orders

Guide

What Is a Change Order in Construction?

Datagrid Team·5 min read
What Is a Change Order in Construction?

A change order is a written, legally binding contract modification that alters the scope, cost, or schedule of a construction project after the original agreement is signed. Change orders are common on projects, and they can materially increase contract price.

I see the same tension on projects repeatedly. A scope change appears in the field, in a drawing revision, or in an owner request. The team keeps moving. Pricing, notice, and documentation lag behind. Then a routine contract modification turns into a cost fight.

This guide covers what a change order is, who initiates one, the common types and triggers, the end-to-end workflow, and where Datagrid's AI agents detect scope changes before they become disputes.

Change Order Definition and Contract Function

A change order is one of the enumerated instruments through which a construction contract is lawfully altered. It is not supplementary documentation, but a formal modification to the contract itself.

The AIA definition

Under AIA Document A201™–2017, a change order is defined as a written instrument prepared by the Architect and signed by the Owner, Contractor, and Architect, stating their agreement on three elements: the change in the Work, the adjustment (if any) in the Contract Sum, and the adjustment (if any) in the Contract Time.

Three structural requirements make this definition legally significant:

  • Three-party execution — Owner, Contractor, and Architect must all sign

  • All three components stated — scope, cost, and time, even if the adjustment to any one is zero

  • Written form is mandatory — oral agreements do not satisfy the A201 definition

In AIA-based workflows, the standard execution vehicle is AIA G701. In this guidance from CMAA, they explain the intended effect of a properly executed change order: "when the Change Order is signed by the parties, it constitutes a final settlement of all matters relating to the change in the work, including any adjustment in the Contract Sum and Time."

Where the contract so provides, that finality can limit subsequent claims relating to the same change, which is why contemporaneous documentation matters so much.

What a Change Order Modifies

Across AIA contracts and EJCDC contracts, a change order consistently addresses the same three elements: work scope, contract cost, and contract time.

Related Instruments Distinguished

A change order is not the only mechanism for modifying work. Under AIA A201 Article 7, three instruments exist:

Instrument

Authorization

Agreement on Price

Nature

Change Order (CO)

Owner + Architect + Contractor

Required before execution

Bilateral agreement

Construction Change Directive (CCD)

Owner + Architect only

Not required

Unilateral owner directive

Minor Change / ASI

Architect alone

N/A (no cost/time impact)

Administrative instruction

The CCD exists for situations where the owner needs work to proceed but agreement on price hasn't been reached. Once agreement on the adjustment is reached, the parties document that change through a change order.

Who Initiates a Change Order

The trigger shapes the workflow that follows. Owners, contractors, and architects or engineers can all initiate a change order, but each gets there through a different path.

Owner-Initiated Changes

Owners initiate change orders when business decisions, program requirements, or budget conditions shift after contract execution. Common triggers include scope additions or reductions, program changes requiring redesign of spaces already under contract, budget-driven scope cuts, and owner-directed acceleration.

When an owner initiates a change, the architect typically issues a Work Changes Proposal Request, such as AIA G709, to the contractor. That is a formal request for pricing, not itself a change order. "Unknown conditions" (e.g., underground utilities, soil defects, Acts of God) are a specific technical term separate from errors and omissions.

Contractor-Initiated Changes

Contractors usually initiate the workflow when field conditions or contract interpretation expose work that sits outside the original scope.

Two primary triggers drive contractor-initiated changes. The first is site conditions, either Type I (conditions materially different from contract document representations) or Type II (unusual conditions not inherent to the work type). The second is errors, inconsistencies, or omissions discovered in contract documents.

Under AIA §3.2.2, the contractor is required to report promptly to the architect any errors, inconsistencies, or omissions discovered in the drawings or specs. Strict notice requirements apply, and under AIA A201 claims procedures, additional compensation claims must be made within 21 days of the triggering event.

Architect/Engineer-Initiated Changes

Architects and engineers can initiate administrative change workflows, but their authority is limited by the contract. The architect occupies a dual role, administering the contract on behalf of the owner while also being the source of design documents that may themselves require correction.

The architect has limited independent authority under AIA §7.4 to order minor changes that do not affect contract sum or contract time. Anything beyond that requires a CCD or formal change order.

For civil and infrastructure projects, EJCDC documents govern the engineer's administrative role, with change order initiation governed under EJCDC C-700 and professional services obligations established under EJCDC E-500.

Common Types of Change Orders

The type of change order usually tells you where review risk sits. I separate them by the kind of impact they create because that makes review faster and surfaces the dispute risk earlier.

Additive Change Orders

An additive change order expands the original contract by increasing scope, cost, or time. This is a common type. Examples include owner-requested finish upgrades, foundation redesigns requiring additional materials, or unforeseen code requirements mandating work beyond the original design.

Deductive Change Orders

A deductive change order removes a specified portion of work from the contract, lowering the total price. Accurate calculation of the credit amount is the central practical concern and a common point of dispute. Examples include eliminating custom millwork packages to cut costs or substituting specified elements with less expensive code-compliant alternatives.

Time-Impact Change Orders

A time-impact change order formally extends, or in rarer cases compresses, the contract completion date without necessarily changing the contract price. Omitting time from a change order can be costly in construction contracting. Without a formal time extension, contractors may face liquidated damages exposure even for owner-caused delays.

Scope Modification Change Orders

Scope modifications alter what the project delivers by changing the nature or configuration of work rather than simply adding or subtracting. These carry high dispute risk because they often expose disagreements over what the original contract price did or did not include.

What Causes a Change Order

Most change orders come from a short list of recurring breakdowns. Teams see the same patterns repeatedly, even when the project specifics differ.

The Volpe report frames the systemic origin, stateing: "Rushed or suboptimal technical project development practices, an unhealthy organizational culture, and financial and funding stressors can lead to project development breakdowns that cause change orders that negatively impact project scopes, schedules, and budgets."

Design Errors and Omissions

Design errors and omissions are typically the single largest individual cause of change orders. MEP coordination failures, conflicts between drawings and specifications, and incomplete structural details drive a disproportionate share of rework cost on both domestic and international projects, and they surface repeatedly as the root cause when field teams hit buildability problems that force a contract modification.

Owner-Directed Changes

Owner-directed changes are another leading source of change orders, trailing only design errors and omissions in their contribution to rework cost. Two legally distinct subtypes exist:

  • Directed changes, where the owner explicitly orders additional or different work

  • Constructive changes, where informal acts or failures to act are alleged by the contractor to constitute a change

Differing Site Conditions

Differing site conditions can drive some of the largest change order impacts. When the trigger is unforeseen conditions, the cost magnitude of the resulting change order tends to be disproportionately high compared to other causes. Subsurface rock inconsistent with geotechnical reports, undisclosed underground utilities, contaminated soil, and structural conditions concealed behind walls in renovation projects all fall into this category.

Design-build projects experience 3.8% less cost growth than traditional design-bid-build, according to DBIA's 2025 Design-Build Data Sourcebook. Delivery method is a material financial variable.

Scope Creep and Regulatory Changes

Project complexity amplifies change order risk. High subcontractor counts, inadequate scope definition at contract execution, and compressed design schedules all contribute.

Regulatory triggers represent a separate but related cause category, including AHJ interpretations differing from design assumptions, fire marshal requirements not anticipated in documents, and environmental compliance requirements triggered by site discoveries.

The Change Order Process: From Request Through Execution

This workflow breaks most often between discovery and signature. Teams know what a change order is. The harder part is keeping drawings, RFIs, pricing backup, and notice deadlines aligned while the job keeps moving.

Step 1: Identification and Notice

The workflow starts when the team identifies a potential change and gives notice under the contract. Changes surface through field conditions discovered during construction, owner-initiated scope modifications, design gaps surfaced through the RFI process, or errors and omissions in contract documents.

Under AIA-based change procedures, changes in the work are handled through formal written instruments. Notice requirements vary by contract, and on some projects the initial notification window may be short.

Step 2: Proposed Change Order (PCO)

A proposed change order, or similar pre-approval document, is commonly used to initiate and document the change request before formal approval. AIA guidance describes the PCO as a way to document the review workflow before the formal change order is executed.

Step 3: Pricing

Pricing has to capture the full impact of the change, not just the obvious direct cost. AIA Article 7.3.3 establishes four pricing methods: lump sum, unit prices, cost plus fee, and the §7.3.7 fallback (time and materials).

PCO documentation should break down hard costs (labor, materials, equipment) and soft impacts (supervision, mobilization), state the schedule impact, and capture labor burden, overhead, and profit.

Step 4: Approval and Execution

Execution is what makes the change order binding. Under the AIA definition, all three signatures (Owner, Architect, Contractor) are required for a change order to be binding. The form is commonly routed in a defined signing sequence before change order costs are integrated into regular payment applications using AIA Forms G702/G703.

How Change Orders Impact Cost and Schedule

Change orders can materially affect both cost and schedule, but the impact varies widely by project type and how early the team identifies the change.

A 2023 AIA Research Note analyzing 892,457 change orders across 18,229 completed U.S. construction projects found that 38.24% of completed projects have only one change order over the project's life, and the average duration impact is 1.07–1.13%.

But those averages obscure tail risk. An ASCE study of 161 school renovation projects totaling $1 billion found that three-fourths of all project cost growth was attributable to change orders, and approximately 40% of projects faced schedule overruns driven by change orders. Projects with schedule overruns had a statistically significantly higher change order rate (5.26%) than those without (2.51%).

Detecting Scope Changes in Drawing Revisions with AI Agents

Drawing revision review is the control point that matters most. Manual comparison is slow, inconsistent, and easy to defer when the job is moving.

That gap, between what teams can review manually and what actually changed in a drawing set, is where unpriced scope drift turns into change orders and later disputes.

How Datagrid's AI Agents Execute This Workflow

Datagrid's Document Comparison Agent compares drawing sets to detect material changes, scope creep, and project risk before they hit the field. It compares revisions against previous releases and generates focused summaries highlighting what changed, where it changed, and why it matters from an owner and project management perspective.

Document Comparison Agent

Analyze differences between drawing sets to identify material changes that may impact scope, cost, schedule, or constructability.

Use Agent
ProcoreSharepointTrimble ConnectOracle AconexSlack

For change order review, the Change Order Agent searches across project requirements and supporting project files to analyze change requests in context.

Change Order Agent

Review change order requests to validate scope, cost, and schedule impacts using supporting project documentation.

Use Agent
Procore

These AI agents execute through cross-referencing, revision comparison, and document-grounded review across connected project records.

Best Practices for Managing Change Orders

The best teams standardize the workflow before the pressure hits. Contract language matters. Notice language matters. The handoff between field discovery, pricing, and approval matters just as much.

Change order clauses and notice clauses are among the leading sources of construction disputes. The practices that matter most break across three project phases.

Pre-Construction

Pre-construction is where teams prevent avoidable change order friction. Define scope with finalized drawings before contract execution. Negotiate an equitable change order workflow before signing, covering who has authority to approve changes, required documentation formats, and time constraints.

Owners should have a biddability and constructability review performed on design documents before bidding, because design professionals review drawings differently than contractors.

For operating facilities, assign senior operators to the design review team to catch maintenance and operations requirements before they surface as change orders during commissioning.

During Construction

During construction, written discipline matters more than good intentions. Put changes in writing. No verbal or handshake agreements. Verbal approvals are a common initiating point for change order disputes.

In AIA-based workflows, use AIA G701 as the formal change order instrument. When an RFI response appears to cause a change, provide timely written notice to the owner. If the owner directs compliance without issuing a change order, comply under protest and document every time and cost impact.

Closeout

Closeout gets harder when teams defer change order resolution. Resolve change orders continuously throughout the project, not at the end. The CMAA closeout guide explicitly identifies delayed change order resolution as one of the top three challenges cited by construction professionals during closeout.

Annotate BIM and CAD files with every change order, ASI, and RFI. Hold a formal post-mortem to capture lessons on change order frequency and process effectiveness.

Datagrid's AI agents can compare revisions, analyze change documentation against project records, and flag potential deviations for human review before they become disputes.

Agents in this guide

📝

Document Comparison Agent

Compare drawing sets to identify material changes, scope creep, and project risk before they hit the field.

Use Agent
IntercomPlanGridSlackSharePointOracle AconexGitLabBigCommerceDatabricksProcoreTrimble ConnectDocuSignBigQueryAirtableBoxAmazon AuroraAmazon AWS S3AcumaticaAccubid AnywhereGoogle DriveOneDriveMS FabricGoogle AnalyticsMS Dynamics 365 NAVBIM360 DocsLinkedIn PagesAmazon RedshiftAsanaGoogle Cloud SQL - SQL ServerOutreachGoogle CalendarMicrosoft ExcelOracle Primavera Cloud (OPC)Azure SQL DatabaseMicrosoft TeamsFREDAzure PostgreSQL DatabaseGoogle Cloud StorageHelloSignJDBC MySQLSalesforceMongoDBCivil 3DStripeMondayMixpanelAmazon RDSDropboxHilti ON!TrackArchiCADSYNCHRO 4D ProFieldwireAzure Blob StorageHubSpotCMiCNotionSurveyMonkeyAzure Data Lake StorageSnowflakeAzure MySQL DatabaseFreshdeskBIM TrackExchangeGoogle Cloud SQL - PostgreSQL
🤖

Change Order Agent

Search deeply across specs, drawings, RFIs, and submittals to get accurate answers grounded in project requirements.

Use Agent
IntercomPlanGridSlackSharePointOracle AconexGitLabBigCommerceDatabricksProcoreTrimble ConnectDocuSignBigQueryAirtableBoxAmazon AuroraAmazon AWS S3AcumaticaAccubid AnywhereGoogle DriveOneDriveMS FabricGoogle AnalyticsMS Dynamics 365 NAVBIM360 DocsLinkedIn PagesAmazon RedshiftAsanaGoogle Cloud SQL - SQL ServerOutreachGoogle CalendarMicrosoft ExcelOracle Primavera Cloud (OPC)Azure SQL DatabaseMicrosoft TeamsFREDAzure PostgreSQL DatabaseGoogle Cloud StorageHelloSignJDBC MySQLSalesforceMongoDBCivil 3DStripeMondayMixpanelAmazon RDSDropboxHilti ON!TrackArchiCADSYNCHRO 4D ProFieldwireAzure Blob StorageHubSpotCMiCNotionSurveyMonkeyAzure Data Lake StorageSnowflakeAzure MySQL DatabaseFreshdeskBIM TrackExchangeGoogle Cloud SQL - PostgreSQL

Works with

Intercom

Intercom

Connect Intercom with Datagrid to structure and analyze customer conversations using AI agents.

T

Textura

Connect Textura to Datagrid for automated payment workflows and financial analysis in construction projects.

PlanGrid

PlanGrid

Connect PlanGrid to Datagrid and automate RFI workflows, submittal tracking, sheet sync, and field data processing with agentic AI agents.

Slack

Slack

Connect Slack to Datagrid and turn workspace conversations, files, and user data into actionable inputs for AI agents that execute cross-platform workflows automatically.

SharePoint

SharePoint

Connect SharePoint to Datagrid to automate document processing and compliance checks across your SharePoint libraries.

Oracle Aconex

Oracle Aconex

Integrate Oracle Aconex with Datagrid to automate project file processing and RFI triage using AI.

Related guides

Construction Daily Reports (The Complete Guide)

Construction Daily Reports (The Complete Guide)

Learn what construction daily reports contain, why they carry legal weight, and how AI agents assemble and validate them before disputes arise.

RFI Meaning in Construction and Procurement: Definition, Types & Examples

RFI Meaning in Construction and Procurement: Definition, Types & Examples

RFI means different things in construction vs. procurement. Learn the key differences, workflow steps, and how AI agents validate RFIs before submission.

Contract Review Services vs. AI Agents: When Construction Teams Should Use Each

Contract Review Services vs. AI Agents: When Construction Teams Should Use Each

Compare outsourced contract review services with in-house teams using AI agents, when to use each and how a hybrid model improves review at scale.

Agents in this guide

📝

Document Comparison Agent

Compare drawing sets to identify material changes, scope creep, and project risk before they hit the field.

🤖

Change Order Agent

Search deeply across specs, drawings, RFIs, and submittals to get accurate answers grounded in project requirements.

Works with

IntercomIntercomTTexturaPlanGridPlanGridSlackSlackSharePointSharePointOracle AconexOracle Aconex

Use cases

AI Document Management Software for ConstructionBluebeam Plan Review Software AlternativeBluebeam Drawing Comparison Agent for ConstructionAI Change Order Management for ConstructionBluebeam Tools Alternative: AI Document Comparison AgentBluebeam PDF Editor Alternative for Construction TeamsBluebeam Review Alternative: AI-Powered Document ComparisonBluebeam PDF Alternative for Construction Document Comparison

You've got more important things to do. Let Datagrid handle the rest.

Watch our quick demo to see how Datagrid transforms workflows. Discover the seamless integration of our AI assistants in real-time tasks.

Book a DemoLearn More