The Subcontractor RFQ Process: 8 Steps From Scope to Award

A subcontractor RFQ process is the sequence an estimator follows to turn a set of bid documents into comparable, trade-by-trade prices: define the scope, build an invite list, send everyone the same package, answer questions in writing, collect quotes by a hard deadline, level them, award, and tell the losers. Skip a step and the price you carry in your bid is a guess. This guide walks through each step, the mistakes that cost bids, and how to keep the paper trail clean.

TL;DR

• Send every invited sub the same scope, drawings, addenda and deadline at the same time, and log it.
• Put questions and answers in writing and share them with everyone, so no one prices a different job.
• Level quotes by normalizing inclusions, exclusions and assumptions, not by comparing totals.
• Treat email as a risk: confirm receipt of quotes, and plan for late and incomplete submissions.
• Close the loop: record the award basis, notify unsuccessful bidders, and feed prices back into your cost history.

Table of Contents

• What people mean by “RFQ” in construction
• The subcontractor RFQ process at a glance
• Step 1: Read the documents and define each package
• Step 2: Build an invite list you can defend
• Step 3: Issue one package to everyone at the same time
• Step 4: Manage questions in writing
• Step 5: Receive quotes through a controlled channel
• Step 6: Level the quotes
• Step 7: Award and carry the numbers
• Step 8: Debrief, notify and record
• Our perspective: where RFQ processes actually break
• Run your RFQs from one command center
• Common mistakes to avoid
• A short RFQ checklist
• FAQ
• Sources

What people mean by “RFQ” in construction

The acronym carries two meanings, and mixing them up causes real confusion in bid rooms.

For most estimators, an RFQ is a request for quotation. A contractor sends a document describing the work to subcontractors or suppliers, and they return a quote listing labor, materials and quantities. Procore describes this as a way for contractors or owners to compare materials and pricing across the companies that respond. That is the process this article covers.

In owner procurement, RFQ often means request for qualifications. Owners use it to build a shortlist based on experience and capability, and then issue an RFP to the qualified firms for detailed cost and method proposals. If you are deciding which one you need, our guide on when to issue an RFQ or RFP lays out the test. Tools for drafting and signing documents, such as RFP software, can help once you know which document you are writing.

The rest of this article is about the quote request that flows down the chain: general contractor to trade subcontractor, or trade subcontractor to its own vendors and sub-tier suppliers.

The subcontractor RFQ process at a glance

Step 1: Read the documents and define each package

The RFQ is only as good as the scope you hand out. Before you invite anyone, read the whole document set, including the front-end clauses, Division 01 and every addendum, and write down what belongs in each trade package.

The American Subcontractors Association scope guidance recommends treating the scope exhibit as a living document during pre-construction and marking it up as if you were already negotiating the contract. That habit surfaces ambiguities and conflicting specifications before they reach the field. The same guidance suggests the trade-specific scope exhibit be sent well ahead of bidding, at least two weeks in its recommendation, which is a useful target even when the schedule rarely cooperates.

For each package, capture:

• Spec sections and drawing sheets that apply
• Addenda that change the package
• Items that sit on the border between trades (firestopping, sleeves, patching, temporary power)
• Owner or GC requirements that affect price: bonds, insurance, prevailing wage, schedule milestones, liquidated damages
• Alternates and unit prices you want priced

Conflicts between spec sections and drawings are the most common trap here. We log them in five fields so they can be resolved before quotes come in; see construction spec conflicts for the format.

Step 2: Build an invite list you can defend

More quotes is not always better. The goal is enough competitive, qualified prices on each package that you trust the number you carry.

Start with vendors and subs who have performed well for you. Add new names where your history is thin or the project type is unfamiliar. For each, confirm basics before you invite: trade license where required, insurance, capacity during the project window, and experience on similar work. When the owner or GC requires a subcontractor list, the AIA-MBA Joint Committee notes that asking for names is a way to assess qualifications, and that it should follow the process in the AIA General Conditions.

For a deeper look at how teams vet and shortlist trade partners, the principles in this guide on managing flooring subcontractor relationships carry over to other trades.

Keep a record of who you invited, who declined and why. If you are working on a public or publicly funded project, procurement rules may require you to document this, and even on private work it protects you in a dispute. The Sievo RFQ guide makes the same point for procurement generally: record how many requests went out, how many came back and the evaluation criteria.

Step 3: Issue one package to everyone at the same time

A good RFQ package is short on prose and long on specifics. Include:

1. Project name, location and bid due date
2. Your quote deadline, set early enough to level and verify before your own bid is due
3. Trade scope description and the spec sections and sheets it references
4. Addenda issued to date, with a statement that later addenda will be sent
5. Required quote format: lump sum, unit prices, alternates, breakouts by phase or area
6. Required inclusions: bonds, taxes, freight, mobilizations, submittals, warranty
7. Contact for questions and the date after which questions will not be answered
8. How to submit and how you will confirm receipt

Sievo’s guidance is that all bidders should receive the same information at the same time, and that the RFQ must give clear instructions and enough time for a considered response. If you send a vendor a drawing set that is one addendum behind, you have created a quote you cannot use.

Two practical habits help. First, send the package through a tool that logs delivery and opens, not a pile of individual emails. Second, ask for a written bid without dollar amounts to confirm scope if your market uses that practice. One industry guideline for GC and subcontractor relations describes subcontractors delivering a written bid without dollar amounts at least 24 hours before the bid, setting out scope, alternates and unit prices. Whether you adopt that exact practice or not, the idea is sound: agree on what is being priced before the price arrives.

Step 4: Manage questions in writing

Vendors will find holes in your package. That is a feature. The ASA guidance reminds contractors that subs are the subject matter experts on how their own trade is applied, and that subs should flag scope exhibit mismatches in writing right away, rather than burying them in a bid qualification. Waiting until submission, it notes, often ends in disqualification instead of clarification.

On your side of the table:

• Keep one question log per project, with date, package, question, answer and who received it
• Share every answer with every invited bidder, not only the one who asked
• If an answer changes scope, issue it as a written clarification or addendum
• Escalate to the design team or GC through the formal RFI route when the answer is not yours to give

When you need to push a question up the chain before bids lock, pre-bid RFI management walks through how estimators keep those requests organized and answerable.

Step 5: Receive quotes through a controlled channel

Quotes arrive in every format: PDF on letterhead, Excel templates, a voicemail with a number, a portal entry. Decide in advance how you will accept them.

The AIA-MBA Joint Committee advises against accepting bids by email for owner bidding, citing blocked servers, misrouted messages and file-size limits, and says that if email must be used, you should document how receipt is verified, such as a read receipt or acknowledgment. That guidance is aimed at formal bid submission, but the failure modes are the same when your inbox is the intake point for fifteen vendor quotes on deadline day.

A workable approach:

• Ask vendors to confirm they will quote, and to confirm again when they send
• Reply to every quote with an acknowledgment and time stamp
• Open all quotes after the deadline, not as they trickle in, so no vendor can be tempted to revise after seeing others
• Decide your late-quote policy before deadline day and apply it consistently

The Sievo guide recommends opening bids immediately at the deadline to maintain confidentiality and fairness. Even in private work where you are free to negotiate, the discipline keeps your records credible.

Step 6: Level the quotes

This is where most RFQ processes win or lose money. A quote total tells you almost nothing until you know what is inside it.

The ASA scope guidance frames leveling as more than comparing totals: you are normalizing the assumptions embedded in each bid, such as material grades or labor hours, so you compare like with like. Proactive scope alignment before the bid, rather than reliance on the final document alone, is what makes leveling reliable.

What to normalize

A worked example

Say three vendors quote a roofing package at $412,000, $438,000 and $471,000. The low number looks like the winner. On review, the low quote excludes sheet metal flashing and assumes a thinner insulation than specified, and the middle quote carries a longer price validity. After adding the excluded work at your own estimated cost and adjusting the insulation, the three come out within a few percent of each other, and the vendor with the most complete quote becomes the real low. The totals alone would have misled you. (The figures are illustrative.)

Gaps that appear after the bid locks tend to be paid for in change orders, so our note on quote scope gaps covers how to protect your position before that point. If you level in spreadsheets by hand, a second pair of eyes helps; our three-stage estimate review checklist is built for that.

Automation can take the repetitive part of this work. AI bid leveling for trade vendor RFQs reads quotes against the scope you issued and flags what is missing, while a person decides what to carry.

Step 7: Award and carry the numbers

After leveling, choose on value, not just price. Consider completeness, schedule fit, capacity, past performance and risk. Write down why you chose the vendor you did, in two or three lines, with the leveled numbers attached.

Before a price goes into your proposal, confirm:

• The vendor’s quote is valid through the period your own bid must hold
• Scope gaps you have identified are either priced by you or clarified in writing
• The proposal’s qualifications and exclusions match the vendor’s, so you are not promising more than you bought
• Every addendum is acknowledged

The AIA-MBA Joint Committee also cautions that instructions to bidders belong apart from the contract documents, since bidding procedures relate to selection, not performance. As a sub, the practical takeaway is to check which document governs each term before you rely on a clause in a bid form or in your own RFQ. Their bidding guidance is worth a read before you draft templates.

If your award decision feeds a compliance-heavy response, see how a compliance-first RFP response is assembled.

Step 8: Debrief, notify and record

Tell unsuccessful vendors promptly and politely. It costs nothing and keeps your bench of vendors willing to quote you next time. Procurement guidance such as Sievo’s lists feedback to unsuccessful bidders as the final step in the cycle, and it is a good habit even where no rule requires it.

Then close the file:

• Archive the issued package, addenda, question log, quotes and leveling sheet together
• Record who was awarded and at what leveled price
• After the owner’s decision, record whether you won and what you learned
• Add actual awarded prices to your cost history so the next estimate starts from real numbers

This is the step most teams skip, and it is what turns a one-off RFQ into an asset.

Our perspective: where RFQ processes actually break

We build bid management software for construction trades, and the same failures show up regardless of trade.

First, the break happens upstream of the quote. Teams collect plenty of prices but never read the full set, including the front-end clauses, so the package they send out is already missing a requirement or contradicting itself. We think document review has to come before the RFQ goes out, not after quotes arrive.

Second, leveling is treated as a math exercise. It is a scope exercise. Software can read twelve quotes against a package faster than a person, and it should, but the authority to carry a number stays with the estimator. That is why we automate error-checking without taking submission decisions out of human hands.

Third, the RFQ is one link in a chain: intake, bid/no-bid, takeoff, quotes, leveling, proposal, buyout and debrief. When each link lives in a different file, nothing carries forward. We design for the whole cycle, and for teams that already live in Excel and Outlook, we integrate with those tools rather than asking anyone to start over.

— arosbid team

Run your RFQs from one command center

If you manage vendor quotes across several bids at once, ArosBid tracks invitations, responses, compliance items and leveled comparisons in a single bid process platform, alongside vendor quote leveling for trade RFQs. It works with Excel and Outlook, so your team keeps its current habits. Plans (One Desk, The Department and The Whole Year) are listed on the pricing page, and you can book a live demo to see it on one of your own bid packages.

Common mistakes to avoid

• Sending different packages to different vendors. One missed addendum makes one quote unusable.
• Setting the quote deadline too close to your own. You need time to level, call vendors and verify.
• Relying on the total. A low price with a thin scope is a future change order.
• Answering questions by phone. If it is not in writing and shared, it did not happen.
• Treating exclusions as the vendor’s problem. If nobody carries the item, you do.
• Discarding the data. Awarded prices and debrief notes belong in your cost history.

A short RFQ checklist

1. Documents read in full, including front-end clauses and addenda
2. Packages defined with spec sections, sheets and boundary items
3. Invite list built, qualifications confirmed, declines recorded
4. Identical package sent with one deadline and one submission method
5. Question log maintained and answers shared with everyone
6. Receipt of each quote acknowledged
7. Quotes leveled on scope, assumptions and commercial terms
8. Award basis written down, losers notified, file archived

FAQ

What is the difference between an RFQ and an RFP in construction?

An RFQ asks for a price on a defined scope or, in owner procurement, for qualifications to build a shortlist. An RFP asks for a proposal that includes cost and method from the firms on that list. Procore’s comparison explains how owners use them together.

How many quotes should I get for each trade package?

There is no universal number. Aim for enough qualified quotes that you can see a credible range and spot outliers, and document any package where you only received one. Public projects may have rules that set a minimum, so check the procurement requirements for yours.

How long should vendors have to respond?

Long enough to price the work properly, and short enough that you can level before your own bid is due. The ASA guidance suggests getting the trade scope exhibit out at least two weeks before bidding, which is a good benchmark when the schedule allows.

Is it acceptable to take quotes by email?

It is common, but it carries risks such as blocked messages and size limits. If you use email, document how you confirm receipt, for example with a reply acknowledging each quote, as the AIA-MBA Joint Committee advises for bid submission.

Should I always carry the lowest quote?

No. Carry the lowest complete, qualified quote after leveling. A cheaper quote that leaves out scope, or assumes lesser materials, will cost you more once the gaps are filled.

Sources

• What is a Request for Quotation (RFQ) in construction? (Procore)
• RFQs in Construction Explained (Procore)
• RFQ, RFP, and RFI in construction: Differences explained (Procore)
• The Request for Quotation (RFQ) Process in 6 Steps (Sievo)
• Scope Best Practices (American Subcontractors Association)
• Bidding (AIA-MBA Joint Committee)
• Guidelines for a Successful Construction Project
• How to Manage Flooring Subcontractor Relationships
• RFP Software

Recommended

• When to Issue an RFQ or RFP for Construction
• Pre-Bid RFI Management: A Practical Guide for Estimators
• Run a 16 Point Scope of Work Review Before Signing