The Difference Between Technical and Financial Proposals in Saudi Government Tenders

Saudi government tenders submitted in two files, which the current Regulations make mandatory from an estimated value of SAR 5 million (an entity may require it below that), split evaluation into two phases: technical and financial. Check the tender booklet to see which applies to your tender. Understanding this split and how each is scored will fundamentally change how you prepare.

Structure: The Technical Proposal. Your technical proposal answers: "Can you deliver the scope? Do you understand the work? Have you done similar work before?" It covers the technical documents the tender booklet requires, for example your methodology, timeline, previous experience and work team, together with the required certificates and licences. It does not mention price. The technical proposal lives or dies on feasibility, clarity, and proof of prior delivery.

Structure: The Financial Proposal. Separately, you submit a financial proposal. The booklet sets its contents, so expect the priced bill of quantities, the payment schedule, and the initial guarantee. Price the items exactly as the entity issued them: amendments, reservations and struck-out items lead to exclusion, so build any risk allowance into your unit prices. The financial proposal is evaluated after, and only if, the technical proposal passes. This is crucial: you are not scored on price until your technical merit is established.

Evaluation Order. In a two-file tender, evaluation proceeds as follows: (1) Compliance check: are you eligible and have you submitted all required documents? (2) Technical evaluation: do your methodology, team, and timeline meet the evaluation criteria? (3) Financial evaluation: of the technically qualified bidders, who offers the best value under the formula in the tender booklet? Only the technically qualified proposals move to financial evaluation.

Implication 1: Technical Fitness Comes First. Your primary goal in the technical proposal is not to win on cost, but to be in the technical winner pool. If you are disqualified or fall below the minimum technical score, your financial offer is never opened, so your price is irrelevant. Focus relentlessly on addressing every evaluation criterion with evidence and detail. Generic, light technical proposals lose.

Implication 2: Price Cannot Rescue a Rejected Technical Offer. A tempting assumption: "We will win on price even if our technical proposal is mediocre." It depends on the tender. Where the entity uses weighted technical criteria, it sets a minimum technical score, and a proposal below it is excluded even if it quotes the lowest price. Above that minimum, the technical and financial scores are combined using the weights in the tender booklet, so in price-heavy categories a competitive price can offset a lower technical score. Meet the technical bar first, then check the booklet to see how much weight price carries.

Implication 3: Once Technical is Approved, Price Becomes Critical. When bidders pass technical evaluation, the committee evaluates their financial offers by the method set in the tender booklet: a weighted formula that combines the technical and financial scores, or, for routine work, the lowest price among compliant offers. The financial score rewards the lowest price (or the lowest life-cycle cost where the booklet uses it); other adjustments, such as the SME and local-content preferences, apply as the booklet states them. If you are technically equivalent to competitors, your price will determine the winner.

Strategic Implication 1: Separate Your Writing Teams. Your technical and financial proposals serve different purposes and audiences. Your technical team (project managers, engineers) should own the methodology section. Your financial team (accountants, estimators) should own the cost breakdown. These are different skills. Do not merge them into a single document or hand them both to a single writer.

Strategic Implication 2: Use Different Evidence. In your technical proposal, lead with past projects, team credentials, and process controls. In your financial proposal, lead with complete, accurate pricing of the bill of quantities and unit rates you can justify from similar work; any risk allowance belongs inside those rates. Technical credibility comes from depth and case studies. Financial credibility comes from structure and benchmarking.

Strategic Implication 3: Coordinate Without Confusion. Your technical methodology and financial estimate must align. If your technical proposal claims you will deliver in 12 months with a team of 6 people, your financial proposal must show costs consistent with that plan (salaries, overhead, materials for a 12-month 6-person scope). Misalignment between the technical and financial offers is a risk to you: a price that cannot fund your plan strains delivery after award, and an abnormally low price can be questioned by the committee.

Red Flag Check: Before submitting, read both proposals side-by-side. Do they tell the same story? Does your budget make sense for your proposed timeline and team size? Are your quoted deliverables 100% aligned between the two proposals? Inconsistencies are costly.

Final Thought: Treat your technical and financial proposals as two halves of a single argument. The technical half says, "Here is how we will succeed." The financial half says, "Here is what it costs." Both must be compelling, consistent, and Saudi-context aware.