A technical bid evaluation, or TBE, is the discipline engineer's line-by-line check of each vendor's technical offer against the specification, carried out before price is compared, ending in a documented compliance verdict for every bidder.
This is a reference for the instrument or project engineer running or checking a TBE on an instrument, valve, or control-system package. It covers what the TBE proves, what it checks against, the columns of a TBE sheet, a worked comparison, and how the technical evaluation gates the commercial one. It is not a guide to procurement contracts or commercial terms.
Key takeaways
- The TBE proves one thing: which bids are technically compliant with the specification. Price is not part of it.
- It checks each offer against the datasheet, one requirement per row, with a comply, deviate, or note verdict.
- The technical evaluation gates the commercial one. Only technically acceptable bids go forward to the commercial bid evaluation (CBE).
- Deviations are the output that matters. Each one is dispositioned as accepted, rejected, or raised as a technical query.
- The datasheet is the reference the whole TBE hangs on. A vague datasheet produces a vague TBE and a weak comparison.
What the TBE is for
The technical bid evaluation exists so that the commercial decision is made among genuinely comparable offers. Two quotations for the same flow transmitter can differ in measurement principle, wetted material, and hazardous-area certification, and the cheaper one is often cheaper because it left something out. The TBE surfaces that difference on one row before anyone looks at the price.
It is read by more than the engineer who writes it. Procurement reads the acceptable and not-acceptable verdicts to know which bidders proceed. The lead engineer reads the deviations to sign off the technical risk. The vendor reads the technical queries and answers them. Because it carries a verdict that removes bidders from contention, the discipline is evidence: every mark traces back to a datasheet line and a stated offer, never to a preference.
What the TBE checks against
The requirement column of a TBE is the instrument datasheet, backed by the material requisition and the standards the datasheet cites. Each field on the datasheet, from measured variable through process connection, becomes a row the bidder must answer. A complete datasheet gives a clean, defensible evaluation; a thin datasheet forces the engineer to invent the requirement mid-evaluation, which is where inconsistent verdicts creep in.
The instrument tags in the package come from the instrument index, so the TBE and the index carry the same tag numbers. That is what lets a reviewer confirm that every instrument in the requisition was actually evaluated, and that no tag was quietly dropped from a bidder's scope.
The TBE sheet columns
Every TBE shares the same spine: the requirement, the offers side by side, and the verdict.
| Column | What it carries |
|---|---|
| Item / spec reference | The requirement line, keyed to the datasheet field or specification clause. |
| Requirement | The specified value, taken verbatim from the datasheet. |
| Offered (per bidder) | Each bidder gets a column; the value they quoted for that line. |
| Compliance | Comply, deviate, or note, marked per bidder per line. |
| Deviation disposition | Accepted, rejected, or raised as a technical query. |
| Technical query | The question issued to the bidder where the offer is unclear. |
The compliance and disposition columns are the ones that carry weight. A row marked deviate with no disposition is unfinished work: the evaluation is not closed until every deviation is accepted, rejected, or answered.
A worked comparison
The values below are synthetic, but they show the shape. This is one flow-transmitter line, FT-101, evaluated across two bidders against the datasheet.
| Requirement | Datasheet | Bidder A | Bidder B |
|---|---|---|---|
| Measurement principle | Coriolis mass | Coriolis mass (comply) | Differential pressure (deviate) |
| Calibrated range | 0 to 40,000 kg/h | 0 to 40,000 kg/h (comply) | 0 to 40,000 kg/h (comply) |
| Turndown | 20 to 1 | 25 to 1 (comply) | 8 to 1 (deviate) |
| Wetted material | 316L stainless | 316L (comply) | 316L (comply) |
| Hazardous-area cert | Zone 1 IIB T4 | Zone 1 IIB T4 (comply) | Zone 1 IIC T4 (comply) |
| Output / protocol | 4 to 20 mA with HART | 4 to 20 mA with HART (comply) | 4 to 20 mA only (deviate) |
| Process connection | 3 inch flanged | 3 inch flanged (comply) | 3 inch flanged (comply) |
Bidder B is the kind of offer the TBE exists to catch. It meets the range and the connection, so a quick read looks compliant, but it changed the measurement principle and dropped the digital protocol. Both deviations get dispositioned: the principle change is rejected because the duty needs mass flow, and the missing protocol becomes a technical query. Only after that does the package go to commercial comparison, and by then Bidder B may no longer be in it.
Technical before commercial
The separation of technical and commercial is deliberate. In the common two-envelope arrangement the bidder submits the technical offer and the priced offer separately, the engineer evaluates the technical envelope with no sight of price, and procurement opens the commercial envelope only for bidders who cleared the TBE.
| Technical bid evaluation | Commercial bid evaluation | |
|---|---|---|
| Question | Does the offer meet the specification? | Which acceptable offer is best value? |
| Owner | Discipline engineer | Procurement |
| Reads from | Datasheet, requisition, standards | Price, delivery, payment terms |
| Order | First; gates the next step | Second; only among technically acceptable bids |
Keeping price out of the engineer's view is what makes the technical verdict defensible. When both are judged together, the cheap non-compliant bid tends to acquire compliance it never earned.
How it reconciles with the package
The TBE sits between three documents that must agree. Every tag it evaluates appears on the instrument index. Every requirement it checks comes from a datasheet. And the accepted deviations feed back onto the datasheet as the as-purchased record, so the instrument that arrives on site is documented against what was actually bought, not against the original specification alone. Reconciling the three is what catches the instrument that was requisitioned, quoted against, and then silently changed in scope during bidding.
A starting point
If you are setting one up, the technical bid evaluation reference covers the term and where it sits in the procurement sequence, and the instrument datasheet fields map each requirement row back to the form it comes from. Build the datasheet properly first: it is the requirement the whole evaluation is measured against, and a TBE is only ever as sharp as the datasheet behind it.