If you manage contract administration on commercial projects, this distinction drives where change exposure starts to accumulate.
A construction change directive (CCD) compels the contractor to proceed with changed work immediately, before anyone agrees on price or schedule impact. A change order (CO) requires all three parties to sign off before the contractor lifts a tool.
That single distinction, unilateral authority versus trilateral agreement, determines who carries the documentation burden, when pricing gets resolved, and where disputes originate months later.
I see project teams confuse these instruments all the time, treating a CCD like a preliminary change order instead of recognizing it as a different contractual mechanism with its own provisional pricing rules, response deadlines, and dispute paths. The difference is the line between controlled change management and an accumulating inventory of unresolved financial exposure.
Construction Change Directive vs Change Order: The Contractual Distinction Under AIA A201
The difference between these instruments comes down to consent. Under AIA A201-2017, a change order is a trilateral agreement. A CCD is a unilateral directive. Everything downstream, including pricing, schedule, documentation obligations, and dispute paths, flows from that structural difference.
Change Orders: Trilateral Agreement Under §7.2
A change order under §7.2 (from AIA A201-2017) is signed by the Owner, Contractor, and Architect. It documents agreement on three elements simultaneously, the change in the Work, the Contract Sum adjustment, and the Contract Time adjustment. The Contractor cannot be compelled to perform changed work through a change order without signing.
Construction Change Directives: Unilateral Authority Under §7.3
A CCD under §7.3.1 is signed by the Owner and Architect only. The Contractor must proceed promptly upon receipt. CCDs are issued under two conditions. One is urgency, where time-critical field conditions cannot wait for a negotiated CO. The other is disagreement, where the parties cannot reach agreement on price, time, or both. The Contractor's remedy is not refusal but the dispute mechanisms in §7.3.6 and Article 15.
Provisional Pricing and CCD-to-CO Conversion
Pricing (§7.3.3) is resolved through one of four methods:
mutual lump sum
contract unit prices
cost-plus with agreed fee
the Architect's fallback determination
The Contractor has 10 calendar days to advise the Architect of agreement or disagreement. If the Contractor disagrees, or fails to respond within the window, pricing proceeds under the Architect's §7.3.4 determination.
The 2017 edition of AIA A201 added §7.3.5, requiring cost records when work proceeds without final price agreement. Under that requirement, records prepared after the fact are not a substitute for records created concurrent with the work.
A CCD converts to a CO once the Owner and Contractor agree on final adjustments. The Architect prepares a change order, AIA G701, for trilateral execution. Teams should not convert a CCD to a CO until time claims and contract values are fully resolved. Premature conversion can waive unresolved claims. CCDs should be numbered sequentially and separately from change orders.
Where Manual Contract Administration Breaks Under Drawing-Revision Pressure
Drawing revisions can outpace documentation. I see the gap between the original Issued for Construction set and the fully conformed state become the place where superseded drawings stay in circulation and unresolved exposure accumulates.
Superseded Drawings Reaching the Field
The failure pattern is predictable. Work is installed per the drawing in hand, the discrepancy surfaces during inspection, rework is directed, and a change order request follows. Whether the GC or subcontractor absorbs the cost depends entirely on whether a transmittal record exists and whether receipt was acknowledged.
Untracked ASIs Becoming Cumulative Impact Claims
Architect's Supplemental Instructions individually characterized as "no cost impact" can accumulate across dozens of issuances into a cumulative impact claim assembled at project end. When ASIs are tracked only in email threads, neither party has the documentary record to resolve the dispute without litigation. This is scope creep driven by documentation gaps.
The Fragmentation Tax
When no system links RFIs, ASIs, drawing revisions, and change orders together, every CCD becomes an unresolved financial liability that project leadership may not see clearly enough or early enough. RFIs can live in one spreadsheet, ASIs in an email folder, drawing revisions on a shared drive, and change orders in a separate log. None are linked.
According to the PlanGrid and FMI report, construction employees spend more than 14 hours per week looking for project data, dealing with mistakes, or handling rework and conflict resolution.
When documentation is fragmented across systems that do not communicate, mechanical specifications conflict with revised structural drawings without anyone noticing. No shared system tracks the connection between them. Every CCD can remain an unresolved financial liability until it crystallizes into a formal claim.
How Agentic AI Changes Contract Administration
Agentic AI delivers two changes to contract administration. Faster review cycles and an earlier detection point that catches conflicts before the revised drawing reaches the field. Traditional contract administration is event-triggered. A field crew encounters a conflict, an RFI is submitted, a directive is issued, and documentation begins after the fact.
Datagrid's Document Comparison Agent compares drawing sets to identify material changes, scope creep, and project risk before they hit the field. When a revised drawing set is uploaded, the agent compares it against prior revisions and flags changes that can shape change management and cost tracking discussions before the revision reaches the field.
The contract administrator's role shifts from comprehensive reviewer to exception handler, engaging where the AI agent has flagged a condition requiring judgment rather than at every project-file touchpoint.
How It Works
Across the change management workflow, Datagrid's AI agents handle the work that would otherwise pull contract administrators away from adjudication:
Detect and flag drawing-set changes and scope conflicts before field distribution
Assemble the contemporaneous record by linking revisions to the originating RFI, ASI, or bulletin
Connect across the project management, scheduling, and file-sharing systems where your project files already live
What Project Teams Are Saying
"With Datagrid we are able to review 8 submittals in 1 hour. This would have taken a team of 4 people at least 8 hours if not more." — Jacob Freitas, Project Executive, Level 10
When contract administrators spend less time reconstructing the RFI-ASI-drawing-revision chain and more time adjudicating change conditions, project teams can resolve CCD-to-CO conversions faster and with stronger documentation. This reduces the chance of disputes that erode owner-GC trust and GC-subcontractor relationships alike.
See Datagrid's Change Order Agent in Action
Datagrid's Change Order Agent reviews change order requests across contracts, subcontracts, drawings, RFIs, ASIs, schedules, and pricing backup to assess whether a change is justified, clearly scoped, and supported.
Used alongside the earlier document-comparison agent workflow, it validates scope, cost, and schedule impacts, identifies missing backup, and strengthens commercial review and approval discussions.
Stop reconstructing the RFI, ASI, and drawing-revision chain after the fact. Start detecting change conditions at the moment they enter the drawing set.
