Esc

↑↓ move↵ openIndex · Pagefind
Concepts / Buyout: from budget to committed cost

Buyout: from budget to committed cost

How construction buyout turns budget lines into subcontracts and POs, how buyout savings and losses are measured per cost code, and how os.construction checks each award against a frozen budget snapshot.

On this page

Buyout is the work of turning the budget you won the job with into signed subcontracts and purchase orders. Every trade’s budget line becomes a commitment, and the gap between the two is buyout savings (or a buyout loss). It’s the first hard test of the estimate, and on most jobs it decides more of the final margin than anything that happens in the field.

This page explains the concept and how the app models it. The click path is in Bidding and buyout.

The chain: budget, award, commitment

Illustrative · one cost code through buyout
  1. The budget says what you expected each trade to cost, by cost code.
  2. Bidding and bid leveling find the real price for the full scope.
  3. The award picks a bidder.
  4. The commitment (subcontract or PO) is the contract you sign, with a schedule of values on the same cost codes.
  5. The buyout comparison sets the commitment next to the budget line and records the difference.

Until step 4, the budget line is an estimate. After it, most of that line’s cost is contractual, and the job’s forecast depends on it.

Buyout savings, per cost code

Buyout savings = budgeted amount − committed amount − cost of excluded scope you bought separately

Work it per cost code, then add up. Report savings and losses separately as well as the net, so one bad trade isn’t hidden behind another’s good one.

Package (illustrative) Budget Committed Gap bought separately Savings / (loss)
Interior glazing and storefront $1,240,000 $1,173,000 $0 $67,000
Drywall and framing $2,310,000 $2,265,000 $38,000 (deck-edge firestopping excluded) $7,000
Elevators $640,000 $689,500 $0 ($49,500)
Bought out so far $4,190,000 $4,127,500 $38,000 $24,500 net

Gross savings $74,000, gross losses $49,500, net $24,500: 0.6% of the $4.19M bought out. The drywall line looked like $45,000 of savings until the excluded firestopping was priced. That is the most common way buyout savings turn out smaller than they first looked.

How os.construction checks an award

The app compares each award with the budget as it stood before buyout, not the live budget, for one reason: once a commitment exists, the live budget already counts it as committed cost, and comparing an award with a budget that contains that same award tells you nothing.

So the check uses three frozen records:

  • A budget snapshot, captured in Budget → Snapshots before the award is converted. It freezes every line’s revised budget, committed cost and direct cost.
  • An award receipt, created when the awarded bid becomes a draft commitment. It records the award amount and how it splits by cost code, with a SHA-256 digest, and later edits don’t change it.
  • A buyout plan, approved by a Budget admin, that allocates the receipt to cost codes against the snapshot.

For each cost code, the plan shows:

Column Meaning
Snapshot headroom Revised budget − committed − direct cost, as captured
Other reservations Allocations from buyout plans already approved on this project
Available headroom Snapshot headroom − other reservations
Allocation What you assign from this award to the code (defaults to the award)
Variance Allocation − awarded quote

The app won’t approve an allocation larger than the available headroom on a code. Reservations matter when two packages draw on the same code: if 09-210 has $300,000 of headroom and the framing award already reserved $260,000, a second award can only take $40,000 there.

Two rules to know:

  • One baseline per project. The first approved buyout plan fixes its snapshot as the project’s buyout baseline. Later plans must use the same snapshot. Capture it once the budget is final and before the first award is converted.
  • Approval moves no money. The plan is a recorded comparison. It doesn’t post cost, execute the commitment or transfer savings anywhere.

Where the savings go

Who keeps buyout savings is a contract question. On a lump-sum job they’re generally the contractor’s. On a GMP job they often go to a savings pool or contingency and may be split under a shared savings clause. Read the contract.

Either way, move them on purpose. In the app, a budget Modification transfers an amount from one line to another, for example $67,000 from 08-800 to your contingency line, with a note. The Modifications tab keeps every transfer, so anyone can see where the savings went. If the budget is locked, modifications are blocked and the move goes through a Budget Change instead.

Many contractors leave savings in contingency until the trade is well along, because scope gaps, disputed changes and sub defaults eat into them. Booking them as profit on day one is how a job shows margin fade six months later.

After buyout: commitment changes

Buyout fixes the commitment’s original amount. Everything after that is a change to the commitment:

  • Scope the owner adds: a PCO on the commitment from the same change event as the owner change.
  • A scope gap found later: a commitment change order on the trade that picks it up, or a new PO.
  • A back-charge: a negative commitment change order.

These move committed cost on the budget line without changing the buyout plan, which records the award as it was. See Change a subcontract or PO and Subcontracts and commitment changes.

Common mistakes

  • Mistake: Comparing awards with the live budget

    In the app: The buyout plan uses a snapshot captured before the award receipt, so the award isn't compared with a budget that already includes it.

  • Mistake: Reporting only net savings

    In the app: The plan is per cost code. Keep gross savings and losses visible, not only the net.

  • Mistake: Counting savings before pricing exclusions

    In the app: The leveling grid marks excluded lines. Price them before award and note how in the recommendation.

  • Mistake: Two packages spending the same budget line twice

    In the app: Other reservations subtract earlier approved allocations on the same code from the headroom.

  • Mistake: Savings quietly absorbed into other lines

    In the app: Move them with a budget modification, which is kept on the Modifications tab with its note.

✅ Before your first award is converted

  • The budget is final, and locked if that’s your practice.
  • A budget snapshot is captured and named so people recognize it (“Buyout baseline”).
  • Bid forms use the same cost codes as the budget lines they buy out.
  • You know whether savings stay on the line, go to contingency or go to a GMP savings pool.
  • A Budget admin is lined up to approve buyout plans.

Next step

See it on one package in the explainer Bidding: from bid package to awarded commitment, then follow the steps in Bidding and buyout.

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