Vivaqua compares the new security price with the old one and calls 7% ‘normal’ — but cannot show that the comparison was ever actually made
The Council of State suspends, under the extreme-urgency procedure, the award to Bevier Security of the static security contract for the Château de Modave, because Vivaqua based its price verification on an increase of ‘+/- 7%’ compared with the previous contract, without the file showing the prices of that previous contract, compliance with the wage scales of joint committee 317 or the reason for the increase.
What happened?
On 25 February 2026 Vivaqua decided to tender a public services contract for the ‘security of the Château de Modave (static guarding)’, for a potential term of four years, through a negotiated procedure without prior publication. Five firms were invited; three submitted a bid: Alliance Security, Bevier Security and Vigicore. In the award report of 20 May 2026 the lead official stated under the heading ‘price verification’ that all prices could be considered normal: the lowest bidder’s prices were ‘slightly higher (+/- 7%)’ than under the current contract, which that same firm was performing ‘to our satisfaction’, which was said to be normal given inflation; moreover the prices allegedly included all cost parameters for performance in line with the specifications and legal requirements, ‘cf. the PC 317 wage scales’. On 27 May 2026 the board of directors awarded the contract to Bevier Security. Alliance Security was informed on 2 June 2026; the same day the award was notified to Bevier Security, which according to Vivaqua concluded the contract. On 17 June 2026 Alliance Security sought suspension under the extreme-urgency procedure and annulment, arguing among other things that Bevier Security’s total price did not allow compliance with the PC 317 wage scales. Bevier Security intervened. As a preliminary point, the Council reprimanded both defending parties: Vivaqua’s note of observations and Bevier Security’s petition to intervene contained lengthy developments but no summary of their arguments, as required by the Royal Decree of 19 November 2024. The Council declined to draft that summary for them. On the merits, the Council accepted that a contracting entity may verify prices by comparing them with those of an earlier, similar contract — provided the file shows that the comparison actually and concretely took place and rests on accurate and relevant grounds. That was not the case here. Vivaqua filed, confidentially, an Excel table setting out the unit and total prices of the three compliant bids side by side, showing an increase of 6% for some of Bevier Security’s items and 7% for others. The table was undated, unsigned and did not identify its author. The correspondence from the previous contract contained no information on the prices at which that contract had been awarded, and the specifications of the previous contract filed by Bevier Security did not help either. No document showed that the earlier prices had been adjusted to the PC 317 wage increases, and no certificate from the social secretariat was produced, although Vivaqua claimed the social secretariat had checked this. Bevier Security’s bid did not explain the increase at all; nothing showed it was due to inflation (according to Vivaqua) or to the health index (according to Bevier Security), and no one could explain why some unit prices rose by 6% and others by 7%. The fact that the previous contract had been performed satisfactorily and that Bevier Security called its price ‘attractive’ was not enough. The second limb of the first plea was found serious. Vivaqua also asked for a balancing of interests but did not identify any concrete negative consequences of a suspension, so the Council did not carry it out. The award decision was suspended, with immediate enforcement of the judgment; the bids, analyses and documents on the prices of the previous contract remained confidential, and costs were reserved.
Why does this matter?
In repeat contracts — security, cleaning, maintenance — it is tempting for a contracting authority to reduce price verification to a single sentence: ‘about the same as last time, plus inflation’. This judgment accepts that method in principle, but attaches a burden of proof that weighs heavily in practice. The benchmark itself must be in the file: the prices at which the previous contract was awarded. And the claim that prices respect sectoral wage scales is a factual ground that must be verifiable — here there was no certificate or calculation. In a labour-intensive sector such as security, where labour costs under PC 317 are largely fixed, that is no detail: it is precisely the test of whether a price is realistic. The judgment also recalls that price verification has a dual purpose — protecting the authority against an unperformable bid and protecting competition against fanciful prices — and that an anonymous Excel overview listing prices side by side serves neither. Finally, it contains a procedural warning that goes beyond this case: in summary proceedings, since the Royal Decree of 19 November 2024, the Council expects a summary of the arguments of the defending and intervening parties, and those who omit it cannot count on the Council doing the work itself. And anyone requesting a balancing of interests without citing concrete consequences will not get one.
The lesson
For contracting authorities: if you want to show that a price is normal by comparing it with the previous contract, put the award prices of that previous contract in the file, explain every percentage point of increase (index, wage agreement, changed services) and keep a dated, signed analysis document. If you refer to sectoral wage scales, show with a calculation or certificate that they are met. ‘Performed to our satisfaction’ is not price verification. For unsuccessful bidders in labour-intensive sectors: confront the competitor’s total price with the minimum labour cost under the applicable joint committee — a concrete and verifiable argument. And for anyone filing a note or petition to intervene in summary proceedings: include the mandatory summary of your arguments, and support any requested balancing of interests with concrete consequences.
Ask yourself
As a contracting authority: can you show from the file at what prices the previous contract was awarded, if your price verification relies on it? Can you explain, and substantiate, why some items rise by 6% and others by 7%? Do you have a dated and signed document showing who carried out the price verification and how? If you state that the prices respect the joint committee’s wage scales: is there a calculation or certificate in the file? As a bidder: have you checked whether the selected competitor’s total price can carry the sectoral minimum wages? Does your note of observations or petition to intervene in summary proceedings contain a summary of your arguments, and have you cited concrete consequences if you request a balancing of interests?
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 →