Potential Change Orders (PCOs): Flag Change Before It Becomes a Dispute

November 17, 2026

6

min read

A potential change order can be raised on time and still be difficult to substantiate.

  • The crew completed the additional work, but the labor hours weren’t recorded separately
  • The instruction is buried in a group chat
  • The photos show the finished work, but not the conditions that made it necessary

A potential change order (PCO) records a change that may affect a project’s cost or schedule before it becomes an approved change order. But the evidence supporting its price needs to exist before anyone starts preparing it.

That’s the gap many PCO processes struggle to close: they track potential changes once they’re identified, but the records needed to support them start much earlier, on site.

What Happens When a PCO Is Raised Late?

A late PCO isn’t necessarily a problem if the supporting evidence was recorded when the work happened and contractual notice requirements were met. But when those records are missing, the project team has to piece together what changed, who authorized the work, and what it cost.

  • Additional costs become harder to support
    Material costs can often be verified through invoices and delivery records. However, additional costs like labor, equipment downtime, and schedule impacts are harder to account for when they weren’t tracked as the work happened.

    For example, an owner or general contractor reviewing a PCO may ask how the additional labor hours were calculated, whether they were tracked separately, and whether the work was outside the original scope.

    Without daily reports, time records, or other supporting documentation, those questions become harder to answer. Disagreements over the additional costs can then turn into disputes over what the contractor is entitled to recover.
    ‍
  • Notice Deadlines Keep Running
    Contractual notice deadlines can pass while teams are still gathering documentation. For example, AIA A201-2017 §3.7.4 requires notice of certain concealed or unknown site conditions to the owner and architect before the conditions are disturbed and no later than 14 days after they’re first observed.

    That deadline applies regardless of when the PCO is prepared. Submitting a PCO doesn’t necessarily count as formal notice, and missing the contract’s notice requirements can put a contractor’s right to additional payment or time at risk.

To see whether this is happening on your projects, review your last five PCOs. Compare when each change happened, when the supporting records were created, and when the PCO was submitted.

If the records were created weeks after the work, your team may be relying on estimates and recollections rather than documentation captured at the time.

Why Potential Changes Get Missed

You probably already have a process for surfacing potential changes. It usually looks like one or more of these:

  • A standing instruction to the site team to flag anything that looks like a change.
  • A shared spreadsheet log where changes are meant to be recorded.
  • A weekly catch-up where changes are supposed to come up.

Each one depends on someone recognizing the cost implications of an issue while they're focused on resolving it.

When a site engineer finds a beam where the drawings show a clear route, the question is how to keep the crew working. The obstruction gets photographed, a new route is agreed, and work moves on. Unless someone identifies the extra work as a potential change, it may never reach the PCO log.

Nobody missed a step through carelessness. The process asks for a judgment call at the worst possible moment.

What evidence should a PCO include?

The supporting documentation depends on the change and the contract requirements, but useful records typically include:

  • Change details: What changed, when and where it happened, and who requested or directed the work.
  • Labor: Additional hours worked, crew details, and daily time records.
  • Materials and equipment: Quantities, invoices, equipment usage, and any downtime attributable to the change.
  • Photos and communications: Dated photos showing relevant site conditions, along with instructions, correspondence, and related issue reports.
  • Cost and schedule impacts: An explanation of the additional costs or time being requested, supported by the relevant records.

According to the American Institute of Architects (AIA), construction change proposals should document proposed adjustments to cost and time, with supporting information such as labor, materials, equipment costs, and schedule analysis.

Records captured when the work happens can make it easier to explain and substantiate a PCO than documentation reconstructed weeks later.

How to Capture Evidence Before a PCO Is Raised

Site teams use Shape to get answers, share photos, and agree what happens next in location-based chats. Those conversations help build the evidence behind potential changes, while Shape AI helps the commercial team turn the supporting records into a change narrative.

Here’s how that works when a crew encounters a beam obstructing the planned route.

  1. Capture the details as work happens

The site engineer raises the obstruction as an issue in Shape, attaching a photo and recording where it was found. The team discusses the alternative route in the same conversation and agrees on the next steps.

The issue, photos, and updates are kept together as a record of what happened and how the team responded. The crew can focus on resolving the obstruction without having to decide whether the additional work qualifies as a PCO.

  1. Identify potential changes from site records

Shape’s Change Tracker automatically surfaces issues that may cause delays, along with recorded downtime and deviations from planned work.

The obstruction can therefore appear for review as a potential change, even if nobody on site initially identified it as one. The project manager reviews the alert, considers whether the rerouting work has cost or schedule implications, and decides whether to investigate it further.

  1. Build the supporting documentation

If the obstruction is identified as a potential change, the project manager can bring together the relevant records in Change Tracker, including the original issue, photos, instructions, and any recorded downtime or additional work.

Shape AI uses the linked evidence and documented impacts to draft a change narrative explaining what happened. The commercial team can review and edit the draft before exporting it with the supporting records.

That report can then support the PCO prepared and submitted through the project’s existing change order process.

Shape doesn’t replace platforms like Procore or Autodesk for managing formal change orders. It helps identify potential changes and organize the supporting records before a PCO is prepared.

For a closer look, see how Shape helps teams manage construction changes.

Build The Record Before You Need the PCO

A potential change order doesn’t have to be prepared the day the work happens, but the evidence supporting it shouldn’t have to be reconstructed weeks later.

Photos, instructions, labor hours, and records of delays are easier to capture while the details are still fresh. When those records are already in place, project teams have a stronger basis for assessing the change, supporting its costs, and preparing the PCO.

Shape helps teams capture that information during everyday site activity and identify potential changes before the supporting details get lost. If you want to see how this could work on your site, ⁠talk to us about your project.

Frequently Asked Questions

Does documenting potential changes mean more paperwork for site teams?
Should you raise a PCO if you're not sure the change is compensable?
Who should raise the PCO, the field or the office?