The Scope on a Bid Is Vague: Decision Tree

Why this matters

A vague bid is where money quietly leaks out of a commercial job before you ever swing a tool. If the documents do not say who owns a piece of work, silence tends to resolve against the sub who bid low without qualifying it. The winning bidder is often not the one who guessed cheapest; it is the one who priced the clear work honestly and fenced off the unclear work in writing. This tree is how you handle a bid where the scope has holes, without either eating the gap or pricing yourself out of the job.

Start here: is it truly vague, or just unfamiliar to you?

Before you treat scope as ambiguous, make sure the answer is not already in the set and you simply have not found it.

• Check document precedence. When a spec and a drawing conflict, the contract usually names an order of precedence, and the higher document wins. Read that clause before assuming a real conflict.
• Confirm you have every addendum. An addendum issued during bidding changes the scope, and bidding off an outdated set creates ambiguity that is not really there.
• If the answer exists in the set, go price it. If it is genuinely missing or the documents contradict each other with no precedence resolving it, continue.

Ask the question in writing: file an RFI

An RFI (Request for Information) is a written question to the GC or design team that becomes part of the project record. It is your primary tool and your protection.

• Reference the specific drawing, detail, or spec section, and ask one clear question. Where it helps, propose the options you see so the answer is a simple pick.
• Submit before the bid deadline, not during construction, when you still have leverage to price the answer.
• If you get a written answer, bid to it and keep the RFI in your file. The answer now binds everyone, not just you.

If the deadline passes with no answer

This is common. You still have to bid, so you bid the gap on your terms, not theirs. Qualify the bid in writing with three tools, and price the unknown with two more.

Attach your assumptions, exclusions, and clarifications to the bid itself. A gap you named in writing is a gap you do not automatically own. A gap you stayed silent on is one a court, or a GC, will hand to you.

Price the risk instead of guessing at it

For a genuinely unknown quantity, do not bury a guess in a lump sum where you carry all the variance.

• If the item is defined but the quantity is uncertain, bid it as a unit price so the final cost follows the actual count. The quantity risk moves to the GC.
• If the item is loosely defined, carry an allowance and state clearly what the allowance covers and what triggers an extra.
• Either way, the unknown is now visible and bounded, not a silent liability inside your number.

When to no-bid and walk

Sometimes the right move is to decline. Walk when all three of these are true at once:

• The ambiguity covers a large share of the work, so you would be guessing at real money.
• The GC will not clarify before the deadline.
• The contract is lump-sum with no unit-price relief, and the risk-shifting clauses (broad catch-all scope, no-damage-for-delay) compound the exposure.

Winning a job you are set up to lose money on is not winning. A clean no-bid beats a bid you will fight to break even on.

Recap

1. Confirm the scope is genuinely vague, not answered by precedence or an addendum.
2. File a specific RFI before the deadline and bid to any answer you get.
3. With no answer, qualify the bid with written assumptions, exclusions, and clarifications.
4. Price unknowns as unit prices or allowances, never a buried guess.
5. No-bid when the ambiguity is large, unclarified, and stuck in a lump sum.

References

• CSI MasterFormat and standard bid-document precedence conventions
• Trade-standard practice for RFIs, bid qualifications, and unit pricing
• See related: Reading Bid Documents; Scoping a Commercial Bid So You Don't Eat the Difference