Esc

↑↓ move↵ openIndex · Pagefind
Using the app / Bidding and buyout: award a package and check it against the budget

Bidding and buyout: award a package and check it against the budget

Run a bid package from vendor release to award, turn the awarded bid into a draft subcontract or PO, then approve a buyout plan against a captured budget snapshot.

On this page

Buyout is the stretch between winning the job and having every trade under contract. In os.construction it runs through two tools: Bidding, where you release a package, collect quotes, level them and award one, and Budget, where the award is checked against a snapshot of the budget you captured beforehand. The result is a draft subcontract or purchase order with its lines and cost codes filled in, and a recorded buyout savings figure per cost code.

This page is the click path. For the story of one package, with a leveling sheet where the low bid left scope out, read the explainer Bidding: from bid package to awarded commitment. For the money concepts, read Buyout: from budget to committed cost.

Who does it
A PM or project engineer builds and levels the package. A second person with Bidding admin approves the recommendation. A Budget admin approves the buyout plan.
When
From notice to proceed until each trade is under contract. Early packages (steel, elevators, long-lead equipment) first.
What you end with
An awarded package, a draft commitment with one SOV line per priced bid line, a frozen award receipt and an approved buyout plan.

How a package moves

Bid package status flowA bid package starts as Draft. Once a vendor release is approved, Open Bidding moves it to Open. Close Bidding moves it to Closed. Confirm award moves it to Awarded. A Closed or Awarded package can be reopened to Open. An open or closed package can go back to Draft for an addendum, which needs a new approved release and new invitations.release approvedreopenaddendumDraftScope, bid form, releaseOpenInvitations and quotesClosedLevel and recommendAwardedCreate the commitment
Bid package statuses in the app

1. Build the bid package

  1. Create it

    Open Tools → Bidding and click Create Bid Package. Enter the Title, Number, Cost Code, Bid Due Date, an Anticipated Award Date and, if there is one, the Pre-Bid Walkthrough Date and notes. Tick Blind Bidding or Sealed Bidding if the package needs them.

  2. Write the bid form

    Add the lines every bidder must price, each with its cost code. Use the same split your budget uses. If the budget carries storefront and interior glazing on separate codes, make them separate bid lines, or the award can’t be compared with the budget line by line later.

  3. Add bidders

    Add Bidders registers vendors on the package. It does not invite anyone or send email.

2. Release it and open bidding

  1. Review the vendor release

    Click Vendor Release, then Generate release preview. The preview shows exactly what bidders will see: title, scope, bidder instructions, dates, form lines and the names and digests of the files you staged and classified for bidders.

  2. Approve it

    Write a Review reason (at least 10 characters), tick the confirmation and click Approve this vendor release. The preview expires; if it does, or if you edit the package, generate a new one.

  3. Open bidding

    Back on the package, click Open Bidding. Until a release is approved, the package shows “Approve the vendor release before opening bidding.”

3. Invite bidders

For each bidder, choose an active contact at that vendor and click Record Local Invitation. You get a private link that expires seven days after the form was opened. The app does not email bidders. Send the link yourself, from your own email. Each invitation shows “Local outbox recorded; delivery unverified” and can be revoked.

If a vendor shows “No active authorized contacts for this vendor”, add the person as an active project user linked to that vendor company in the project Directory first.

The package header counts down: a tag reads 9d left inside 14 days of the due date and 2d late after it.

4. Collect and level the quotes

Bidders price each line, can mark lines excluded and add alternates, qualifications and lead time. Each bidder sees only their own quote. When quotes are in, click Close Bidding.

The Bid Leveling grid puts submitted quotes side by side. The lowest price on each line is highlighted, excluded lines read Excl., and a Spread column shows high minus low. The grid marks the lowest total as low without filling excluded lines. Pricing the gaps is your job.

Line (illustrative) Clearview Northline Keystone
08-410 Storefront $412,000 $404,000 $425,500
08-800 Interior glazed partitions $586,000 $598,000 $572,000
08-880 Fire-rated glazing $148,000 Excl. $139,500
08-830 Mirrors and misc. $38,500 $41,000 $36,000
Total as submitted $1,184,500 $1,043,000 (low) $1,173,000
Leveled (excluded line priced at $139,500) $1,184,500 $1,182,500 $1,173,000

Northline looks $130,000 cheaper until you price the fire-rated glazing it left out. Leveled, Keystone is $9,500 lower. There are no plug values in the grid, so write how you leveled into the recommendation.

5. Recommend, approve and award

  1. Record the recommendation

    Open Open frozen comparison and award review. The quotes there are frozen, so nobody approves a number that changed. Pick the quote, write a Recommendation reason (10 to 1,000 characters), list Scope exceptions one per line, add review notes for alternates, qualifications, schedule and cost codes, tick the confirmation and click Record recommendation.

  2. Get a second approval

    A different person with Bidding admin access opens the same page, writes an Approval reason and clicks Approve recommendation. The person who recommended can’t approve their own recommendation.

  3. Award

    Click Confirm award. The app checks that the bid was submitted, that an approved recommendation exists and, if the bidder gave both line prices and a lump sum, that they match. The package becomes Awarded. No commitment exists yet.

6. Create the draft commitment

On the awarded bid, click Review commitment, choose Subcontract or Purchase Order, and pick a Fallback cost code only if some bid or package line has no code. Tick the confirmation and click Confirm commitment.

The app creates the commitment as a Draft, titled after the package, with the awarded vendor and one schedule of values line per priced bid line, each carrying its cost code. The lines must add up to the award. The package keeps a frozen Award to commitment receipt with a SHA-256 digest, and clicking again opens the same commitment instead of making a second one.

7. Approve the buyout plan

  1. Open the buyout page

    On the package, click Review buyout against captured Budget. You need view access to Budget and Commitments to open it, and Budget admin to approve.

  2. Pick the baseline

    Under Budget baseline, choose a snapshot captured before the award receipt. Only those are listed. Once the project has an approved buyout plan, use that plan’s snapshot.

  3. Allocate

    Each cost code from the receipt starts with its awarded amount in Proposed allocation. Leave it as is unless you are deliberately carrying part of the award elsewhere. Every receipt code must be allocated exactly once.

  4. Review, then approve

    Click Review allocation against baseline. The approval preview shows, per code, Revised budget, Prior committed, Prior direct, Snapshot headroom, Other reservations, Available headroom, Receipt quote, Allocation and Variance. It is valid for 10 minutes. Click Approve this buyout plan.

How the preview is calculated:

  • Snapshot headroom = revised budget − committed − direct cost, all as captured in the snapshot.
  • Available headroom = snapshot headroom − allocations from buyout plans already approved on the project.
  • Variance = your allocation − the awarded quote.

The app refuses an allocation larger than the available headroom on a code. On the glazing example, a $595,000 revised budget on 08-800 with nothing committed in the snapshot leaves $595,000 of headroom; Keystone’s $572,000 fits, and $23,000 stays on the line. Across the four lines the award is $1,173,000 against $1,240,000 of budget: $67,000 of buyout savings.

8. After the buyout

  • Execute the commitment. Open it in Commitments, check the SOV, retainage, inclusions and exclusions, then move it to Approved and tick Executed. Until it’s approved, its lines show in the budget as Pending Cost Changes; after, as Committed Costs.
  • Move the savings on purpose. If your practice is to park savings in contingency, record a Modification from the trade line to the contingency line in Budget. A locked budget blocks modifications; use a Budget Change instead.
  • Handle later changes as commitment changes. Scope added to the sub after award goes on the commitment’s Change Orders tab. See Change a subcontract.

Common mistakes

  • Mistake: Converting the first award before capturing a budget snapshot

    In the app: The buyout page lists only snapshots captured before the award receipt, so capture one first. There is no retroactive baseline.

  • Mistake: Awarding the low total on the leveling grid

    In the app: The grid marks Excl. lines but never fills them. Price the gaps yourself and put the method in the recommendation reason, where the approver reads it.

  • Mistake: One person recommends and approves

    In the app: Approve recommendation is refused for the person who recorded it. A second Bidding admin has to sign off.

  • Mistake: Assuming bidders got an email

    In the app: Record Local Invitation creates a link only. Send it yourself and watch the bid status move from Invited to Viewed.

  • Mistake: Bid lines that lump two budget codes together

    In the app: Commitment lines take their cost codes from the bid lines, and the buyout compares by code. Split the bid form the way the budget is split.

  • Mistake: Booking buyout savings straight into profit

    In the app: Approval records the savings but moves nothing. Decide where they go, and record it with a budget modification.

Checklist: before you click Confirm commitment

Ready to create the commitment

  • A budget snapshot exists that was captured before this conversion (and, after the first plan, it’s the project’s buyout baseline).
  • Excluded lines are priced and the leveling method is written in the recommendation.
  • Scope exceptions are listed, so they can be written into the subcontract’s exclusions.
  • Every bid line has a cost code, or you know which fallback code you’ll pick.
  • The bid’s line items match its lump sum, if the bidder gave both.
  • You know whether this is a subcontract (labor on site) or a purchase order (material).

Not in the app today

Sending invitations or bid emails from the app, bid bond tracking, plug values in the leveling grid, closing a package automatically at the due date, and revising an approved buyout plan after later budget changes.

Next step

Once the subcontract is approved and executed, changes to it go through commitment change orders: Change a subcontract or PO.

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