---
title: 'Construction change directive vs. change order: keep authority, scope and price separate'
url: 'https://piper-ai.com/resources/construction-change-directive-vs-change-order'
description: 'A change directive can move work ahead before price and time are agreed. A GC review method for preserving the scope baseline, cost evidence and open decisions.'
contentTypes: [guide]
publishedAt: '2026-11-15T10:38:25.000Z'
updatedAt: '2026-11-18T15:32:26.160Z'
author: 'Ido Gedanken, CEO'
readingTime: 3
---

# Construction change directive vs. change order: keep authority, scope and price separate

1. Authorization to proceed and agreement on price are separate decisions.
2. Compare the changed work with the scope and estimate that were actually approved.
3. Preserve the record needed to resolve cost and time under the governing contract.

A construction change directive and a change order handle different states of agreement. Under the AIA process, a change order records an agreed change, including its cost and time treatment. A construction change directive can direct changed work before those adjustments are fully agreed. The governing contract determines the authority, process and obligations on the actual project.

For a GC estimating or preconstruction leader, the practical issue is keeping three records connected: what the contract authorized, what changed in the work, and what cost and schedule treatment remains open. A direction to start does not make an unsupported price complete.

## Confirm the authority before treating an instruction as a directive

[AIA's comparison of directives and change orders](https://learn.aiacontracts.com/articles/construction-change-directive-vs-change-order/) explains the distinction within its contract framework. Read it alongside the executed agreement and its amendments. Do not assume that an email, RFI response or revised drawing carries the same authority as the contract's formal change instrument.

Identify who issued the instruction, which document it references, what work it directs and which procedure applies. Escalate unclear authority through the project's contract administration process. The estimator's scope analysis supports that process; it does not decide contractual entitlement.

## Reconstruct the approved baseline before pricing the difference

Start with the scope that the approved number carried. That may require the drawing and specification revision, subcontractor proposal, accepted qualifications, clarifications and estimate basis. Comparing the new instruction with an obsolete bid set can produce a neat price for the wrong difference.

Use the [drawing-revision review method](https://piper-ai.com/resources/drawing-revisions-cascade-scope-bids-estimate) to identify affected packages. Separate added work, deleted work, changed means or sequence, and requirements already included. Record why each item belongs in its category rather than assuming every revised detail is an extra.

An illustrative example is a revised equipment location. The equipment itself may be unchanged while supports, connections, access and temporary work differ. A quote covering the equipment move alone may leave several packages unresolved.

## Keep the open decisions visible in one change register

The following is a working review structure, not a replacement for the required contract forms.

| Review lane | Evidence to preserve | Decision still needed |
| --- | --- | --- |
| Authority | Issued instruction and applicable contract procedure | Who can authorize the action and resolve the adjustment |
| Scope | Baseline documents and marked changed requirements | Which packages add or remove work |
| Price | Itemized proposal and supporting basis | What is agreed and what remains unsupported |
| Time | Affected activities and the documented sequence | What schedule treatment requires determination |
| Closeout | Final approved modification and revised records | Which estimate and scope versions become the baseline |

Do not hide an unresolved time question inside an agreed cost total. Likewise, an estimated exposure is different from an approved contract adjustment. Keep status labels clear enough that a reviewer can tell which number may be used for which decision.

## Collect evidence while the work and its consequences are identifiable

Use the contract's notice and record requirements. Assign responsibility for the contemporaneous records needed on this project, such as labor and equipment records, quantities, deliveries, photographs, subcontractor support and schedule information. Do not invent a universal deadline or cost-recovery rule.

The estimator should distinguish the calculation from the evidence behind it. An itemized spreadsheet is easier to review when the material scope difference, production assumption and relevant source can be found without reconstructing an earlier conversation.

[AIA's change-order explanation](https://learn.aiacontracts.com/articles/6378493-the-fundamentals-of-change-orders-in-construction/) also notes that adjustments can include credits or no change in price or time. Review deletions and retained obligations as carefully as additions.

## Close the change by updating the working project understanding

When the adjustment is resolved, identify what becomes the new baseline. Reconcile the approved modification with affected subcontract scopes, the estimate, procurement commitments and schedule records. Preserve any remaining qualification rather than treating one signature as proof that every downstream record agrees.

The [addenda-management guide](https://piper-ai.com/resources/construction-addenda-management-for-gc-estimators) covers the analogous problem before award: an acknowledgment does not prove the scope and number were updated. The same discipline helps prevent a later change from creating a second, disconnected version of the project.

## Trace the scope difference before reviewing the number

Piper connects the project understanding used in scope work with the review of an estimate. Its [Scope Generation](https://piper-ai.com/use-cases/scope-generation) and [Final Bid Review](https://piper-ai.com/use-cases/final-bid-review) workflows can help a preconstruction team follow requirements through documents, trade scope and proposals, with findings linked to sources.

That is useful when establishing or revisiting a pricing baseline. Contract authority, notices, entitlement, field records and final approval remain responsibilities of the project team. Piper's preconstruction workflows do not issue a contractual change directive or settle a change order.
