Two planes with opposite logics
General requirements concern the reliability of the party and operate as grounds for exclusion. They are not held to a greater or lesser extent: their absence bars participation regardless of technical capacity, and their presence confers no competitive advantage.
Specific requirements concern the capacity to perform that contract and are graduated according to subject matter and value. They cover professional suitability, economic and financial standing, and technical and professional ability.
The operational consequence is that the two checks belong to different moments. General requirements are maintained continuously, independently of any procedure in progress, because losing one excludes from all. Specific requirements are checked procedure by procedure, against the tender documents.
The structure of the grounds for exclusion
The code organises the grounds for exclusion by distinguishing those operating automatically from those requiring an assessment by the contracting authority. Automatic grounds leave the authority no margin of assessment.
Automatic grounds concern objectively verifiable situations, typically final convictions for particular offences and definitively established irregularities in social security and tax matters. Their existence produces exclusion with no margin of appreciation.
Non automatic grounds instead require an assessment, and their application depends on the reasons the authority gives. Inadequate reasoning is the defect most frequently established in this area.
The code also governs self cleaning measures, by which an operator in a situation attracting exclusion may show it has adopted steps adequate to demonstrate its reliability, with the assessment falling to the authority. The assessment must be reasoned and its omission is contestable.
| Plane | Subject | How it operates | Consequence of absence |
|---|---|---|---|
| General requirements | Reliability of the party | Ground for exclusion, automatic or assessed | Participation barred |
| Specific requirements | Capacity to perform that contract | Graduated by subject matter and value | Exclusion unless reliance or grouping |
| Self cleaning measures | Remedies adopted by the operator | Reasoned assessment by the authority | The excluding ground persists |
Serious professional misconduct
Among the non automatic grounds one deserves separate attention because it is the most litigated and the least predictable. It is serious professional misconduct.
Serious professional misconduct is the ground allowing exclusion of an operator whose conduct in a professional context casts doubt on its integrity or reliability. The 2023 code defined both the relevant conduct and the admissible means of proof more tightly than before, with the stated aim of reducing discretion.
Two elements matter in practice for an operator. The first is the duty to disclose: silence about relevant facts is itself conduct capable of assessment, and in many cases produces harsher consequences than the fact withheld. The second is that the effect is temporary: the excluding effect has a defined duration and is not perpetual.
Specific requirements and their graduation
Specific requirements are set by the contracting authority in the tender documents, within the limits the code imposes. The general limit is proportionality to the subject matter.
The governing principle is proportionality: requirements must be adequate and proportionate to the subject matter and value of the contract. Disproportionate requirements are contestable, because they restrict competition without a technical reason.
For works of 150,000 euros or above, demonstrating specific requirements runs through the qualification attestation, which the code treats as a necessary and sufficient condition. For services and supplies the requirements are demonstrated in the manner the tender documents identify.
The two lines of case law that widen the scope
Two judicial lines carry direct practical value and are worth knowing before giving up on a bid. They concern substantive consistency and services rendered to private clients.
The first concerns identity of services. Verification of specific requirements does not require formal identity between the services declared and those covered by the contract: what matters is their technical and economic consistency with the minimum thresholds set in the tender documents.
The second concerns the client. Services performed for private clients may be relied on to demonstrate specific requirements, and not only those rendered to public authorities.
The combined effect is that the portfolio an operator can demonstrate is typically wider than a literal reading of the tender documents would suggest. The check should be made on substantive consistency rather than on nominal correspondence of services.
Reliance on another party's capacity
Where requirements are wholly or partly absent, the code permits reliance on the capacity of another party. The contribution must be substantive and not merely financial.
The limit case law has drawn is substantive. The agreement must secure the effective transfer of means and professional capability, as distinct from mere economic and financial support: reliance amounting to a financial guarantee does not perform the function and its inadequacy can be raised.
The practical consequence is that a reliance agreement is not a form. It must identify the resources made available, how they will be deployed in performance and their connection with the subject matter of the contract. A generic agreement is the defect most frequently identified in this area.
Verification of the requirements
The code has substantially changed when and how verification takes place, with direct effects on the documentary burden. The burden has shifted from production to keeping data current.
The digital architecture provides for verification by drawing on public databases through the economic operator's virtual file, reducing the documentation the tenderer must produce. An out of date position with those databases produces an objection.
Two consequences for an operator. The first is that keeping one's positions with the databases up to date becomes a task with effects on admission: an out of date position produces a negative outcome discovered at verification stage rather than on filing. The second is that the declaration made in the tender and the position appearing in the databases must match, because a discrepancy even of formal origin opens a process that consumes time at the most exposed stage.
Multi party forms of participation
Where the requirements are not held by a single operator, the alternative to reliance is participation in a multi party form, and the choice between the two has different consequences. A grouping distributes performance, reliance leaves it intact.
A temporary grouping brings together distinct operators submitting a single tender, with a lead member and one or more members. Requirements are aggregated under the rules the regime lays down for the type of contract, and liability towards the authority follows the regime applicable to the form adopted.
An ordinary consortium and a stable consortium answer to different logics, the first occasional and the second structured, with distinct effects on demonstrating requirements and on designating the performing members. The choice between the two forms follows from the continuity expected.
The difference from reliance on capacity is substantive and worth bearing in mind. Under reliance the operator bids alone and uses another's resources; under multi party participation several operators bid together and share performance. The first preserves commercial autonomy, the second shares the contract but also distributes risk and resource commitment.
The choice should be made before expressing interest rather than at the tender deadline, because forming a grouping takes time and settling the internal relationships is not a formality. Settling shares and roles takes days rather than hours.
The most frequent errors
Abandoning a bid for lack of formal identity between the services performed and the subject matter of the contract is the first, and ignores the line of case law on substantive consistency. Consistency is assessed on the nature of the service and not on its label.
Excluding services rendered to private clients from one's portfolio is the second, and artificially reduces demonstrable capacity. Private services count where the service performed is comparable.
Drafting a generic reliance agreement is the third, and is the defect case law identifies most often. The agreement must identify the means and the professional capability made available.
Neglecting to keep positions with the public databases up to date is the fourth, and produces exclusions for reasons unrelated to the operator's capacity. Updating should be scheduled rather than left to the eve of a competition.
Omitting disclosure of facts potentially relevant to professional misconduct is the fifth, and turns a manageable risk into conduct capable of assessment. The omission is assessable in itself, whatever the weight of the fact omitted.
Note: the legislative references in this page relate to Italy and are current as at the date of publication. The grounds for exclusion and the rules on reliance on capacity were amended by the corrective decree and case law is abundant: the text in force and the tender documents of the individual award should be checked before any operational use.