Owner Change Order (OCO)

Definition — what it is

An owner change order is a signed, bilateral amendment to the prime contract between the owner and the general contractor that formally adjusts the contract sum, the contract time, or the defined scope of work. It is the instrument that converts a requested change into a binding contractual reality: once both parties execute it, the adjusted contract sum and completion date become the new baseline against which the project is measured and paid. An owner change order is not a proposal, a directive, or an internal record — it is the executed agreement that supersedes all of them. Its defining characteristic is bilateral signature; a change that only one party has signed is not an owner change order, and work performed against an unsigned document carries the risk that the agreement never actually formed.

Also known as: Change Order, Prime Contract Change Order, Owner-Contractor Change Order, OCO

Why it matters — what it protects

The owner change order is the only document that changes what the contract is worth. Every PCO, COR, and directive is preliminary; the executed OCO is what adjusts the contract sum and the completion date on the record. Until it is signed, the contractor's revenue on that change is contingent, and the completion date the contractor is measured against has not moved — which is why the accumulation of executed OCOs, not requested ones, is the true measure of a project's contract value.

It fixes schedule entitlement permanently. When an OCO adjusts the contract time, that adjustment becomes the new baseline, and when it is silent on time, it typically constitutes an accord that the change carried no schedule impact. Executing an OCO that adds scope without adjusting time is one of the most consequential and irreversible mistakes in change management, because it contractually concedes that the added work fit within the original duration.

It carries release and waiver language that closes the door on the change. Most owner change orders include language stating that the adjusted sum represents full compensation for the change, including all direct, indirect, and impact costs, and that the contractor waives further claims arising from it. Signing an OCO without understanding this language can extinguish cumulative-impact and delay claims the contractor did not intend to release, which is why the fine print matters as much as the dollar figure.

The executed OCO is the anchor for billing and financial reporting. It updates the schedule of values, becomes billable on the next pay application, flows into the work-in-progress schedule and revenue recognition, and adjusts the contract backlog. An OCO that is executed but not propagated into billing and reporting creates a mismatch between what the contract is worth and what the contractor can bill, which surfaces as under-billing and distorted margin.

Lifecycle — how it moves

1. Agreement reached

   The owner and contractor settle scope, price, and time, usually after negotiation of one or more CORs. The OCO documents the agreement they reached, so its terms must match what was actually negotiated, not what was originally requested.

2. Drafting

   The OCO is drafted with the adjusted contract sum, the adjusted contract time, the scope description, and the standard release language. The line items usually reference the underlying CORs so the buildup is traceable.

3. Internal review

   The contractor's project manager and often finance review the release language, the time adjustment, and whether the sum captures impact and indirect costs, not just direct costs. This is the last chance to catch a waiver that gives away more than intended.

4. Bilateral execution

   Both parties sign. Until both signatures are present the OCO is not effective, and a common failure is performing work against an owner-signed-but-not-yet-contractor-signed document or vice versa.

5. Contract sum and time adjustment

   The executed OCO adjusts the contract sum and completion date. These become the new baseline for schedule and payment, superseding the original values for that scope.

6. Propagation to billing and reporting

   The OCO updates the schedule of values, becomes billable on the next pay application, and flows into the WIP schedule, revenue recognition, and backlog. Failure to propagate creates under-billing and reporting drift.

7. Flow-down to subcontracts

   Where the change affects subcontracted work, corresponding subcontract change orders are issued so the sub-tier commitments match the prime change. A prime OCO without matching SCOs leaves the GC exposed on the buy-out.

8. Closeout reconciliation

   At closeout, all executed OCOs are reconciled against the original contract sum to establish the final adjusted contract value, and the OCO record supports final billing and any retainage release.

Anatomy — the data it carries

OCO number

Sequential prime-contract change order number, linked to the CORs it settles, so the buildup from request to executed amendment is traceable.

Scope description

The precise change to the work being agreed. What is written here, not what was discussed, is what the contractor is now obligated to perform.

Adjusted contract sum

The dollar change to the contract, and the resulting new contract total. The figure that updates billing, backlog, and revenue recognition.

Adjusted contract time

The days added to or subtracted from the contract time and the new substantial completion date. Silence here usually waives the time impact.

Referenced CORs

The change order requests the OCO settles, so the negotiated result can be traced back to what was requested and why.

Pricing method

Lump sum, unit price, or time-and-material result. Determines how the change was measured and how any remaining unit-price work will be paid.

Release and waiver language

The statement that the adjusted sum is full compensation for the change, including impact costs, and that further claims on it are waived. The clause that most often gives away more than intended.

Reservation of rights

Any explicit carve-out preserving cumulative-impact or unresolved-time claims. Its absence, combined with broad release language, can extinguish claims the contractor meant to keep.

Owner and contractor signatures and dates

The bilateral execution that makes the OCO effective. One signature is a proposal, not an amendment.

Effective date

When the change takes effect, which may differ from the signature dates and governs when the adjusted sum and time apply.

Cost code allocation

How the change value maps to the budget and SOV, so job cost and billing stay reconciled to the executed amount.

Attachments

The settled CORs, final pricing backup, and any revised drawings or scope exhibits that define the changed work.

Failure modes — how it breaks

Scope added, time waived

The OCO adjusts the contract sum but leaves the contract time unchanged and includes broad release language. The contractor has now contractually agreed that the added scope fit within the original duration, forfeiting the delay and compression claim it might otherwise have had.

Broad release swallows impact claims

The standard 'full and final compensation including all impact costs' language is signed without a reservation of rights, extinguishing a cumulative-impact or acceleration claim the contractor was still building. The individual change looked fairly priced; the waiver quietly closed a much larger door.

Work performed against a one-signed OCO

The owner signs and the contractor proceeds before executing, or the contractor signs and works before the owner does. If the deal never fully forms, the work sits on an unexecuted document and the contractor is negotiating for money already spent.

Executed but never propagated to billing

The OCO is signed but the schedule of values and pay application are never updated. The contractor cannot bill the change, carries it as under-billing, and its WIP schedule and backlog understate the true contract value.

Prime change without matching subcontract change orders

The GC executes an OCO for changed work performed by a sub but never issues the corresponding SCO. The sub performs, bills, or claims on a scope that is not committed on the buy-out, and the GC's cost exceeds what it locked in.

Terms drift from what was negotiated

The OCO is drafted from the original COR rather than the negotiated settlement, so the signed scope, sum, or time does not match what the parties actually agreed. The mismatch surfaces during performance as a dispute about what was really bought.

Metrics — how it is measured

Executed change order value

Total signed OCO value and its share of the contract sum. The true measure of contract growth, distinct from requested changes still open.

Contract sum growth percentage

Executed changes as a percentage of the original contract. High growth signals scope instability or design incompleteness in the base documents.

Time-capture ratio

Share of scope-adding OCOs that also adjusted the contract time. A low ratio means the contractor is systematically executing changes that waive schedule.

Request-to-execution realization

Executed OCO value as a share of the CORs it settled. Measures how much of the ask survived to a signed amendment.

Billing propagation lag

Days from OCO execution to reflection in the SOV and the next pay application. Long lags create under-billing and cash drag.

Subcontract flow-down completeness

Share of prime OCOs with matching executed SCOs for the affected sub scope. Measures whether the GC's buy-out matches its prime commitments.

Reservation-of-rights coverage

Share of executed OCOs where impact or time claims were expressly reserved when appropriate. A control against inadvertently waived claims.

The AI shift — what actually changes

Conversational

The executed change order record becomes interrogable. You ask which OCOs added scope but no time, which contain broad release language without a reservation of rights, and which have not yet propagated to the schedule of values — each answer tied to the signed document, so waived time, swallowed claims, and under-billing all stop hiding in the fine print.

Generative

From a negotiated settlement and the underlying CORs, a model drafts the OCO with the adjusted sum and time, a scope description matching what was actually agreed, appropriate release language, and a proposed reservation of rights where impact or time claims remain open — flagging any place where the standard waiver would give away more than the parties intended, for a human to confirm.

Orchestrated

The OCO stops being a document that dies in a drawer. On execution it updates the schedule of values, becomes billable on the next pay application, flows into the WIP schedule and backlog, and triggers matching subcontract change orders for affected sub scope — so contract value, billing, reporting, and the buy-out all move together.

Autonomous

The routine motion runs inside guardrails: executed OCOs are propagated to the SOV, billing, and reporting; flow-down SCOs are drafted for affected sub scope; and closeout reconciliation runs continuously. Humans always review release and waiver language, decide the time adjustment, and approve any reservation of rights, because those terms cannot be reversed once signed.

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 — Before signing a batch of change orders, you need to know what you might be waiving.

Review the executed and pending owner change orders on this project. Identify every OCO that (a) adds scope but does not adjust the contract time, (b) contains full-and-final release language with no reservation of rights, or (c) is executed but not yet reflected in the schedule of values and pay application. For each, give me the OCO number, scope, sum, time adjustment, the exact release language, and the specific risk it creates. Flag any that could extinguish a delay or cumulative-impact claim we are still building.

What good output looks like: A risk-ranked review of change orders with waived-time, unreserved-release, and unbilled items called out, and the exact release language quoted — the fine print made visible before signature, not after.

Follow-ups:

• Draft reservation-of-rights language for the ones still awaiting our signature.
• Which executed OCOs are we currently unable to bill, and what is the value?
• What is our total contract sum growth as a percentage, and how does the time capture compare?

Generative — A settlement was reached on several CORs and you need the OCO drafted to match what was actually agreed.

Draft an owner change order settling CORs 12, 14, and 15. We negotiated a combined lump sum of the agreed amount and a 6-working-day extension to substantial completion; COR 15 included a cumulative-impact reservation we intend to keep open. Write the OCO with a scope description matching the settled scope, the adjusted contract sum and new contract total, the adjusted contract time and new substantial completion date, release language that covers the direct and indirect costs of these three changes only, and an explicit reservation of rights preserving the cumulative-impact claim. Flag anywhere the standard full-and-final language would over-release relative to what we agreed.

What good output looks like: An OCO whose scope, sum, and time match the negotiated settlement, with release language scoped to these changes and an explicit reservation preserving the open claim — with any over-release flagged for confirmation.

Follow-ups:

• Rewrite the release so it cannot be read to waive our pending acceleration claim.
• Produce the matching subcontract change orders for the sub scope in these CORs.
• Draft the internal note explaining what this OCO does and does not release.

Orchestrated — An OCO was just executed and everything downstream needs to move with it.

Owner change order 18 was executed today for the agreed sum and a 4-day time extension. Propagate it: update the schedule of values with the new line and adjusted contract total, confirm it is billable on our next pay application, reflect it in the WIP schedule and backlog, and generate the matching subcontract change orders for the affected sub scope with the correct flow-down markup. Verify the adjusted contract sum and completion date now match the executed OCO across every system, and return a propagation report tying each update to the executed document. Flag any place the numbers do not reconcile.

What good output looks like: A propagation report showing the SOV, billing, WIP, backlog, and subcontract commitments all updated to the executed OCO, with every update traced to the signed document and any reconciliation gap flagged.

Follow-ups:

• Confirm our next pay application includes this change and nothing unsupported.
• Which subs need their SCO issued before their next billing?
• Does the new completion date create any downstream schedule conflicts?

Autonomous — Standing policy for handling executed change orders without giving away claims.

Operate our owner change order handling continuously under these rules. On execution, propagate every OCO to the schedule of values, the next pay application, the WIP schedule, and backlog, and draft matching subcontract change orders for affected sub scope with the correct flow-down markup. Continuously reconcile the executed change order total against the adjusted contract sum and surface any variance. Before any OCO is cleared for our signature, analyze the release language and the time adjustment and flag any that adds scope without time or that would release an impact, acceleration, or cumulative claim without a reservation of rights. Never approve release or waiver language, never decide the time adjustment, and never authorize signature — route all of those to me with your analysis. Give me an exception queue and the reconciliation status, not the whole log.

What good output looks like: A running process where propagation, flow-down, and reconciliation happen automatically, but release language, time adjustments, and signature clearance always require a human — because those terms cannot be undone.

Follow-ups:

• Show what you propagated and what you flagged for release-language risk this week.
• Which OCOs are awaiting my signature clearance and why?
• What is our contract sum growth and time-capture ratio right now?

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

Maturity — locate yourself honestly

0. Level 0 — Paper amendments

   Change orders are signed and filed with no systematic link to billing or reporting. Contract value, the SOV, and the WIP schedule routinely diverge.

1. Level 1 — Logged

   An OCO register tracks numbers, sums, and time adjustments. Propagation to billing and flow-down to subcontracts are manual and often lag.

2. Level 2 — Linked

   OCOs trace to the CORs they settle, adjust the contract sum and time, and update the SOV. Flow-down SCOs and reconciliation are tracked.

3. Level 3 — Assisted

   OCOs are drafted from negotiated settlements with release language and reservations flagged, propagation to billing and reporting is generated, and flow-down SCOs are drafted for review.

4. Level 4 — Operated

   Propagation, flow-down, and reconciliation run unattended inside guardrails, while humans own release and waiver language, the time adjustment, and signature clearance.

Common questions

What makes an owner change order binding?

Bilateral execution — both the owner and the contractor must sign. A document signed by only one party is a proposal or a directive, not an executed change order, and performing work against it carries the risk that the agreement never fully formed. The effective date and the signatures are what convert the negotiated terms into a binding amendment to the contract sum and time.

Why is the release language on a change order so dangerous?

Because standard change order language often states that the adjusted sum is full and final compensation for the change, including all direct, indirect, and impact costs, and waives further claims arising from it. Signing that without a reservation of rights can extinguish delay, acceleration, or cumulative-impact claims the contractor is still building, even though the individual change looked fairly priced. The waiver reaches further than the dollar figure suggests.

What happens if we add scope but the change order does not adjust time?

You have generally agreed, in writing, that the added scope fit within the original contract time. That concession is very hard to reverse, and it forfeits the delay and compression claim the added work might have justified. If a change genuinely has no schedule impact, say so explicitly; if it might, reserve the time question in the change order rather than leaving it silent.

Why does contract sum growth get watched so closely?

Because executed change orders as a percentage of the original contract are a direct read on the completeness of the base documents and the stability of the scope. Owners and sureties track it as a risk signal, and unusually high growth points to design incompleteness, scope creep, or an owner making decisions late. It is one of the cleanest quantitative measures of how a project is actually running relative to how it was bid.