Rejection Dutch-speaking chamber

Ferry for the Scheldt: SKB loses its annulment action against the award to Scheepswerf Grave, because a score explained in words is a reasoned score

Ruling nr. 210970 · 3 February 2011 · XIIe kamer

Antwerp-based SKB challenged the award of a ferry for the Scheldt crossings to Scheepswerf Grave (2,031,330 euros), criticising the reasoning, the Argus evaluation method and its scores on electrical installation, paint system, delivery time and training, but the Council of State dismisses the action: a bidder who received the evaluation report before filing knows the reasons, and every score was explained in words and reasonable.

What happened?

In autumn 2004 the Fleet division of the Waterways and Maritime Affairs administration launched a general call for tenders for the construction of a ferry for the Scheldt ferry services (specifications no. 16 EQF/04/019/A, published in the Bulletin of Tenders of 1 October 2004). The specifications set four award criteria: price and the technical quality of the vessel, both of ‘very great importance’, the technical quality being split into six sub-criteria (layout, propulsion, auxiliary sets and electrical installations, fixed equipment, nautical instruments and paint system), and delivery time and training of the operating crew, both of ‘great importance’. Delivery time was capped at 200 working days. On 18 November 2004 four tenders were opened: from NV SKB of Antwerp, Scheepswerf I.D.P. of Ostend and the Dutch yards Grave and Reimerswaal. An evaluation committee scored the tenders with the Argus system on a five-point scale from ‘very poor’ to ‘very good’ and explained each score in words. Grave came out as the most advantageous regular tender and was awarded the contract on 14 December 2004 for 2,031,330 euros, VAT included. SKB learned on 27 January 2005 that its tender ‘had not been selected’, received the award decision on 16 February but not the report, and obtained that report only by fax of 23 March 2005, after an order of the interim-relief judge. Two days later it filed an annulment action. That action was decided almost six years later. The Council first notes that there is no ‘decision of 27 January 2005’: that letter was merely the notification; the action is read as directed against the implicit decision not to award to SKB, contained in the award of 14 December 2004. Annulment of such an implicit refusal would not automatically oblige the authority to award to SKB. The first plea, on formal reasoning, fails: the notification is not subject to the reasoning act, and the award decision referred to the evaluation report, which SKB had in hand before filing — so the purpose of the duty to give reasons was achieved. The second plea targeted the scores. The Council holds that a bare score is not adequate reasoning, but that here every score was explained in words. On sub-criterion 2.3 SKB received a ‘–’ because its engine and alternators were ‘generously sized’; SKB did not show that more power automatically means better quality. On 2.6 it received a ‘–’ because its paint system was ‘not described’, whereas Grave had enclosed extensive specifications from its paint supplier Sigma; SKB’s certifications related to its capability (selection), not to the quality of the system offered (award). For delivery time SKB, with 200 working days — the permitted maximum — received a ‘–’ against an ‘o’ for Grave with 190 working days; that a shorter time scores better is, according to the Council, ‘logic itself’, even without the specifications saying so expressly. And training by the bidder’s own firm and suppliers could score better than SKB’s proposal to have the crew follow the works during the last month of construction. The third plea, that Grave had not proved its technical capability, failed because annex B to its tender met the requirements of the specifications. The action is dismissed; SKB bears the costs of 175 euros.

Why does this matter?

The judgment explains clearly what an award report must contain when a scoring scale is used: a plus or minus on its own explains nothing, but a score explained in words per (sub-)criterion does, even when it is processed in a calculation model such as Argus. The complaint that such a system ‘makes subjective evaluations look objective’ does not help the bidder as long as the underlying words hold up. The judgment also draws two lines that are still often blurred in practice. The first is between notification and decision: the letter telling you that you were not chosen is not itself the challengeable act. The second is between selection and award: certificates about your capability do not count under an award criterion that measures the quality of the product offered. For bidders there is a further practical lesson: a bidder who limits its tender to ‘compliant with the specifications’ without technical documentation should not be surprised that a competitor who does enclose data sheets scores better — even if the specifications did not expressly require those annexes. Finally: criticism that you no longer substantiate concretely after the auditor’s report will not be re-examined on the merits by the Council.

The lesson

For bidders: document every technical sub-criterion in your tender, even if the specifications impose no annexes. An evaluation committee can only score what is in front of it; ‘not described’ is a reason for a poor score. Where delivery time is an award criterion, do not simply offer the maximum, because shorter scores better even if the specifications do not say so explicitly. Do not confuse your certifications (selection) with the quality of your offer (award). Request the evaluation report immediately and direct your action against the award decision, not against the notification letter. If the auditor’s report is negative, substantiate your criticism concretely in the final brief or drop it. For contracting authorities: this judgment shows what works — an evaluation report that explains in words, for every (sub-)criterion, why a tender receives that score. Do send that report to unsuccessful bidders promptly; that SKB had to go to the interim-relief judge to obtain it was avoidable.

Ask yourself

As a bidder: does your tender contain concrete documentation (data sheets, supplier specifications) for every technical sub-criterion, or does it merely state ‘compliant with the specifications’? Where delivery time is an award criterion, have you considered whether a shorter period than the permitted maximum is feasible? Do you know which of your strengths belong to selection (capability) and which to award (quality of the offer)? Is your action directed against the award decision itself rather than against the letter notifying it? As a contracting authority: does your award report explain every score in words, so that an unsuccessful bidder can check whether it is lawful, and do you provide that report in good time?

About this database

The Council of State (Raad van State / Conseil d'État) is Belgium's supreme administrative court. In disputes over public procurement — from contract awards to tenderer exclusions — the Council of State is the final arbiter. The rulings in this database are summarised by TenderWolf in plain language, with practical lessons for tenderers and contracting authorities. View all rulings →