Egyptian Government Tenders: How to Build the Technical Offer

In an Egyptian government tender, most bids are won or lost in the technical envelope. The financial envelope is opened only if the technical one is accepted. So a contractor with a good price and a weak technical file can end up out of the running before anyone reads its numbers. This guide is for contractors, MEP firms and suppliers bidding to Egyptian public entities. It walks through what the law and its executive regulations expect in the technical offer, and how to lay that offer out so a committee can check it quickly and score it fairly.

What the law actually requires of the technical envelope

Three rules shape everything that follows.

1. Two sealed envelopes. Article 23 of Law 182 says bids are submitted in two sealed envelopes, one technical and one financial, and that financial envelopes are opened only for bids that are technically accepted.
2. The committee checks capability, not just paperwork. Article 34 requires the adjudication committee to verify the bidders’ technical competence, financial solvency and good reputation. Article 66 of the Executive Regulations sets out the technical review. The committee confirms technical competence against the booklet’s criteria, using past work and performance records. It also checks financial capacity from the balance sheet, the ability to meet the delivery or execution dates, bid validity, compliance with the technical specifications, and the limits on subcontracting.
3. Award follows the booklet’s method. Under Article 35, the award goes to the bidder offering the best terms and the lowest price, or to the highest-ranked bidder under a points-based evaluation system whose elements and bases are set in the tender conditions. The Executive Regulations (Article 34, with Article 32 for the internal tender memo) require the booklet to state the evaluation method, the criteria, their relative weights and, where points are used, the minimum score for acceptance.

The law does not set one weighting for all tenders. The weights, if there are any, are in the booklet for that tender. Do not assume them from a previous bid or from another country’s system. If you also bid in the Kingdom, see how the technical proposal works in Saudi government tenders; the rules there are different.

Before you write: registration and the booklet

Under the Executive Regulations (Article 65), bids from bidders who are not registered on the Public Contracting Portal are excluded at the formal review stage. The portal is etenders.gov.eg. Get registration done and your data up to date well before the deadline. Check the portal’s current registration requirements yourself, because they can change. For smaller firms: under Article 59 of the law, before a local tender the entity notifies the Micro, Small and Medium Enterprise Development Agency, which encourages enterprises in the governorate to register and update their data on the portal.

Then take the conditions and specifications booklet apart line by line. Before anyone drafts a page, build a requirements matrix: a simple table with every requirement in the booklet, the document or section that answers it, the person responsible, and its status. This is the single most useful working tool in a tender. It catches missing undertakings early, and it later becomes the index of your technical offer.

Use the inquiry window. The booklet must set deadlines for clarification requests and responses (Executive Regulations, Article 42), and Article 19 of the law requires the entity to answer inquiries in writing and publish the answers on the portal. If a requirement is unclear, for example which certificates count or what “similar work” means, ask in writing within the deadline. Do not guess and hope the committee reads it your way.

The technical envelope, item by item

Article 49 of the Executive Regulations lists what goes in the technical envelope: proof that the provisional guarantee has been paid, plus the documents the booklet stipulates. The list is long. The table groups its items by the question each one answers for the evaluator.

Article 23 of the law also requires the technical envelope to include, where the nature of the work requires it, the bidder’s undertaking to employ labour in line with the social insurance laws. If the booklet asks for it, make sure it is there. Keep anything that shows price out of the technical envelope: under Article 51 of the regulations, price lists, rate schedules and payment terms belong in the financial envelope.

Where the company profile fits, and where it does not

Many contractors put their glossy corporate brochure on top of the technical envelope and stop there. A committee checking Article 66 points does not score adjectives. It needs evidence it can tick off: registers, references, people, method and compliance. A brochure written for marketing rarely answers those questions in the order they are asked.

The better approach is a tender version of the company profile. It is short and factual, it follows the same visual identity as your brochure, and it is organised around what evaluators check:

• Legal identity and registrations, stated plainly with numbers and dates.
• Core capabilities, described the way the booklet describes the scope.
• Selected projects of the same nature, cross-referenced to the reference table and the proof.
• Key people and their roles.
• Quality, safety and maintenance arrangements, each backed by a document further in the file.

Consistency matters more than design flourish. If the profile gives one number of completed projects and the reference table gives another, the evaluator will notice. If you use a common visual system across your profile, CVs and section dividers, the file reads as one coherent submission, not a pile of photocopies. That is the work a brand identity and company profile system should do for a contractor. Our article on company profiles for prequalification goes further into structure.

For YAMA Engineering Systems, a Cairo fire-fighting company, RX wrote and designed the company profile covering its product lines, services, industries, projects, clients and partners, plus the presentation decks used with consultants and contractors: the kind of verified source material a tender version of the profile is cut from.

Make the file fast to score

Evaluators usually work through many bids against the same list. Help them find each answer in seconds.

1. Mirror the booklet. Order your sections in the same sequence as the booklet’s requirements, and use its headings and clause numbers. Your requirements matrix becomes the first page, with page or tab references.
2. One requirement, one place. Do not scatter a single requirement’s evidence across three sections. If something must appear twice, cross-reference it.
3. Use the booklet’s language. Write in the language and terms the booklet uses. Where it calls something a “maintenance centre” or “similar works”, use the same phrase so the match is obvious.
4. Compliance statements, clause by clause. For technical specifications, a compliance sheet works well: clause, requirement, your offer, comply or deviate, and where the proof is.
5. Sign, stamp, number. Unsigned bids are among those excluded at formal review. Number the pages and initial or stamp them if the booklet asks you to.
6. Follow the submission method stated. Article 45 of the regulations allows electronic delivery only where the tender conditions permit it. Follow exactly the method, copies and format the booklet sets.

A hypothetical example, not a real client: a mechanical contractor bidding for a hospital HVAC scope could open its technical envelope with the matrix. Behind it would come the registers, a one-page summary of five similar hospital projects with completion letters, the project team chart and CVs, a method statement and schedule, the equipment compliance sheet with marked-up data sheets, the maintenance-centre proof and, last, the signed undertakings. The order follows the booklet, and a reviewer can confirm each point without searching.

The first rows of that contractor’s requirements matrix might look like this. Clause numbers and documents are placeholders; the two problem rows are the ones the matrix exists to catch.

Review the status column at every bid meeting. A row that is still open two working days before submission is a decision for management, not a task for the bid coordinator.

Mistakes that end a bid before anyone reads the method statement

Article 65 of the Executive Regulations lists bids that are excluded at the formal review stage. They include:

• late bids;
• bids not signed by the bidder;
• bids incomplete under the tender conditions;
• bids without the required provisional guarantee;
• bids from entities not registered on the Public Contracting Portal;
• in works contracts that require them, bids that omit the price-adjustment factors.

Do not plan on fixing gaps after opening. That is our reading of the texts, not a legal opinion. Law 182 does not allow the tender documents or conditions to be amended after the date set for opening the technical envelopes (Articles 19 and 35), and Article 65 of the regulations lists incomplete bids among those excluded at formal review. Read together, we take this to mean an incomplete bid should be treated as a candidate for exclusion, not for a reminder. How a committee applies the rules in a particular tender is a legal question, so take advice from an Egyptian lawyer if a specific case depends on it. Build in a final check, two working days before submission, against the matrix: every document present, current, signed and in the right envelope.

Watch the guarantee. Article 16 of the law sets the provisional guarantee as a percentage of the estimated value, capped at 1.5% for the purchase or lease of movables, works, services and consultancy studies, and requires it to remain valid for 30 days after the bid validity period ends, including any extension. Check the amount and validity that the booklet asks for, and confirm early with your bank. Bid validity itself is set in the booklet, between 45 and 90 days depending on the type of transaction, counted from the opening of the technical envelopes, and longer only where the nature of the transaction requires it (Article 27).

After the decision: use the reasons

Exclusion and award decisions must state their reasons. Bidders can ask why their bid was not accepted, and a written complaint can be filed within seven days of notification (Articles 35 and 39 of the law). If your technical offer was rejected, ask for the reasons in writing and log them against the row of your requirements matrix they relate to. How to turn those reasons into a fix list is covered in why companies keep losing tenders. If you have the committee’s reasons and want them read against your file, a business diagnosis session is a paid 45-minute review that ends with a fix list.

Before the next booklet arrives, keep five items current: the register and tax documents with expiry dates, the contractors’ federation card, a reference table with completion letters filed in the same order, standard CVs, and the tender version of the profile. Then each bid starts from the matrix, not from a search for papers. The tender profile, the matrix template and the section dividers are the parts RX prepares through its sales enablement and tender file work; the portal registration stays in the company’s name, and the company submits.