Quick answer: The technical bid proves eligibility and delivery capability without disclosing price; the financial bid states the evaluated commercial offer in the prescribed format. They must be separated for submission but reconciled internally.
In a two-cover or two-packet tender, the buyer evaluates capability before opening price. A bidder can fail by leaking price into a technical attachment, by putting a technical qualification in the BOQ, or by promising a solution that its cost model does not fund.
The right approach is controlled separation with one internal source of truth. Technical and commercial teams work from the same scope baseline, then package their outputs according to the portal and tender instructions.
What belongs in the technical bid
The technical pack commonly includes legal and eligibility records, past experience, financial-capacity proof, technical compliance statement, solution or methodology, project plan, staffing, OEM authorisation, licences, quality and test certificates, declarations, bid security proof and signed tender forms.
Organise the pack in the evaluator’s clause order. State “complies” only where evidence supports the claim and identify the offered model or method clearly. Avoid vague brochures that cover many configurations. Where deviations are permitted, disclose them in the prescribed schedule rather than hiding them in narrative text.
What belongs in the financial bid
Use the buyer’s BOQ or price schedule without changing protected structure, formulas or file format. Enter base price, tax, freight, unit rates, totals, discounts and optional items exactly as requested. Check whether the portal expects tax-inclusive or tax-exclusive values and how arithmetic discrepancies will be treated.
Do not insert conditions such as “price subject to exchange rate” in an unapproved cell. A conditional financial bid can be rejected or evaluated adversely. If a commercial term is unacceptable, raise it before bidding or record a permitted deviation in the correct schedule.
Prevent price leakage
Remove prices from technical brochures, old purchase orders, commercial quotations, calculation screenshots and file metadata where relevant. Experience proof may contain contract value because eligibility requires it; that is different from revealing the current quoted price. Follow the tender’s treatment of historical values.
Use separate controlled folders and a final price-leak scan. PDF search for currency symbols and terms such as “unit price”, “quotation” and “total”. Ensure file names do not disclose the amount. On portals, upload each file only to the intended cover.
Reconcile before submission
Build an internal scope-cost bridge. Every technical promise—staff count, uptime, delivery, warranty, spare, training, travel, report or integration—must have a cost owner. Every financial line must map to a deliverable. Review quantity, unit of measurement and tax across both packs.
Freeze the technical baseline before final commercial approval. If a last-minute technical change occurs, reopen the cost sheet rather than assuming the impact is immaterial. A jointly signed reconciliation sheet is one of the strongest controls in a high-value bid.
Practical checklist
- Organise technical evidence in clause order.
- Identify the exact offered model, method and exclusions.
- Use the unaltered prescribed BOQ.
- Confirm tax and discount treatment.
- Scan technical files for current-price leakage.
- Map every technical promise to cost.
- Upload each file to the correct cover and verify.
Frequently asked questions
Can the technical bid contain past contract values?
Yes where needed to prove experience or turnover, subject to tender instructions. It should not reveal the current financial offer.
Can a bidder modify the BOQ to add a missing item?
Usually not. Raise the issue through clarification. Changing a protected BOQ structure or formula can make the bid unreadable or non-responsive.
What if the technical team changes the solution after price approval?
Reopen the commercial model and approval. Otherwise the financial bid may not cover the final promise.
Final takeaway
Separate the two bids for evaluation, unite them for governance. A clean technical pack proves compliance; a clean financial pack follows the formula; an internal reconciliation protects margin and execution.
Related reading
- Pre-Bid Meetings and Clarifications: Ask Better Questions, Reduce Risk
- Corrigendum Tracking: The Tender Habit That Prevents Rejection
- Bid/No-Bid Framework for Government Tenders: A Practical Scorecard
Official references
- General Financial Rules, 2017 — updated to 31 January 2026
- Department of Expenditure — Procurement Manuals
- CPPP special instructions for online bid submission
- GeM all bids
Editorial note: This article is educational, not legal or bid-specific advice. Tender conditions, portal workflows, thresholds and government instructions can change. Always read the latest tender document, corrigenda, applicable office memoranda and portal guidance before acting.