Skip to main content
All resources

Guides

Responding to Jordanian government tenders: the rules, JONEPS and the submission pack

Which framework governs a Jordanian tender, what JONEPS changed about submission, and why donor-financed projects in Jordan follow different rules entirely.

First, establish which rules govern this tender

A tender published by a Jordanian ministry is not automatically procured under Jordanian rules. Where a project is financed by a multilateral institution — the World Bank, the EBRD and others — procurement typically follows that institution's own regulations, even though the contracting authority is a national body. The eligibility conditions, the standard forms, the evaluation method and the complaint route all change with the framework, so reading the notice for this one fact before anything else saves the most expensive kind of rework.

Standing rule
Many Jordanian projects financed by multilateral institutions such as the World Bank and the EBRD follow those organizations' procurement regulations rather than domestic rules.
Standing rule
Jordan has not signed the WTO Government Procurement Agreement, so its national procurement is not bound by that agreement's disciplines.
The first question on any Jordanian tender is not what to write. It is which rulebook the notice was issued under — because a donor-financed project in Amman is not procured under Jordanian rules.

The national framework, and who runs what

Where the national framework does apply, the governing instrument is Bylaw No. 8 of 2022, together with the Instructions for Regulating Government Procurement Procedures issued the same year. It replaced Bylaw No. 28 of 2019 and consolidated roughly fifty separate regulations into one framework, which is why guidance written before 2022 should be treated as out of date. Tender notices themselves commonly cite it directly.

  • Government Tenders Department — major public works and centralized tenders, under the Ministry of Public Works and Housing.
  • Government Procurement Department — goods and services, under the Ministry of Finance.
  • The Jordanian Armed Forces run their own procurement offices with exclusive jurisdiction over defence.

What JONEPS changed

JONEPS is the national e-procurement system, operating in Arabic and English and launched in 2018. Notices are published, documents are downloaded, bids are submitted and results are tracked through it. Adoption has moved quickly — utilisation on major construction tenders rose from under half to full coverage — and deployment across government is scheduled to complete by 2027. The practical consequence for a bidder is that submission is now a timed electronic event rather than a courier deadline, and an upload that fails at the last hour fails completely.

Our reading, not a rule
Treat the platform deadline as earlier than the published one. Assembling the pack a day ahead converts an upload failure from a lost bid into an inconvenience.

The gender mainstreaming preference

An addendum adopted towards the end of 2022 introduced gender mainstreaming into Jordanian public procurement, with special preference given when evaluating offers that integrate it. This is an evaluation advantage that costs nothing to claim if the evidence already exists in the organization — staffing composition, past programme design, relevant policies — and is simply lost if nobody thinks to assemble it before the deadline.

Standing rule
The 2022 bylaw was amended late that year with an addendum on gender mainstreaming, under which the Council of Ministers gives special preference when evaluating offers that integrate gender into government procurement.
Set by each tender
How the preference is weighted, and what evidence is accepted for it, is set by the individual tender. Read the evaluation section rather than assuming a fixed margin.

Where these bids are actually lost

Rarely on technical quality. Formal procurement disqualifies on form, and the pattern is consistent across the firms that lose: a certificate that expired between shortlisting and submission, a form completed in the wrong language, a signature page scanned without its stamp, an experience statement with no completion certificate behind it, and a pack assembled by three people who never checked it as one document.

Our reading, not a rule
This is ProposalOS's own reading of recurring failure modes, not a published statistic. Treat it as a checklist to run, not as a measured distribution.

A sequence that holds under a Jordanian deadline

The order matters more than the effort. Teams that start writing before establishing the framework and the mandatory list end up adapting the wrong material to the wrong rules.

  1. Identify the funding source and therefore the governing framework, before opening the technical requirements.
  2. Extract every mandatory item — forms, certificates, eligibility conditions, language, formats — into a list you can track against, with the clause attached to each.
  3. Check validity dates on every certificate and registration against the submission date, not today's date.
  4. Retrieve approved evidence for each experience claim, and prefer a weaker claim you can prove to a stronger one you cannot.
  5. Assemble and review the pack as one document, in the required language and format, with one named owner for completeness.
  6. Upload a day early, then confirm the platform has accepted every file.

Primary sources

Quotations are reproduced from the published document at the date shown above. Procurement documents are revised, and the request for proposals you receive governs your bid — check the clause in your own tender before relying on it.