A practical guide to writing a winning Etimad technical proposal
A technical proposal on Etimad is not a marketing document. It is a structured response to a published booklet, scored against an explicit rubric, by a committee that reads dozens of bids in a single sitting. If your proposal makes the committee work hard to find your answer, you lose points — even when your underlying solution is the strongest in the room.
This guide walks through the structure that consistently scores highest on Etimad tenders, why each section matters, and the common mistakes that cause otherwise capable suppliers to lose.
Why most bidders lose Etimad contracts
From tracking thousands of Saudi government tenders, the picture is consistent: most rejected bids are not rejected for price. They are rejected because the technical proposal is incomplete, generic, or misaligned with the booklet's clauses.
Evaluation committees are not looking for the most eloquent prose. They are looking for explicit alignment between every requirement in the booklet and what the supplier is offering — clause by clause, in the order the booklet presents them.
How a 1,000-point Etimad scoring model is typically split
Weights vary by tender, but the general distribution is remarkably stable across sectors. Reading the booklet's evaluation matrix before you write a single section is the single highest-leverage thing you can do.
Indicative weights based on common Etimad evaluation models. Always confirm the exact weights in your booklet.
If a section is worth 30 points and you submit a generic two-page response, you have not lost a few points — you have lost a tier. Conversely, over-investing in a 5-point criterion is wasted effort.
The standard structure of a winning technical proposal
The proposals that score highest follow a clear, predictable structure. Predictability is a feature: it makes the committee's job easier and signals that you understand how procurement works.
| # | Section | Typical length | Why it matters |
|---|---|---|---|
| 1 | Executive summary | 1 page | Sets the committee's first impression of fit |
| 2 | Scope understanding | 3–6 pages | Proves you read the booklet, clause by clause |
| 3 | Methodology & timeline | 6–12 pages | Highest-impact technical section after spec compliance |
| 4 | Team & qualifications | 4–8 pages | Translates promises into named, credentialed people |
| 5 | Past experience & references | 4–10 pages | Converts claims into evidence with documents |
| 6 | Quality assurance & risk plan | 2–4 pages | Reduces perceived delivery risk for the committee |
| 7 | Support, warranty & knowledge transfer | 1–3 pages | Closes the loop on post-delivery commitments |
1. Executive summary
One page. State your understanding of the requirement, the proposed solution at a high level, the team's headline credentials, and your differentiators. This page is sometimes the only thing every committee member reads in full — make it count.
2. Scope understanding
For each booklet clause, restate it in your own words and reference its section number (e.g., "Per Section 3.2.1 of the booklet…"). This is tedious. It is also where most committees decide whether you actually read the document.
3. Methodology and timeline
Phases, deliverables, acceptance criteria, owners, and a Gantt-style schedule. A separate guide in this series is dedicated to this section because it is the second-largest swing on most scorecards.
4. Team and qualifications
CVs (one page per key role), professional certifications relevant to the scope, and an organization chart that maps named people to phases.
5. Past experience and references
Reference projects similar in scope, sector, contract size, and duration — backed by completion certificates wherever possible.
6. Quality assurance and risk management
A short, structured risk register and the QA process you will apply during execution.
7. Support, warranty, and knowledge transfer
Warranty period, SLA targets, training plan for client staff, and documentation deliverables.
Common mistakes to avoid
Avoid
- — Reusing a previous proposal verbatim — committees notice immediately.
- — Mentioning price anywhere inside the technical envelope (instant disqualifier).
- — Generic phrases like 'extensive experience' or 'best-in-class quality'.
- — Missing one mandatory document and assuming a clarification will save you.
- — A methodology that doesn't name owners or acceptance criteria per phase.
Do instead
- — Rewrite each section against the current booklet's exact clauses.
- — Keep technical and financial envelopes strictly separate, as Etimad requires.
- — Replace claims with numbers: '12 similar projects since 2020, total value SAR 84M'.
- — Build a mandatory-documents checklist and verify it before submission.
- — Tag every deliverable with an owner, a date, and a measurable acceptance test.
The author's pre-submission checklist
Run this checklist 24 hours before the submission deadline. If any item is unchecked, do not submit.
- Every booklet clause is referenced by its section number in the proposal.
- All mandatory certificates (Nitaqat, contractor classification, Local Content) are valid past the contract period.
- Methodology lists owners, acceptance criteria, and dates for every deliverable.
- Reference projects map to the current scope by sector, size, and duration.
- No price, discount, or commercial term appears anywhere in the technical envelope.
- Saudization rate at the project-team level is stated explicitly with a written commitment.
- Risk register has at least 6 risks with mitigation owners.
- Document version, date, and a 'prepared for [client]' line appear on every page.
A short, real-world example
A mid-size IT integrator we work with was bidding on a SAR 12M government workplace modernization tender. Their first draft scored 71/100 in our internal review:
- 30/30 on technical compliance
- 12/20 on methodology (no owners per phase, no acceptance criteria)
- 9/15 on past experience (5 references, only 2 truly comparable)
- 10/10 on Saudization, 10/10 on local content
- 0/10 on financial alignment (a price line had been left in the technical file)
After three targeted rewrites — adding owners and acceptance per phase, swapping references for the three closest comparable projects, and removing the price line — the same proposal scored an estimated 92/100. The bid was awarded.
The takeaway is not that the team got lucky. It is that the gap between a 71 and a 92 is almost always mechanical: structure, evidence, and discipline rather than new content.
How Technical Proposal helps
Our tool extracts every requirement from the Etimad booklet automatically, proposes the full proposal structure clause by clause, and drafts each section in formal Arabic backed by your company's data. Three AI evaluation agents — Legal, Business, and Technical — then score the draft against a Saudi-procurement-style rubric and surface every gap as a one-click rewrite. The result: a coherent, requirement-aligned proposal ready for review in hours rather than days.