Subcontract Change Order (SCO)

Definition — what it is

A subcontract change order is a signed, bilateral amendment between a general contractor and a subcontractor that adjusts the subcontract sum, time, or scope of work. It is the downstream counterpart to the owner change order: where the OCO changes what the owner owes the GC, the SCO changes what the GC owes the sub, and keeping the two in alignment is what protects the GC's margin on changed work. An SCO is not a directive to the sub, not the sub's request for more money, and not the GC's internal estimate — it is the executed commitment that changes the subcontract. Its central discipline is matching: an SCO issued without a corresponding owner change order exposes the GC to unrecovered cost, and an owner change order without a matching SCO exposes the GC to a sub performing uncommitted scope.

Also known as: Sub Change Order, Subcontractor Change Order, Trade Change Order, SCO

Why it matters — what it protects

The SCO is where the general contractor's margin on changed work is protected or lost. When an owner change order adds scope performed by a subcontractor, the GC must issue a matching SCO at a price that preserves the allowed markup between what the owner pays and what the sub is paid. A prime change executed without a corresponding SCO, or an SCO priced without reference to the owner change, is how a GC ends up paying a sub more than it collected from the owner on the same scope.

It controls flow-down of terms and risk. The SCO carries down the same scope, schedule, and often the same release language that the GC agreed to with the owner, keeping the sub's obligations aligned with the prime. When flow-down breaks — the sub's SCO grants time the owner never granted, or omits a release the owner required — the GC absorbs the gap between its upstream commitment and its downstream one.

It governs the sub's right to bill and to claim. A subcontractor cannot properly bill changed work without an executed SCO, and disciplined GCs use that fact to prevent unauthorized sub work from becoming an unavoidable cost. Conversely, subs perform directed changes on the promise of a forthcoming SCO that never arrives, and the resulting backlog of unissued SCOs is a frequent source of sub-tier disputes, mechanics liens, and eroded relationships.

The SCO record is essential to accurate committed cost and forecasting. Executed SCOs update the subcontract commitment, which drives the job cost report, the cost-to-complete, and the WIP schedule. If changed sub scope is being performed but not committed through SCOs, the GC's committed cost understates reality, the cost-to-complete is wrong, and the project reports a margin it does not actually have.

Lifecycle — how it moves

1. Change identified for sub scope

   A change event or owner change order affects work a subcontractor performs. The GC determines the sub's portion of the change and whether it is compensable up to the owner, self-inflicted, or backchargeable.

2. Sub pricing solicited

   The GC requests the sub's price and time for the change, ideally before committing a number to the owner, so the owner-facing PCO reflects real sub cost rather than a guess.

3. Reconciliation against the prime

   The sub's price and time are checked against the owner change order or PCO for the same scope. Gaps or overlaps between the sub's scope and any self-performed portion are resolved here, before the SCO is issued.

4. SCO drafting

   The SCO is drafted with the adjusted subcontract sum, time, scope, and the flow-down release language mirroring the prime. The markup between the owner-collected amount and the sub-paid amount is confirmed to be within the allowed range.

5. Bilateral execution

   The GC and sub sign. Until executed, the sub is performing changed work on a promise, which is both a sub-tier risk and a common source of disputes when the SCO stalls.

6. Commitment and cost update

   The executed SCO updates the subcontract commitment, flowing into committed cost, the job cost report, cost-to-complete, and the WIP schedule so forecasting reflects the changed scope.

7. Billing enablement

   The SCO enables the sub to bill the changed work on its next subcontractor invoice, and the GC to pass that cost through against the corresponding owner change on its pay application.

8. Closeout reconciliation

   At closeout, executed SCOs are reconciled against the owner change orders and the sub's final billing, so no changed sub scope is left uncommitted and the sub's lien waiver covers the full adjusted subcontract value.

Anatomy — the data it carries

SCO number

Sequential subcontract change number, linked to the sub and to the owner change order or PCO it corresponds to, so the up-and-down chain is traceable.

Subcontractor and subcontract reference

Which sub and which subcontract is being amended. The change attaches to the specific buy-out commitment, not the project at large.

Scope description

The precise change to the sub's work. Must reconcile with the owner change scope and with any GC self-performed portion to avoid gaps or double-payment.

Adjusted subcontract sum

The dollar change to the subcontract and the new subcontract total. Drives committed cost and must sit below the owner-collected amount by the allowed markup.

Adjusted subcontract time

Days added to or subtracted from the sub's schedule. Flowing down more time than the owner granted leaves the GC absorbing the difference.

Corresponding owner change reference

The OCO or PCO the SCO matches, so the GC can prove the sub cost is recoverable and priced within markup.

Pricing method

Lump sum, unit price, or time-and-material against the sub. Should mirror how the change is priced up to the owner to avoid a risk mismatch.

Flow-down release language

The release the sub grants for this change, mirroring what the GC gave the owner. A missing or narrower release leaves the GC exposed between its two commitments.

GC and subcontractor signatures and dates

The bilateral execution that makes the SCO effective and enables the sub to bill. One signature is a directive, not an amendment.

Cost code allocation

How the sub change maps to committed cost and the budget, keeping the job cost report reconciled to the executed subcontract value.

Backcharge or offset flags

Whether the SCO includes a deduct, backcharge, or credit against the sub. Bundling deducts and adds in one SCO must be done transparently to avoid dispute.

Attachments

The sub's pricing, the corresponding owner change, and any revised scope exhibits defining the changed work.

Failure modes — how it breaks

Owner change with no matching SCO

The GC executes an OCO for scope the sub performs but never issues the SCO. The sub performs and eventually bills or liens for the work, and the GC discovers it committed nothing on the buy-out for cost it is now obligated to pay.

Markup eroded between prime and sub

The SCO is priced without checking it against the owner change, so the sub is paid an amount that leaves the GC with less than its allowed markup, or even a loss, on the changed scope. Margin on the change is gone before the work starts.

More time flowed down than granted

The SCO grants the sub a time extension the owner never granted the GC. The GC now owes the sub schedule relief it cannot recover upstream, absorbing the compression itself.

Sub performs on a promise, SCO never issued

The GC verbally directs the sub to proceed with a forthcoming SCO, then never issues it. The sub performs uncommitted work, tension builds, and the dispute often surfaces as a lien or a stalled sub relationship at exactly the wrong time.

Scope gap or overlap with self-performed work

The SCO scope does not cleanly reconcile with the GC's self-performed portion of the same change, leaving a gap nobody is committed to build or an overlap the GC pays for twice.

Committed cost not updated

The SCO is executed but the subcontract commitment is never updated in the cost system. Committed cost understates reality, the cost-to-complete is wrong, and the job reports a margin it does not have.

Metrics — how it is measured

Prime-to-sub match rate

Share of owner change orders affecting sub scope that have a corresponding executed SCO. The core control against uncommitted sub cost.

Markup preservation

Actual markup retained between owner-collected and sub-paid amounts on changed scope, versus the contract-allowed markup. Measures whether margin survives the flow-down.

Time flow-down alignment

Difference between time granted to the sub and time granted by the owner on the same change. Should be zero or favorable to the GC.

Unissued SCO backlog

Count and value of directed sub changes performed without an executed SCO. Quantifies sub-tier dispute and lien exposure.

Commitment update lag

Days from SCO execution to reflection in committed cost and the job cost report. Long lags distort cost-to-complete.

Sub billing enablement lag

Days from directing changed work to issuing the SCO that lets the sub bill. Long lags strain sub relationships and cash.

Closeout reconciliation completeness

Share of executed SCOs reconciled to owner changes and to the sub's final billing and lien waiver at closeout.

The AI shift — what actually changes

Conversational

The subcontract change record becomes interrogable. You ask which owner changes affecting sub scope have no matching SCO, where the markup between prime and sub has eroded below the allowed range, and which subs are performing directed work with no executed SCO — each answer tied to the OCO and subcontract records, so uncommitted cost and margin leakage stop hiding.

Generative

From an owner change order and the sub's pricing, a model drafts the matching SCO with the adjusted sum and time, scope reconciled against the corresponding prime change and any self-performed portion, flow-down release language mirroring the prime, and a check that the markup and the time granted stay within what the owner allowed — for the GC to confirm.

Orchestrated

The SCO stops being a disconnected form. It is matched to its owner change, the markup and time are validated against the prime, on execution the subcontract commitment and job cost update, the sub's billing is enabled, and the cost flows into the cost-to-complete and WIP schedule — so prime, sub, cost, and forecast all stay aligned.

Autonomous

The routine motion runs inside guardrails: owner changes affecting sub scope trigger draft matching SCOs, markup and time flow-down are validated against the prime, unissued-SCO backlog is tracked, and executed SCOs update committed cost. Humans always approve the sub price, the flow-down terms, and any backcharge or offset bundled into the change.

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 suspect you are paying subs for changes you never committed and want to size the exposure.

Cross-check our executed owner change orders against our subcontract change orders. Identify every owner change that affects subcontracted scope but has no matching executed SCO, and every case where the sub is being paid an amount that leaves us below our contract-allowed markup on the changed scope. Also flag any SCO that grants the sub more time than the owner granted us on the same change. For each, give me the sub, the OCO reference, the scope, the dollar and time exposure, and whether the sub is already performing. Rank by dollars at risk.

What good output looks like: A ranked exposure summary showing unmatched owner changes, eroded markup, and over-granted time — the gap between what we collect and what we owe subs, quantified rather than assumed.

Follow-ups:

• Draft the missing SCOs at prices that preserve our allowed markup.
• Which subs are performing directed changes with no executed SCO right now?
• What is our total uncommitted sub-change exposure?

Generative — An owner change was executed for sub-performed work and you need the matching SCO drafted correctly.

Draft a subcontract change order to match owner change order 18, which added heavier-gauge framing at level 4 performed by our drywall sub. The owner granted us a 4-day extension and paid the agreed sum. Our subcontract allows us to retain 5 percent markup on sub changes. Using the sub's submitted price, draft the SCO with the adjusted subcontract sum and new subcontract total, confirm the markup we retain between the owner-collected amount and the sub-paid amount meets our allowed 5 percent, grant the sub no more than the 4 days the owner granted us, reconcile the sub scope against our self-performed portion so there is no gap or overlap, and include flow-down release language mirroring what we gave the owner.

What good output looks like: A matching SCO with the markup preserved, time flow-down capped at what the owner granted, scope reconciled against self-performed work, and flow-down release language mirroring the prime — ready to execute.

Follow-ups:

• Show me the exact markup we retain and flag if it falls short.
• Rewrite the release so the sub's waiver matches ours to the owner.
• If the sub asks for more time than the owner granted, what do I offer?

Orchestrated — An SCO was executed and committed cost and forecasting need to move with it.

Subcontract change order 22 with our mechanical sub was executed today. Propagate it: update the subcontract commitment and committed cost, reflect it in the job cost report and the cost-to-complete, enable the sub to bill the change on its next invoice, and confirm the corresponding owner change is billable to the owner on our next pay application so the cost passes through. Verify the markup we retain between the owner change and this SCO, and confirm nothing about this change leaves us paying more than we collect. Return a propagation report tying each update to the executed SCO and the matching owner change, and flag any reconciliation gap.

What good output looks like: A propagation report showing committed cost, the job cost report, cost-to-complete, and billing all updated to the executed SCO, with the prime-to-sub markup verified and any gap flagged.

Follow-ups:

• Does this change our forecasted margin on this cost code, and by how much?
• Confirm the sub cannot bill more than the executed SCO amount.
• Which upstream owner change must be billed before this cost hits us?

Autonomous — Standing policy for keeping the sub buy-out matched to the prime on every change.

Manage our subcontract change orders continuously under these rules. Whenever an owner change order affects subcontracted scope, draft a matching SCO from the sub's pricing, verify the markup we retain meets the contract-allowed percentage, cap the time flow-down at what the owner granted, and reconcile the sub scope against any self-performed portion. Track the backlog of directed sub changes performed without an executed SCO and escalate any that are being billed or lien-noticed. On execution, update the subcontract commitment, the job cost report, and cost-to-complete. Never approve the sub price, never finalize flow-down terms, and never bundle a backcharge or deduct into an SCO without my approval. Give me an exception queue and the uncommitted-exposure total, not the whole log.

What good output looks like: A managed sub-change process where matching, markup checks, time flow-down, and commitment updates run automatically, while sub pricing, flow-down terms, and backcharges stay with a human.

Follow-ups:

• Show what you drafted, the unissued-SCO backlog, and what you escalated this week.
• Which draft SCOs fall short of our allowed markup and need my decision?
• What is our total uncommitted sub-change exposure right now?

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

Maturity — locate yourself honestly

0. Level 0 — Handshake changes

   Subs are told to proceed verbally and SCOs are issued late or never. Committed cost, prime changes, and sub billing routinely fall out of alignment.

1. Level 1 — Logged

   An SCO register tracks numbers, sums, and time. Matching to owner changes and markup checks are manual and inconsistent.

2. Level 2 — Linked

   SCOs are matched to owner changes, markup and time flow-down are checked against the prime, and executed SCOs update committed cost and the job cost report.

3. Level 3 — Assisted

   Matching SCOs are drafted from owner changes and sub pricing, markup and time are validated against the prime, and unissued-SCO backlog and scope gaps are surfaced.

4. Level 4 — Operated

   Matching, validation, backlog tracking, and commitment updates run unattended inside guardrails, while humans own sub pricing, flow-down terms, and any bundled backcharge.

Common questions

Why must every subcontract change order match an owner change order?

Because the general contractor's margin on changed work lives in the gap between what the owner pays and what the sub is paid. If the sub is committed through an SCO but the owner never executed a matching change, the GC eats the cost; if the owner executes a change for sub work but no SCO is issued, the sub performs uncommitted scope the GC still owes. Keeping the two matched, at prices that preserve the allowed markup, is the entire discipline.

Can a subcontractor bill changed work without an executed SCO?

It should not be able to. Requiring an executed SCO before changed work is billable is the GC's main control against unauthorized sub cost becoming unavoidable. In practice subs often perform directed changes on the promise of a forthcoming SCO, which is why the backlog of unissued SCOs is such a common source of disputes and liens, and why issuing the SCO promptly after directing the work matters.

What happens if we grant the sub more time than the owner granted us?

The general contractor absorbs the difference. The GC has committed to a schedule with the owner, and granting a sub more relief than the owner allowed leaves the GC owing schedule downstream that it cannot recover upstream. Time flow-down should be capped at what the owner granted on the same change unless the GC deliberately chooses to give the sub relief for a reason it is willing to fund.