I. Legal Framework & Thresholds

Core legal requirements and EU threshold values for 2026–2027

▼

EU Threshold Values (2026–2027)

€140,000
Central Government (supplies/services)
€216,000
Sub-central authorities (supplies/services)
€5,404,000
Works contracts
€432,000
Utilities sector (supplies/services)
Source: Commission Delegated Regulation (EU) 2025/2152 of 22 October 2025 (classic sector, applicable from 1 January 2026); utilities threshold per Reg. (EU) 2025/2150.

Legal Framework

GWB (Gesetz gegen Wettbewerbsbeschränkungen): German Competition Act governing above-threshold procurement

VgV (Vergabeverordnung): Procurement Regulation implementing EU directives

UVgO (Unterschwellenvergabeordnung): Below-threshold procurement regulation

Vergabebeschleunigungsgesetz (in force 1 July 2026, BGBl. 2026 I Nr. 137): amends the GWB and VgV to simplify and speed up public procurement; raises the federal Direktauftrag (direct-award) threshold to €50,000 net (§ 55(2) BHO, as amended by Art. 3) and leans out suitability evidence and procurement documents. The EU thresholds above are unaffected.

Legal Sources:
• GWB: Neufassung BGBl. 2013 I S. 1750 (26 June 2013, corrected BGBl. 2013 I S. 3245), amended among others by the Vergabebeschleunigungsgesetz (BGBl. 2026 I Nr. 137, in force 1 July 2026)
• VgV: BGBl. I S. 624 (2016), amended among others by Art. 9 of the Vergabebeschleunigungsgesetz with effect from 1 July 2026
• UVgO: Model regulation by Federal Ministry for Economic Affairs and Energy (BMWE)
Service Provider Pitfall

Different rules apply above/below thresholds. Ensure you understand which legal framework governs your specific tender to avoid compliance issues.

II. Procurement Procedures (Vergabeverfahren)

Complete overview of all German procurement procedures and their applications

▼

Offenes Verfahren (Open Procedure)

Process: Single-stage procedure where any interested party can submit tenders

Timeline: Minimum 35 days for submissions, reducible to 30 days with electronic submission (Art. 27 Directive 2014/24/EU)

Best for: Standard IT services, software licenses, hardware procurement

Legal Basis: § 15 VgV, Art. 27 Directive 2014/24/EU
Common Mistakes

Tenders received late are excluded unless the bidder is not responsible for the delay (§ 57(1) No. 1 VgV). Ensure you submit well before the deadline and account for technical upload issues.

Nicht-offenes Verfahren (Restricted Procedure)

Process: Two-stage - Initial qualification phase, then invitation to tender

Timeline: 30 days qualification + 30 days tender submission

Best for: Complex IT projects, custom software development

Legal Basis: § 16 VgV, Art. 28 Directive 2014/24/EU
Qualification Risk

Even qualified suppliers can be excluded in stage 2. Don't assume qualification guarantees contract award - maintain competitive pricing and technical excellence.

Verhandlungsverfahren (Negotiated Procedure)

Process: Direct negotiations with selected suppliers

Timeline: Flexible, depends on negotiation complexity

Conditions: Only permitted in specific circumstances (urgency, failed procedures, technical specificity)

Legal Basis: § 17 VgV, Art. 26(4), 29 and 32 Directive 2014/24/EU
Limited Availability

Requires strict justification. Contracting authorities must prove no other procedure is suitable. Don't rely on this procedure being available.

Wettbewerblicher Dialog (Competitive Dialogue)

Process: Multi-stage dialogue to develop solutions

Timeline: Extended process with multiple dialogue rounds

Best for: Large-scale digital transformation, complex innovative solutions

Legal Basis: § 18 VgV, Art. 30 Directive 2014/24/EU
Resource Intensive

Requires significant time and resource investment with no guarantee of success. Budget for multiple dialogue rounds and solution development costs.

Innovationspartnerschaft (Innovation Partnership)

Process: Structured partnership for research, development and subsequent purchase

Timeline: Divided into research/development phases with milestones

Duration: no statutory maximum. The duration and value of each phase must reflect the degree of innovation (§ 19(8) VgV, Art. 31(7) Directive 2014/24/EU).

Best for: Advanced technology development, innovative solutions not available on the market

Legal Basis: § 19 VgV, Art. 31 Directive 2014/24/EU
Development Risk

No guarantee the authority will purchase the developed solution. Intellectual property arrangements must be carefully negotiated upfront to protect your investment.

Rahmenvereinbarungen (Framework Agreements)

Process: Umbrella contracts establishing terms for future call-offs

Duration: Maximum 4 years

Types: Single supplier or multiple supplier frameworks

Legal Basis: § 21 VgV, Art. 33 Directive 2014/24/EU
Call-off Competition

Being on a framework doesn't guarantee work. Multi-supplier frameworks often require mini-competitions for each call-off, maintaining competitive pressure.

III. EVB-IT Contract System

Five of the twelve standardized EVB-IT contract types for German public sector procurement

▼

EVB-IT Contract Structure Overview

Each EVB-IT contract type consists of two legally binding components:

  • Main Contract (Hauptvertrag): Core contractual terms and specific requirements
  • General Terms & Conditions (AGB/GTCs): Standardized supplementary conditions
Official Source: Digitale Verwaltung (federal portal) - current EVB-IT versions
Two-Tier Legal System

Both the main contract AND the associated GTCs are legally binding. Service providers must comply with ALL provisions across both documents.

EVB-IT System (Complete IT Systems)

Main Contract Covers:

  • Complete IT system creation and integration
  • System architecture and technical specifications
  • Integration of hardware, software, and services into functioning systems
  • System commissioning and acceptance testing

Associated AGB System Include:

  • Limitation for defects: 24 months from final acceptance, 36 months for defects of title in custom software, unless agreed otherwise (Ziff. 13.3 EVB-IT System-AGB, Stand 1 March 2026)
  • System-wide performance guarantees
  • Integration liability and system functionality obligations
  • System maintenance and lifecycle management

Typical Applications: Enterprise Resource Planning (ERP) systems, Content Management Systems (CMS), Human Resources suites, custom business applications, integrated IT infrastructure projects

Current Version: EVB-IT System + AGB System (current version at digitale-verwaltung.de)
System Integration Complexity

Complete system responsibility means the contractor is liable for the entire system functioning as a whole, not just individual components. Factor in comprehensive testing and integration costs.

EVB-IT Erstellung (Software Development & Creation)

Main Contract Covers:

  • Development methodology and project phases
  • Functional and technical specifications
  • Testing, acceptance and delivery procedures
  • Documentation and training deliverables

Associated AGB Erstellung Include:

  • Intellectual property ownership rules
  • Change request and scope management
  • Limitation for defects: 24 months from acceptance, 36 months for defects of title in custom software, unless agreed otherwise (Ziff. 12.3 EVB-IT Erstellungs-AGB, Stand 1 March 2026)
  • Source code delivery and technical documentation
Current Version: EVB-IT Erstellung + AGB Erstellung (current version at digitale-verwaltung.de)
IP Ownership Issues

Public sector often requires full IP transfer. This may conflict with your standard licensing models or reusable components strategy.

EVB-IT Dienstleistung (IT Services & Support)

Main Contract Covers:

  • Service scope and delivery specifications
  • Service level agreements (SLAs) and metrics
  • Staffing requirements and qualifications
  • Reporting and documentation obligations

Associated AGB Dienstleistung Include:

  • Performance penalties and service credits
  • Escalation procedures and governance
  • Staff security clearance requirements
  • Continuous improvement obligations
Current Version: EVB-IT Dienstleistung + AGB Dienstleistung (current version at digitale-verwaltung.de)
SLA Penalties

Service credit penalties can significantly impact revenue. Build buffer capacity and robust monitoring to ensure SLA compliance from day one.

EVB-IT Pflege S (Maintenance of Standard Software)

Hardware maintenance is covered by EVB-IT Instandhaltung, the maintenance of complete IT systems by EVB-IT Service.

Main Contract Covers:

  • Maintenance scope and service specifications
  • Response times and resolution targets
  • Preventive maintenance schedules
  • Update and patch management procedures

Associated AGB Pflege Include:

  • Availability guarantees and uptime targets
  • Escalation procedures for critical issues
  • Long-term support obligations
  • Technology refresh and migration planning
Current Version: EVB-IT Pflege S + AGB Pflege S (current version at digitale-verwaltung.de)
Long-term Commitment Risks

Maintenance contracts often span multiple years with technology evolution risks. Plan for obsolescence and factor long-term support costs into pricing.

EVB-IT Cloud (Cloud Services & SaaS)

Main Contract Covers:

  • Service specifications and availability targets
  • Data location and sovereignty requirements
  • Scalability and performance metrics
  • Migration and onboarding procedures

Associated AGB Cloud Include:

  • Data protection and GDPR compliance
  • Security certification requirements (ISO 27001, etc.)
  • Disaster recovery and business continuity
  • Data portability and exit procedures
Current Version: EVB-IT Cloud + AGB Cloud (current version at digitale-verwaltung.de)
Data Sovereignty

German public sector often requires data to remain within EU/German borders. Ensure your cloud infrastructure can meet strict data residency requirements.

Additional EVB-IT Contract Types

Further EVB-IT types: Überlassung Typ A and Typ B (software licensing), Kauf (hardware purchase), Instandhaltung (hardware maintenance), Systemlieferung, Service and the Rahmenvereinbarung (framework agreement). Each type consists of a contract form, AGB and model documents. The Rahmenvereinbarung consists of a contract form only.

Complete Contract Portfolio: View all current EVB-IT contracts and AGBs at digitale-verwaltung.de

Cross-Cutting Compliance Requirements

GDPR & Data Protection:

  • Data Processing Agreements (DPA) mandatory under Art. 28 GDPR
  • Privacy by Design implementation required
  • Regular data protection impact assessments

Security Standards:

  • BSI IT-Grundschutz compliance often required
  • ISO 27001 certification frequently mandated
  • Regular penetration testing and security audits

Operational Requirements:

  • German-speaking support staff availability
  • Business continuity and disaster recovery plans
  • Regular reporting and governance meetings
Compliance References:
• GDPR: Regulation (EU) 2016/679
• BSI IT-Grundschutz: Current BSI Compendium
• ISO 27001: ISO/IEC 27001:2022 Information Security Management
Certification Investment

Multiple certifications and ongoing compliance create recurring costs. Include these operational costs in your long-term pricing strategy and contract negotiations.

IV. Strategic Insights for Service Providers

Key success factors and common pitfalls to avoid in German public procurement

▼

Winning Strategies

Early Market Engagement: Participate in market consultations and prior information notices to understand requirements before formal tenders

Reference Building: Develop relevant German public sector references through smaller initial contracts

Consortium Partnerships: Partner with established local firms for better market access and credibility

Compliance Excellence: Exceed minimum qualification requirements to differentiate from competitors

Market Intelligence Sources:
• TED Database: Official Journal of the EU for tenders
• BITKOM: German Digital Association procurement resources
• State procurement portals: Bayern, NRW, Baden-Württemberg

Critical Pitfalls

Underestimating Bureaucracy: German procurement involves extensive documentation requirements and formal processes

Language Barriers: Contracts and communications often exclusively in German - ensure adequate language support

Cultural Differences: Long-term relationship building approach vs. transactional business models

Payment Terms: An agreement that a public contracting authority pays only after more than 30 days is valid only if expressly made and objectively justified. Payment periods of more than 60 days are void (§ 271a(2) BGB, Art. 4(6) Directive 2011/7/EU).

Cultural & Business References:
• GTAI: Germany Trade & Invest business guides
• German-American Chamber: Chamber of Commerce business resources
• DIHK: German Chamber of Commerce procurement guidance

Market Intelligence & Opportunities

TED Database Monitoring: Track upcoming EU-wide tenders and market trends

State-level Platforms: Each Bundesland operates independent procurement portals with local opportunities

Framework Agreements: Multi-year revenue potential through strategic framework positioning

Industry Associations: Use BITKOM and eco Association for market insights and networking

Key Procurement Platforms by State:
• Bayern: auftraege.bayern.de
• Nordrhein-Westfalen: vergabe.nrw.de
• Baden-Württemberg: vergabe.landbw.de
• Berlin: berlin.de/vergabeservice
• Federal Level: evergabe-online.de