Choosing the relevant EVB-IT contract model for a German public IT offer

An EVB-IT contract review begins by identifying what the German public customer expects the supplier to provide. Access to existing software, a defined development result, professional services and continuing operation create different commercial obligations. A supplier should understand those boundaries before converting its standard price list into a public-sector offer.

The customer selects and completes the contract documents for its procurement. The supplier's task is to assess the proposed commitment, identify a mismatch between the described work and the commercial model, and raise any permitted clarification while it can still make an informed bid decision. A familiar contract-family name should not replace reading the selected terms and schedules.

Start with the current contract family

The government's current EVB-IT catalogue separates service provision, permanent and temporary standard-software use, hardware purchasing, maintenance, cloud services, software creation, systems and system support. It also provides a framework-agreement model spanning relevant service areas. Individual contract forms are accompanied by their applicable conditions and supporting forms.

Consider a hypothetical company offering a public records-search product. The customer's requirement could involve a licence for the existing product, adaptation to a particular records collection, training, or a hosted service with continuing support. Those elements may be marketed together, but they should be identifiable in the commercial analysis.

Draw the boundary around each promised result or activity. Identify what already exists, what the company will create, what it will operate and what the customer must supply. This gives the bid team a clearer starting point than selecting the contract form whose heading most resembles the product's marketing category.

The catalogue includes both digital playbooks and conventional documents, with particular treatment for the framework model. Record the actual version included in the procurement. A supplier's old local template may be useful for comparison, but it is not evidence of which terms the buyer has proposed now.

Distinguish service effort from a defined result

The BAköV's published service contract and conditions, version 3.0.0 of March 2026, exclude work-contract services from their subject matter. The short form records the service, location, period, charging unit and payment model, with separate choices addressing travel costs and time.

The current EVB-IT creation conditions take a different approach: software creation or adaptation is organised on a work-contract basis, with responsibility for the agreed result. The distinction affects what the supplier must estimate and demonstrate under the particular agreement.

For the records-search business, providing a specialist to advise on data organisation is commercially different from promising an adapted application meeting a defined requirement. The first estimate may focus on the activities and time to be provided. The second must account for the complete result, the company's delivery dependencies and the contractual treatment of completion.

The supplier should identify that distinction in the proposal's language. If the price assumes advisory effort but the description promises a completed adaptation, management is approving two different obligations. The ambiguity should be resolved before a customer-facing commitment is made.

Examine the price mechanism alongside the scope

The service form illustrates why a day rate alone is insufficient. Its charging options include effort-based payment, an upper limit and a fixed amount. Those selections should be read with the corresponding conditions. A ceiling is a contractual term requiring review, not simply an internal budget warning that the supplier can disregard once staff have worked additional days.

In the hypothetical records project, suppose the company estimates twenty days for a defined advisory task. It should identify the information it expects the customer to provide and how delayed or incomplete material would affect the planned work. The commercial review then asks whether the proposed charging arrangement adequately addresses that situation.

Travel provides another concrete example. An attractive professional rate can produce a poor return if frequent site visits consume staff time and incur costs that the offer has not accounted for. Read the relevant selections and price the actual delivery pattern. Do not assume the company's usual commercial-customer travel policy has automatically become part of the public contract.

Keep the internal estimate connected with the offered scope. When the customer clarifies an activity, the person responsible for pricing should assess its effect on the resources required. That allows management to approve the whole obligation rather than a rate detached from the work.

Review the 2026 rights position deliberately

The BMDS March 2026 modernisation announcement describes updated open-source provisions and the availability of the contract models through EVB-IT digital. It presents open-source development and provision as the standard reflected for new software projects while confirming that proprietary purchasing remains possible. The actual contract's rights choices therefore deserve explicit review.

For the records-search supplier, distinguish its existing product from newly developed work and third-party components. A commercial team cannot sensibly price a rights commitment without knowing which assets it covers. A broad statement that the company retains its intellectual property may conflict with another part of the proposed package or fail to answer what the customer needs to use.

The creation terms separately address standard-software rights and open-source licensing. The supplier should connect its proposed components with the applicable treatment and identify any licence it must obtain or pass through. This is a contract and commercial-record exercise; the product team provides the relevant component information, while the responsible adviser assesses the promised rights.

A clear component-and-rights schedule also helps explain a price difference between two offers. One may include a broader right to reuse a developed result, while another covers a narrower service. Those offers are not commercially comparable merely because their demonstrations look similar.

Identify continuing obligations and customer dependencies

A product purchase can be followed by support, and a development project can be followed by maintenance. The supplier should identify whether those later activities are included, optional or separately purchased under the proposed documents. Their timing and price can materially affect the business case.

For the records-search company, a completed adaptation may still require staff to answer user questions or maintain compatibility during the service period. Estimate that continuing work using the actual commitment rather than an informal expectation that the customer will require little help.

Customer contributions should also be specific. If the supplier needs access to source records, an authorised decision-maker or a review of proposed terminology, identify when those inputs are required. The contract team's job is to establish how the agreement treats those dependencies; the project team's job is to plan their practical delivery.

Our guide to German suitability evidence covers a separate question: whether the bidder can substantiate its proposed capability. A strong reference record does not itself settle the commercial obligations of the new contract.

Hand the agreed model to delivery and finance

Once the offer is agreed, retain the selected form, conditions, schedules and relevant clarifications together. Delivery staff need the actual scope and change process; finance needs the charging basis and supporting records. Both should work from the same contractual package. Where the agreement offers optional services, identify who can request them and how the request reaches the staff responsible for allocating delivery capacity.

A useful handover identifies the first payable activity, the evidence needed for billing and the decisions requiring customer agreement. The German federal invoice guide explains the related routing and order references. Choosing and understanding the relevant EVB-IT model becomes commercially valuable when its boundaries remain visible throughout performance and payment.