The Bid That Was Right and Still Got Rejected — How EU e-Submission Turns Format Into Fate

It is 22:10. The deadline is 23:00.

Elena has the bid open in two windows. The technical offer is 61 pages, signed, exported to PDF/A. The pricing schedule is locked. Tomas uploaded the ESPD an hour ago. Everything is in the room.

She drags the package into the contracting authority’s portal. The upload bar fills. Then a red line appears.

Signature could not be validated.

Not “your price is too high.” Not “your method statement is weak.” The bid is good. The bid is conforming. And the portal will not take it, because of something that has nothing to do with whether you can build the thing.

This is the part of public procurement nobody warns you about. The bid can be right and still be rejected. Not on merit. On format.

E-submission is the law, not a courtesy

Since Directive 2014/24/EU, electronic communication in public procurement is not a nice-to-have. Article 22 requires that communication and information exchange — in particular the submission of tenders — be performed using electronic means. Member States could postpone it, but no later than 18 October 2018. After that, paper is the exception, and a narrow one.

So the portal is not a convenience. It is the gate. If your file does not pass through it, your bid does not exist. There is no counter where a clerk takes the envelope at 22:59 and nods.

Read that again before your next deadline. The machine is the clerk now. And the machine does not do nods.

The signature is the most common reason good bids die

Here is where it goes wrong most often.

Under the eIDAS Regulation — Regulation (EU) No 910/2014, in full effect since 1 July 2016 — a qualified electronic signature has the legal effect of a handwritten signature. That is Article 25. And a qualified signature backed by a qualified certificate from a trust service provider on one Member State’s trusted list must be recognised in every other Member State. That is the cross-border promise.

The promise is real. The execution is where you bleed.

A qualified signature is not “I typed my name.” It is not a scanned image of a pen. It is a specific cryptographic object, created with a qualified certificate from a qualified trust service provider that appears on an EU Trusted List. If your signatory signs the offer with a tool that produces something else — an advanced signature, an internal company stamp, a PDF “certify” the portal does not recognise — the file is technically signed and legally insufficient at the same time.

The portal cannot read your intent. It validates the object. Object valid, you pass. Object not valid, you are out, at 22:10, with a perfect bid and no time.

The cross-border version is worse. A Belgian firm bidding in Portugal is entitled to use a Belgian qualified signature. The Portuguese platform should accept it. “Should” is doing a lot of work in that sentence. Format profiles, validation services, and what a specific portal actually accepts on the night do not always match the regulation in full. Which is why you test the signature on the real platform, with the real certificate, days before — not at the gate.

The ESPD is a declaration, not your evidence folder

There is a second trap, quieter, and it catches people who think they over-prepared.

The European Single Procurement Document — the ESPD, set out under Article 59 of Directive 2014/24/EU and the standard form in Implementing Regulation (EU) 2016/7 — is a self-declaration. It is you stating, formally, that you are not excluded and that you meet the selection criteria. Preliminary evidence. A promise that the real certificates exist and you can produce them.

Only the winner submits the actual documents. The e-Certis service, under Article 61, exists precisely so you can see which document proves which criterion in which country.

So two failures happen here. People attach a folder of tax certificates and insurance attestations no one asked for yet — noise. Or they submit the ESPD from the wrong procedure, or last month’s version, with a criterion that has since changed. The form is conforming on its face. The content is stale. And one thing worth knowing: the Commission switched off its central ESPD service on 2 May 2019. The obligation did not go away. You now use national ESPD services, and they are not identical. Same document, different doors.

The notice you are answering changed shape

If the tender feels structured differently than the ones you bid two years ago, it is.

Since 25 October 2023, eForms — Commission Implementing Regulation (EU) 2019/1780 — became mandatory for publishing notices on TED, the EU’s official procurement journal. They replaced the old standard forms under Regulation (EU) 2015/1986. eForms are structured data with mandatory and conditionally mandatory fields, not free text on a PDF.

What this means for you is dull and important. The dossier you are answering is machine-defined. The fields the authority must publish are fixed. Your completeness is measured against a structured list, not against a reviewer’s patience. Match the structure or get gated out.

And it is still moving. eIDAS 2.0 — Regulation (EU) 2024/1183 — requires every Member State to provide an EU Digital Identity Wallet by the end of 2026. Identity and signature in procurement will keep shifting under your feet. Plan for change, not for a frozen rulebook.

The real gap is between “finished” and “accepted”

Notice what all three failures share.

The signature, the ESPD, the format — none of them are about whether you can do the work. They are about whether the package crosses the gate. Your engineers built a winning bid. The bid lost to a validation rule.

Design has CAD. Construction has ERP. Bid assembly has a shared drive and a file called Offer_final_v3_REAL.pdf. That is not a process problem. It is a missing tool. The thing that checks, before you click submit, that every signature validates, every required field is filled, every declaration is the current one — that thing has not existed in most bid rooms.

It is starting to. Tools like Steinlog gate the package against the dossier before submission, so the red line appears on your screen at 17:00, not on the portal’s screen at 22:10.

That is the whole shift. Move the rejection earlier, where you can still fix it.

It is 17:00. The deadline is in three hours. Everything checks. The signature validates. The ESPD is the right one. You export the package. You close the bid.

And you go home.