A Potential Change Order (PCO) is the earliest written signal that a cost or scope change may be heading toward the contract.
From my experience, profit losses on construction projects typically begin the moment something unexpected happens in the field or an RFI response expands the scope of work. If you don't catch it early with a PCO, you lose money.
A PCO is nonbinding. It does not modify the contract or bind the parties. The PCO gives the team an early place to document the change before contract modification. The PCO is often where a project team starts the audit trail used to assess whether a change is recoverable and defensible months later at closeout.
In many workflows, the PCO prevents undocumented triggering conditions from turning into unrecoverable change exposure.
What Is a PCO and Who Creates It
A PCO is a record project teams use to track a change in a work condition when that change is expected to result in extra work or extra cost above the agreed-upon contract amount. It is informal and pre-execution, with negotiation still to come before it becomes a binding Change Order.
The GC Usually Owns Authorship in GC-Led Workflows
In many GC-led workflows, the PCO is created to track a work condition that may be over and above the base contract and to establish a chain of events leading to contract modifications. Subcontractors contribute pricing and schedule impact data when the GC routes the PCO to them. Project teams also use a PCO to gather information before deciding whether a change should move forward.
What Triggers a PCO
Three conditions commonly initiate the PCO workflow:
An RFI response reveals that the architect's direction requires work not contemplated in the original bid documents.
Field conditions diverge from what the contract documents represented, such as concealed structural conditions on a renovation or soil conditions that differ from the geotechnical report.
A change to scope or contract value puts the change management process in motion.
AIA's contingency management guidance confirms that even a Construction Change Directive should be priced as if it were a PCO and recorded in the PCO log. In many workflows, the PCO log is a key mechanism for tracking unresolved change exposure.
What Is a PCO vs. a Change Order
A PCO comes before a Change Order becomes binding. It exists before all required parties sign off.
Until the parties execute a Change Order, the contract sum and contract time remain unchanged. The PCO gives all parties an opportunity to review the requested change before it becomes binding.
Owner and contractor timing can diverge. Contractors focus on when a change impact began, while owners focus on when the formal change order workflow commenced. The PCO can bridge that gap by creating a timestamped record both parties can reference.
PCO vs. PCCO
A Prime Contract Change Order (PCCO) is the executed change order at the owner-to-GC contractual tier. A PCO is the pre-execution tracking record that can feed into the PCCO once all parties reach agreement.
For example, a construction document set from Marion County shows a single PCCO titled "Prime Contract Change Order #002: PCOs #008-#019 & #021" that bundled a dozen individual PCOs into one executed prime contract modification.
Why PCOs Exist as a Project Control Mechanism
Project teams use PCOs to surface cost exposure without requiring a binding modification at each step. Their primary purpose is to establish a chain of events leading to contract modifications. Teams should document schedule consequences when they author the PCO. Without that record, the causal link between that specific change and downstream delay can become much harder to prove retroactively.
The RFI-to-PCO Pipeline
RFIs surface conditions that frequently trigger PCOs. An AI agent can screen RFIs before submission. Datagrid's RFI Validator Agent validates RFIs before submission by identifying trivial requests and flagging cost, schedule, or quality implications.
Large projects often generate hundreds of RFIs, each carrying meaningful administrative and technical review costs. Any RFI that triggers a PCO and goes uncaught can create unrecoverable exposure.
Where Manual PCO Workflows Break Down
Manual PCO workflows break down in recurring ways that Navigant Construction Forum has catalogued across thousands of disputes.
The Waiver Trap
Field personnel encounter changed conditions or verbal owner directives and proceed with work without issuing timely written notice. The consequences can be severe. In Brandt Corp. v. City of New York, the contractor lost a substantial claim because acceptance of final payment barred recovery. In documented cases like that one, the waiver consequence can be a legal bar.
Verbal Authorization Dissolves Scope Boundaries
Owners' representatives and GC superintendents routinely direct work verbally to avoid slowing the schedule. Verbal commitments and handshake deals in the field are a pattern that leaves contractors exposed. That can leave both parties without the protection the written change order clause was designed to provide.
Subcontractor PCO Pass-Through Failures
Contractors routinely pass through subcontractor lump-sum pricing without independent verification. In an auditor review of the Eliot-Hine Middle School modernization project, they found mathematical calculation errors and unsupported costs across PCOs in a project with ~$8.9 million in change order value. Reviewers identified those errors during review.
The Cumulative Cost
Most built world firms never analyze the change order data they collect. A 2023 Deloitte study of 1,275 construction leaders across 12 countries found that only 19% of firms capture and use change order and RFI data for business decisions. The remaining report this data is either not captured (44%) or captured and analyzed but not used (37%).
FMI research found that over 40% of projects studied had spiraling budget costs due to changes, and on some projects, up to 20% of the base contract dollar amount was tied up in unpaid changes or unresolved financial disputes.
Noise in the RFI log makes that problem worse. Filtering trivial or unnecessary RFIs before they enter the workflow keeps project teams focused on the few issues that actually carry PCO exposure.
Shift PCO Detection Upstream with AI Agents
Teams rarely lose control at the executed change order. They lose it earlier, when the triggering condition sits in an RFI or a scope gap nobody routes into a documented path.
Datagrid connects systems and interprets project files to complete real workflows that keep projects moving. That changes detection from reactive to proactive, identifying conflicts and scope gaps before they reach the jobsite. The clearest example is validating RFIs before submission. The RFI Validator Agent flags project impacts while there is still time to route the issue into a documented PCO path.
How It Works
Cross-check incoming RFIs against specs, drawings, and contract language to surface cost, schedule, or scope implications before submission.
Detect conflicts and scope gaps across drawing revisions, addenda, and vendor proposals that would otherwise surface as field-discovered conditions or unpriced work.
Route structured findings to the project team with grounded citations, so the PM can initiate the PCO with contemporaneous evidence already assembled.
Start Catching PCO Triggers Before They Hit the Field
Validating RFIs before submission identifies trivial requests and flags project impacts. The RFI Validator Agent connects to existing project tools, processes project files on the fly, and returns structured results. Your team focuses on the decisions. The agent handles the project file work between them.
