Writing a Government Tender Offer: How the Technical and Financial Proposals Fit Together

A government bid is not a single document. It is two offers that have to agree with each other: the technical offer that proves you can deliver the work, and the financial offer that prices it. The most common reason a capable company loses is not a weak idea or an uncompetitive price - it is a bid package that is incomplete, internally inconsistent, or non-compliant with the tender's rules. Writing the offer well begins with understanding how the two halves fit together.

This guide covers the anatomy of a government bid - the two-envelope structure, what belongs in each offer, how they are evaluated, and how to keep them telling one consistent story.

Two offers, one bid - the two-envelope structure

On Etimad, the technical offer (العرض الفني) is submitted separately from the financial offer (العرض المالي). They are evaluated in sequence: the technical offers are opened and examined first, and the financial envelopes of technically rejected bids are returned unopened. Only bids that pass the technical stage have their prices opened and evaluated. The implication is decisive - the technical offer is the gate, and the financial offer wins the bid among those who clear it.

What goes in the technical offer

The technical offer answers one question: can you deliver this work, to standard, on time? It typically contains:

• Your understanding of the scope and objectives.
• The technical approach and methodology - how you will actually do the work.
• A work plan and schedule - phases, milestones, and a realistic timeline.
• The team and key personnel, with roles and CVs.
• Relevant experience and similar projects, with evidence.
• Quality, health-and-safety, and risk management where the work calls for it.
• Compliance with the specifications, and the required certificates.

What goes in the financial offer

The financial offer prices exactly what the technical offer promises. It typically contains:

• The priced bill of quantities (جدول الكميات), against the approved items.
• Unit and total prices, entered in both figures and words.
• Full compliance with the pricing rules - no altered, struck-out, or unpriced items.
• VAT handled exactly as the tender's instructions require.
• The initial guarantee (الضمان الابتدائي), submitted with the offer.

Keep the two offers aligned

The classic failure is a mismatch between the two: a technical offer promising a senior team and an elaborate method that the price plainly cannot fund, or a bill of quantities that does not match the scope the technical offer describes. Evaluation committees notice these gaps, and they erode trust in the whole bid. Your methodology, your team, your schedule, and your price must describe the same project - one consistent story told twice, once in capability and once in cost.

Compliance is the baseline, not the goal

Meeting every mandatory requirement is what gets you evaluated; it does not, by itself, win. The bids that win are compliant first and then differentiated in the few areas that actually carry points. So map every requirement into a checklist before you write a word - turn the tender into a compliance map - and only then invest your best effort where the evaluation criteria reward it.

Frequently asked questions

A winning bid reads as one coherent argument across both offers: here is how we will deliver, and here is what it costs - consistent, compliant, and competitive. Our team writes both halves to the evaluation criteria and keeps them aligned through final submission, so the package never undercuts itself. It is the discipline behind our Golden Warranty.