How to Showcase Company Experience That Convinces Etimad Committees
The reference and team sections are where most bidders volunteer the most material — and lose the most points. A 60-page experience appendix containing 40 references is not stronger than a tight 20-page appendix containing the 5 most relevant ones. Committees do not score volume; they score relevance and evidence.
This guide walks through how to choose, organize, and present past work and team credentials so the committee can verify your fitness in minutes rather than hours.
How committees actually read the experience section
In our scoring work we observe a consistent pattern: the committee opens your reference list, looks for similarity in scope, sector, size, and duration, and stops paying attention after the first three or four entries that miss those filters. After that, even genuinely relevant references later in the list often go unread.
The implication: lead with your three most comparable references. If you have only two genuinely comparable projects, that is the message — pad with adjacent ones, but be honest about the difference.
What "relevant" actually means
A reference is genuinely relevant when it scores well across all four of these dimensions:
A reference scoring high on all four dimensions counts roughly 3× as much as one scoring on only one.
A telecom infrastructure project bid into a healthcare cybersecurity tender will score low even if the contract value matches. The committee weights sector and scope match more heavily than size.
A reference-project template that scores
Use the same template for every reference. Predictability helps the committee read fast.
| Field | What to write |
|---|---|
| Client name and type | "Ministry of X (government)" — attach completion certificate |
| Contract value | SAR figure; note if multi-year |
| Contract duration | Start and end dates; flag if ongoing |
| Your role | Prime, subcontractor, or consortium member; % share of value if relevant |
| Scope of work | 4–6 bullets, mapped to deliverables relevant to the current tender |
| Outcomes delivered | Measurable: % uptime achieved, days saved, users trained, savings % |
| Team continuity | Names of key people on this past project who will work on the new one |
| Verification contact | Client-side reference with name, role, and contact (with permission) |
Presenting team credentials
Team credentials are evaluated on three things: relevance to the scope, currency of certifications, and continuity (people who actually exist and will actually work on the project).
A team CV template
- One page per key role (PM, Solution Architect, Lead Engineer, QA Lead, etc.)
- Photo, name, role on this project
- 3–5 most relevant past projects with one-line descriptions
- Certifications relevant to the booklet (PMP, ITIL, CCNA, ISO lead auditor, etc.)
- Short statement of what the person specifically will do on this engagement
Certifications: relevance over volume
Listing 30 certifications dilutes the impact of the 5 that actually matter. Highlight the certifications the booklet asks for, and the 2–3 most relevant beyond that. The rest belongs in an appendix, not the main team section.
| Booklet asks for… | Strongest evidence to attach |
|---|---|
| PMP-certified PM | Current PMP certificate (not expired) for the named PM |
| ISO 27001 audit experience | Certified Lead Auditor cert + 2 past ISO 27001 audit projects |
| Cloud architecture | Current AWS/Azure/GCP solution architect cert for named arch |
| Saudi-licensed engineers | Current SCE membership card for each named engineer |
The most common mistakes
Avoid
- — 40 reference projects, none clearly comparable to the current scope.
- — CVs that are clearly generic — same person 'Lead' on every project type.
- — Listing certifications without dates (committee assumes expired).
- — Naming people who won't actually be on the project (bait-and-switch).
- — Past outcomes stated as adjectives ('successful', 'on time') without numbers.
Do instead
- — 3–5 references that are clearly comparable, ordered by closeness of match.
- — Tailored CVs that map each person's past work to the new booklet's scope.
- — Current certificates with effective dates; replace expired ones before submission.
- — Commit named people; if they may rotate, say so explicitly with named replacements.
- — Outcomes with numbers: '99.7% uptime over 24 months', 'SAR 2.1M annual savings'.
A short worked example
A boutique consulting firm was bidding a SAR 3.2M public-sector strategy engagement. Their first reference list had 22 entries — most were private-sector tech work. They scored 8/15 on past experience.
For the rewrite, we removed 17 of the 22 entries and kept only the 5 closest matches. Each was rewritten in the template above with measurable outcomes and named team continuity. They scored 13/15 on the rewrite.
| Round | References | Avg. relevance score | Past-experience score |
|---|---|---|---|
| 0 | 22 | 41 / 100 | 8 / 15 |
| 1 | 7 | 78 / 100 | 11 / 15 |
| 2 | 5 | 92 / 100 | 13 / 15 |
Less material, more points.
How Technical Proposal helps
We store your company file and reference projects in a private workspace, then automatically pick the most relevant past work for each new booklet — drafting professional write-ups that map each reference to the current tender's clauses. The Technical and Business evaluation agents flag references that don't carry their weight and recommend which to drop. CVs are similarly tailored per-bid so each person's narrative maps to the role the booklet describes.