What a bid tabulation is
A bid tabulation, or bid tab, puts each bidder in a column and each requirement or price item in a row. The evaluator fills in what each bidder offered, so differences are visible at a glance. In construction the term often means a price comparison across subcontractors. In engineered-equipment buying it usually has a technical side and a commercial side.
Bid tabulation and technical bid evaluation
| Technical bid evaluation (TBE) | Bid tabulation | |
|---|---|---|
| Question it answers | Is this offer technically acceptable? | How do acceptable offers compare on price, scope and terms? |
| Rows | Technical requirements from the requisition and specification | Price items, scope items, exclusions, delivery and terms |
| Typical owner | Discipline engineer | Procurement or cost engineer, with engineering input |
| Output | Acceptable, acceptable with clarifications, or not acceptable | A levelled comparison and a recommendation |
Some companies combine both in one sheet; others keep them separate. See the technical bid evaluation guide and the free TBE matrix template.
How evaluators build a bid tab
- Fix the baseline: the requisition, specification and datasheet revisions every bidder quoted against, plus any addenda.
- List the rows: each price item and option, then scope items such as spares, documents, inspection, painting and packing.
- Fill in each bidder's offer from the price schedule, the technical offer and the deviation list.
- Mark each row as included, excluded, deviated or unclear for each bidder.
- Send clarification questions for unclear rows, and update the tab with the answers.
- Level: add an estimated cost for what each bidder excluded, so the totals compare like for like.
- Record the assumptions behind every adjustment, and have a second person check them.
What bid levelling means
Levelling, or bid equalisation, adjusts each total so it covers the same scope. If one bidder excludes third-party inspection and another includes it, the evaluator adds an estimate to the first. If a deviation would cost the buyer money, such as a longer delivery or extra site work, that may be loaded too. The levelled total, not the quoted total, is what gets compared.
For suppliers: how to come out well in the tab
- Quote against the evaluator's rows: answer every price item and scope item in the buyer's format.
- State exclusions plainly. An unclear scope item is often loaded at the evaluator's worst-case estimate.
- Declare deviations in a clear technical deviation list, with the cost of withdrawal, so the evaluator does not guess.
- Answer clarification questions fast and in writing; late answers can leave a loading in place.
- Keep the priced and unpriced offers consistent, so the technical and commercial tabs agree.
Common bid tab mistakes
- Comparing bidders who quoted against different specification revisions.
- Treating a silent row as included.
- Levelling with no written assumptions, which makes the recommendation hard to defend.
- Mixing technically unacceptable bids into the price comparison.
Where OdysseyGPT fits
On the evaluator's side, Technical Bid Evaluation (beta) checks each supplier offer against one requirement baseline, records declared and undeclared technical deviations with citations and drafts clarification questions. It never picks a winner, and it does not level prices; commercial terms review is not a separate tool today. On the supplier's side, Document Review checks your offer against the customer's specification before you send it, and the Deviation Register (beta) tracks each declared deviation to the customer's decision. For evaluator platforms, see Mintmesh RUDY alternatives.
These tools are in beta
Technical Bid Evaluation and the Deviation Register are in beta. You can request access, and we onboard each team ourselves. Every finding cites the page, sheet or cell it came from, and your engineers decide what to do with it.