Reading Etimad: how technical scoring is actually weighted

On Etimad, most government tenders are decided in the technical envelope, before a single price is opened. Bidders who read the scoring model first tend to win; bidders who treat it as fine print and lead with a polished narrative tend to lose well. The difference is rarely effort. It is knowing where the points are before the bid team starts writing.

The technical envelope is a gate, not a scorecard

Saudi public procurement runs on a two-envelope evaluation. Technical and financial submissions go in together, but they are opened in sequence: the technical envelope is assessed first against published criteria, and the financial envelope is opened only for bidders who clear the technical threshold set for that tender. Fall short on the technical score and your price is never seen. The design keeps price from colouring the technical judgement: the panel marks the work without knowing what you have bid.

That one mechanism should change how the bid is planned. A technical score is not a quality mark collected alongside a competitive price. It is the gate that decides whether you are in the competition at all. A keen price behind a weak technical submission is a sealed envelope no one opens.

Clearing the threshold is not the same as scoring well. The threshold puts you in the room; the margin above it decides where you rank once price is weighed in. Aiming only to pass is how a bidder ends up technically compliant and commercially beaten.

The weighting is published, and it moves

There is no fixed split between technical and financial scoring across Etimad. The weighting is set per tender, published in the tender documents, and it moves with the category and the buyer. A complex works or advisory tender may load most of the total onto technical merit; a straightforward supply tender may let price carry most of the weight. The document sets it out explicitly; there is no house rule to lean on.

That interaction matters more than most bid teams allow for. Where technical carries the majority of the marks, a lower price does not rescue a mediocre submission, and a higher-scoring technical bid can beat a cheaper one outright. How the two envelopes then combine into a final ranking is itself defined per tender, not a rule you can carry over from the last one.

So treat every tender’s model as its own fact. Read the weighting, confirm it, and build the bid to it before you assume the previous one still holds.

Where the points actually sit

Inside the technical envelope, the score breaks into criteria and sub-criteria, each carrying its own allotted marks. The evaluation table tells you plainly what the buyer will reward: methodology, relevant and evidenced experience, the proposed team, the delivery programme, local content and Saudization, each with a defined share of the total. Where local content and Saudization apply, they are scored on what you can prove, not on what you assert.

Evidence is where good firms lose avoidable points. Experience that is not documented in the format the tender specifies — certificates, references, completion records — is scored as if it never happened. The evaluator marks the file in front of them, not the reputation behind it.

Most losing technical submissions are not badly written. They are written to a template instead of to the table. A strong methodology section earns nothing if the marks sit in experience and evidence. The work is unglamorous and it wins: map every requirement to the points it carries, and put the weight of the proposal where the score actually is.

The mechanics that lose bids before scoring begins

A technically strong bid can still be eliminated before it is read. Registration and contractor classification have to match the tender’s activity and grade. Bid bonds and guarantees have to be valid, correctly formatted, and held for the required period, and the offer itself has to stay valid for as long as the tender demands. Where a bilingual submission is required, a gap in either language is a gap in the bid.

Deadlines on Etimad are fixed; a submission complete a minute late did not arrive. The clarification window is the one chance to close an ambiguity in the requirements before it costs marks, and it closes well ahead of submission. None of this earns a point. All of it can render a bid non-responsive and cost the whole thing. The teams that win treat the platform mechanics with the same seriousness as the technical content, because the evaluator applies both without sympathy.

Read together, the scoring tells you something before you spend a single week of the bid team: whether this tender is winnable at your cost base, or whether you are about to earn a respectable second place. That is the real use of reading the model — a bid or no-bid decision made on evidence rather than appetite.

It is also where the reading pays for itself. Across more than fifteen government tenders managed last year, on Etimad, NUPCO and semi-government procurement, our submissions averaged 95 out of 100 on technical score. That number is what reading the model first buys you.

If a live tender is in front of you and the weighting is not yet clear, that is the conversation worth having.