The change order request that lands in your inbox often arrives short of approval-ready. A subcontractor may send a number, a one-line scope description, and a time-extension request, with little of the documentation you need to defend the approval six months later when the owner questions the cost or the schedule slips into final accounting.
As the GC reviewer, you sit between the prime contract and the subcontract, with entitlement exposure in both directions. Approve without a defensible record and you may owe a sub for work you cannot recover upstream. Reject without a clear basis and you invite a claim.
This guide walks through the validation workflow a GC uses to evaluate a subcontractor's change order request before approving or rejecting it. The four checks (entitlement, scope bounding, pricing support, and schedule impact) anchor the review in AIA G701 and the prime/sub contract chain.
Where the COR Sits in the Contract Chain
A change order request (COR) is a proposed contract adjustment and may become a claim if entitlement, cost, or time is disputed. Your review decides whether it has merit before it becomes a binding modification. AIA Document G701-2017 documents the executed change in the work and the related adjustments to the contract sum and contract time. Once the owner, contractor, and architect sign it, the new contract sum and substantial completion date become the official baseline.
The subcontract layer adds a second baseline. AIA also offers a G701S change order for contractor-subcontractor changes. That prime/subcontract layer has teeth in both directions.
ConsensusDocs warns that a GC who has flowed down the owner's directives and instructed the sub to proceed may struggle to deny the resulting change order. The warning applies 'regardless of the general contractor's ability to obtain a corresponding change order from the owner.' Reciprocity matters. Flow-down terms imposing obligations on a subcontractor should also flow up, so subcontractor obligations and corresponding rights are addressed together.
Without that reciprocity, you can be obligated to pay the sub for changed work while the owner refuses to issue a corresponding change order upstream on the prime contract, leaving you to absorb the cost.
The Four-Pillar Change Order Request Validation Checklist
Every change order request runs through four sequential checks: entitlement, scope bounding, pricing support, and schedule impact. The order matters.
Entitlement comes first because pricing and schedule review only produce useful answers once you have established that the work qualifies as a change at all. Teams that jump straight to commercial negotiation either accept liability for work they could have rejected or negotiate from a position with no legal basis.
Pillar 1: Is the Change Justified? (Entitlement)
Entitlement asks whether the claimed work falls outside the base contract and traces to a triggering document. A COR may follow an Architect's Supplemental Instruction (ASI), a Construction Change Directive (CCD), a proposal request, or an RFI response. The triggering document must actually modify scope. A clarification of existing scope does not support a COR.
Two types of changes show up at this stage:
A directed change occurs when the owner or architect formally orders work through a CCD or change directive, which usually establishes that changed work was ordered.
A constructive change arises when field conditions, defective documents, or owner conduct effectively alter the scope without a written order, forcing you to build the entitlement record from the facts.
Either way, you still validate notice, causation, pricing, and schedule impact.
ASIs create the most common dispute point. By definition, AIA G710 ASIs cover minor changes that do not affect cost or time. If a sub claims cost or time from an ASI, that is the precise question you have to analyze.
To validate entitlement, identify the triggering document, confirm it is in the project record, and cross-reference its date against the COR submission date. Verify written notice was submitted within the contractually required window. Confirm the claimed work is not already described in base contract drawings or specifications.
A defensible entitlement record requires reading the change against the full project file, including drawings, specifications, the RFI log, submittals, schedule updates, and project correspondence. If the claimed work is already addressed anywhere in that set, the COR fails at this pillar.
Pillar 2: Is Scope Clearly Bounded? (No Scope Creep)
Scope bounding catches work that was already inside the original contract or has already been paid.
Map the claimed work line-by-line against the subcontract scope and contract drawings. Check bid items, allowances, and any unit-price provisions before approving extras.
Every claimed cost must fall within the original statement of work and must not already have been paid, either under the base contract or on a prior change order.
Check prior pay applications and previously approved change orders for duplicate billing, and confirm no verbal authorization was given without a corresponding written directive.
Pillar 3: Is the Pricing Supported at Agreed Rates?
Cost must arrive broken out by labor, material, and equipment, never as a single lump sum. Required backup includes itemized material take-offs, labor hours at actual cost, and subcontractor quotes where they support the claimed work.
For time and materials (T&M) work, where the sub bills actual labor hours plus material cost rather than a fixed price, demand daily time sheets that separate base contract hours from extra work. Confirm labor rates match prevailing wage schedules or contractually agreed rates, and recalculate overhead and profit markup against contractually specified percentages.
Pillar 4: Is the Schedule Impact Real and Documented?
A time extension is only warranted if the change pushes the completion date or an internal milestone, and the Time Impact Analysis (TIA) is how you test that.
Confirm the sub submitted a written TIA tied to the current approved project schedule, then use it to compare the impacted finish against the accepted schedule. If the completion date changes, a time extension may be warranted. If it stays the same, the changed work likely has sufficient float and no extension is owed, subject to contract float provisions and concurrency analysis.
Confirm the affected activities are actually on the critical path (zero float) before accepting any extension claim, and check for concurrent delays in the same window that may offset it.
From the Subcontractor's Seat
The same four pillars tells a sub what a defensible COR must contain before submission. Bring a clear triggering document, scope mapped against the subcontract, broken-out pricing tied to agreed rates, and a TIA against the accepted baseline. Build the position before you submit.
Where Manual COR Review Fails
Manual review breaks down at the seams between project files, and the gaps usually surface only after you approve. By final accounting, the cost of a thin record is locked in.
Three failure modes account for most post-approval pain:
Unsubstantiated backup. A lump sum that looked reasonable at signoff falls apart at final accounting when the labor burden was never substantiated, material quantities never matched delivery tickets, or the entitlement record was never assembled. Files gathered retroactively rarely close the evidentiary gap, especially when daily records and delivery tickets were not captured contemporaneously.
Unresolved entitlement. When disputed work cannot be resolved by signature, some contracts allow a unilateral change order or a similar directive to keep the work moving. Entitlement and valuation issues then carry forward to later resolution, often during final accounting.
Weak negotiating position. Time is of the essence, so both sides feel pressure to settle fast. Thin documentation cuts directly into your leverage at the table, and the discipline you skip during review becomes the bargaining power you lose during negotiation.
Each of these failures traces back to the same root cause, that is, an approval decision made against a partial file.
Reviewing CORs With AI Agents
AI agents shift COR review from memory-based checking against a partial file to document-grounded review of entitlement and scope. Few reviewers can reliably hold every drawing revision, the full RFI log, the ASI history, and the relevant project requirements in working memory at the same time, and that gap is where post-approval surprises come from.
Datagrid's Change Order Agent closes the gap by searching across specs, drawings, RFIs, and submittals and returning answers grounded in project requirements. People still make the approval call. The agent assembles the project-file context and cross-references around that decision so the reviewer is working from a broader base before signing.
How the Change Order Agent fits a COR review
The agent connects directly to the systems where COR-relevant files already live (e.g., Procore for RFIs and submittals, Autodesk Construction Cloud for current drawing sets, SharePoint for contract documents and correspondence), so the review runs against the live project record rather than a manual export. From that connected base, the agent supports the validation workflow without replacing the GC's judgment:
Entitlement investigation. Trace a claimed change back to the triggering document and check whether the work is already addressed in the drawings, specs, RFI log, or submittals.
Scope cross-checking. Compare the claimed work against the subcontract scope, prior pay applications, and previously approved change orders to surface duplicate billing or work already inside the base contract.
Document retrieval at speed. Pull the relevant project-file context in one pass instead of hunting across disconnected systems.
The GC retains notice review, pricing judgment, schedule analysis, and contractual approval authority. The agent does the cross-referencing that a human reviewer rarely has time to complete from memory alone.
Stop Reviewing CORs From a Partial File
Your approval is only as defensible as the cross-checking behind your review. Check out the Change Order Agent to see how you can validate entitlement and bound scope before negotiation. Pin every dollar to a rate and every day to the critical path.
