The line that disqualifies the bid
A mandatory site visit is four words in a front-end section and an entire pursuit on the floor. Here is why it goes missing.
There is a kind of loss that never gets a post-mortem, because there is nothing to review. You did not lose on price. You did not lose on scope. You were never eligible, and the whole estimate was spent before anybody noticed.
Mandatory pre-bid attendance is the cleanest example. The requirement is usually one sentence, sitting in the front end, in a section nobody on the estimating team was assigned to read.
Attendance at the pre-bid conference is mandatory. Bids from firms not represented at the conference will not be considered.
The invitation email did not mention it. The bid form does not reference it. The drawings certainly do not. It is one sentence, and it outranks every number in the set.
Why it hides
- It lives in the front end, the part of the set an estimator reads last and a takeoff never touches at all.
- It sits inside a hundred pages of boilerplate that everybody has read a version of before, which is exactly what makes skimming feel safe.
- It is often issued by addendum, after the pursuit has been scoped, assigned, and started.
- It contains no number. Nothing about it triggers the reflexes that a dollar figure triggers.
The last one is the real reason. Estimating attention follows money, and it should. The problem is that eligibility clauses are written in the same flat register as the paragraph about submitting three copies in a sealed envelope, and they carry a consequence that no pricing decision on the job can match.
Eligibility clauses read like boilerplate and cost like a whole bid.
What finding it actually takes
The honest answer is unglamorous: reading every page of every document, including the ones that never contain a price, and then reading every addendum against what you already read. There is no shortcut that is also reliable, which is why this is the first thing ArosBid does rather than the impressive thing it does later.
Intake recognizes the invitation, opens the pursuit workspace, and reads the set — front end included, addenda included — looking specifically for the class of statement that governs eligibility rather than cost. Mandatory attendance. Registration deadlines. Prequalification. Bonding thresholds. Licensing. Every route by which a compliant, competitive number gets thrown out unopened.
Every finding is cited. Not “a mandatory site visit was detected,” but the section, the paragraph, and the page, so the estimator can open the document and read the sentence themselves. A finding you cannot verify in ten seconds is a finding your team will eventually stop reading.
And then it stops
What ArosBid does next is draft the calendar invitation and put it in front of a person. What it does not do is send it. The requirement was found by a machine; the decision to act on it stays with the estimator, and the mail connector will not release anything that does not cite that decision.
There is no plan on our pricing page that changes that. It is not a setting.