Five fatal mistakes when analyzing a tender booklet
Most failed Etimad bids are not failures of writing. They are failures of analysis — the work that happens before anyone opens a Word document. A proposal built on a misread booklet will score badly no matter how polished its prose, because the proposal answers questions the committee did not ask.
This guide walks through the five mistakes we see most often in tender analysis on Etimad, why they cost points, and the structured fix for each.
Why analysis quality predicts your score
Across the bids we analyze, a clear pattern shows up: teams that spend more time on structured booklet analysis score consistently higher, even when their underlying solution is the same.
The good news: every one of the mistakes below has a mechanical fix. None of them require a stronger solution — only a stricter process.
1. Skimming the annexes
Many suppliers read the main booklet and skim the technical annexes. Annexes are where the precise specifications live: SLA tables, acceptance criteria, schemas, integration matrices, and the technical scoring breakdown. A 2-line annex bullet often carries more scoring weight than a full page of the main booklet.
The fix: build a single requirements register that pulls clauses from every document in the package — main booklet, annexes, attachments, and any addenda issued before the deadline. Tag each row with its source document and page number.
2. Ignoring the technical scoring matrix
Every Etimad tender publishes a technical and financial scoring matrix. Treating it as background reading instead of the master plan is the most expensive analysis mistake we see.
The right move: re-allocate your drafting hours in proportion to the weights. If sector experience is 30 points and innovation is 5 points, your effort split should look the same.
When teams spend equal time on every section, low-weight criteria absorb effort that should go to high-weight ones.
3. Not flagging mandatory requirements
Some requirements are flagged "mandatory" or "compliance" in the booklet — meaning failure to meet them disqualifies the bid before scoring even begins. These are pass/fail. They include things like:
- A valid Nitaqat certificate at the right band
- The correct contractor classification grade
- Specific professional memberships (SCE, SOCPA, etc.)
- A signed commitment letter, sometimes notarized
- Bid bond / performance guarantee in the prescribed format
| Mandatory item | Common failure mode | Fix |
|---|---|---|
| Nitaqat certificate | Expired before contract end date | Renew or re-issue before submission |
| Contractor classification | Wrong grade or category for the scope | Confirm grade against the booklet's stated minimum |
| Bid bond | Issued by a non-approved bank | Use only banks listed in Etimad's approved roster |
| Saudization commitment letter | Boilerplate text, no project-team rate | State the project-team Saudization rate explicitly |
| Local Content certificate | Sister-company certificate attached | Use the bidding entity's own certificate |
4. Conflating core scope with optional add-ons
Many booklets define a core scope and a list of optional add-ons that the buyer may or may not exercise. Two failure modes are common:
- Bundling add-ons into the core scope — inflates your price unnecessarily and makes you uncompetitive against bidders who priced cleanly.
- Ignoring add-ons entirely — costs you points in the technical evaluation when reviewers expect them to be addressed.
The fix is to maintain a clear scope map:
Wrong
- — Single price line that mixes core scope and add-ons.
- — Methodology that treats every requirement as in-scope.
- — Resource plan staffed for everything in the booklet at full capacity.
Right
- — Core price + a separate, itemized add-on price list.
- — Methodology marks each add-on phase as 'if exercised by client'.
- — Resource plan shows base team for core scope and surge plan for add-ons.
5. Overlooking the payment schedule
Payment terms decide whether a contract is profitable in practice, even if it looks profitable on paper. Some Etimad booklets tie payments to specific milestones; others use percentage-based completion; a few hold a meaningful retention until final acceptance.
| Payment model | What it means for cash flow |
|---|---|
| Milestone-based | Cash arrives when the milestone is formally accepted (slow). |
| Monthly progress invoices | Smoother cash flow; usually requires a measurable progress report. |
| Final-acceptance lump sum | Almost all cash arrives at the end; needs strong working capital. |
| Retention 5–10% until warranty end | Funds tied up for months past delivery — price it in. |
The fix: model the payment schedule as part of your pricing. If the booklet implies 90 days from delivery to payment, your financing cost belongs in the price.
How to run a structured booklet analysis
Use this short workflow for every new Etimad tender:
- Read the entire package end-to-end once, without writing anything.
- On the second pass, extract every requirement into a single register with source document and page number.
- Tag each row: mandatory / scored / informational.
- Map scored rows to the technical evaluation matrix and compute your projected score.
- Flag every gap — missing capability, missing certificate, missing reference — as a separate task with an owner.
- Re-allocate drafting hours in proportion to scoring weights.
- Have a second pair of eyes review the requirements register before drafting starts.
A short example: how the same booklet produced a 30-point swing
Two suppliers we worked with bid on the same SAR 8M operations tender. Their solutions were technically similar. Their analysis processes were not.
| Step | Supplier A | Supplier B |
|---|---|---|
| Time spent on booklet analysis | 4 hours | 16 hours |
| Annexes read in full | 1 of 4 | 4 of 4 |
| Requirements register built | No (notes only) | Yes (87 rows) |
| Mandatory checklist owner | Implicit | Named individual |
| Final technical score | 64 / 100 | 91 / 100 |
The 27-point gap was almost entirely created during analysis, not drafting.
How Technical Proposal helps
We read the full Etimad booklet — annexes included — and extract a structured requirements register: mandatory criteria with page references, the technical and financial scoring matrices, the core-vs-add-ons split, and the payment schedule. We then propose a drafting plan that addresses every item in proportion to its weight, so you do not lose points to incomplete analysis.