Potential Change Order (PCO)

Definition — what it is

A potential change order is a priced proposal, prepared by the contractor, that quantifies the cost and schedule impact of a validated change event and requests the owner's authorization. It is the stage at which a captured deviation becomes a specific dollar figure and a specific number of days, supported by a cost breakdown and a basis of estimate. A PCO is not yet a contract amendment and does not authorize the work or guarantee payment — it is an offer awaiting acceptance, and until it is executed as a change order the contractor performs the work at its own risk unless separately directed. The PCO is the pivot point of change management: it is where the loose narrative of a change event is converted into a defensible, negotiable number.

Also known as: Pending Change Order, Proposed Change Order, Change Order Proposal, PCO

Why it matters — what it protects

The PCO is where money is either captured or lost. A change event that is never priced into a PCO becomes an untracked cost overrun; a PCO priced too low leaves margin on the table permanently, and one priced without a defensible basis of estimate invites the owner to negotiate it down to nothing. The rigor of the cost breakdown directly determines how much of the legitimate cost the contractor actually recovers.

It controls schedule entitlement. Cost is only half of a change; the time impact is the half contractors most often forfeit. A PCO that quantifies only dollars and stays silent on schedule effectively waives the time extension, and a contractor who accepts added scope without a corresponding time extension has agreed to absorb the schedule compression that scope creates.

It is the contractor's negotiating instrument. Owners scrutinize markup, labor rates, productivity assumptions, and equipment costs line by line, and the PCO is the document that must survive that scrutiny. A well-structured PCO with clear direct costs, defined markup consistent with the contract, and a transparent basis of estimate closes faster and at a higher value than a lump-sum number with no supporting detail.

The aggregate of open PCOs is a real financial exposure that many contractors underweight. Work is frequently performed against PCOs the owner has not yet executed, which means the contractor is financing unauthorized work and carrying it as an at-risk receivable. The open PCO log, aged and totaled, is one of the truest measures of how much of a project's revenue is still contingent.

Lifecycle — how it moves

1. Trigger from change event

   A change event characterized as compensable is advanced to pricing. The PCO inherits the event's cause characterization, source records, and notice status so entitlement is carried forward, not re-argued.

2. Scope definition

   The exact added, deleted, or modified work is defined precisely. Ambiguous scope is the primary reason a PCO gets bounced back or negotiated to a fraction of its value, because the owner disputes what is actually included.

3. Cost estimating

   Direct costs are built up — labor hours and rates, material quantities and pricing, equipment, and subcontractor quotes — then marked up per the contract's allowed overhead and profit percentages. Self-performed work and subcontracted work often carry different markup ceilings.

4. Schedule impact analysis

   The time effect is assessed against the current schedule: does the change extend the critical path, and by how many days. A time impact analysis or fragnet may be attached for significant durations.

5. Internal review

   The project manager and often the estimator or a change manager review the pricing, the basis of estimate, and the markup for consistency with the contract before it is issued. Errors caught here are cheap; errors the owner finds are expensive to credibility.

6. Submission to owner

   The PCO is transmitted, logged, and enters the owner's review. The contract usually specifies a response window; the reality is that PCOs sit, which is why aging must be tracked from submission.

7. Negotiation

   The owner or their representative reviews line by line, challenges productivity and markup, and negotiates. Multiple rounds are normal. The contractor's basis of estimate is what holds the value here.

8. Disposition

   The PCO is accepted and converted to an executed change order request and ultimately an owner change order, rejected, or directed to proceed under a construction change directive when the parties cannot agree on price but the work must go forward.

Anatomy — the data it carries

PCO number

Unique identifier linked back to the originating change event and forward to the resulting change order, preserving the full chain.

Scope description

A precise statement of the added, deleted, or modified work. Precision here is what survives owner negotiation; vagueness is what erodes the value.

Cause reference

The RFI, ASI, differing condition, or directive that caused the change, carried forward from the change event to support entitlement.

Direct labor

Crew composition, hours, and rates, ideally with a productivity basis. The most heavily challenged line, so it must be defensible independent of the total.

Direct material

Quantities and unit pricing with quote support. Owners test material pricing against market, so backup matters.

Equipment

Owned or rented equipment cost, at rates consistent with the contract or a recognized rate schedule. Often disputed when idle or standby time is included.

Subcontractor costs

Sub-tier quotes for the change, which typically flow up as their own subcontract change orders and carry a different allowable markup than self-performed work.

Overhead and profit markup

Applied per the contract's stated percentages, which frequently cap markup on subcontracted work below self-performed work. Getting this wrong is the fastest way to have the whole PCO questioned.

Basis of estimate

The assumptions, quantities, productivity, and quote sources behind the number. The single most important attachment for defending value in negotiation.

Schedule impact / time requested

Days of extension sought and the analysis supporting them. Silence here is treated as a waiver of the time extension.

Pricing method

Lump sum, unit price, or time-and-material with a not-to-exceed. Determines how the work will be measured and paid, and how risk is allocated.

Status and aging

Submitted, under review, in negotiation, executed, rejected, or converted to a CCD — plus days outstanding, the field that quantifies at-risk work.

Failure modes — how it breaks

Priced without a basis of estimate

A lump-sum number is submitted with no labor hours, no productivity assumption, and no quote backup. The owner has nothing to accept and everything to challenge, so the PCO is negotiated down to whatever the owner is willing to concede, which is always less than the cost.

Cost quantified, time ignored

The PCO captures the dollars but says nothing about schedule. The owner executes the cost, the contractor performs the added work inside the original duration, and the resulting compression shows up later as a delay the contractor now cannot recover because it accepted the change silent on time.

Wrong markup on subcontracted work

The contractor applies self-perform markup to a subcontractor's change cost when the contract caps sub markup lower. The owner catches it, the credibility of the entire PCO drops, and every other line now gets extra scrutiny.

Work performed before execution

The crew does the changed work because the schedule demands it, while the PCO sits unexecuted. If the owner later disputes scope or price, the leverage is gone — the work is already in place and the contractor is negotiating for money it has already spent.

Scope creep inside one PCO

Several loosely related changes are bundled into a single PCO to reduce paperwork, but the owner rejects one line and holds the entire PCO hostage. Bundling that mixes strong and weak entitlement lets the weak lines drag down the strong ones.

Open PCOs never aged

Submitted PCOs sit in the owner's court for months with nobody tracking the total. The contractor discovers at project's end that it has performed hundreds of thousands of dollars of unauthorized, unexecuted change work it is now fighting to collect.

Metrics — how it is measured

Open PCO value and aging

Total dollars submitted but not executed, bucketed by days outstanding. The measure of how much revenue is still at risk and how long the owner is sitting on it.

Execution rate

Share of submitted PCO value that is ultimately executed as change orders. Low rates point to weak pricing, weak entitlement, or an owner disputing legitimate changes.

Realization rate

Executed value divided by submitted value. Reveals how much of the asked-for amount survives negotiation, and thus the quality of the basis of estimate.

Cycle time to execution

Days from submission to executed change order. Long cycles mean the contractor is financing unauthorized work for extended periods.

Schedule capture rate

Share of cost-bearing PCOs that also requested and obtained time. A low rate means the contractor is systematically forfeiting schedule entitlement.

Rejection / rework rate

Share of PCOs returned for repricing or rejected outright. Measures the quality of scope definition and estimating discipline.

Unauthorized work exposure

Value of work performed against unexecuted PCOs. The number that tells a project executive how much at-risk work is actually in the ground.

The AI shift — what actually changes

Conversational

The open PCO log becomes interrogable. You ask which PCOs have been sitting past the contractual review window, which carry cost but requested no time, and what the total unauthorized-work exposure is right now — with each answer tied to the underlying records, so at-risk revenue stops being a surprise at closeout.

Generative

From a validated change event and the associated quotes and crew data, a model drafts the PCO cost breakdown — labor hours and rates, material with quantities, equipment, subcontractor costs with the correct markup ceiling per the contract, and a written basis of estimate — plus a proposed time impact, which the estimator refines rather than builds from zero.

Orchestrated

The PCO stops being a standalone spreadsheet. Markup is validated against the contract's stated percentages, subcontractor change costs are pulled from their own SCOs, the schedule impact is checked against the live CPM schedule, the value is reflected against the budget and cost codes, and on execution the PCO flows into the owner change order and the schedule of values automatically.

Autonomous

The routine motion runs inside guardrails: PCOs are drafted from validated change events, markup and cost-code coding are checked against the contract, aging is monitored against the review window with escalations, and unauthorized-work exposure is tracked continuously. Humans always set pricing judgment, approve the basis of estimate, and decide whether to proceed on unexecuted work.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — You need to know how much at-risk change work you are carrying before a project review.

Analyze our open PCO log. Give me total submitted value not yet executed, broken out by days outstanding in 0-30, 31-60, 61-90, and 90+ buckets. Then identify every PCO that (a) carries cost but requested no time extension, (b) has related work already performed in the field, or (c) is past the 21-day contractual review window. For each flagged PCO, give me the number, scope, submitted value, days outstanding, and the specific risk. Tell me our total unauthorized-work exposure and rank the flagged items by dollars at risk.

What good output looks like: An aged exposure summary with the at-risk work quantified and the schedule-waiver risks called out — a clear picture of contingent revenue, not just a list of open items.

Follow-ups:

• Draft a status-request letter to the owner for everything past the review window.
• Which of the no-time PCOs still let us assert a time extension, and how?
• Which PCOs should we stop performing against until they are executed?

Generative — A change event is validated and you need a defensible PCO built fast.

Build a PCO from this validated change event. Scope: add 2,400 linear feet of heavier-gauge metal stud framing at level 4 demising walls per RFI 88. Inputs: our framing crew runs 3 carpenters and 1 foreman, historical productivity is roughly 90 linear feet per crew-day for this assembly, fully burdened carpenter rate is applied per our contract labor schedule, material quote attached at the per-linear-foot delta between gauges. Our contract allows 10 percent overhead and 5 percent profit on self-performed work and caps subcontractor markup at 5 percent. Produce the direct labor, material, and equipment breakdown, apply the correct markup, write a basis of estimate documenting every assumption, and propose a schedule impact given framing is on the critical path. Mark the pricing method as lump sum.

What good output looks like: A complete, line-itemed PCO with defensible labor hours, correct markup, a written basis of estimate, and a supported time request — ready to submit, not a lump sum with no backup.

Follow-ups:

• Show the same PCO priced as time-and-material with a not-to-exceed instead.
• Rewrite the basis of estimate to preempt the owner's likely productivity challenge.
• What time extension does this justify, and what analysis supports it?

Orchestrated — A subcontractor's change came in and you need it rolled into the owner-facing PCO correctly.

Our drywall sub submitted a subcontract change order for the level-4 framing change. Roll it into our owner-facing PCO: pull the sub's direct cost, apply the contract-allowed 5 percent markup on subcontracted work (not our self-perform markup), verify the sub's scope matches the change event scope with no gaps or overlaps against our self-performed portion, check the sub's requested time against our current CPM schedule, and reflect the combined value against the correct cost codes in the budget. Return the assembled PCO with each number traced to its source, and flag any mismatch between the sub's scope and ours.

What good output looks like: An assembled owner PCO with the subcontractor cost correctly marked up, scope reconciled against self-performed work, schedule checked, and every figure traceable — with scope mismatches flagged before the owner finds them.

Follow-ups:

• Is the sub's productivity assumption consistent with what we told the owner?
• Draft the transmittal to the owner with the full backup package listed.
• If the owner rejects the sub's markup, what is our fallback position?

Autonomous — Standing policy for keeping the PCO pipeline honest and current.

Manage our PCO pipeline continuously under these rules. Draft PCOs from validated change events using the contract's labor schedule and markup ceilings, flag any PCO that carries cost but no time request, and validate every markup against the contract's stated percentages. While open: age PCOs against the 21-day review window, escalate items past the window to the project manager and items past 60 days to the project executive, and maintain a running total of unauthorized-work exposure. Never set final pricing judgment, never approve a basis of estimate, and never authorize performing work against an unexecuted PCO — route all of those to me with your analysis. Give me a weekly exception queue and the total at-risk value, not the entire log.

What good output looks like: A managed pipeline with aging and exposure tracked automatically, where drafting and validation are assisted but pricing judgment, basis of estimate, and any decision to perform unauthorized work stay with a human.

Follow-ups:

• Show everything you drafted and escalated this week and the at-risk total.
• Which of your markup validations did I override, and why?
• Which PCOs have crossed into work-being-performed-without-authorization?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Reactive

   Changes are priced only when the owner asks, often after the work is done. There is no PCO log, no aging, and no picture of unauthorized-work exposure.

1. Level 1 — Logged

   A PCO register tracks numbers, values, and statuses. Pricing is manual and inconsistent, and schedule impact is frequently omitted.

2. Level 2 — Linked

   PCOs trace to change events and forward to change orders, markup is checked against the contract, and schedule impact is analyzed against the CPM schedule. Aging and exposure are visible.

3. Level 3 — Assisted

   Cost breakdowns and bases of estimate are drafted from change events and quotes, markup and coding are validated automatically, and no-time and overdue PCOs are surfaced for action.

4. Level 4 — Operated

   Drafting, validation, aging, and exposure tracking run unattended inside guardrails, while humans own pricing judgment, the basis of estimate, and any decision to perform unexecuted work.

Common questions

What is the difference between a PCO and a change order?

A PCO is a priced proposal awaiting the owner's acceptance; a change order is the executed, bilateral amendment that actually changes the contract price and time. Until the PCO is executed, it authorizes nothing. Performing work against an open PCO means financing that work yourself and carrying it as an at-risk receivable until the owner signs.

Should we perform work while a PCO is still open?

Only with eyes open to the risk. If the schedule forces the work forward, the safer path is to obtain a written directive to proceed — often a construction change directive — which authorizes the work even while price is still being negotiated. Proceeding on an unexecuted, undirected PCO means the owner can later dispute both scope and price after you have already spent the money.

Why does markup on subcontracted work get capped lower?

Because the general contractor's role on subcontracted change work is largely administrative rather than performing the labor itself, most contracts allow a lower overhead and profit percentage on subcontracted amounts than on self-performed work. Applying the higher self-perform markup to a subcontractor's cost is a common error that undermines the credibility of the whole PCO once the owner catches it.

How do we keep from waiving time on a change?

Address schedule explicitly on every cost-bearing PCO, even if the answer is that there is no time impact. Silence is routinely interpreted as agreement that the change had no schedule effect, so a contractor that adds scope without a documented time position has effectively agreed to absorb the resulting compression. Reserve the time extension in writing and support it with a schedule analysis when the duration is material.