- tenders
- compliance
Eligibility requirements vs scoring criteria in public tenders
A missed eligibility requirement ends your bid. A weak scoring criterion only costs points. Treating them the same is the most common and most expensive mistake in bid preparation.
A team can prepare a technically excellent bid and still be knocked out over a certificate. They knew how to do the work. The certificate was requested in an annex and ended up on the same list as a criterion that only gave points.
Two different kinds of requirement
An eligibility requirement is binary. It exists to confirm that the bidder can deliver: legal capacity, experience, financial and organizational capacity, as the tender defines them. There are no degrees. You prove it or you don't, and that decides whether your bid is evaluated at all.
A scoring criterion is gradual. It exists to rank bids that have already shown they are capable. It can be met better or worse, and its effect is on your position in the ranking.
The practical consequence is an asymmetry of risk. Falling short on a scoring criterion costs points you might win back elsewhere. Falling short on an eligibility requirement costs the whole process.
| Eligibility requirement | Scoring criterion | |
|---|---|---|
| Nature | Pass or fail | Gradual |
| What it decides | Whether the bid stays in | Where the bid ranks |
| Effect of missing it | Out of the process | Fewer points |
| Where to put effort | Absolute certainty | Optimization |
Why the confusion is so common
They almost never appear separately in one place. The main document states general conditions. Technical annexes detail how to prove them. Forms reveal mandatory fields the text never mentioned. Addenda change any of the above.
How to separate them from the first read
Gather the complete file before reading
Main document, annexes, forms, matrices and every addendum. Extracting requirements from an incomplete file produces a list you will have to redo.
Classify each requirement as you record it
Eligibility or scored, at the moment you write it down. Classifying later means rereading, and context gets lost on the reread.
Record the source of each one
Document and page. Without that you can't re-check when an addendum comes out, and an addendum will come out.
Write down how to prove it, not just the requirement
"Proven experience" is not actionable. Which document, issued by whom, valid for how long and in what format is.
Cross the addenda against your list at the end
Go through each addendum and mark which lines it changes. This pass prevents most rejections.
Questions that surface what gets missed
When you review the tender file, these questions recover buried requirements most often:
- Which requirements are disqualifying, and in which document and page is each one set?
- Which documents must the bidder provide that the main document never mentions?
- Which requirements were changed by addenda, and what is the current version?
- What minimum validity periods apply, and from which date do they run?
- Which conditions apply to bids submitted by a consortium or joint venture?
The deliverable
A list where every line has the requirement, whether it is eligibility or scored, the proof required, the source with its page, and whether an addendum changed it.
That is the list you review before submitting. The only way to review it quickly is for every line to point to where it came from, so you can confirm it without rereading three hundred pages.
Frequently asked questions
- What is the practical difference between an eligibility requirement and a scoring criterion?
- An eligibility requirement is binary and disqualifying: if you can't prove it, your bid is out, however strong the rest of it is. A scoring criterion is gradual: you meet it better or worse, and it affects your ranking, not whether you stay in.
- Can a missing eligibility document be fixed after submission?
- It depends on the procurement rules that apply and on what the tender document says. The usual line is between proving something that already existed at the deadline and providing something new. It is a specific legal question, so check it against the tender and the applicable rules for that process, not against a general rule.
- Why do teams mix them up so often?
- Because they are rarely listed together. The main document states some, the annexes detail others and the addenda change both. Whoever reads straight through ends up with a list where everything weighs the same.
Written by
BrainBox Team
Document intelligence, by ExaByte Company
We build BrainBox — the platform teams use to ask questions across their own documents and get answers with exact page citations.
Keep reading
How to read a 300-page tender document without missing a requirement
Tender documents bury disqualifying requirements in annexes and addenda. A repeatable method to extract every one of them with its exact source.
How to compare two versions of a contract with AI and catch every change
Mention both versions, ask for the table of differences, and verify each change on its page. Works for renegotiated contracts, tender documents with addenda, thesis drafts and any document that has passed through several hands.
How to verify an AI answer about your documents
An answer without a source is not an answer. It is a hypothesis. A practical guide to checking what an AI system claims about your own documents.