How to Structure a Technical Proposal (العرض الفني) That Scores

The technical offer (العرض الفني) is the gate every bid must clear, and in some tenders it carries most of the points. Yet it can be written as a wall of company boilerplate - history, vision, generic capability statements - that answers questions no evaluator asked. A technical offer that scores is built the opposite way: around the evaluation criteria, section by section, so a reviewer working through the scoring sheet can find, and award, every point you have earned.

This guide gives you a section-by-section skeleton for the technical offer, and the principle that should govern every page of it. For what the tender booklet itself sets, see Etimad technical proposal requirements; for the wider writing process, see how to write a winning technical proposal.

Start from the evaluation criteria, not a template

The tender documents state how the technical offer will be scored - the criteria and their weights. That is your table of contents. Etimad does not show the weights to private-sector users, so if the booklet does not state them, ask before the inquiry deadline. Build your sections in the order and emphasis of those criteria, so the evaluator finds each answer exactly where they expect it. If the booklet prescribes a structure or a maximum number of pages, follow it first and map each criterion to a heading inside that structure. A reviewer who has to hunt through your document for the point you are making may miss it, and a point that is not found cannot be awarded. Structure is not presentation; it is points.

A section-by-section skeleton

Build your technical offer on this spine, then tune it to the specific criteria:

1. Understanding of the scope and objectives - prove you grasp the actual need and its context, not a generic restatement of the title.
2. Technical approach and methodology - how you will deliver, step by step, tied directly to the scope. Its weight varies by tender, so check the criteria in the booklet.
3. Work plan and schedule - phases, milestones, dependencies, and a realistic timeline.
4. Team and key personnel - roles, responsibilities, and CVs that match what the method demands.
5. Relevant experience - similar projects, with evidence the evaluator can verify.
6. Quality, HSE, and risk management - where the nature of the work calls for it.
7. Compliance and required certificates - the mandatory items, clearly evidenced and easy to check.
8. Deliverables - what the buyer receives, stated against the scope. Do not add reservations or conditions to the offer: raise any ambiguity through an inquiry before the inquiry deadline.

Write to be scored, not to be admired

Every paragraph should earn a point. In practice that means:

• Answer the criterion explicitly - name it, then respond to it.
• Lead with the point, then give the evidence - do not bury the answer at the end.
• Use the buyer's own terms and the scope's language, not your internal jargon.
• Make compliance checkable - tables, cross-references, and a clear map to each requirement.
• Cut boilerplate that earns nothing; length without relevance earns no extra points.

Common technical-offer mistakes

• Ignoring the weighting - spending pages on a low-weight section and rushing the high-weight one.
• A generic methodology not tied to this scope - it makes a bid look copy-pasted.
• Unsupported claims - assertions of excellence with no evidence behind them.
• Inconsistency with the financial offer - promising more than the price can fund.
• Missing a mandatory requirement - the avoidable way a strong offer is excluded before scoring.

Frequently asked questions

A technical offer that scores is not the longest or the most polished - it is the one structured so the evaluator can award every point without searching for it. Our team builds each technical offer around the tender's own criteria, working from a compliance matrix and reviewing the offer before final sign-off.