Specifications for public IT tenders
For federal offices, cantons, municipalities and public companies tendering an IT solution who want robust requirements.
Updated: 2026-11
We prepare the specification of an IT tender for contracting authorities: requirements elicitation following IREB with the business units, product-neutral requirements with acceptance criteria, proposals for suitability and award criteria with a scoring method, and a price sheet that makes bids comparable over the term. Responsibility for the procedure stays with the authority.
Tenders rarely fail on procedure but on content: requirements too vague to compare bids, or so narrow they seem tailored to one product. The result is many questions, incomparable bids and the risk of appeals.
Business units rarely have the time and method to formulate requirements so they are unambiguous for suppliers and verifiable at acceptance.
What you get
Requirements elicitation
Workshops with business units and stakeholder analysis following IREB.
Specification
Starting point, product-neutral requirements with priority and acceptance criteria.
Criteria proposal
Suitability and award criteria with weighting and a transparent scoring method.
Price sheet
Structured request for all costs over the term.
Quality review
Review of documents for contradictions and clarity before publication.
How it runs
- 01
Clarify
Goals, constraints and clarification of prior involvement.
- 02
Elicit
Elicit and prioritise requirements with business units.
- 03
Documents
Create specification, criteria and price sheet.
- 04
Review
Review with the authority and clean-up.
Price framing
Effort depends on scope and number of business units. Anyone preparing the specification with us can only take part in the later procedure if prior involvement can be offset; we clarify this before starting.
Indicative, not a binding quote — the frame is confirmed during scoping.
What drives the price? → Cost guide
Parent service: Custom Software Engineering
FAQ
Do you bid in the tender afterwards?
Generally not. We clarify prior involvement in writing before the engagement so the procedure stays clean.
Do you work with HERMES?
Yes, on request. The specification fits into the HERMES outputs of the concept phase.
Who decides on the procedure?
The authority. We provide the content; responsibility for choice of procedure and deadlines stays there.
How do you ensure product neutrality?
With requirements that describe the goal rather than the solution, and a check for wording that favours a product.
Specifications for public IT tenders
For federal offices, cantons, municipalities and public companies tendering an IT solution who want robust requirements.