Pre-Bid RFI Management: A Practical Guide for Estimators

Pre-bid RFI management is the discipline of finding ambiguities in the bid documents, asking about them in writing before the question deadline, tracking every answer to an issued addendum, and pricing only what the addenda confirm. Done well, it keeps you from pricing a conflict, missing a clause or carrying an unwritten assumption into the contract. Done badly, it leaves you with a stack of emails and a bid nobody can defend. This guide covers the process step by step, with the rules that matter and the mistakes we see most often.

TL;DR

• A pre-bid RFI is a written request for clarification sent during the solicitation, before bids are due. It is not the post-award field RFI.
• Rely only on answers issued by addendum. AIA-MBA guidance says bidders should not rely on anything else, and addenda should be acknowledged on the bid form.
• Deadlines come from the solicitation, not from a universal rule. Find the question cutoff on day one and work backward from it.
• Keep one log: question, document reference, owner, status, addendum number, and the estimate line it affects.
• Automation should surface conflicts and track status. A person decides what to ask and how to price.

Table of Contents

• What a pre-bid RFI is, and what it is not
• Why pre-bid RFIs fail
• The pre-bid RFI process, step by step
• What your RFI log should hold
• Measuring pre-bid RFI performance
• Our perspective: automation should expose ambiguity, not decide it
• Where ArosBid fits
• Common mistakes to avoid
• FAQ
• Sources

What a pre-bid RFI is, and what it is not

A pre-bid RFI is a bidder’s formal written request for clarification, interpretation, missing information or correction concerning the plans, specifications, contract requirements or bidding instructions, submitted before bids are received. AIA’s A701 Instructions to Bidders covers exactly this: how bidders get documents, how they submit requests for clarification or interpretation, and how they submit bids.

Much of what ranks for this topic describes the other kind of RFI: the question a contractor sends the design team after award, when the work is underway. The two share a name and little else. A field RFI is part of project delivery. A pre-bid RFI is part of the solicitation, and its answer changes what every bidder prices. If you want a view of the field side, a contractor’s field guide to the construction RFI process is a useful contrast.

Does an RFI come before an RFP?

Not as a universal rule. The invitation or solicitation establishes the opportunity and the documents. Bidders then send clarification questions through the channel the solicitation names. AIA separates invitation and instructions-to-bid documents from RFI forms, and ConsensusDocs 705 covers invitations and subbid proposals while 790 covers formal RFIs. Terminology varies by procurement method and owner, so follow what your solicitation says. If you are unsure whether the invitation is an RFQ or an RFP, our guide to when to issue an RFQ or RFP lays out the difference.

Why pre-bid RFIs fail

Most teams do not fail because the architect answered slowly. 2025 digitalization research frames RFI trouble as a workflow problem: fragmented documentation, inconsistent procedures and decentralized communication. That matches what happens on a bid desk.

The usual breakdowns:

1. Questions live in inboxes. One estimator emails the architect, another calls the GC, and nobody knows what was asked.
2. Conflicts are found too late. The spec says one product, the drawings show another, and the discrepancy surfaces two days before bid day.
3. Verbal answers get treated as answers. A helpful phone reply feels like a resolution, but it binds no one.
4. Addenda are not tied back to the estimate. The answer arrives, gets filed, and never reaches the line it changes.
5. Nobody owns the log. Each person assumes someone else is checking.

The fix is a structure: one owner, one log, one source of truth, and a hard link between each answer and the number it moves.

The pre-bid RFI process, step by step

1. Read the instructions before the drawings

Open the instructions to bidders and the front-end documents first. Note the question deadline, the submission channel, the named contact, the date of the final addendum, and whether a pre-bid conference or site visit is mandatory. Front-end clauses are where bids get disqualified: bonding, insurance, alternates, unit prices, bid form requirements and acknowledgment of addenda.

The typical order of events on public work shows why the dates matter. On the Asheville Middle School track and restroom bid, for example, the advertisement set a virtual pre-bid conference on April 16, 2026, well ahead of the May 7 bid opening. Your own calendar should show those dates the day the invitation arrives. For the conference and job walk itself, use our nine-step pre-bid agenda and job walk checklist.

2. Review the full set for conflicts and gaps

Compare specifications against drawings, drawings against each other, and both against the front-end documents. Look for:

• Product or manufacturer named in the spec but not on the drawings
• Scope that sits between two trades with no owner
• Quantities or dimensions that disagree between sheets
• Alternates and allowances with unclear limits
• Superseded sheets still in the set (see version control for bid documents)
• Clauses that shift risk, such as unusual liquidated damages or unclear schedule terms

The point is to resolve conflicts before pricing. A study of 2,690 RFIs across 17 high-rise projects found that preventive design review, specialty design, 3D coordination and engineering analysis were the leading ways BIM could avoid information requests. The lesson for estimators: a conflict you record after award has already cost you.

3. Decide what deserves an RFI

Not every question should go to the owner. Every RFI you submit is visible to the design team and, once answered by addendum, to all your competitors. Sort your questions into three groups:

Many owners and agencies track unjustified RFIs. The WisDOT benchmarking report lists the percentage of unjustified RFIs as a metric alongside RFIs per million dollars, percentage answered by the requested date and average response time. Asking well is part of being a bidder people take seriously.

4. Write each question so it can be answered once

A good pre-bid RFI is short, specific and answerable without a follow-up. Use the same structure every time:

• Reference: sheet number, detail, spec section and paragraph
• Issue: what conflicts or is missing, in one or two sentences
• Question: the exact thing you need decided
• Impact: why it affects the bid, stated neutrally
• Proposed reading (optional): your interpretation, so the designer can confirm or correct it

Compare two versions. Weak: “Please clarify the roofing.” Better: “Spec 07 54 23 calls for a 60-mil TPO membrane. Sheet A-501 detail 4 notes 80-mil. Please confirm which governs.” The second takes a minute to answer and cannot be misread.

Keep one issue per RFI. Bundled questions get partial answers, and partial answers are hard to track.

5. Send it through the official channel, before the cutoff

Use the channel named in the solicitation. Some owners use a bidding portal, others a named person. ODOT’s construction manual shows the controlled version: written questions, a single agency point of contact, tracking and archival, and technical answers distributed to all bidders through the official bidding system. Treat any solicitation that way, even if the owner is less formal.

On timing, there is no universal turnaround. Instructions normally set a question deadline and a final addendum date. AIA-MBA guidance recommends written questions no later than seven days before bid receipt, and interpretations or corrections at least four working days before bids. Many solicitations are tighter than that, so do not count on the recommendation. Send questions early, in batches as you find them, not in one pile on the last day.

6. Wait for the addendum, then act on it

A phone call, a hallway comment or an email reply from a project manager is not an interpretation of the documents. AIA-MBA’s position is that bidders should rely only on formal interpretations or corrections issued by addendum, and that addenda should be numbered and acknowledged on the bid form.

When an addendum lands:

1. Log the number, date and the RFIs it answers.
2. Update the affected drawings and specs, and retire superseded versions.
3. Adjust the estimate lines and note which addendum drove each change.
4. Send changed scope to vendors and subs so their quotes reflect it.
5. Confirm acknowledgment on the bid form before submission.

Missed addenda are one of the cheapest ways to lose a bid, which is why we built a dedicated check for missed addenda on trade bids.

7. Close the loop at debrief

Win or lose, record which questions mattered, which were answered clearly and which came back vague. That history shapes the next bid/no-bid decision. An owner whose documents routinely generate dozens of unresolved questions is carrying risk you should price or avoid.

What your RFI log should hold

A spreadsheet works if it is disciplined. Whatever the tool, each row should carry:

For teams whose bid invitations and replies arrive by email, our piece on bid email management covers how to catch invitations and keep correspondence from scattering.

Measuring pre-bid RFI performance

Raw RFI counts say little. The WisDOT benchmarking report suggests a more diagnostic set: RFIs per million dollars, percentage answered by the requested date, average response time and percentage of unjustified RFIs. Track pre-bid questions separately from post-award RFIs so solicitation quality is not buried in construction-phase volume.

The research behind that approach, by Hanna, Tadt and Whited, treats high RFI volume and slow response as performance signals. Their highway study covered more than 65 bridges and $857.3 million of construction. The takeaway is that teams can benchmark RFI performance rather than manage it by anecdote.

For your own desk, a modest version is enough:

• Questions submitted per bid
• Share answered before the cutoff
• Share that changed your price
• Bids where a missed or late answer caused an exclusion or a loss

After a handful of bids, patterns appear: certain owners, certain design firms, certain trades.

Our perspective: automation should expose ambiguity, not decide it

We built ArosBid around a simple observation. Bids are rarely lost because estimators cannot add. They are lost because a clause in the front end was missed, or two documents disagreed and nobody caught it before pricing.

So our approach combines software with human authority. The platform reads the entire set of bid documents, including front-end clauses, and flags conflicts and gaps so they can become well-formed questions. It does not submit anything on its own, and it does not decide how an ambiguity is priced. Your estimator and project manager keep authority over what is asked, what is assumed and what is submitted.

That matches what the 2025 research on RFI digitalization recommends: structured data and automated decision support, paired with explicit ownership, status controls, audit trails and human oversight. A tool that answers contractual questions without review adds risk. A tool that makes sure no ambiguity goes unnoticed and no answer goes untracked removes it.

The other half is fit. Estimating teams already live in Excel and Outlook, and we integrate with them rather than asking you to replace them. A process people have to abandon their tools to follow is a process people stop following.

— arosbid team

Where ArosBid fits

If your pre-bid questions are scattered across email and spreadsheets, our construction bid management software gives the whole bid cycle one command center: document review, compliance checks, vendor quote tracking and leveling, proposal assembly, buyout and debrief. Plans and details are on the pricing page, where you can see One Desk, The Department and The Whole Year. Estimators who work mostly in takeoff and pricing can start with our software for trade estimators.

Common mistakes to avoid

• Asking on the last day. The designer may not have time to answer, and the answer may miss the final addendum.
• Pricing a verbal answer. Get it in writing and wait for the addendum.
• Ignoring front-end documents. Bid form requirements and acknowledgment of addenda decide whether the bid is even read.
• Sending vague questions. They produce vague answers, or none.
• Not telling your vendors. A sub’s quote built on pre-addendum scope can undo your leveling. Our guide to AI bid leveling shows how to compare quotes on equal scope.
• Skipping review before submission. A final pass against your RFI log catches stragglers. The three-stage estimate review checklist is a good model.

FAQ

What is a pre-bid RFI?

It is a written question a bidder sends during the solicitation to clarify, interpret or correct the plans, specifications or bidding instructions. The answer should come back as an addendum that applies to all bidders. It differs from a post-award RFI, which comes up during construction.

How long does the RFI process take?

There is no universal pre-bid turnaround. The solicitation sets a question deadline and a final addendum date, so read those first. AIA-MBA guidance suggests written questions at least seven days before bid receipt, while post-award response times depend on the contract.

Can I rely on a verbal or emailed answer?

No. Bidders should rely only on formal interpretations or corrections issued by addendum. If someone answers informally, ask them to route the question through the official channel so the response reaches every bidder.

Does an RFI come before an RFP?

Generally the solicitation comes first, then bidders submit clarification questions through the channel it names. Exact sequence and terminology depend on the procurement method and the owner’s instructions.

Sources

• AIA A701-2018 Instructions to Bidders summary
• AIA Contract Documents: invitation to bid documents FAQs
• AIA-MBA Joint Committee: Bidding
• ODOT Construction Manual, Chapter 6
• Enhancing the RFI process through digitalization and automation (2025)
• Potential application of BIM in RFI in building projects
• WisDOT best practices: RFI benchmarks and metrics
• Hanna, Tadt and Whited: RFI benchmarks and metrics for major highway projects
• Asheville Middle School track and restroom advertisement for bid

Recommended

• When to Issue an RFQ or RFP for Construction
• Win Bids Without Cutting Scope: Value Engineering for Estimators
• Improve Bid Accuracy Without Cutting Margin: 8 Checks for Estimators
• Bid Tabulation for Estimators: 7 Steps, Unit Price Checks, Automation