Pre-Bid Clarifications: When to Ask and When to Walk

Not every bad bid starts with a bad estimate.

A lot of them start earlier, when the plans are fuzzy, the scope is half-baked, and your team is left guessing what the GC actually wants. That is where pre-bid clarifications come in.

Used well, clarifications protect margin, schedule, and sanity. Used poorly, they turn into unpaid detective work on a job you probably should not have touched in the first place.

Here is the blunt version: ask when the answer can sharpen the bid. Walk when the whole job still feels slippery after that.

Clarifications are not a red flag. Guessing is.

This should not be controversial, but here we are.

AIA’s bidder guidance makes it clear that competitive bid procedures are built to handle requests for clarification, interpretation, and substitutions, along with addenda that answer those questions. Asking smart pre-bid questions is part of the process, not a sign that you do not know what you are doing.

Autodesk makes a similar point from the estimating side. A strong estimate should clearly spell out assumptions and exclusions so the number can be reviewed properly and trusted.

That is the point of clarification. Not to be difficult. Not to prove a point. To stop hidden assumptions from turning into visible pain later.

Subs already know the real problem: bad-fit jobs eat time

Riffle’s subcontractor survey found that 73% of subs named filtering suitable projects as their top bidding challenge. Among firms with 11 to 30 employees, 95% said filtering was the number one issue. The same survey also found that smaller firms struggle with scope clarity, while owners focus heavily on whether a project is truly a good fit.

That tells you something important.

Pre-bid clarification is not just about filling in blanks on a plan set. It is also a qualification tool. Sometimes the question is not “What does detail 5 mean?” Sometimes it is “Is this job even worth us touching?”

If the answer is no, that is a win. It just does not feel like one in the moment.

Ask when the answer changes your number, risk, or delivery plan

A clarification is worth sending when the answer will materially affect one of three things:

Your number
If the scope is unclear enough to change labor, material, equipment, or exclusions, ask.

Your risk
If there is confusion around responsibilities, phasing, access, long-lead items, or coordination, ask.

Your delivery plan
If schedule assumptions, manpower, alternates, or sequencing are still up in the air, ask.

This lines up with what GCs told Riffle in the GC survey report. The top drivers in bid decisions were profit margin, project timeline, client relationship, and resource availability. The same report says GCs struggle with accurate cost estimation, time pressure, data organization, and determining scope quickly and accurately. It also says the fastest way for subs to build trust is with clear assumptions, exclusions, and schedule-safe alternates.

So if a question affects price, timing, or resource risk, ask it. That is not overthinking. That is protecting the bid.

Walk when the confusion is systemic, not incidental

Here is where some teams get stuck.

They keep asking question after question because they want to stay in it. But there is a difference between one missing detail and a bad bid environment.

You should think hard about walking when:

• The plans are incomplete and key scopes are still moving
• Addenda keep changing core assumptions late
• Nobody can clearly answer ownership between trades
• The GC is slow, vague, or inconsistent before bid day
• You are being asked to absorb obvious design holes with no room for proper qualification

That is not a clarification problem. That is a project setup problem.

And those jobs have a nasty habit of staying messy after award.

Industry guidance on preconstruction has made the same point in a broader way: the earlier teams identify gaps, assumptions, and constructability issues, the less pain gets locked into the job later. If the gaps are still everywhere right before bid, do not fool yourself into thinking the chaos ends after award. It usually just gets a new folder name.

GCs do not want perfect. They want clear.

Riffle’s GC survey is pretty blunt on this.

GCs say subcontractors miss original estimates at least some of the time, and only 21% say subs rarely miss. They also said they choose the number they can trust, not just the lowest one. Their biggest frustrations include scope clarity issues, slow response times, inconsistent communication, missing alternates, and poor follow-through.

That gives subs a pretty simple playbook.

If you ask a clarification, make it sharp.
If you submit with assumptions, make them obvious.
If the answer never comes, qualify it plainly or walk.

Do not bury risk in the number and hope it behaves.

A simple rule that actually works

Here is a clean way to handle it:

Ask if one answer can make the bid more accurate, cleaner, or safer.
Qualify if the issue is limited and you can define your assumption clearly.
Walk if the project still depends on too many guesses after that.

That last one matters. There is no trophy for pricing a mess perfectly.

What this means for subcontractors

The best bidding teams are not the ones that answer every ITB with blind confidence. They are the ones that know when to press for clarity and when to protect their time.

Every unanswered question has a cost. Sometimes that cost is margin. Sometimes it is schedule. Sometimes it is a week of effort on a job that was never clean enough to pursue.

The smart move is not always to bid harder. Sometimes it is to qualify better. Sometimes it is to walk earlier.

Riffle helps subcontractors track bid opportunities, manage clarifications, and keep the right jobs moving without the usual inbox chaos.

If your team is tired of sorting ITBs, chasing answers, and pricing jobs with too many moving targets, start a free trial at rifflecm.com.