The pre-submission checklist — the moving parts the EU framework hides in plain sight

It is 23:40. The deadline is 20 minutes away.

The TED notice is open in one browser tab — 2024/S 189-571432, a framework agreement for structural renovation works across three municipalities in northern Portugal. In another tab: your national e-procurement platform, progress bar at 94%. The eIDAS token is plugged in. The ESPD file is attached.

You are ready.

Except you are not. And the reason will not appear in any rejection letter. It will arrive as a brief, administrative notice: your tender has been declared inadmissible. No further detail.

This is what the EU public procurement framework does quietly. It hides the moving parts in plain sight — in the implementing regulations, in the footnotes of national platform guidance, in a tool most bidders have never opened. The checklist you need is not about the quality of your bid. It is about the machinery around it.

The ESPD Is Not What You Think It Is

The European Single Procurement Document is a self-declaration. It is the mechanism by which you declare — provisionally — that you are not subject to the exclusion grounds under Article 57 of Directive 2014/24/EU and that you meet the selection criteria under Article 58. It replaces certificates at the point of submission. Only the prospective awardee is required to produce the actual supporting documents before award, under Article 60. The ESPD is provided exclusively in electronic form, and its standard form is set by Commission Implementing Regulation (EU) 2016/7.

That is the theory. Here is the practice.

The Commission ran a central ESPD service. That service was switched off on 2 May 2019. It no longer exists.

If you searched for “EU ESPD portal” tonight, you may have found cached references, archived pages, or third-party explainers that still point to it. None of them will help you submit. There is no single EU ESPD portal anymore.

You need to find the national ESPD service for the contracting authority’s Member State. Not the Commission’s tool. Not a generic EU gateway. The national one — the one your receiving platform will actually accept. This varies. Some Member States host it centrally through their national procurement authority. Others integrate it directly into specific platforms. A handful of platforms generate the ESPD internally and do not accept external XML imports at all.

Verify. Do not assume.

Check the contracting notice. Check the platform’s technical guidance. Check whether the file format it accepts — XML, PDF, or something proprietary — matches what the national ESPD service produces. Do this the week before submission, not the night of.

Every Entity in Your Consortium Needs Its Own ESPD

Article 63 of Directive 2014/24/EU permits an economic operator to rely on the capacities of other entities to meet selection criteria — a named subcontractor for technical capability, a group member carrying the financial standing. This is how joint ventures and capacity-reliance arrangements work across the single market.

What Article 63 requires, and what many bids get wrong: the ESPD must contain the Article 59 information for each such entity separately. Not a reference to them. Not a covering declaration. A separate ESPD, completed and signed by each capacity-reliance partner and each named subcontractor.

If your consortium has a lead entity, two capacity-reliance partners, and one named subcontractor, that is four ESPDs. Not one.

The platform may not warn you. The contracting authority may not chase you for the missing documents before the deadline. They will simply treat the submission as non-compliant.

Run through your team structure now:

• Lead economic operator: one ESPD
• Each Art. 63 capacity-reliance entity: one ESPD each
• Each named subcontractor whose capacity is relied upon: one ESPD each
• Consortium members not providing capacity: check the national rules — many Member States require ESPDs from all members regardless

This is administrative, not substantive. It has nothing to do with whether your technical offer is strong. It is a structural requirement, and it will eliminate you before anyone reads your methodology.

e-Certis Is a Map, Not a Guarantee

At some point between submission and award, the contracting authority will ask for the underlying documents that prove what your ESPD declares. This is where e-Certis becomes relevant.

e-Certis is a free reference tool maintained by DG GROW under Article 61 of Directive 2014/24/EU. It maps what each Member State accepts as proof for exclusion and selection criteria — criminal record certificates, tax compliance statements, social security clearances, professional registers. It covers EU Member States plus Iceland, Norway, and Liechtenstein under EEA provisions.

It is genuinely useful. If you are a Polish contractor bidding into a Spanish framework, e-Certis tells you what the Spanish contracting authority is likely to require and whether your Polish certificates are accepted equivalents.

Here is what e-Certis does not do: it does not legally bind the contracting authority. The tool itself is explicit that it is a reference, not legal advice. Accepted document lists may lag behind national administrative changes. A certificate that e-Certis shows as accepted may require apostille, certified translation, or notarisation in practice — requirements that vary by authority and are not always captured in the database.

Use e-Certis early. Build your document matrix from it. Then verify the specific requirements with the contracting authority or their published guidance — do not treat the database entry as a final answer.

The Checklist That Actually Matters

The standard tender checklist — price schedule complete, technical references attached, insurance certificates uploaded — is necessary. It is not sufficient.

Here is what to layer on top of it, structured around the three silent bid-killers.

Before you build the ESPD

• Identify the Member State of the contracting authority
• Find that Member State’s national ESPD service — not the Commission’s (it is gone), not a generic EU tool
• Confirm the file format the receiving platform accepts
• Check whether the platform generates the ESPD internally and does not accept external imports

Before you finalise the consortium structure

• Map every entity whose capacity is being relied upon under Art. 63
• Assign one ESPD per entity, in addition to the lead operator’s ESPD
• Confirm national rules on whether all consortium members require ESPDs regardless of capacity reliance
• Allocate time for each entity to complete, sign, and return their ESPD — this is a coordination task, not a solo one

Before you accept e-Certis as definitive

• Use e-Certis to draft your supporting document matrix
• Cross-reference against the contracting authority’s published selection criteria and any notice annexes
• Check translation and legalisation requirements for documents originating in a different Member State
• Note that the underlying law is still Directive 2014/24/EU and Commission Implementing Regulation (EU) 2016/7 — reform proposals exist but the 2014 framework remains operative

Verify, Do Not Assume

It is 17:00. The deadline is three hours away. The documents are in order.

The ESPD XML is generated. The consortium partners have returned their declarations. The e-Certis matrix is cross-referenced against the contracting authority’s notice. The platform’s accepted format has been tested. You have three hours and nothing that should surprise you.

That is the goal. Not confidence — readiness. The EU procurement framework is not adversarial. It is procedural. Its requirements are published, implementable, and survivable if you treat verification as a step, not an afterthought.

The bid killers described here are not obscure. They are structural. They live in the implementing regulations and platform documentation that most teams skim once and never return to. A central ESPD service that stopped existing years ago still costs teams their submissions. A missing ESPD from a capacity-reliance partner — four lines in Article 63 — eliminates bids that took weeks to prepare.

Read the notice. Find the national service. Map the entities. Check e-Certis, then check again. Confirm the format. Do all of this before the week of submission.

If those checks live somewhere organised — one place rather than in someone’s memory at 23:40, whether that is a shared folder, a platform like Steinlog, or a disciplined internal template — the preparation window works as it should.

The preparation window is where tenders are won or lost. The submission window is just where you find out.