The ESPD explained: one form instead of a folder of certificates

The single biggest paperwork reform in EU procurement has a clumsy name: the European Single Procurement Document, or ESPD. It replaces the folder of certificates that bidding used to require with one self-declaration: you state that you meet the conditions, and only the winner has to prove it with actual documents.

Used well, the ESPD ESPD The European Single Procurement Document: a self-declaration that replaces certificates at the bidding stage. Full entry cuts days off bid preparation. Used carelessly, it is one of the most common reasons compliant companies get excluded.

What the ESPD actually is

A standard electronic form (defined by an EU implementing regulation) in which you declare three things:

1. No exclusion grounds apply to you. No relevant criminal convictions (fraud, corruption, money laundering, terrorism, child labour), taxes and social security paid, no grave professional misconduct, no bankruptcy that compromises delivery, no conflict of interest.
2. You meet the selection criteria the buyer set for this contract - suitability to trade, economic standing (turnover, insurance), technical ability (references, staff, equipment).
3. Where the evidence lives - which authority or database can confirm each statement, so the buyer can fetch or request it later.

Above the EU thresholds, buyers must accept the ESPD at submission stage. They may still ask any bidder for supporting documents during the procedure if needed to keep things fair - but the default is: declare now, prove if you win.

How you'll meet it in practice

The ESPD is electronic. Depending on the country and platform you will meet it as a form built into the procurement portal, as a reusable XML file (request/response), or occasionally as a PDF rendering of the same structure. Two practical consequences:

• Keep a master XML. Almost every platform can import a previous ESPD response. Maintain one canonical, up-to-date file and reuse it - retyping company data twenty times a year is how typos creep into legal declarations.
• The buyer's request defines the questions. Part of the form is generated from what this buyer requires. Never blind-copy last month's answers over a new request without reading it.

The parts, in bidding order

• Part I - the procedure. Identifies the tender; usually pre-filled.
• Part II - your company. Identity, size (SME status matters for statistics and some set-asides), whether you rely on other entities, and any subcontractors. If you bid as a consortium, every member files its own ESPD; if you rely on another entity's capacity (a parent's turnover, a partner's references), that entity files an ESPD too.
• Part III - exclusion grounds. The yes/no declarations. A "yes" is not automatically fatal: the self-cleaning mechanism lets you describe remedial measures (compensation paid, staff changes, compliance programmes), and the buyer must weigh them.
• Part IV - selection criteria. Either detailed answers per criterion or - where the buyer allows it - a single global "α" tick stating you meet everything. Tempting shortcut, but detailed answers force you to actually check each minimum against your numbers. Do the check either way.
• Part V - shortlisting (restricted procedures Restricted procedure Two steps: companies first ask to take part, and only those selected are invited to bid. Full entry only).
• Part VI - signature. Who signs, and that the information is accurate.

When the real evidence is due

The winner-to-be receives a request for the supporting documents: criminal-record extracts, tax and social-security certificates, accounts, reference letters. Two traps:

• Validity windows. Many certificates are only valid 3-6 months from issue. A criminal-record extract ordered in January may be stale by the July award. Track expiry dates like you track the bid deadline.
• Slow authorities. Some documents take weeks to obtain. Order them when you submit the bid, not when you win - the award-stage deadline for producing evidence is short, and missing it can cost you the contract.

Buyers must also check databases they have free access to (national registers, the e-Certis e-Certis The EU's guide to which certificate proves what in each member state. Full entry directory maps which certificate proves what in each country) before demanding paper from you - worth politely pointing out when asked for something the buyer can retrieve itself.

The mistakes that actually exclude bidders

1. Signature by the wrong person. The signer must have authority to represent the company; platforms verify e-signatures strictly.
2. Missing ESPDs from consortium members or capacity-providers. The most common formal defect in multi-party bids.
3. Inconsistency with the bid. Your ESPD says the references are from subsidiary A; the technical proposal names subsidiary B. Evaluators notice.
4. Hiding a problem instead of self-cleaning. A concealed issue found later is grounds for exclusion and often a listed ground for terminating the contract; a declared issue with credible remediation is frequently survivable.
5. Stale answers. Turnover figures from three financial years ago, expired insurance values, staff who left. Update the master file quarterly.

A 30-minute ESPD routine

Keep one folder: master ESPD XML · company registry extract · last three annual accounts · insurance certificate · standard reference sheets · signatory's power of attorney. Review it four times a year. Every new bid then starts with an import, a read-through against the buyer's request, and the Part IV check - half an hour instead of half a week.

The ESPD rewards companies that treat compliance as maintained infrastructure rather than a per-bid scramble. Build the file once, keep it alive, and the form becomes what it was meant to be: a formality.