Quick summary
Procuring event management software is not a product comparison for universities, associations and public bodies. What matters is a legally sound procedure: contract value over 48 months, a functional specification, and hard criteria such as GDPR, accessibility and data export.
- Contract value: For open-ended SaaS contracts the estimate covers 48 months, including onboarding, training and add-on modules, not the annual fee alone.
- Procedure: Direct award, restricted or open tender depends on the documented total value and the rules of the Land.
- Specification: write functional requirements, do not copy a product you already know, or you risk a finding of distorted competition.
Related: Software for associations and universities · GDPR and server location · Accessible events (EAA / BFSG)
Procuring event management software: a guide for contracting authorities
When a university, association or public authority wants to introduce new software, a solid product comparison is not enough. You need a procedure that stands up under procurement law. This is where many projects fail, not on the technology, but on the process before it. This guide sets out what contracting authorities should watch when procuring event management software.
Why buying software is different from a classic service
From a procurement-law view, software-as-a-service contracts are ongoing awards without a fixed end date. That sets them apart from a one-off purchase such as office furniture or catering. Which procedure is lawful depends not on the annual fee, but on the estimated total value over the contract term.
For open-ended contracts, the German UVgO requires the estimate to be based on 48 months. In practice that means a solution that looks cheap at first glance can move into a different award class once you project it over four years. Skip that step and you risk choosing the wrong procedure, and in the worst case a challenge or review.
The relevant contract types, briefly
Direct award. Below certain value thresholds, public bodies can award without a formal procedure. The exact thresholds differ by Land and are set in the Land procurement rules, in Lower Saxony for example through the relevant ordinance. These figures are adjusted politically from time to time. Several Länder are currently looking at raising them to simplify procurement.
Restricted tender. Above the direct-award threshold but below the EU thresholds, a restricted tender with a participation contest is usually required. The contracting authority invites several offers without a fully public call.
Open / EU-wide tender. From the EU thresholds (updated annually) the full procurement regime applies: Europe-wide notice, fixed deadlines and a much higher administrative burden.
Which category applies depends on the estimated 48-month total, including licence fees, onboarding, training and any add-on modules. Document that figure early so the choice of procedure remains auditable later.
Criteria that actually matter
Besides price and features, contracting authorities should check the following for event management software:
- Server location and processing: Is the infrastructure in Germany or the EU? Is there a DPA under Art. 28 GDPR, and are all subprocessors (payments, hosting, CDN) listed transparently? See GDPR-compliant event management software.
- Accessibility: Public bodies have a legal duty to provide accessible services. The vendor should have an accessibility statement, or at least a clear roadmap. More under accessible events and the BFSG.
- Public-sector references: Has the vendor already worked with universities, associations or authorities? That reduces risk on authority-specific needs such as invoicing, cost centres or multi-user administration.
- Exit path: How do you get your data when the contract ends or you switch? An export format and clear notice periods belong in every specification.
- Availability and support SLAs: A public status page and defined response times in the SLA are a good sign of reliability.
Typical mistakes in the needs assessment
A common mistake is to write the specification too closely around a product already known in-house. That can be treated as a distortion of competition. It is better to state functional requirements, for example “digital ticket management with attendee export and an accessible booking path”, instead of a brand name.
A second mistake: costing only the core function and leaving out onboarding, training or later extensions. Onboarding fees in particular go into the 48-month view and can change which procedure applies.
Conclusion
Procuring event management software for associations, universities and public institutions is not a purely technical selection. It is a procurement process with formal rules. If you estimate the contract value cleanly from the start, treat GDPR and accessibility as hard criteria, and write a functional specification instead of a product brief, you avoid the most common pitfalls.
The wider institutional picture, from documents to support, is in event management software for associations, universities and public institutions.
See Institutional → · Contact Institutional → · GDPR and server location →