Esc

↑↓ move↵ openIndex · Pagefind
Using the app / Change a subcontract or PO: commitment change orders

Change a subcontract or PO: commitment change orders

Raise, deduct or move scope on a subcontract or purchase order with a commitment change order or a PCO from the change event, and see where each one lands in the budget.

On this page

A commitment changes for four ordinary reasons: the owner added scope and the trade doing it needs paying, you’re deducting a back-charge, scope is moving from one sub to another, or the buyout missed something. Each of these is a change to the subcontract or purchase order, and each has to be on the commitment before the sub bills for it. Otherwise the sub’s next invoice is larger than its contract, and someone spends a week finding out why.

This page shows how to make those changes in the app. For why they matter and how they relate to owner changes, read Subcontracts and commitment changes.

Who does it
The PM or project engineer who owns the subcontract. Approving needs Edit on Commitments.
When
As soon as the sub is told to proceed with the change, and before their next invoice.
What it changes
The revised contract amount on the commitment, and committed or pending cost on the budget line.

Two ways to change a commitment

PCO from the change event Commitment change order (CCO)
Use it when The change started on the owner side: an RFI, a hidden condition, an owner request The change is between you and the sub only: back-charge, scope transfer, buyout gap
Where you create it Change Events → Create PCO from Change Event, picking the subcontract or PO as the Contract The commitment’s Change Orders tab, Create CCO
What it carries The change event’s line items, cost codes and origin A title, one cost code and an amount
Where it shows on the commitment Approved Change Orders list Commitment Change Orders list

Both add into the Revised Contract card on the commitment: Original Contract Amount, Approved PCOs, Approved CCOs, Approved Change Orders and Revised Contract Amount.

Pass an owner change to the sub

Use this when the same event changes both the owner’s contract and the sub’s.

  1. Start from the change event

    Open the change event in Tools → Change Events. Its line items should already carry the cost codes and the sub as Proposed Vendor.

  2. Create the cost-side PCO

    Choose the sub’s subcontract or PO as the Contract and click Create PCO from Change Event. The PCO copies the event’s line items. Adjust the amounts to the sub’s agreed price, which is usually less than the owner price because yours includes markup.

  3. Review and approve it

    Submit for Review, then the reviewer clicks Approve. It now appears on the commitment’s Change Orders tab under Approved Change Orders and in its revised amount.

Worked example (sample data). On Riverside Medical, owner CO #14 for the fire damper change is priced to the owner at $86,400. The mechanical sub’s share is $68,000. The other $18,400 is your own supervision ($6,500), firestopping ($3,600), and fee, insurance and bond ($8,300). Only the $68,000 goes on the mechanical subcontract. The owner-side PCO and the sub-side PCO both come from the same change event, so anyone looking at either can trace it back to the RFI that started it.

Create a commitment change order

  1. Open the commitment

    Tools → Commitments, open the subcontract or PO, then the Change Orders tab.

  2. Fill in the CCO

    Under Commitment Change Orders, enter a Title that says what changed and why, pick the Cost Code and enter the Amount ($). A deduction is a negative amount.

  3. Create it

    Click Create CCO. It’s numbered per commitment (CCO-001, CCO-002…) and starts as Draft.

  4. Approve it

    Click Approve on the row once the change is agreed with the sub. The approved amount is added to the commitment’s revised amount.

Commitment change order statusesA commitment change order starts as Draft. It can move to Pending while it's being agreed, and then to Approved or Rejected. A CCO that should never have existed is Void. In the commitment screen, the Approve button approves a CCO directly. Draft CCOs count nowhere in the budget; Pending ones count as pending cost; Approved ones count as committed cost.DraftCounts nowherePendingPending Cost ChangesApprovedCommitted CostsRejectedVoid
CCO statuses in the app

The commitment screen’s form creates a Draft and its Approve button approves. Pending, Rejected and Void are set through the REST API (commitment_change_orders) today.

Three worked examples

All illustrative.

Back-charge. The drywall sub left debris on level 3 and your labor crew spent 38 hours cleaning it at $75 an hour: $2,850. Create a CCO on the drywall subcontract titled “Back-charge: L3 debris cleanup, 38 h × $75, per notice dated 10/14”, cost code 09-290, amount −2,850.00. Approved, the subcontract’s revised amount drops by $2,850, and so does committed cost on 09-290. Your own cleanup labor lands on your cost code through payroll or a direct cost, not on the sub’s.

Scope moved between subs. The fire-stopping at the shaft walls was in the drywall sub’s scope, but the firestop sub is already mobilized and will do it for the same $14,000. Make two CCOs: −14,000 on the drywall subcontract and +14,000 on the firestop subcontract, each on its own cost code. Committed cost on the job doesn’t change in total; it moves between lines, which is what really happened.

Buyout gap. The awarded glazing bid excluded a $6,200 mirror package that the budget carried on 08-830. If the glazing sub agrees to add it, a +6,200 CCO on their subcontract covers it. If another vendor supplies it, it’s a new purchase order instead. Either way the cost was in your budget, so there’s no owner change.

Where it shows up

Status Commitment Budget line
Draft Listed, not in revised amount Not counted
Pending Listed, not in revised amount Pending Cost Changes
Approved Added to Revised Contract Amount Committed Costs

A CCO moves the cost side of the budget only. It never changes the owner’s contract or the revised budget. If the owner is paying, the change also needs an owner-side PCO; see Change events and change orders.

Common mistakes

  • Mistake: Owner CO approved, sub told to proceed, commitment never changed

    In the app: Create the sub-side PCO from the same change event as the owner change, so the gap is visible from either record.

  • Mistake: Putting the owner price on the sub

    In the app: The sub-side PCO copies the event lines; edit them to the sub's agreed number. Your markup stays on the owner side.

  • Mistake: A back-charge kept in an email and taken off the next payment by hand

    In the app: A negative CCO puts it on the subcontract with a title and date, so the revised amount and the sub's balance to finish agree.

  • Mistake: Leaving CCOs in Draft and wondering why the budget didn't move

    In the app: Draft counts nowhere. Approve it, or keep it as a Pending change so it shows as pending cost.

  • Mistake: Using one CCO for a scope transfer between two subs

    In the app: A CCO belongs to one commitment. Make a deduct on one and an add on the other.

Checklist: before you approve a CCO

Ready to approve

  • The title says what changed, why, and points to the notice, RFI or change event.
  • The amount is the sub’s agreed price, and a deduction is negative.
  • The cost code is the one the work is budgeted on.
  • If the owner is paying, the owner-side PCO exists from the same change event.
  • The sub has the change in writing before they bill for it.
  • For a scope transfer, the matching CCO on the other commitment is ready too.

Next step

When the sub bills, enter the invoice against the revised schedule of values: Commitments and sub invoices. For how the award became a subcontract in the first place, see Bidding and buyout. The Life of a change order explainer follows CO #14 through the owner contract, the sub’s commitment, the pay app and the WIP.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file