Before award: how to identify a contractor’s unworkable technical bid

The lowest tender price does not necessarily produce the lowest final cost, and the most polished presentation does not demonstrate the strongest delivery capability. Technical evaluation tests whether a bidder understands the scope and can translate it into a verifiable plan for resources, programme, quality and risk. An overall impression—or criteria introduced after bids have been opened—makes the decision harder to defend and the differences between bidders harder to explain.

A sound evaluation begins before bids arrive: with clear tender documents, disclosed criteria and defined evaluation responsibilities. Apply those criteria consistently, retaining the evidence, questions and answers. Separate technical and financial evaluation as required by the owner’s procedures and the applicable framework.

For government procurement in Saudi Arabia, work within the applicable Government Tenders and Procurement Law, its implementing regulations, the tender documents and the authority’s delegated powers. Private projects follow their tender documents, the owner’s policies and the proposed contract within the applicable framework. A clarification, exclusion or correction process from one procurement should not be transferred to another without checking what is permitted. This article provides an engineering review approach; it does not determine a bidder’s legal entitlement or replace the applicable procurement procedure.

First: do the tender documents support a like-for-like comparison?

An evaluation committee cannot compare bids consistently if the scope itself is unclear. Before tendering, review drawings, specifications, quantities and handover requirements, and identify permitted alternatives and mandatory requirements. A constructability review before tender can expose gaps that might otherwise lead bidders to make different assumptions.

Manage bidder questions through one controlled channel. Issue material answers and amendments to all bidders through the same formal process. Providing significant information to one bidder alone undermines the consistency of the comparison.

Build the evaluation matrix

Derive criteria from the project’s risks and objectives rather than copying a standard matrix unchanged. Relevant areas may include:

• Understanding of the scope, constraints and interfaces.
• Construction methodology, sequence and logistics.
• Programme detail and realistic production rates.
• Key personnel, relevant experience, availability and authority.
• Procurement planning and long-lead materials.
• Quality assurance, inspections and testing.
• Safety and risk management.
• Design management, coordination and BIM where applicable.
• Relevant past work and references that can be verified.
• Exclusions, assumptions and consistency with the tender documents.

For criteria assessed comparatively, establish the weighting, evidence requirements and written scoring scale before evaluation, in accordance with the tender procedure. For example, “excellent programme = 5” is not a sufficient definition. Explain what the highest score requires: an integrated sequence, milestones consistent with the contract, a clear critical path and links to resources and procurement.

These are examples of criteria, not mandatory weights or a universal scoring model. The project’s approved evaluation method determines which criteria apply and how they are assessed.

Apply compliance gates before comparative scoring

Some requirements are better treated as pass/fail conditions rather than quality scores: a required licence, security, mandatory form or acceptance of a material condition, for example. Identify these gates in accordance with the tender documents before comparing the qualitative elements.

A compliance gate should not become a reason to exclude a bid for a formal omission that the applicable procedure permits the bidder to clarify or complete. Equally, the evaluator cannot assume that a material deficiency may be corrected. Follow the applicable framework, tender documents and delegated authority, and record the basis of the decision consistently.

Read the contractor’s methodology critically

A useful methodology connects site constraints to specific actions. Limited site access should be reflected in logistics, delivery phases and lifting arrangements. Where part of a facility remains operational, the bid should address isolation, temporary diversions, sequencing and communication.

Look for consistency between sections. A short proposed duration may be unsupported by the organisation chart, equipment or procurement plan. A detailed programme may contradict the construction methodology. Such internal conflicts matter more than the appearance of the document.

Test the programme and resources together

Review start and finish dates, milestones, reviews and approvals, procurement, testing and handover. Then test the logic of the relationships, durations, calendars and constraints. A programme that hides delay within broad activities or relies heavily on imposed constraints may not provide a reliable monitoring baseline.

Compare resources with production rates, quantities and available work fronts. Large numbers are not automatically an advantage. More labour without suitable work fronts, supervision or logistics may reduce productivity. The objective is an achievable plan, not the largest stated workforce.

Names and equipment lists alone are insufficient. Check commitments and availability, possible allocation of the same resources to concurrent projects, and whether key subcontractors and manufacturers can meet the proposed timeframes. Where a bid appears unusually low, seek a documented explanation of resources, productivity, procurement and exclusions through the permitted tender process. Do not automatically accept or reject it merely because its price is low.

Control questions and clarifications

Consolidate uncertainties in a formal clarification register. Seek explanations without allowing a change to the substance of a bid where the rules prohibit it. Retain the questions and answers and reassess the affected criterion through the established process.

Meetings and oral presentations can help explain a proposal, but they should not replace written evidence or earn scores unsupported by the evaluation requirements. Maintain a clear distinction between clarifying the submitted bid and permitting a new submission.

Analyse exclusions and technical-commercial risks

A low price may depend on exclusions that reduce the scope or transfer unacceptable risks to the owner. Prepare an item-by-item comparison of exclusions and explain their potential effects on time, cost and quality.

Do not create apparent price equivalence through uncontrolled estimated additions. The purpose is to expose the basis of comparison and support an informed decision under the authority’s procedure. Any permitted adjustment or treatment must follow that procedure, rather than an evaluator’s improvised rule.

Use governance to reduce bias

• Apply the organisation’s conflict-of-interest and confidentiality declarations.
• Hold a calibration session before evaluation so assessors understand the scoring scale consistently.
• Have assessors evaluate independently first, then discuss significant differences using evidence.
• Record the reason for each score, not only the number.
• Control bid and clarification revisions and their dates.
• Document the final recommendation, remaining risks and any permitted pre-award conditions.
• Do not introduce new criteria or evidence requirements after opening bids. Record non-compliance and its treatment, and give bidders equal opportunities for clarification where the procedure permits them.

Warning signs of an unworkable bid

• A compressed duration unsupported by programme logic or production rates.
• Key staff proposed for several concurrent projects without explaining their availability.
• Procurement planning that omits approval, manufacture, shipping or the required-on-site date.
• Exclusions dispersed through appendices that remove essential scope.
• A generic methodology that ignores site constraints or continuing operations.
• Extensive labour resources without the work fronts, equipment or supervision to support them.
• Past experience that does not match the project’s complexity or cannot be verified.

A warning sign calls for examination through the approved procedure. It is not, by itself, an automatic exclusion rule.

Common evaluation mistakes

• Using broad criteria that do not distinguish between bids.
• Changing weights after seeing the results.
• Awarding scores for reputation without the evidence required in the submission.
• Reviewing the programme separately from resources and procurement.
• Overlooking exclusions because they appear in a distant appendix.
• Confusing clarification with permission to resubmit.
• Selecting the highest technical score without explaining residual risks and their proposed treatment.

Worked example: two bids offer different handover scope

In a hypothetical building project, one bid includes system testing, operations-team training and as-built documents. Another excludes some of those activities even though the tender documents require them. Comparing the totals as though the scope were identical would hide an important difference.

Record the gap, request clarification through the permitted channel and apply the predetermined evaluation procedure. Do not revise a bid or price after opening except within the limits allowed by the applicable rules and procedures.

The recommendation should explain how the exclusion affects technical compliance and handover. It should not conceal the issue within a high average score. If the tender uses weighted scoring, connect the score to evidence: a named, verifiable resource plan is stronger evidence than a general statement that labour is available, provided the same published criterion is applied to every bidder.

This example illustrates an evaluation issue. It is not an AYM project outcome, a standard award formula or permission to modify a bidder’s offer.

What should the technical award recommendation contain?

Include the compliance matrix, exclusions and clarification registers, an assessment of programme and resource feasibility, and the remaining risks and their treatment under the tender process.

Engineering expertise and technical advisory can support this assessment. Connect its findings to the post-award site supervision plan and project-management requirements, within the respective appointments. The final award decision remains with the authorised decision-maker.

Executive takeaway

Technical evaluation tests whether the bid can be delivered under the project’s constraints. A stronger recommendation connects risk-based criteria, a clear scoring scale, traceable evidence and analysis of internal consistency and exclusions. The owner can then understand the basis of the recommendation and the risks that still need management after award. Price, presentation and the highest technical score are each insufficient on their own.

Professional reference and limits of application

The Arabic source records its content review on 8 September 2026. For this English draft, the official EXPRO contracts library page was checked on 2 November 2026. Its listing includes technical bid evaluation criteria, tender evaluation and award-recommendation materials. This confirms the reference entry point, not the current controlled issue or detailed requirements of an individual procedure.

• EXPRO National Manual for Project Management — contracts and tender-evaluation materials.

Obtain the controlled documents, applicable requirements and approved evaluation method for the particular project. General guidance does not create a procurement entitlement, establish mandatory numerical weights or replace authorised legal/procurement review. The worked example is illustrative and does not report a completed company project.