Some grounds for exclusion are visible from a distance — a missing declaration, an arithmetic error, an expired certificate. And there is one that is not visible at all until it is too late: a requirement that forms part of the tender without being written in it.
One sentence, an entire section
The phrasing is familiar to anyone who has read construction or infrastructure documentation:
“in accordance with the technical specification of the national rail infrastructure company in force”
“observing the methodological guidance of the Public Procurement Agency”
“under the Public Procurement Act and its implementing rules”
Each of those sentences is a reference. It does not describe a requirement — it attaches an external document to your tender. A document that is often not enclosed, sometimes runs to hundreds of pages, and almost always updates on its own schedule, independent of the procedure at hand.
Legally the construction is sound and entirely ordinary. Practically it produces this situation: the bidder read the whole tender file carefully and still never saw a requirement that binds them.
Why it is the quietest ground for exclusion
The other traps leave a trace. A missing document shows up in the protocol. An error in the bill of quantities is cited by line number. A requirement incorporated by reference leaves nothing — the technical proposal simply fails to conform and the committee records the fact.
And because the decision reads “non-conformity with the technical specification” rather than “the bidder did not read a document we never gave them”, this cause is counted as a technical non-conformity. In the statistics it looks like incompetence. In reality it is an information problem.
“That wasn’t in the documentation” does not work as a defence. The reference was there. So was the duty to follow it.
Who meets it and who does not
The trap is not evenly distributed:
High risk
- Rail projects — bulky agency technical specifications with their own update cycle
- Road infrastructure — guidelines and standard solutions in force outside any single tender
- Design-and-build — references to design codes and standards
- EU-funded procedures — an extra layer of rules on top of the procurement act
Low risk
- Supply of standard goods — the requirement usually ends with the description
- Services with a clear subject and a short specification
- Small tenders under simplified rules
If you supply office consumables you will probably never meet this problem. If you bid on rail or road infrastructure you will meet it routinely — and the difference between the firms that win there and the ones that drop out is often exactly this.
What can be done
A requirements check is only worth running if it also covers what is not in the folder. That is why, alongside the tender documents, we hold the sources they point to — the rail and road agency technical specifications, the Public Procurement Agency’s methodological guidance, the texts of the procurement act, its implementing rules, the Commerce Act and the Obligations and Contracts Act — linked to the tenders that cite them.
In practice this means one thing: when we compare requirements against completed documents, the list of requirements does not end where the attached file ends.
The rest is discipline. Every reference in a tender file is a requirement until proven otherwise. Follow it before you treat it as a formality.
