Download the bid tabulation template
XLSX
Bid tabulation template (Excel)
Header block, 17 columns, offered, compliance and price columns for three bidders, drop-downs, Not comparable rows in red and Clarify rows in amber, frozen header row, filters and a How to use sheet.
CSV
Bid tabulation template (CSV)
The example rows as plain CSV (UTF-8), for Google Sheets or any other tool.
Both files are free under CC BY 4.0, with no form to fill in. The XLSX opens in Excel, Google Sheets, LibreOffice and Numbers. The CSV carries the table only; the header block is in the XLSX.
What it is for and who uses it
Offers for engineered equipment rarely cover the same scope. One bidder leaves out a line, another prices documents separately, a third offers a different certificate type. A bid tabulation shows those differences row by row before anyone compares totals. For the method, see the bid tabulation guide.
- Procurement and package engineers at EPC contractors and end users, who build the tabulation and recommend an award.
- Manufacturers buying castings, forgings, actuators or instruments from their own suppliers.
- Bid engineers at equipment makers, who use it to see how their offer will be levelled against competitors.
The tabulation sits next to the technical bid evaluation (TBE). The TBE decides which offers are technically acceptable. The tabulation levels scope, price and terms across them.
Header block
| Field | Example |
|---|---|
| Project | Example Gas Compression Station, Phase 2 (fictional) |
| Buyer | Example EPC Contractor Ltd (fictional) |
| RFQ no. | RFQ-EX-3105 Rev 0 (fictional) |
| Material requisition | MR-VAL-001 Rev 1 |
| Governing specification | PS-VAL-001 Rev 2 |
| Bid tabulation no. | BT-EX-3105 |
| Revision | A |
| Date | 2026-10-06 |
| Currency | USD |
| Delivery terms (Incoterms) and place | FCA supplier works |
| Bidder A | Example Bidder A (fictional), offer dated 2026-09-28 |
| Bidder B | Example Bidder B (fictional), offer dated 2026-09-29 |
| Bidder C | Example Bidder C (fictional), offer dated 2026-09-25 |
| Prepared by | Procurement lead |
| Checked by | Package engineer |
Example rows: three offers for valve package RFQ-EX-3105
| Item | Requirement line | Bidder A | Bidder B | Bidder C | Levelling note | Status |
|---|---|---|---|---|---|---|
| 1 | Ball valve, trunnion-mounted, 6 in, ASME Class 600, RF flanged, gear operated; PEEK seats | Figure A-TB-600; PEEK seats (Complies): 81000 | Figure TB-600-6; RPTFE seats (Deviation): 74400 | Figure C-T6-600; PEEK seats (Complies): 86700 | No price adjustment. If the RPTFE seats are not accepted, Bidder B to confirm its PEEK option: no price change, 2 weeks longer. | Clarify |
| 2 | Ball valve, floating, 2 in, ASME Class 600, RF flanged, lever operated | Figure A-FB-600 (Complies): 9200 | Figure FB-600-2 (Complies): 8600 | Figure C-F2-600 (Complies): 9900 | None. | Like for like |
| 3 | Gate valve, 8 in, ASME Class 300, RF flanged, handwheel | Figure A-GV-300 (Complies): 14800 | Figure GV-300-8 (Clarification): 13900 | Figure C-G8-300 (Complies): 15600 | None until Bidder B confirms the impact test temperature. | Clarify |
| 4 | Check valve, dual plate, 6 in, ASME Class 600, wafer | Figure A-DC-600 (Complies): 6100 | Not offered | Figure C-D6-600 (Complies): 6500 | Bidder B does not make this valve. Add 6500 to Bidder B (the highest price offered by the others) or buy the line separately. | Not comparable |
| 5 | Commissioning spares | Seat and seal kits per tag (Complies): 2600 | Seat and seal kits per tag (Complies): 2300 | Seat and seal kits per tag (Complies): 2900 | None. | Like for like |
| 6 | Documentation to the VDRL, including the final data book | Per VDRL (Complies): Included | Per VDRL; data book electronic only (Clarification): Included | Per VDRL (Complies): 4000 | None. Bidder C prices documents as a separate line; the others include them. | Like for like |
| 7 | EN 10204 type 3.2 certificates for pressure-containing parts | Type 3.2 (Complies): Included | Type 3.1; type 3.2 as a priced option (Deviation): Not included | Type 3.2 (Complies): Included | Add 3000 to Bidder B: its own option price for type 3.2 certificates. Inspector fees by the buyer in all three offers. | Levelled |
| 8 | Pressure tests witnessed by the buyer | Included; 10 working days' notice (Complies): Included | Included; 10 working days' notice (Complies): Included | Included; 5 working days' notice (Clarification): Included | None. Ask Bidder C to confirm the notice period the RFQ asks for. | Clarify |
| 9 | Delivery, FCA supplier works: 24 weeks or better | 24 weeks (Complies) | 26 weeks (Deviation) | 22 weeks (Complies) | No price adjustment. Bidder B is 2 weeks late against the required date. | Clarify |
| 10 | Quotation validity: 90 days | 90 days (Complies) | 60 days (Deviation) | 90 days (Complies) | Ask Bidder B to extend validity to 90 days. | Clarify |
| 11 | Payment terms as the RFQ conditions | Accepted (Complies) | 30% advance payment requested (Deviation) | Accepted (Complies) | Not priced here. Finance to say whether an advance payment is acceptable and at what cost. | Clarify |
| 12 | Warranty period as the RFQ conditions | Accepted (Complies) | Accepted (Complies) | Accepted (Complies) | None. | Like for like |
| Total as quoted | 113700 | 99200 | 125600 | Before levelling. Bidder B's total leaves out line 4 and the type 3.2 certificates. | Not comparable | |
| Levelled total | 113700 | 108700 | 125600 | Bidder B: plus 6500 (line 4) and 3000 (line 7). Open clarifications are not priced. | Levelled |
In the file, each bidder has separate offered, compliance and price columns. It also has Section, RFQ reference, Qty and Remarks columns. Bidder B looks cheapest as quoted, but it left out line 4 and priced type 3.1 certificates, so two adjustments are added before the totals are compared. Every example value is invented: the project, customer, bidders, purchase order, prices and every document, certificate, serial and report number do not exist. Standards are named but not quoted.
Columns and what to write
| Column | What to write |
|---|---|
| Item | Line number. Keep RFQ line numbers for the RFQ lines, then add rows for scope and commercial terms. |
| Section | Technical, Scope or Commercial (drop-down). |
| Requirement line | What every bidder was asked to offer, in one line. This is the baseline all three are compared against. |
| RFQ reference | The RFQ line, requisition section or specification clause the row comes from. |
| Qty | Quantity and unit, where the row is priced. |
| Bidder A / B / C: offered | What the bidder offers against the line: model, material, term or value, from its offer and deviation list. |
| Bidder A / B / C: compliance | Complies, Clarification, Deviation, Not offered or Not applicable (drop-down), as the technical evaluation found it. |
| Bidder A / B / C: price | Extended price for the line in the tabulation currency, or Included or Not included. Leave blank on rows that carry no price. |
| Levelling note | What you add, remove or ask so the three offers cover the same scope, and where the figure comes from. |
| Status | Like for like, Levelled, Clarify or Not comparable (drop-down). Not comparable rows turn red; Clarify rows amber. |
| Remarks | Clarification numbers, or anything the approver needs to know. |
Row status values
| Status | Meaning |
|---|---|
| Like for like | All bidders offer the same scope on this row. The prices compare as they stand. |
| Levelled | One or more offers differed, and you have added or removed a stated amount so the row compares fairly. |
| Clarify | You cannot compare the row until a bidder answers a question. Raise the clarification and note its number. |
| Not comparable | A bidder left the row out or offered something different, and no fair adjustment is agreed yet. |
How to use the template
- Fill in the header block: RFQ number and revision, requisition, governing specification, currency, delivery terms and the three bidders with their offer dates.
- Add one row per RFQ line, keeping the RFQ line numbers. Then add rows for scope items the offers treat differently (spares, documents, certificates, witnessed tests) and for the commercial terms.
- Write the requirement line once, as the RFQ states it. Every bidder is compared against that baseline, not against another bidder.
- For each bidder, enter what is offered, the compliance status from the technical evaluation and the extended price. Write Included or Not included where there is no separate price.
- Where offers differ in scope, write a levelling note: the amount you add or remove and where it comes from, such as the bidder's own option price. Do not level a row on a guess; set it to Clarify and ask.
- Set the status of each row. Not comparable rows turn red and Clarify rows amber.
- Add a Total as quoted row and a Levelled total row under the table. Keep both, so the approver sees what was adjusted.
- Close every Clarify row in writing before you recommend an award, and file the answers with the tabulation.
Before and after the tabulation
- Issue the enquiry with the RFQ template. Its supplier columns come back in the same order as the tabulation rows.
- Score technical acceptability with the technical bid evaluation (TBE) template, then carry each compliance status into the tabulation.
- In OdysseyGPT's Tender & Quotation module, Technical Bid Evaluation (beta) compares supplier offers against one requirement baseline, with each finding cited to its page. Tools marked beta are open on request, and we onboard each team ourselves.
See how OdysseyGPT reviews a tender
Tell us how your team reviews tenders today. We can walk through an example together.
