Depot Lourdeshoek in Ghent: the e-Procurement error message was not an outage but an unshared submission space — and a WeTransfer tender six minutes before the deadline saves nothing
BV F., selected as the top-ranked candidate for the City of Ghent’s Design & Build contract for the ‘Depot Lourdeshoek’ warehouse, received on the morning of the deadline the message that ‘another user has already started a submission’ and e-mailed a WeTransfer link at 9:54, but the Council of State rejected its extreme-urgency application against the finding of irregularity: the platform worked, the blockage arose because someone within its own consortium had confirmed participation without sharing the submission space, so there were no grounds for postponement and the specifications excluded regularisation of a late tender.
What happened?
The City of Ghent put out a public works contract, published at European level, under the Design & Build formula: the design and construction of a warehouse, ‘Depot Lourdeshoek’, in the New Orleansstraat (reference FAG/2024/014/PJ/INV/5670), awarded through a competitive procedure with negotiation. The city council adopted the contract conditions and selection guidelines on 25 November 2024. Candidates had to form a consortium of at least a contractor, an architectural firm and engineering firms for structural design and building services. Of the six candidates, the applicant — then nv A., now BV F. — obtained the highest score in the selection report: 88 points. On 3 April 2025 the board of mayor and aldermen selected the three highest-ranked candidates. On 4 June 2025 they were invited via e-Procurement to submit an initial tender before 10:00 on 2 December 2025. The specifications were crystal clear: submission mandatory via e-Procurement, no tenders by e-mail, and ‘the Tenderer is itself responsible for the timely, correct and complete upload of its single Tender’. On the morning of the deadline, at around 8:50 according to the applicant, it received the following message when confirming its participation: ‘Another user has already started a submission for the company to which this invitation was addressed. If you want access to this submission, the user must explicitly share it with you.’ Attempts with every internal login ran into the same message, and calls to the city initially went unanswered. At 9:54 the applicant e-mailed the city that uploading was impossible, enclosing a screenshot, the message that the BOSA helpdesk had advised asking the contracting authority to ‘adjust the deadline somewhat’, and its tender via a WeTransfer link. A city employee said by phone that nothing more could be done so close to the deadline, but that the e-mail had been received. The opening report generated at 10:08 listed two tenders, with construction costs of 15,833,633.45 euros and 14,085,388.75 euros, but not the applicant’s. BOSA later stated that someone else within the company had already used the invitation to confirm participation — according to the audit, a designated subcontractor, company I. — adding that it is ‘never a good idea’ to upload a tender only in the last half hour. A first exclusion decision of 16 January 2026 by the director of FM Themagebouwen was suspended by judgment no. 265.863 of 2 March 2026 because its author lacked competence, and was then withdrawn. On 9 April 2026 the board took the decision itself: on the basis of a review report of 31 March 2026, the tender was excluded ‘for having, through its own doing, failed to submit a tender in time’, and negotiations were launched. That decision was notified on 13 April 2026; on 28 April 2026 BV F. applied for suspension under extreme urgency. The Council of State first noted that the application contained no summary of the pleas, although one has been mandatory since 2023: the applicant therefore had to accept the Council’s own summary of its grievances. On the merits, the Council found no plea serious. The error message did not point to a system fault but to an action on the bidder’s side: according to the e-Procurement help centre, to which the specifications referred, only one person within a company can confirm participation, and that person must share the submission space if others are to upload the tender. A professional bidder can be expected to know this in time. Neither the helpdesk nor the city had to work out, minutes before the deadline, who in the consortium had confirmed participation. The difference with judgment no. 240.186 of 14 December 2017, where the server itself was unavailable, was therefore decisive. Article 57(1) of the Royal Decree on award procedures only allows a postponement where the platform is unavailable, which it was not. That an employee had opened the WeTransfer link did not make the tender regular: the specifications prohibited submission by e-mail. Non-compliance with article 14 of the Act of 17 June 2016 is a substantial irregularity under article 76(1) of the Royal Decree, and the specifications expressly excluded regularisation of a late tender. Given the importance of the platform for the integrity of the procedure and equal treatment, the city’s refusal to allow regularisation was not manifestly unreasonable. The application was rejected; BV F. pays a roll fee of 200 euros, a contribution of 26 euros and a procedural indemnity of 770 euros to the City of Ghent.
Why does this matter?
This judgment draws a sharp line between two situations that feel identical to a bidder on the morning of the deadline: a platform that does not work, and a platform that does exactly what it should but that your own organisation has not set up correctly. In the first case there may be force majeure and the contracting authority must consider a postponement, as the Council accepted in 2017. In the second case the bidder bears the full risk — even where the blockage is caused by a subcontractor or partner in a Design & Build consortium. For complex contracts where contractors, architects and engineers bid together, that is a real danger: whoever accepts the invitation and confirms participation holds the key to the submission space. The judgment also confirms that a tender sent by e-mail or WeTransfer, even if complete and received before the deadline, is not a regularly submitted tender where the specifications impose e-Procurement, and that the authority need not regularise it. That the city could have downloaded the tender changes nothing. For a candidate that came out of selection on top with 88 points, the outcome is harsh: it is out of a procedure in which the two remaining initial tenders amounted to 14.1 and 15.8 million euros, without the quality of its tender ever being assessed. Finally, the judgment carries a procedural warning: anyone who omits the mandatory summary of their pleas must accept that the Council will formulate it itself.
The lesson
If you bid as part of a consortium, agree well before the deadline who on e-Procurement accepts the invitation and confirms participation, and make sure that person shares the submission space with whoever uploads and signs the tender. Do not let a subcontractor or engineering firm click that button ‘just for a moment’. Confirm participation and upload the tender at least a day ahead: BOSA’s advice that it is ‘never a good idea’ to upload in the last half hour is painfully concrete here. If you do get an error message, read it literally: ‘another user has already started a submission’ means the solution lies in-house, not with the helpdesk or the authority. A tender by e-mail or WeTransfer is no safety net where the specifications prohibit it. And always include a summary of each plea in an extreme-urgency application. As a contracting authority, lay down the submission obligation and the ban on e-mail submission clearly in the specifications, refer to the platform’s manual, and have the review report show factually — for instance with an audit and a statement from BOSA — that the platform worked. State expressly whether and which irregularities can be regularised, and have the exclusion decision taken by the competent body: the first decision, taken by a director, was suspended in this very case for that reason.
Ask yourself
Do you know who in your consortium confirms participation on e-Procurement — and has that person shared the submission space with whoever actually uploads and signs the tender? Do you plan submission so that, after an error message, hours rather than minutes remain to solve the problem? Can you tell a genuine unavailability of the platform (possible postponement, article 57 of the Royal Decree) from an access problem within your own organisation (your risk)? Do you realise that a tender sent by e-mail or WeTransfer, even before the deadline, is a substantial irregularity where the specifications impose e-Procurement? As a contracting authority: can you show with an audit and BOSA’s answer that the platform worked, and is the exclusion decision taken by the competent body?
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 →