Saudization and Local Content in Etimad Bids: What You Can't Afford to Miss
Saudization and local content are not optional preferences on Etimad. They are formal scoring categories, often worth 10–20 percentage points in total — enough to decide the award between two bidders whose technical and financial scores are otherwise identical. Treating them as paperwork to staple at the end of the bid is the most common reason capable suppliers lose to comparable competitors.
This guide walks through what each preference actually requires, how points are calculated, the documents you must attach, and the most common mistakes that cost suppliers the win.
Why these preferences matter so much
Vision 2030 explicitly directs procurement to favor higher Saudization rates and higher in-Kingdom content. Etimad implements this by adding bonus points to the evaluation matrix, often heavily enough to flip the outcome of close tenders.
The implication: even a strong technical and financial proposal can lose to a slightly weaker bid that scored higher on these preferences.
How the points are typically distributed
Distribution varies by tender. Always confirm the exact weights in the booklet's evaluation matrix.
Saudization: what you must prove
Saudization scoring on Etimad is more nuanced than just attaching a Nitaqat certificate. Reviewers check four things:
- A valid Nitaqat certificate issued by the Ministry of Human Resources, with the band color (Platinum, High Green, etc.) and overall Saudization rate.
- The Saudization rate within the project team specifically, which can differ from the company-wide rate. Many booklets reward the project-team rate, not the company rate.
- A written commitment to maintain the rate for the full contract duration, signed by an authorized signatory.
- A gradual localization plan for key technical roles when the booklet asks for it (often required on multi-year IT, healthcare, and energy contracts).
A project-team Saudization table
| Role | Headcount | Saudis | Saudization % | Notes |
|---|---|---|---|---|
| Project Manager | 1 | 1 | 100% | Saudi PMP-certified PM |
| Solution Architect | 1 | 0 | 0% | Knowledge transfer to Saudi understudy |
| Senior Engineers | 4 | 3 | 75% | Two SCE-licensed |
| Operations & support | 6 | 5 | 83% | Tier-1 100% Saudi |
| Total | 12 | 9 | 75% | Above contract minimum |
This single table answers the committee's three implicit questions: who is on the team, what is the Saudi share, and is it sustainable.
Local content: how points are earned
Local content is governed by the Local Content & Government Procurement Authority. Etimad scoring typically rewards four contributions:
- A current Local Content Certificate issued by the Authority, showing the bidder's local content score percentage.
- In-Kingdom spend with local suppliers and subcontractors, with a planned ratio for the contract.
- Use of Saudi-made products where equivalent specifications are available.
- Investment in knowledge transfer and training for Saudi nationals during the contract.
A local content commitment table
| Category | Planned for this contract | Verification |
|---|---|---|
| Local Content Certificate score | 64% (current cert attached) | LCGPA-issued certificate, valid 12 mo. |
| In-Kingdom subcontractor spend | ≥ 70% of subcontractor budget | List of named local subcontractors |
| Saudi-made products | All routers and access points | Vendor list with Saudi origin proof |
| Training hours for Saudi nationals | 480 hours over contract | Training plan with named trainees |
The most common mistakes
Mistakes that cost points
- — Attaching an expired Nitaqat certificate.
- — Submitting a sister company's certificate instead of the bidder's.
- — Stating only the company-wide Saudization rate.
- — Claiming a local content percentage without an Authority certificate.
- — Burying the localization plan as one paragraph in a generic appendix.
Defensible practice
- — Replace certificates that expire before contract end before submitting.
- — Use the bidding entity's own certificate, even if the parent has a stronger one.
- — State both company and project-team rates; back team rate with a named table.
- — Attach the LCGPA Local Content Certificate with current effective date.
- — Dedicate a standalone section to the localization and training plan.
A worked example: how 8 points decided an award
Two bidders we worked with submitted on the same SAR 18M operations tender. Their technical scores were within 2 points of each other. Their financial offers were within 4%. The decision came down to preferences:
| Criterion | Supplier A | Supplier B |
|---|---|---|
| Technical | 64 / 70 | 62 / 70 |
| Financial alignment | 9 / 10 | 9 / 10 |
| Saudization (project team rate) | 4 / 7 | 7 / 7 |
| Local Content Certificate | 3 / 6 | 5 / 6 |
| Saudi-made products | 2 / 3 | 3 / 3 |
| Knowledge transfer plan | 1 / 2 | 2 / 2 |
| Training hours for Saudi nationals | 1 / 2 | 2 / 2 |
| Total | 84 | 90 |
Supplier A had the stronger technical solution. Supplier B won by 6 points, all of them earned in the preference categories — and most of them earned through better documentation rather than better operational reality.
A pre-submission documents checklist
- Nitaqat certificate is current and remains valid past the contract end date.
- Certificate is in the bidding entity's name, not a sister company.
- Project-team Saudization rate is stated explicitly in a named-team table.
- Written commitment letter signed by an authorized signatory.
- Local Content Certificate is current and attached.
- In-Kingdom subcontractor list is named and specific to this contract.
- Saudi-made products list is included where applicable.
- Localization and training plan is a standalone section, not buried in an appendix.
How Technical Proposal helps
We auto-detect Saudization and local content clauses in every booklet, remind you to attach the required certificates with their expiry dates, and draft a dedicated section that highlights your commitments and rates in the format that aligns with Etimad's evaluation model. The Legal evaluation agent verifies that every required document is named, current, and in the right entity's name before submission.