Insights · Bidding
Two days: the response-time standard that keeps you on the list
An estimator sends an invitation to bid and starts a clock. What the estimator expects to hear, when, and what the silence costs. A workable standard for a sub without a full-time estimator.

When an estimator sends an invitation to bid, a clock starts, and the sub usually does not know it is running.
The estimator has a bid due to the owner on a date. Working backward from that date, they need sub bids in hand two or three days before, time to level them, and time to chase the scopes that came back thin. Every invitation they send is a slot in that plan. A sub that goes quiet leaves the slot empty until it is too late to fill, and the estimator remembers.
What the estimator expects
Within two days: an acknowledgment. “Received, we will bid it” or “received, we will pass on this one.” Either answer is fine. The estimator can plan around a pass; they cannot plan around silence. Many bid platforms make this a button, and the estimator’s dashboard shows who has not clicked it.
By the bid date: the number, complete. The scope with inclusions and exclusions, the attachments the invitation asked for, in the format it asked for, by the time it asked for. A bid that arrives an hour late on bid day may not be opened. A bid that arrives on time without the insurance certificate gets a phone call the estimator did not have time to make.
Within a day of a question: an answer. Estimators call during leveling to confirm a scope or clarify an exclusion. A sub that returns the call the same day is a sub whose number the estimator can use. One that returns it in three days has been replaced by the second-lowest bidder’s number.
After the award, either way: nothing required, but a question helps. “What would have won it?” asked once, politely, after a loss, is how a sub learns whether it was price, scope or something on the prequalification form. Estimators answer that question more often than subs expect, because a sub that asks is a sub that will bid better next time.
What silence costs
An estimator keeps a mental list of subs who respond and subs who do not, and the second list stops receiving invitations without anyone deciding it. Three unanswered invitations is usually enough. The sub never learns this; the invitations simply stop, and the sub concludes the GC is not building anything, or that the market is slow.
It also costs the bids you do submit. An estimator leveling eight electrical bids on a Tuesday night with a Wednesday deadline weighs a bid from a sub who has been responsive differently from one who has been a chase. The number is the number, but the clarifying call that could save a scope gap goes to the responsive sub first.
Why subs go quiet
Not from rudeness. The owner is the estimator, the owner is on a roof, and the invitation came by email to an address nobody checks until Friday. Or the sub decided not to bid and saw no reason to say so. Or the invitation was for a scope the sub does not do and it went in the trash.
Every one of those has the same fix: someone whose job is the inbox and the portal, with authority to acknowledge, decline, or route the invitation to whoever prices it.
A standard a small sub can keep
For a sub without a full-time estimator, this is enough, and it is close to what the Ridgebeam desk holds a client to:
- One inbox and one portal login, checked twice a day, by a named person. Invitations arrive by email, by platform notification and occasionally by phone; all three land in the same place.
- Acknowledge within two business days, every time. Bid, pass, or “need a day to decide.” A pass is a sentence: “Thank you for the invitation; we are going to pass on this one, please keep us on the list.”
- A go/no-go that takes five minutes. Right trade, right size, right territory, a start date the crew can make, a GC you are prequalified with or can be. Two no’s and it is a pass.
- The packet ready before the bid. Insurance certificate, bonding letter, capability statement, project sheets, references, in a folder, so the bid day is spent on the number and not on the attachments.
- Submit a few hours early, because platforms go down and email bounces, and an estimator who sees a bid in the morning of bid day remembers who made their day easier.
- Return every leveling call the same day.
- Ask what would have won, once, after every loss.
Measuring it
Two numbers tell you whether the standard is being kept, and both are on a Ridgebeam client’s dashboard: the average time from invitation to acknowledgment, and the share of invitations submitted on time. The first should be under two days. The second should be every bid you said you would make.
A third number tells you whether the standard is paying off: invitations received per month from GCs you did not call that month. That is the number that grows when estimators have you on the responsive list, and it is the one the GC desk is built to move.
What this has to do with the Bid-Ready Score
Twenty of the hundred points are for the bid process, and five of those are response time: acknowledged within two days and submitted on time scores five; within a week, three; deadlines missed, zero. A sub cannot start in Pipeline without twelve of the twenty bid process points, because a desk setting six GC meetings a month for a sub that answers invitations in a week is generating invitations that go nowhere, and that hurts the sub’s name with the GCs the desk just called.
It is the cheapest five points on the form. Nothing has to be bought. Someone has to own the inbox.


