NACE 62 – Computer Programming, Consultancy and Related Activities | Public Tenders

Definition: NACE 62 covers the provision of IT services, in particular the development of custom software, IT consultancy, IT systems integration as well as the operation and maintenance of IT infrastructure. This division is among the most significant in European public procurement.

Legal basis: NACE Rev. 2 (Regulation (EC) No 1893/2006) · Last updated: January 2026

What does NACE 62 cover?

NACE 62 (Computer programming, consultancy and related activities) classifies companies that provide IT services — software development, IT consultancy, systems integration and IT infrastructure operation. In public procurement, this division is one of the highest-spending areas, driven by digitalisation and e-government.

Division 62 within Section J (Information and Communication) is concentrated in one principal group:

Within group 62.0, the classes 62.01 (programming), 62.02 (IT consultancy), 62.03 (IT facilities management) and 62.09 (other IT services) are distinguished.

Public Tenders: Sector NACE 62

Public IT service contracts are among the most dynamic segments in European procurement — authorities at all levels invest heavily in digitalisation, e-government and cybersecurity.

Typical types of contract

• Software development (bespoke): Specialist procedures for administration, portal solutions, register applications, e-government platforms
• IT consultancy and project management: Strategy consultancy, IT architecture, project management for digitalisation projects
• Systems integration: Connection of legacy systems, middleware, API development
• IT operations and managed services: Operation of data centres, helpdesk, monitoring and IT support
• Cybersecurity: Penetration tests, SIEM implementations, security audits, SOC services
• Cloud migration and DevOps: Migration to government cloud platforms, CI/CD infrastructure

Relevant CPV codes for NACE 62

The link between the NACE classification and tender search is provided by the CPV codes (Common Procurement Vocabulary), which must be stated in every contract notice on TED.

Current tenders with these CPV codes can be found on TED (Tenders Electronic Daily) as well as on national procurement platforms.

For Contracting Authorities and Bidders

Public contracting authorities

Federal ministries and their IT service providers (ITZBund, BRZ), regional administrations, municipalities, education and research institutions as well as public enterprises are the main contracting authorities for IT services. In Austria, the Federal Computing Centre (BRZ) coordinates central IT platforms; in Germany, ITZBund does so. For the digitalisation of the healthcare sector, health insurers and hospital operators are relevant contracting authorities. The European Commission and EU agencies award large contracts for IT infrastructure and software development.

Companies and bidders

IT companies participating in public tenders must typically provide the following evidence:

• Reference projects: Comparable projects in terms of complexity, technology stack and contract volume
• Quality certifications: ISO 9001, ISO/IEC 27001 (information security), CMMI maturity levels
• Security evidence: BSI IT baseline protection, SOC 2 Type II, NIS2 compliance
• Personnel evidence: Qualification evidence for the IT experts deployed (certificates, CVs)
• Open standards: Many public tenders require interoperability and open interfaces

Frequently Asked Questions on NACE 62 and public tenders

Which companies fall under NACE 62?
Software houses, IT consultancies, systems integrators, IT managed service providers as well as IT departments that act in the market as independent companies. This is distinct from standard software publishers (NACE 58.2) and telecommunications operators (NACE 61).

How is agile software development to be handled in public procurement?
Agile development approaches (Scrum, Kanban) pose procurement law challenges, as the scope of services and price are difficult to define in advance. Proven models are framework agreements with call-offs by sprint, the competitive dialogue or the negotiated procedure with prior notice.

Are open-source requirements permissible in public IT tenders?
Public contracting authorities may give preference to open-source software, but may not require it exclusively where this would unjustifiably restrict competition. "Public Money, Public Code" is a policy principle that is increasingly implemented in Germany (e.g. Sovereign Tech Fund) and Austria.

What needs to be considered for work contracts vs. service contracts in IT?
Many IT projects fail due to the wrong contract structure. Work contracts (success liability) are suited to clearly defined deliverables, service contracts (best-efforts liability) to agile or advisory activities. Public procurement law does not impose mandatory requirements but recommends a clear description of services.

Navigation: NACE 62 in context

• NACE J – Information and Communication: Parent section
• NACE 61 – Telecommunications: Networks and transmission infrastructure
• NACE 63 – Information service activities: Data processing and hosting
• NACE 58 – Publishing activities: Standard software publishers

Last updated: January 2026
All information is provided without guarantee. For legally binding advice, please consult a law firm specialising in public procurement law.