Bid invitation tracking is knowing, for every trade package on a job you are pricing, who was invited, who confirmed, who declined and why, and whose number you have in hand as bid day approaches. What follows is scope leveling: adjusting each bid for what it excluded before ranking anything. A system holds the invitation states, builds the bid tab from the scope sheet you sent, and records which number you carried.
The holes in an invitation list
Silence gets read as intent to bid
Twelve invitations go out for a trade package. Nine firms never respond. On bid day two numbers arrive, and the estimator learns at four in the afternoon that the coverage everyone assumed existed was never confirmed.
The low number is low because something is missing
One bidder came in well under the others. The reason is on page two, in a clarification excluding the fire caulking and the layout. Ranking on the submitted number without leveling for scope is how that gap becomes yours after award.
Addenda acknowledgment goes unchecked
Addendum three changed the ceiling assembly. Two of the four bidders acknowledged it. Nobody checked, and the number carried into the proposal priced a drawing set that no longer exists.
Nobody records why a firm did not bid
A subcontractor declines. The reason, an unclear scope sheet or a payment history from last year, is not captured. The same firm is invited on the next three jobs and declines each time.
Bid tab columns and the invitation status model
Two structures do the work, and they belong together because the status model is what fills the tab. One tab per trade package, never per company, and no submitted number is ever overwritten.
| Element | What it holds | Rule or status values | What it prevents |
|---|---|---|---|
| Tab: base bid as submitted | The figure exactly as it arrived | Locked once entered; adjustments live elsewhere | Losing what was actually bid |
| Tab: addenda acknowledged | A checkbox per addendum issued | A bid missing the latest addendum is not comparable | Carrying a number that priced a superseded drawing set |
| Tab: scope sheet items | One line per item you sent | Included, excluded, or not addressed | A low bid that is low because an item was omitted |
| Tab: exclusions and clarifications | The bidder’s own wording, quoted | Read verbatim; paraphrasing loses the qualifier | A clarification pushing hoisting or layout back to you |
| Tab: scope gap adjustments | Your dollar value per excluded item | Entered per item with a note on the source | An apples-to-oranges award decision |
| Tab: adjusted comparable number | Base bid plus adjustments | The only column the tab should be sorted by | Calling the low base bid the winner |
| Tab: alternates, unit prices, allowances | Priced separately, one line each | Awarded independently and carried to buyout | Alternates forgotten when the subcontract is written |
| Status: not yet invited | A prequalified firm with no invitation sent | Flags coverage risk below three invited firms | Bid day with one number in a trade |
| Status: invited, no response | Invitation sent, opened or not | Automatic follow-ups at set intervals | Reading silence as intent to bid |
| Status: intends to bid | The firm has confirmed | Counts toward coverage for that package | Counting an unconfirmed invitation as coverage |
| Status: declined | No-bid with a coded reason | Too busy, wrong size, scope unclear, bonding, payment history | Missing what repeated scope unclear replies say about your invitation |
| Status: bid received | The number logged and a tab row created | Timestamped at receipt; a late bid is marked late | Arguments afterward about when a number arrived |
| Status: non-responsive | Missing addenda acknowledgment, a form, or the bond | Flagged rather than discarded, with a chance to cure | Finding the gap after you have carried the number |
| Status: carried, then awarded | Which number went into your proposal, per package | Award recorded, declines sent to the firms that lost | Buying out against a different number than you priced |
Running a package from invitation to award
The bidder list is built from a maintained pool
Firms are held by trade, geography, and the size of work they take, with prequalification and insurance state attached. Building the invitation list becomes a filter rather than a search through old email, and it surfaces firms nobody has asked in a while.
The invitation carries the scope sheet, not just the plans
The invitation to bid goes out with the plan set link, the addenda log, the due date and time, and the scope sheet listing what you expect included. That scope sheet is the structure the bid tab uses later, which is what makes leveling possible.
Responses are captured as states, not as replies
A bidder confirms, declines with a reason, or asks a question through a short form. Each response sets the status and updates coverage. Firms that have not answered get follow-ups on a schedule that tightens as bid day approaches.
Addenda go to the invitation list automatically
When an addendum is issued, everyone with an open invitation receives it and their acknowledgment is tracked on the tab. Nobody has to remember who was invited three weeks ago.
The carried number is recorded and handed to buyout
When the proposal goes out, the system records which bidder’s adjusted number was carried per package. At award, buyout starts from that record, and the subcontract is written against the scope sheet that was leveled.
What the bid record hands off
- invitation and bid response forms — Confirmations, no-bid reasons, and number submissions come back as structured records, not email replies.
- document assembly for invitations and award letters — Invitations, addenda transmittals, and notices to unsuccessful bidders generated from the bid record.
- approval routing through award — Award decisions and buyout handoffs route with the leveled tab attached.
Is this a fit for your business?
A good fit when
- You bid work that needs coverage across several trade packages
- Your bidder list lives in one estimator’s contacts
- You have carried a number that excluded scope you then owned
- You want to know which firms decline your invitations and why
Probably not a fit when
- You self-perform nearly everything and subcontract one or two trades
- You want a takeoff and estimating package, a different category of tool
- You already run a bid platform your subcontractors are used to
What to have ready
- Your current bidder list, however it exists today
- A scope sheet from a recent job, even a rough one
- The last bid tab you built, including the hand-done parts
Questions we get asked
Do subcontractors have to create an account to respond?
No, and requiring one works against you. The invitation carries a link that opens a short form with their firm and the package already filled in. They confirm, decline with a reason, or submit a number in a few taps. Demanding a password before they can say yes or no is a barrier at the worst moment.
How is this different from the plan room we post to?
A plan room distributes documents and shows who downloaded them. It does not tell you who intends to bid, hold your scope sheet, or level numbers against it. The two work together: the plan room hosts the drawings, and the bid record tracks intent, coverage, and comparison.
Can the system compare bids for us automatically?
It assembles the tab, applies your scope gap adjustments, and calculates the adjusted comparable number. It cannot read a subcontractor’s clarification paragraph and decide what it means for your job. Leveling is estimator work. What the system removes is the assembly and the arithmetic.
What happens to the bidder list on jobs we do not win?
It stays, and it is often worth more than the job was. Who bid, who declined and why, and how their numbers compared shows which firms want your work. That record carries into the next invitation list and into prequalification.
Related
- subcontractor onboarding and prequalification
- estimate request intake and qualification
- Cognito Forms consultant and build services
- workflow automation for construction companies
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.