Electronic procurement covers access to documents, communications, submission and the procedural record. A reliable technical and organisational process is essential because a completed offer has no value if it does not reach the required system in the correct form and on time.
Prepare access and responsibilities
Check platform registration, permissions, supported formats and the required form of submission early. Assign responsibility for the final version and establish a legitimate backup arrangement for absence. Different platforms and procedures may have different technical requirements. Do not assume that an ordinary email is an acceptable alternative to the specified route.
Submission and technical incidents
Test the process with enough time to correct problems. Keep the final files and receipt together. If a failure occurs, record time, messages, attempted steps and contact with the designated support service. Whether a fault is attributable to the bidder or the authority depends on the facts; a screenshot alone does not automatically prove lawful timely submission.
Monitor the communication channel
Questions, corrections and requests for evidence may arrive through the platform. Check for updates and identify the valid document version before bidding. A missing additional email alert does not necessarily make a platform message irrelevant. Authorities should ensure equal information, controlled access and a traceable opening process.
Evidence for a dispute
Retain the notice, technical requirements, exact submitted files, receipt and incident chronology. Distinguish creation of a file, start of upload and actual receipt. Legal deadlines continue to require attention while technical issues are discussed. A support request is not automatically a complaint or a review application.
Four practical examples
The following scenarios are illustrative, not reports of actual client matters. The outcome depends on the documents and circumstances of the individual procurement.
Example 1: Upload error
Minutes before closing, the platform shows an error. Preserve the evidence and contact the designated support service immediately. An email to an unrelated address is not automatically a valid substitute.
Example 2: New document version
A buyer publishes an amended price schedule. The bidder checks the platform and updates its controlled version. An earlier local copy may no longer be the correct basis for the offer.
Example 3: Wrong format
A tender arrives in a format not requested. Assess the actual rule, readability and applicable exclusion provisions. The possibility of later conversion does not cure every defect.
Example 4: Staff absence
The submission manager becomes ill. Properly authorised backup access and a documented final version allow continuity. Sharing credentials informally is not an adequate substitute for a clear process.
Related topics
Bidder checklist: from notice to award · Tender exclusion and requests for missing documents · Rüge: complaints and procurement deadlines
Discuss your procurement
For a review, please identify the authority, contract or lot, current procedural stage and any deadline. We can then clarify the scope of the requested work. Contact our team. An enquiry does not itself create a retainer or preserve a legal deadline.
Legal sources
Official legislation and materials, some in German: § 97 GWB · § 9 VgV · § 41 VgV · § 53 VgV
Updated 13 November 2026. Illustrative guidance on German and EU procurement law.