RFQs: get sub pricing for a change
Ask subs and suppliers to price a change, record and level their quotes, award one, and hand the price to a change event so it can become a PCO on the owner contract and the sub's commitment.
On this page
When something changes on the job, you need a number from the trade that will do the work before you can price it to the owner. An RFQ (request for quote) is that ask. In os.construction an RFQ lists the vendors you asked, the quotes they gave, and the one you picked, and the awarded quote turns into lines on a change event with the vendor and cost code already set. From there the same numbers become the potential change order to the owner and the change on the sub’s commitment.
RFQs here are for pricing changes during the job. To buy out a whole trade package at the start, use Bidding. For when to use which, see RFP vs RFQ.
- Who uses it
- PMs and project engineers pricing changes. Vendors don't log in: you record their quotes.
- When
- Between "this is a change" (the change event) and "here is the price" (the PCO).
- What it holds
- Title, scope of work, due date, estimated amount, cost code, invited vendors, quotes with lead time, and the award.
- Connects to
- Change eventsCommitment changesBudget
How an RFQ moves
Start from the change event
The cleanest path starts on the change event, so the RFQ and the event point at each other from the beginning.
-
Open the change event
In Tools → Change Events, open the event and click Create RFQ from Change Event. Or use Link RFQ for one you already started in Tools → RFQs.
-
Fill in the RFQ
Give it a Title (“Rooftop steel staircase, add per RFI-212”), a Scope of Work a sub can price without calling you, a Due Date, the Cost Code and your own Estimated Amount. Assign it to the person chasing the prices. Tick Open for pricing immediately (assigns an RFQ number) to skip Draft; a draft RFQ has no number yet.
-
Invite vendors
Under Invite Vendors (or Invite vendor on the RFQ), pick the vendors from the project directory. Each shows as a quoter with status Invited, Viewed, Quoted or Declined. The app doesn’t send them anything. Send the scope from your own email.
Record and level the quotes
When a price comes back, open Record a Quote, choose the Vendor, enter the Total Cost, Lead Time (days) and any Notes, and click Submit Quote. A vendor you didn’t invite can still be picked; they’re added as a quoter.
The Bid Leveling grid lines the quotes up with their lead time and schedule impact, and the strip across the top shows the Estimate, the Lowest quote, the Spread between quotes and Low vs estimate.
| Quote (illustrative) | Total | Lead time | Notes |
|---|---|---|---|
| Summit Steel | $18,400 | 21 days | Galvanized, field-welded |
| Ridgeline Fabrication | $16,900 | 35 days | Excludes touch-up paint |
| Apex Steel | $19,750 | 14 days | Includes paint |
Estimate $17,500. The low quote is $600 under it, but 35 days out and missing paint. If the stair is on the critical path for the roof turnover, the 14-day quote may be the cheaper one once you count the schedule. Write that reasoning into the change event or PCO description; the RFQ records the numbers, not your argument.
Award and hand off
-
Award
In the leveling grid, click Award under the winning quote. Only a submitted quote can win. Awarding freezes the RFQ, the winner and its quote.
-
Check the change event
If the RFQ came from (or was linked to) a change event, the award adds lines to that event in the same step: one line per cost code on the quote, with the winning vendor as Proposed Vendor, the description and the quoted amount as the line’s ROM. A quote without lines goes on the RFQ’s cost code.
-
No change event yet?
For an RFQ that isn’t linked, the Change Management panel shows Create Change Event from awarded quote. Clicking it again later opens the same event; it doesn’t make a second one.
Change event lines that carry an award can’t have their cost code, vendor, description, quantity, unit cost or ROM edited, and can’t be deleted. You still set each line’s Budget Change ($) on the event, because what posts to the budget is your decision, not the sub’s price.
From the change event onward
- On the change event, set Budget Change ($) per line if the budget should move.
- Create PCO from Change Event against the prime contract, adding your markup, for the owner.
- Create PCO from Change Event against the sub’s subcontract or PO at the awarded price, for the sub. See Change a subcontract or PO.
With the example: Apex’s $19,750 becomes a change event line on 05-510 Metal stairs. The owner PCO might carry $19,750 plus 10% fee, $21,725. The PCO on Apex’s commitment carries $19,750.
Common mistakes
Mistake: Pricing a change with one phone call and no record
In the app: Even one quote recorded on an RFQ keeps the vendor, amount, lead time and date with the change event it priced.
Mistake: Re-keying the sub's number into the change event by hand
In the app: Award on a linked RFQ creates the change event lines with the vendor, cost code and amount.
Mistake: Picking the low number without reading the notes
In the app: The leveling grid shows lead time and schedule impact next to each total. Exclusions live in the notes, so read them before Award.
Mistake: Assuming the vendors got the RFQ
In the app: Invitations are recorded, not sent. Email the scope yourself and record the quote when it comes back.
Mistake: Forgetting the commitment side
In the app: The award prices the change event. The sub's contract only changes when you create and approve the PCO or CCO on their commitment.
✅ Before you click Award
- The scope of work is the same one every vendor priced.
- Each quote’s exclusions are in its notes, and you’ve priced any gap.
- Lead times are checked against the schedule.
- The RFQ is linked to the right change event (or you’ll create one from it next).
- The winning quote is entered against the right vendor: you can’t change it after award.
Not in the app today
Sending RFQs or reminders by email, a vendor portal for subs to enter their own quotes, entering quote line items from the RFQ screen (they can be sent through the REST API), and re-awarding to a different vendor after an award.
Next step
Turn the priced change event into change orders: Change events and change orders. The explainer Change events vs change orders shows how the RFQ, change event, PCO and package relate.
Keep exploring
Related across os.construction
- GlossaryChange Order (CO)A signed agreement between owner and contractor that changes the contract scope, price, time, or a combination of them.
- DocsChange a subcontract or PO: commitment change ordersRaise, 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.
- DocsBidding, RFQs and prequalificationPut work out to bid with bid packages, level the quotes, award with an independent approval and turn the award into a commitment. Price changes with RFQs, and record vendor prequalification.
- GlossaryCost-to-completeThe estimated remaining cost to finish a job, based on remaining commitments, remaining labor and known risks, not just budget minus actuals.
- ExplainerChange events vs change orders: the full lifecycleWhat a change event is, what a PCO and change order are, and where each one shows up in the budget, the contract and the pay app in os.construction.
- BlogHow to run a construction buyout: buy-by dates, a buyout log and where the savings goBuyout turns the estimate into signed subcontracts and purchase orders. Run it as a schedule, not a to-do list: work back from each package's need-on-site date to a buy-by date, bid and level, write the scope into the contract, record every variance against the budget, and track the log weekly. Here is each step with a worked buyout log.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →