FIELD NOTES · PROCUREMENT
A well-structured request for proposal is the foundation of a successful construction project. It sets out what is being bought, on what terms, and how the winner will be chosen. When it does that clearly, bidders compete on the right things. When it does not, the project pays for the gaps later.
Ambiguity in an RFP does not disappear when the contract is signed. It gets priced in as contingency, or it resurfaces months later as variations, claims and delay. The cheapest point at which to remove it is before the tender is issued.
Why this matters more in the Kingdom
Saudi Arabia's pipeline means the same consultants and contractors are often bidding several large packages at once, across several clients. Tender teams are stretched. An RFP that is hard to read, inconsistent between volumes, or vague on scope does not get the market's best response. It gets a cautious one, or none at all.
Government and giga-project tenders also carry requirements that do not exist in many other markets: local content commitments that now weigh on evaluation, regional headquarters rules for foreign firms, and Saudization targets that affect how a bidder staffs and prices the work. If the RFP is not explicit about how these will be assessed, bidders will guess, and their guesses will differ.
The process, step by step
Define the need and the decision. Be clear about what problem the package solves and what the client must decide at award. An RFP written before that is settled will change during the tender.
Sound the market. Speak to likely bidders early about capacity, risk appetite and realistic programmes. It is cheaper to adjust the package than to receive non-compliant bids.
Fix the scope and the interfaces. Most disputes on large masterplans sit at the boundaries between packages: utilities, roads, public realm, adjacent plots. State who owns each interface and what "complete" means at handover.
Issue the draft contract with the RFP. Bidders should price the actual risk allocation, not an assumed one. Negotiating core terms after selection erodes whatever competition the tender created.
Publish the evaluation criteria and their weights. Technical, commercial, local content and programme. If price will decide between technically close bids, say so.
Allow a realistic tender period and run clarifications properly. Answer questions in writing, share answers with every bidder, and extend the deadline when an answer changes the scope.
Keep a clean evaluation record. A documented, defensible evaluation protects the client in a dispute and builds the market's trust in the next tender.
What to take from this
For clients, the RFP is the first and best risk-management tool on the project. Time spent on it is rarely wasted.
For bidders, the quality of an RFP is information in itself. A clear, consistent document usually means a client that knows what it wants and will run the project the same way. A confused one is worth pricing accordingly, or worth asking about before you commit a tender team to it.
— Walid
