Requirements ↔ documents check

Why formal exclusion grounds are so common

Tender documentation in Bulgaria can be extremely voluminous. The notice, the participation documentation, technical specifications, the evaluation methodology, templates — often hundreds of pages. Every page may contain a requirement that calls for a specific document. The selection criteria under Articles 59–64 of the Public Procurement Act cover economic-financial and technical-professional standing, specific certificates, key personnel, and equipment. Each is evidenced by a precisely defined document type — an NRA statement, a reference, a diploma, a certificate, a declaration.

The problem is that people tend to remember the "big" items and overlook the "small" ones. The experience reference is there — it's ten pages and impossible to forget. But the declaration of offer validity is half a page and very easily gets left in draft, unsigned. Or the ISO certificate is submitted as a copy from three years ago, while the requirement says "current" — and the committee interprets "current" differently from you.

Data from our platform shows that in more complex procedures the number of selection requirements and the documents needed to evidence them can exceed 20–30 line items. At that volume, manual cross-checking is unreliable — it takes hours and still misses things.

How the automated matching works

The system runs in two parallel tracks. On one side: requirement extraction. The language model, trained on thousands of Bulgarian tender documents from our base of 84,532 tracked tenders, reads the notice and documentation and structures the complete list of requirements — not only the mandatory selection criteria, but also hidden technical requirements buried in specifications, requirements for templates and declarations, and time-sensitive requirements such as offer validity and certificate validity.

On the other side: document analysis. You submit the package of documents prepared for the bid. The system reads each document, identifies its type, and extracts key attributes — the period covered by the experience reference, the value of the reference, the expiry date of the certificate, the signing date of the declaration.

The third track is the matching. Every requirement is matched to a document that covers it — or to the absence of one. The result is a matrix: requirement, document, status. Three statuses: "Covered" (the document is present and satisfies the requirement by value and period), "To check" (the document is present but has an attribute that needs to be verified — for example a validity date approaching expiry or already expired), "Missing" (no document covering this requirement has been found). The matrix is the centrepiece of the service — it is exactly what you need to see before you press "submit."

• Full requirement extraction — mandatory, technical, declarative, and time-sensitive.
• Automatic recognition of each document's type within the package.
• Coverage matrix with three statuses: Covered / To check / Missing.
• Attribute-level checking: values, periods, validity dates.
• Prioritisation: critical gaps (Missing) surface first.
• Concrete guidance for every "Missing" or "To check" item.

The coverage matrix — the centrepiece of the service

The coverage matrix is the instrument around which the service is built. It isn't simply a checklist — it's a structured answer to the question "Is my bid ready to enter the procedure?" Each requirement occupies its own row. Beside it sits the document that should cover it. Beside that sits the status.

When the status is "Covered," you can stop worrying about that item. When it's "To check," you have a specific attribute to verify — for example, the certificate has been attached but its expiry date falls after the submission deadline, whereas it must remain valid through the contract-signing date. When the status is "Missing," you have a clear signal: either find and attach the document, or consciously accept the risk of exclusion.

An important caveat: the matrix does not substitute for legal advice and does not interpret ambiguous requirements in their full legal depth. It is a completeness and coverage check — "do we have the document?", "does it satisfy the values?" — not "has the requirement been interpreted correctly?" For interpretive questions we recommend consulting a public procurement lawyer.

The cost of one missed criterion

Let's be specific about the cost. If you're bidding on a contract worth €250,000 and your margin is 15%, that's a potential revenue of €37,500. If your bid is excluded because of a missing document, you lose not only that potential revenue — you also lose all the preparation hours, the bank guarantee costs, the document-gathering costs, and — crucially — the time you could have spent on another tender.

The figures below are illustrative samples, grouped around the real scale of our base of 84,532 tracked tenders and ≈2.88 million documents. They show the typical order of magnitude, not exact official statistics.

If even 10% of exclusions in a given procedure are on formal grounds — and if your bid is among them while the gap was preventable — the cost is 100% of your preparation investment plus 100% of the potential revenue. The requirements ↔ documents check is the insurance with an incomparably lower price.

Typical gap categories caught by the system

In our work with real bids, certain categories of gap repeat. Not because bidders are careless — but because tender documentation is written in a way that makes these requirements look self-evident or scatters them across different sections.

• Expired or near-expiry certificate (ISO, OHSAS, national) — the certificate is present but the date doesn't cover the required period.
• Declarations left unsigned or unstamped — the correct template is filled in but the signature or stamp is missing.
• References that don't precisely hit the value threshold — the experience is real but the reference is for a contract with a value slightly below the required minimum.
• eESPD without a qualified electronic signature or with the wrong tender identifier.
• Bank guarantee with the wrong beneficiary or an expired validity period.
• Missing declaration of offer validity — brief but mandatory.
• Key expert CV submitted without the diploma or without proof of employment relationship.
• Technical specifications requiring a specific standard without a conformity document attached.

When to run the check

The ideal moment is when the document package is near-final — all documents gathered, the bid prepared, only finalisation remains. No earlier than 24–48 hours before the deadline, so there is a real package to check. Not at the last possible moment, because if a gap is found there must be actual time to act.

The check is also possible at an earlier stage — as a "dry run" against a preliminary package — to identify structural gaps that will take more than 24 hours to fill, such as engaging a new key expert or obtaining an up-to-date certificate. In those cases an early check is especially valuable.

We recommend running the check in parallel with the final review of the bid, not instead of it. The two processes are complementary: the coverage check deals with "do we have everything?", the final review with "is everything we have of good quality?"

What you get

The result is a structured coverage report — readable, specific, directly actionable. Not an academic document but a working tool for the 48 hours before submission.

• Full coverage matrix: requirement × document × status (Covered / To check / Missing).
• A summary card with the count of items per status — a quick view of bid readiness.
• A prioritised action list for "Missing" and "To check" items.
• Attribute notes for each "To check" item — exactly which attribute needs verifying.
• Criticality indication — which gaps lead to certain exclusion, which are merely risky.
• A final bid status: "Ready to submit," "Ready with conditions," or "Critical gap."