A defensible procurement starts with a clear need, suitable procedure and consistent documents. Authorities must connect legal requirements with operational responsibilities so that the competition and the resulting contract deliver the intended public service.
Prepare the procurement
Determine contracting authority status, contract type, estimated total value and applicable rules. Include options and foreseeable extensions in the assessment where required. Examine lots, market structure, funding conditions and timetable. A procedure should be chosen because its legal conditions are met, not simply because a familiar template is available.
Draft consistent documents
The notice, selection requirements, specification, price schedule and draft contract should fit together. Separate minimum requirements from award criteria and define how quality will be assessed. Product restrictions require proper justification. If bidders need to promise particular performance, the contract should make those promises measurable and enforceable.
Run and document the competition
Communicate material clarifications consistently to affected participants. Control document versions and consider whether changes require more time. Distinguish clarification, supplementation and negotiation according to the procedure. Record substantive reasons for evaluation and any exclusion. An unusually low price may require investigation rather than automatic acceptance or rejection.
Award and contract management
Before signing, check information duties, standstill and pending review. Transfer evaluated commitments, options, maximum volumes and monitoring obligations to the contract team. Proposed changes should return to legal review before they are ordered. This avoids disconnecting a careful tender from uncontrolled implementation.
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: Conflicting needs
Departments disagree about required software functions. Resolve mandatory features and scored improvements before publication. Otherwise evaluation may drift towards expectations that bidders never received.
Example 2: Question affects everyone
One bidder identifies a conflict between the price schedule and contract. Clarify it through the designated channel for all affected participants and assess whether the deadline remains adequate.
Example 3: Low price
The lowest tender raises doubts about performance. Investigate when required and evaluate the explanation. A numerical gap alone is neither an automatic exclusion nor a reason to ignore risk.
Example 4: Additional sites
After award, another department wants more locations served. Check the original options and modification rules before ordering. Budget approval alone does not establish procurement compliance.
Related topics
Contracting authority checklist · Specifications and procurement documents · Contract modifications and additional public works
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: § 97a GWB – Losgrundsatz · § 122 GWB – Eignung · § 8 VgV – Dokumentation · § 31 VgV – Leistungsbeschreibung
Updated 13 November 2026. Illustrative guidance on German and EU procurement law.