When you spot an ambiguity in bid documents before the deadline, submit a written pre-bid RFI that cites the project number, the exact sheet or spec section, and attach a plan callout. This creates a paper trail, protects your number, and can trigger an addendum that changes the scope for every bidder, not just you.
TL;DR:
- Submitting a detailed pre-bid RFI with project and sheet references helps create a clear paper trail and can trigger official addenda affecting all bidders.
- RFIs should be filed immediately during takeoff, drafted with a unique ID and concise questions, then tracked through official channels with timestamps.
- Prioritize urgent RFIs affecting the bid number, responding within 24 hours, and escalate unaddressed critical questions before bid closing.
- Use a standardized log to record all RFIs, referencing specific issues and examples, to support estimating and resolve disputes later.
- Regularly treat pre-bid RFIs as risk management tools that prevent scope creep and protect your pricing integrity through documented clarifications.
Table of Contents
- How to create, submit, and track a pre-bid RFI
- What belongs in every pre-bid RFI
- Where pre-bid RFIs go and what timing to expect
- Deciding which RFIs need to jump the line
- A one-page checklist and three example RFIs
- Why I treat every pre-bid RFI as a risk control, not paperwork
- How SubAscent keeps your RFIs and bid tracking in one place
- FAQ
- Sources
How to create, submit, and track a pre-bid RFI
A pre-bid RFI only works if it follows the same four steps every time. Skip one and you either lose the paper trail or miss the window entirely.
- Capture the issue during takeoff. When you hit an ambiguous detail, screenshot it immediately and write a one-line note on what's unclear and why it affects pricing.
- Draft the RFI. Include an internal tracking ID, the project name and number, the exact sheet or spec callout, and a question specific enough that a design team can answer it in one reply.
- Submit through the official channel (planroom tool, portal, or designated email) and log the timestamp, the recipient, and the confirmation you got back.
- Follow up and watch for the addendum. Set a reminder a few days before bid close. If you haven't heard back, escalate. Never assume a verbal or informal answer is binding; wait for the official written response.
This routine takes maybe ten minutes once you've done it a few times, and it's the difference between a documented clarification and a verbal promise nobody can prove later — learn more about managing subcontractors in a design-build project here. Our guide to drafting concise, answerable RFIs covers how to phrase the question itself so you get a usable answer instead of a vague one.
What belongs in every pre-bid RFI
Design teams and procurement officers answer RFIs faster when the fields are consistent and complete. Leave one out and you'll get a request for clarification instead of an answer, which burns days you don't have.
Every pre-bid RFI needs:
- Project name and project ID or bid number
- Your internal RFI ID (with a PRE- prefix to separate it from construction-phase RFIs)
- Submitter name and direct contact information
- A short question title and the exact question, written so it can be answered in one or two sentences
- The referenced sheet number, spec section, or zone
- An attachment, usually an annotated PDF snip of the detail in question
A sample template for an electrical sub might read: "PRE-04, Sheet E-5, Panel LP-2: Conduit schedule appears omitted for circuits 14 through 18. Please confirm if this is intentional or if a revised schedule will be issued." A plumbing version: "PRE-02, Spec Section 22 11 00: Pipe insulation thickness not specified for domestic hot water risers above grade. Please clarify minimum R-value." An HVAC example: "PRE-07, Sheet M-3: Mechanical riser conflicts with structural beam at Grid Line 6. Please confirm routing or issue revised riser diagram."
Pro Tip: Tag every pre-bid RFI with the PRE- prefix in your internal log so you can pull a clean audit trail if a dispute comes up after award.
Where pre-bid RFIs go and what timing to expect
Submission channels vary by project, and each one comes with its own rules about turnaround and what counts as an official answer.
- Reply to the bid invitation email. Common on smaller private jobs, but slow and easy to lose track of.
- Planroom Q&A tools. Most commercial planrooms route your question to the design team and log the response for all bidders to see.
- Direct GC contact. Works for informal clarifications, but a verbal or email-only answer from a GC doesn't carry the same weight as a published addendum.
- Public agency portals. State DOT projects typically run a formal Pre-Bid Q&A process. TxDOT's job aid documents a portal that opens within 21 days of the letting date, requires specific form fields, and typically posts answers within about 48 hours for every bidder to see.
The practical rule: capture the official public response or addendum, not the private email thread. If a GC tells you something on a call, ask them to confirm it in writing through the same channel everyone else can see. Our piece on what a bid invitation actually includes walks through where these Q&A windows typically get set during the bid package release.
Deciding which RFIs need to jump the line
Not every RFI carries the same weight, and treating them all as equally urgent means the one that actually matters gets lost in the queue.
- Urgent (answer needed within 24 hours): Conflicts that affect your base bid number, like a structural clash or a missing quantity that changes your material count.
- High (answer needed within 3 days): Spec ambiguities that affect scope but not necessarily price, like an unclear finish detail.
- Normal (answer needed by bid close): Clarifications that are helpful but won't change your number either way.
When something lands in the urgent tier, copy procurement directly, ask that the answer be issued as a public addendum rather than a private reply, and log every timestamp. If you get silence, document the lack of response in writing before bid close. A known ambiguity you never asked about can shift the risk of that assumption onto you as the bidder, so the log matters as much as the question.
Pro Tip: If a critical RFI goes unanswered within your window, consider submitting a formal protest or flagging it in your bid cover letter rather than guessing and hoping.
A one-page checklist and three example RFIs
A pre-bid RFI workflow only sticks when it's simple enough to use on every job, not just the complicated ones.
Keep a single tracking sheet with these columns: RFI ID, date submitted, channel, question summary, referenced sheet or spec, assumed scope if unanswered, and final disposition (answered, addendum issued, or no response). That log feeds directly into your estimate and becomes evidence later if a change order dispute comes up.
| Trade | Issue | Example RFI |
|---|---|---|
| Electrical | Missing conduit schedule on panel sheet | Confirm if circuits 14-18 conduit schedule omission on E-5 is intentional |
| Finish carpentry | Trim detail not specified at transition | Confirm trim profile and material at room transition, specified sheet |
| HVAC | Riser conflicts with structural beam | Confirm routing or revised riser diagram at Grid Line 6, Sheet M-3 |
Store completed pre-bid RFIs with your estimate file, not in a separate email folder. If the job gets awarded, that log becomes your first line of defense on any change order tied to the original ambiguity. Our field RFI submittal guide for foremen covers how to carry this same discipline into the construction phase once the job starts.
Why I treat every pre-bid RFI as a risk control, not paperwork
Routinely filing pre-bid RFIs stopped more scope creep on my jobs than any contract clause ever did. Once an ambiguity is on record and answered, there's no argument later about who assumed what. It's a small habit that pays for itself the first time it saves you from eating a change order.
— Dave
How SubAscent keeps your RFIs and bid tracking in one place
Our software tracks pre-bid RFIs alongside bid invitations, PDF takeoffs, and mobile tools for foremen, helping ensure nothing gets lost between a planroom email and your estimate.
If you're tired of hunting through email threads for the answer to an RFI you filed three weeks ago, visit SubAscent to see how job and bid management software built for specialty trade subs handles it.
FAQ
What is a pre-bid RFI?
A pre-bid RFI is a written request for clarification submitted before bid close when a bidder finds an ambiguity, omission, or conflict in the bid documents. It typically references a specific sheet or spec section and asks for an answer that can be published as an addendum for all bidders.
What are the 5 steps in the bidding process?
Most bid cycles follow invitation, document review and takeoff, pre-bid RFI and clarification, bid submission, and award. The pre-bid RFI step is where ambiguities get resolved before pricing is finalized.
What is an RFI procedure?
An RFI procedure typically follows a status-driven lifecycle: draft, submit, review, answer, and close, with a manager selecting and distributing the official response. This structure applies to both pre-bid and construction-phase RFIs.
How does prebid work?
The prebid phase covers the window between a bid invitation and the submission deadline, when bidders review documents, do takeoffs, and submit RFIs on anything unclear. Research on pre-bid RFI analysis found it can improve project risk prediction by up to 15% when ambiguities are addressed before bidding instead of after award.
Sources
- Uncertainties prevailing in construction bid documents and their impact on project pricing through the analysis of prebid requests for information
- Txdot
- Process RFI (Autodesk Build) — RFI lifecycle and manager actions